[
https://issues.apache.org/jira/browse/RATIS-396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16677558#comment-16677558
]
Tsz Wo Nicholas Sze commented on RATIS-396:
-------------------------------------------
r396_20181106.patch: adds retries and makes BlockingQueue capacity
configurable.
> Support retry if writeStateMachineData throws TimeoutIOException
> ----------------------------------------------------------------
>
> Key: RATIS-396
> URL: https://issues.apache.org/jira/browse/RATIS-396
> Project: Ratis
> Issue Type: Improvement
> Components: server
> Reporter: Tsz Wo Nicholas Sze
> Assignee: Tsz Wo Nicholas Sze
> Priority: Major
> Attachments: r396_20181106.patch
>
>
> If the future from writeStateMachineData throws TimeoutIOException, the
> RaftLogWorker will terminate Java VM. In some cases, such behavior is
> undesirable. For example, the application may want to just shut down Ratis
> server but not the entire application.
> In this JIRA, we allow retrying on TimeoutIOException. Then, application
> could detect no progression if TimeoutIOException happens again and again.
> Note that RaftLogWorker has a BlockingQueue with capacity of 4096. If
> TimeoutIOException happens again and again, it won't accept further
> appendEntry and block the callers.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
