[ https://issues.apache.org/jira/browse/RATIS-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17084256#comment-17084256 ]
Jitendra Nath Pandey commented on RATIS-622: -------------------------------------------- [~an...@apache.org] [~elserj] this one probably needs to be rebased to get committed. It has been reviewed once already. > 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)