[
https://issues.apache.org/jira/browse/RATIS-2012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17810059#comment-17810059
]
Tsz-wo Sze commented on RATIS-2012:
-----------------------------------
The new test {{RaftLogTruncateTests}} will fail without this fix:
# A client writes a few {{messagesToBeTruncated}} requests to the old leader
with three nodes (n3, n4, n5) down in a 5-node group. These entries are written
to the log but they cannot be committed since only two nodes (n1, n2) are
available.
# Shut down n1, n2.
# Restart n3, n4, n5. These nodes have a majority. They can elect a new leader
and commit new entires.
# Restart n1, n2. They should truncate their log and the
{{messagesToBeTruncated}} entries will disappear.
Bug: since the client keeps retrying even after it has been closed, the client
will retry the same requests to the new leader. The {{messagesToBeTruncated}}
entries will re-appear.
> 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: 1h 40m
> 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)
