[
https://issues.apache.org/jira/browse/UNOMI-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Serge Huber updated UNOMI-71:
-----------------------------
Fix Version/s: (was: 1.5.0)
2.0.0
> Improve startup and test if ES server is available before trying to start
> Unomi services
> ----------------------------------------------------------------------------------------
>
> Key: UNOMI-71
> URL: https://issues.apache.org/jira/browse/UNOMI-71
> Project: Apache Unomi
> Issue Type: Sub-task
> Components: core
> Affects Versions: 1.0.0-incubating, 1.1.0-incubating, 1.2.0-incubating,
> 1.3.0-incubating, 1.4.0
> Reporter: Damien Gaillard
> Priority: Minor
> Fix For: 2.0.0
>
>
> As today we do not test if ES server is available/started which result in a
> crash of the Unomi server, this can be easily avoid by making sure that your
> ES server is started however it will be nice to improve the startup process
> of Unomi to avoid logging exception and instead logging a human readable
> message saying that you need an instance of ES server in order to start your
> Unomi server.
> Also the server should try to restart by checking if the server is available
> every X minutes
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
