[
https://issues.apache.org/jira/browse/HDDS-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17088699#comment-17088699
]
Mukul Kumar Singh commented on HDDS-3459:
-----------------------------------------
I think the issue is similar to HDDS-3451.
cc [~nanda]
> Datanode use a single thread to process the command of scm
> ----------------------------------------------------------
>
> Key: HDDS-3459
> URL: https://issues.apache.org/jira/browse/HDDS-3459
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Reporter: runzhiwang
> Assignee: runzhiwang
> Priority: Major
> Attachments: screenshot-1.png, screenshot-10.png, screenshot-11.png,
> screenshot-12.png, screenshot-13.png, screenshot-14.png, screenshot-2.png,
> screenshot-3.png, screenshot-4.png, screenshot-5.png, screenshot-6.png,
> screenshot-7.png, screenshot-8.png, screenshot-9.png
>
>
> *What's the problem ?*
> There are 3 datanodes in a group: leader, follower1, follower2. Steps to
> reproduce the problem are as following:
> 1. follower2 report close pipeline
> 2. scm send close pipeline command
> 3. leader and follower1 remove group, but follower2 socket timeout and does
> not remove group
> 4. follower2 then begin infinite LeaderElection at least 6 hours, leader and
> follower1 response group not found
> You can find it in following screenshot.
> 1. follower2 report close pipeline
> !screenshot-8.png!
> 2. Scm close pipeline:
> !screenshot-9.png!
> !screenshot-10.png!
> 3. leader remove group
> !screenshot-11.png!
> follower1 remove group
> !screenshot-12.png!
> follower2 socket timeout
> !screenshot-13.png!
> 4. follower2 then begin infinite LeaderElection at least 6 hours
> !screenshot-14.png!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
