You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ozone.apache.org by "Siddhant Sangwan (Jira)" <ji...@apache.org> on 2023/03/21 13:36:00 UTC

[jira] [Created] (HDDS-8230) Let ReplicationManager decide the timeout for commands in Datanodes

Siddhant Sangwan created HDDS-8230:
--------------------------------------

             Summary: Let ReplicationManager decide the timeout for commands in Datanodes
                 Key: HDDS-8230
                 URL: https://issues.apache.org/jira/browse/HDDS-8230
             Project: Apache Ozone
          Issue Type: Sub-task
          Components: SCM
            Reporter: Siddhant Sangwan
             Fix For: 1.4.0


Right now, "hdds.scm.replication.command.deadline.factor" is a fraction. For long durations such as 60 minutes, the difference between SCM deadline and Datanode deadline will be 60 - 60 * 0.9, which is 6 minutes. This is a significant difference, so perhaps this configuration should be a duration instead, like 30 seconds.

Currently the APIs provided by RM expose the DN deadline as a parameter. We could remove this and just let the RM decide a deadline for commands in the DN.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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