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

Posted to issues@ozone.apache.org by "Attila Doroszlai (Jira)" <ji...@apache.org> on 2023/03/21 18:32:00 UTC

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

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

Attila Doroszlai updated HDDS-8230:
-----------------------------------
    Fix Version/s:     (was: 1.4.0)

> 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
>            Priority: Major
>
> 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