[
https://issues.apache.org/jira/browse/HBASE-21806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16755568#comment-16755568
]
Sergey Shelukhin commented on HBASE-21806:
------------------------------------------
The sync timeout is currently 5 minutes; I assume setting it too low might
cause a lot of client failures on values that are high, but not ridiculously
high... I was thinking we can just switch the WAL to avoid disruption on such
intermediate values.
> add an option to roll WAL on very slow syncs
> --------------------------------------------
>
> Key: HBASE-21806
> URL: https://issues.apache.org/jira/browse/HBASE-21806
> Project: HBase
> Issue Type: Bug
> Reporter: Sergey Shelukhin
> Assignee: Sergey Shelukhin
> Priority: Major
> Attachments: HBASE-21806.patch
>
>
> In large heterogeneous clusters sometimes a slow datanode can cause WAL syncs
> to be very slow. In this case, before the bad datanode recovers, or is
> discovered and repaired, it would be helpful to roll WAL on a very slow sync
> to get a new pipeline.
> Otherwise the slow WAL will impact write latency for a long time (slow writes
> result in less writes result in the WAL not being rolled for longer)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
