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

Posted to hdfs-issues@hadoop.apache.org by "Mukul Kumar Singh (Jira)" <ji...@apache.org> on 2019/09/05 05:46:00 UTC

[jira] [Assigned] (HDDS-1504) Watch Request should use retry policy with higher timeouts for RaftClient

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

Mukul Kumar Singh reassigned HDDS-1504:
---------------------------------------

    Assignee:     (was: Shashikant Banerjee)

> Watch Request should use retry policy with higher timeouts for RaftClient
> -------------------------------------------------------------------------
>
>                 Key: HDDS-1504
>                 URL: https://issues.apache.org/jira/browse/HDDS-1504
>             Project: Hadoop Distributed Data Store
>          Issue Type: Bug
>          Components: Ozone Client
>    Affects Versions: 0.5.0
>            Reporter: Shashikant Banerjee
>            Priority: Major
>
> Currently, Raft Client request times out with default of 3s but, watch request can have longer timeouts as some followers can be really slow. It would be good to enforce a retry policy with higher timeouts while submitting watch request over raft client in ozone.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

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