[
https://issues.apache.org/jira/browse/JAMES-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Quynh Nguyen updated JAMES-1999:
--------------------------------
Description:
We had implemented the delayed start for James. When launching James +
Cassandra +ES, James is supposed to wait sometimes for Cassandra and
ElasticSearch when they are not yet started. This allow rebooting
components in any order. This especially useful in docker-compose, or
when your infrastructure do handle service dependencies.
This feature appeared to be buggy.
We will:
- Implement integration tests demonstrating this behavior
- Extract the underlying retry service and unit test it.
Summary: JAMES do not delayed startup on not yet started ElasticSearch
(was: Elasticsearch does not retry to connect when error)
> JAMES do not delayed startup on not yet started ElasticSearch
> -------------------------------------------------------------
>
> Key: JAMES-1999
> URL: https://issues.apache.org/jira/browse/JAMES-1999
> Project: James Server
> Issue Type: Bug
> Reporter: Quynh Nguyen
> Fix For: 3.0.0
>
>
> We had implemented the delayed start for James. When launching James +
> Cassandra +ES, James is supposed to wait sometimes for Cassandra and
> ElasticSearch when they are not yet started. This allow rebooting
> components in any order. This especially useful in docker-compose, or
> when your infrastructure do handle service dependencies.
> This feature appeared to be buggy.
> We will:
> - Implement integration tests demonstrating this behavior
> - Extract the underlying retry service and unit test it.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
