Reindex gets stuck after shutdown
12 views
Skip to first unread message
Lucas Higa
Apr 29, 2026, 8:32:43 PM (10 days ago) Apr 29
to HAPI FHIR
We're using the reindex operation with optimizeStorage so that we can get rid of the resources in hfj_res_ver being stored as large objects (as its not allowing us to update our cloudsql postgres version)
When running the process it works fine but if the server shuts down the batch2 job gets stuck later on as it sees the chunks in IN_PROGRESS status but does nothing. It constantly logs the same job instance status
- I've been searching but i couldn't find any API for canceling or just monitoring the reindex operation. Is there any use of the returned job id? How can i stop/delete the stuck job? Im guessing that deleting the job instance and work chunk table data could work but it doesn't seem like a good idea
We're using HAPI FHIR 6.6 and upgrading to 7+ is not possible right now
When running the process it works fine but if the server shuts down the batch2 job gets stuck later on as it sees the chunks in IN_PROGRESS status but does nothing. It constantly logs the same job instance status
- I've been searching but i couldn't find any API for canceling or just monitoring the reindex operation. Is there any use of the returned job id? How can i stop/delete the stuck job? Im guessing that deleting the job instance and work chunk table data could work but it doesn't seem like a good idea
We're using HAPI FHIR 6.6 and upgrading to 7+ is not possible right now
Reply all
Reply to author
Forward
0 new messages