-
Type:
Improvement
-
Status: Resolved
-
Priority:
Minor
-
Resolution: Duplicate
-
Affects Version/s: 10.10
-
Fix Version/s: 11.x
-
Component/s: Elasticsearch
-
Tags:
-
Team:PLATFORM
-
Story Points:3
Since NXP-20418 Nuxeo will abort startup if Elasticsearch is not live or ready:
ERROR [ComponentManager] Component service:org.nuxeo.elasticsearch.ElasticSearchComponent notification of application started failed: java.io.IOException: elasticsearch: Name or service not known
nuxeo | org.nuxeo.ecm.core.api.NuxeoException: java.io.IOException: elasticsearch: Name or service not known
..
many NPE
...
======================================================================
nuxeo | = Component Loading Status: Pending: 0 / Missing: 0 / Unstarted: 3 / Total: 694
nuxeo | - service:org.nuxeo.ecm.core.uidgen.UIDGeneratorService
nuxeo | - service:org.nuxeo.ecm.platform.audit.service.NXAuditEventsService
nuxeo | - service:org.nuxeo.elasticsearch.ElasticSearchComponent
nuxeo | ======================================================================
[OSGiAdapter] Error during Framework Listener execution : class org.nuxeo.runtime.osgi.OSGiRuntimeService
nuxeo | java.lang.IllegalStateException: Startup aborted due to previous failures (strict mode)
Using a org.nuxeo.launcher.config.backingservices.BackingChecker will fail faster without producing too much errors and even in the --lenient mode is activated.
