hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yufei Gu (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HADOOP-14926) Reconsider the default value of RPC timeout and document it
Date Tue, 03 Oct 2017 20:49:01 GMT
Yufei Gu created HADOOP-14926:

             Summary: Reconsider the default value of RPC timeout and document it
                 Key: HADOOP-14926
                 URL: https://issues.apache.org/jira/browse/HADOOP-14926
             Project: Hadoop Common
          Issue Type: Improvement
          Components: common
    Affects Versions: 3.0.0-alpha3, 2.8.1
            Reporter: Yufei Gu

We use zero as the default value of RPC timeout, which mean we don't enforce any timeout aka
infinity timeout. I think that *zero means infinite* is counter-intuitive and error-prone
through some Java libs(e.g. Socket #setSoTimeout()) do that as well. Zero could be considered
as a valid timeout value, while negative one isn't. If we use zero to represent infinite,
which number could be used to represent zero timeout? I suggest use -1 as the default value
to indicate infinite. 
We also need to document the default value and it means infinite timeout. 

This message was sent by Atlassian JIRA

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

View raw message