unomi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Francois Papon (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (UNOMI-71) Improve startup and test if ES server is available before trying to start Unomi services
Date Thu, 17 Jan 2019 11:19:00 GMT

     [ https://issues.apache.org/jira/browse/UNOMI-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Francois Papon reassigned UNOMI-71:
-----------------------------------

    Assignee: Francois Papon

> 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
>            Reporter: Damien GAILLARD
>            Assignee: Francois Papon
>            Priority: Minor
>             Fix For: 1.4.0-incubating
>
>
> 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
(v7.6.3#76005)

Mime
View raw message