Open rafalbroll-datapharm opened 1 month ago
@rafalbroll-datapharm - Are you provisioned on Cosmos DB/ SQL persistence layer?
@rafalbroll-datapharm - Are you provisioned on Cosmos DB/ SQL persistence layer?
It's the SQL Server.
@rafalbroll-datapharm I am facing the same issue with Azure FHIR Service with SQL server.
@rafalbroll-datapharm I am facing the same issue with Azure FHIR Service with SQL server.
Just to clarify, which scenario do you experience? Having a completed task with 0.0% progress, or the latter - having 99% of completion?
@rafalbroll-datapharm It shows completion with 0.0% progress although indicating that a few resources reindexed successfully. And a few resources do return as a result of using that custom search parameter in the query.
Please have a look at the screenshot below:
Thanks for reporting , we will investigate further #AB125852
Describe the bug While running the reindex job for newly defined custom search parameter, FHIR Server reports completion, even though no record is indexed (neither can be found using the new search param).
Hosting details: The FHIR Server is hosted inside the Azure Container App, with assigned resources:
1 CPU, 2 GB RAM
The data instance sizes: The entire Resources table is ~60 GB, 978 676 rows The biggest Resource row (measured as
datalength(rawresource)
) is 5 MB, average is 58 KBFHIR Version? R4B, [3.4.342]
Data provider? SQL Server
To Reproduce Steps to reproduce the behaviour:
GET /_operations/reindex/<reindex job id>
Expected behavior The result is
and attempts of searching by that parameters succeed.
Actual behavior The result is
and attempts of searching by that parameter fail.
Applying maximumNumberOfResourcesPerQuery:
In addition, we were experimenting with adding the parameter
maximumNumberOfResourcesPerQuery
while running the Reindexing Job. That partially deals with the problem, but sometimes it indexes only 99% of the records. ie. for Reindex Job defined like that:we got that response