hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "chencan (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDDS-814) dfs.ratis.leader.election.minimum.timeout.duration should not be read by client
Date Thu, 15 Nov 2018 06:40:01 GMT

     [ https://issues.apache.org/jira/browse/HDDS-814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

chencan updated HDDS-814:
-------------------------
    Attachment: HDDS-814.001.patch

> dfs.ratis.leader.election.minimum.timeout.duration should not be read by client
> -------------------------------------------------------------------------------
>
>                 Key: HDDS-814
>                 URL: https://issues.apache.org/jira/browse/HDDS-814
>             Project: Hadoop Distributed Data Store
>          Issue Type: Improvement
>            Reporter: Arpit Agarwal
>            Priority: Major
>              Labels: newbie
>         Attachments: HDDS-814.001.patch
>
>
> dfs.ratis.leader.election.minimum.timeout.duration is read by client for the following
assertion.
> {code}
>     Preconditions
>         .assertTrue(maxRetryCount * retryInterval > 5 * leaderElectionTimeout,
>             "Please make sure dfs.ratis.client.request.max.retries * "
>                 + "dfs.ratis.client.request.retry.interval > "
>                 + "5 * dfs.ratis.leader.election.minimum.timeout.duration");
> {code}
> This does not guarantee that the leader is using the same value as the client. We should
probably just ensure that the defaults are sane and remove this assert.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org


Mime
View raw message