[
https://issues.apache.org/jira/browse/RATIS-2012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17809364#comment-17809364
]
Attila Doroszlai commented on RATIS-2012:
-----------------------------------------
Thanks [~szetszwo] for finding this issue. If I understand correctly, retry
after close may be the cause for "ManagedChannel not shutdown properly" where
client request is triggered by TimeoutTimer (e.g. HDDS-10097).
> Client should not retry after close
> -----------------------------------
>
> Key: RATIS-2012
> URL: https://issues.apache.org/jira/browse/RATIS-2012
> Project: Ratis
> Issue Type: Bug
> Components: client
> Reporter: Tsz-wo Sze
> Assignee: Tsz-wo Sze
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Tried to add a test RaftLog truncate test for RATIS-2011. Found that
> RaftClient may retry after close().
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
