[
https://issues.apache.org/jira/browse/HDDS-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16890414#comment-16890414
]
Arpit Agarwal commented on HDDS-1836:
-------------------------------------
{quote}which is leading to leader election taking much longer time to timeout
in case of network failures
{quote}
I think this is okay. We don't want over-eager response to network blips or
small GC pauses.
bq. leading to delayed creation of pipelines in the system
This sounds like a more serious issue. Why does it delay pipeline creation?
> Change the default value of ratis leader election min timeout to a lower value
> ------------------------------------------------------------------------------
>
> Key: HDDS-1836
> URL: https://issues.apache.org/jira/browse/HDDS-1836
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: Ozone Datanode
> Affects Versions: 0.5.0
> Reporter: Shashikant Banerjee
> Assignee: Shashikant Banerjee
> Priority: Major
> Labels: pull-request-available
> Fix For: 0.5.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The default value of min leader election timeout currently is 5s(done with
> HDDS-1718) by default which is leading to leader election taking much longer
> time to timeout in case of network failures and leading to delayed creation
> of pipelines in the system. The idea is to change the default value to a
> lower value of "2s" for now.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
