[
https://issues.apache.org/jira/browse/RATIS-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17046502#comment-17046502
]
Hadoop QA commented on RATIS-622:
---------------------------------
| (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 6s{color}
| {color:red} RATIS-622 does not apply to master. Rebase required? Wrong
Branch? See https://yetus.apache.org/documentation/0.8.0/precommit-patchnames
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | RATIS-622 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12974565/RATIS-622.001.patch |
| Console output |
https://builds.apache.org/job/PreCommit-RATIS-Build/1245/console |
| Powered by | Apache Yetus 0.8.0 http://yetus.apache.org |
This message was automatically generated.
> createLog will block indefinitely if group creation fails
> ---------------------------------------------------------
>
> Key: RATIS-622
> URL: https://issues.apache.org/jira/browse/RATIS-622
> Project: Ratis
> Issue Type: Bug
> Components: LogService
> Reporter: Josh Elser
> Assignee: Josh Elser
> Priority: Critical
> Fix For: 0.6.0
>
> Attachments: RATIS-622.001.patch
>
>
> I've seen this bug a few times, but finally got to the bottom of it. The
> VerificationTool will get to the end, but not exit. The reason is that at
> least one log has still not yet been created.
> * The client will be blocked asking the metadataquorum to create a log
> * The metadata leader will have tons of threads blocked on the writeLock
> What I just found today was an exception, logged to stderr (not stdout), that
> was thrown when the group create failed.
> However, we don't catch and re-throw this exception on group create failure,
> but proceed then to try to send a message to the group which failed to be
> created.
> We must catch this failure, try to clean up, and propagate the original
> createLog exception back to the client.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
