You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@curator.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/03/23 17:22:00 UTC

[jira] [Work logged] (CURATOR-564) Changes to retry failed TestingServer starts should be applied to TestingCluster

     [ https://issues.apache.org/jira/browse/CURATOR-564?focusedWorklogId=408078&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-408078 ]

ASF GitHub Bot logged work on CURATOR-564:
------------------------------------------

                Author: ASF GitHub Bot
            Created on: 23/Mar/20 17:21
            Start Date: 23/Mar/20 17:21
    Worklog Time Spent: 10m 
      Work Description: Randgalt commented on pull request #351: [CURATOR-564] catch startup issues for TestingCluster
URL: https://github.com/apache/curator/pull/351
 
 
   Like was done for TestingServer, catch startup issues for TestingCluster and then re-recreate and re-start the cluster one time. Hopefully this will make the tests more stable.
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 408078)
    Remaining Estimate: 0h
            Time Spent: 10m

> Changes to retry failed TestingServer starts should be applied to TestingCluster
> --------------------------------------------------------------------------------
>
>                 Key: CURATOR-564
>                 URL: https://issues.apache.org/jira/browse/CURATOR-564
>             Project: Apache Curator
>          Issue Type: Improvement
>          Components: Tests
>    Affects Versions: 4.3.0
>            Reporter: Jordan Zimmerman
>            Assignee: Jordan Zimmerman
>            Priority: Major
>             Fix For: 5.0.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> We recently made changes to catch server start issues (usually bind problems) which close the server and re-create/re-start it (see BaseClassForTests.setup). We should apply these to TestingCluster as well as we see Travis tests occasionally fail for TestingCluster startup issues.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)