[jira] [Commented] (RATIS-178) New servers may not be able to join an existing raft group

["Hadoop QA (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/RATIS-178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16309136#comment-16309136 ] 

Hadoop QA commented on RATIS-178:
---------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red}  0m  3s{color} | {color:red} RATIS-178 does not apply to master. Rebase required? Wrong Branch? See https://yetus.apache.org/documentation/0.5.0/precommit-patchnames for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | RATIS-178 |
| JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12903493/r178_20171223.patch |
| Console output | https://builds.apache.org/job/PreCommit-RATIS-Build/83/console |
| Powered by | Apache Yetus 0.5.0   http://yetus.apache.org |


This message was automatically generated.



> New servers may not be able to join an existing raft group
> ----------------------------------------------------------
>
>                 Key: RATIS-178
>                 URL: https://issues.apache.org/jira/browse/RATIS-178
>             Project: Ratis
>          Issue Type: Bug
>            Reporter: Tsz Wo Nicholas Sze
>            Assignee: Tsz Wo Nicholas Sze
>         Attachments: org.apache.ratis.grpc.TestLeaderElectionWithGrpc-output.txt, r178_20171223.patch
>
>
> When two servers starts in a 3-server group, they may elect a leader and then start the service.  Then, start the third server.  It somehow fails to join the group.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)