EGF Instrument Error on Elasticsearch 8 #845
Replies: 6 comments
|
Upgrading the service with elastic 8 will send build by eod |
|
egf-instrument:CCSD491-74781a8764-15 . Deploy this build |
|
instrument log: 2025-08-13 03:51:30.057+0000 INFO --- [ main] o.e.EgfInstrumentApplication -- : Starting EgfInstrumentApplication v1.2.0-SNAPSHOT using Java 17.0.10 with PID 1 (/opt/egov/egf-instrument-1.2.0-SNAPSHOT.jar started by root in /opt/egov) Error starting ApplicationContext. To display the condition evaluation report re-run your application with 'debug' enabled. org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'instrumentAccountCodeRepository' defined in URL [jar:nested:/opt/egov/egf-instrument-1.2.0-SNAPSHOT.jar/!BOOT-INF/classes/!/org/egov/egf/instrument/domain/repository/InstrumentAccountCodeRepository.class]: Unsatisfied dependency expressed through constructor parameter 3: Error creating bean with name 'instrumentAccountCodeESRepository' defined in URL [jar:nested:/opt/egov/egf-instrument-1.2.0-SNAPSHOT.jar/!BOOT-INF/classes/!/org/egov/egf/instrument/domain/repository/InstrumentAccountCodeESRepository.class]: Unsatisfied dependency expressed through constructor parameter 0: Error creating bean with name 'restHighLevelClient' defined in org.egov.EgfInstrumentApplication: Failed to instantiate [org.elasticsearch.client.RestHighLevelClient]: Factory method 'restHighLevelClient' threw exception with message: org/elasticsearch/action/admin/indices/flush/SyncedFlushRequest |
|
@manish050994 will inform here once service upgraded to elastic 8 Still working on that yesterday we stuck in some other blocker issue. Meanwhile if you have bandwidth ask developer to checkout code from master branch and upgrade elastic dependency to elastic 8 and test. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
We are facing an issue with the EGF Instrument service related to its Elasticsearch integration.
Currently, we are using Elasticsearch version 8, and it seems the service is not functioning as expected with this version.
looking for your support to resolve this issue.
All reactions