hadoop-hdfs-dev mailing list archives

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

             Summary: 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


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-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org


Mime
View raw message