You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Arpit Agarwal (Jira)" <ji...@apache.org> on 2020/06/01 21:06:00 UTC

[jira] [Updated] (HDDS-2917) Add a different retry policy for watch requests

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

Arpit Agarwal updated HDDS-2917:
--------------------------------
    Labels: Triaged pull-request-available  (was: pull-request-available)

> Add a different retry policy for watch requests
> -----------------------------------------------
>
>                 Key: HDDS-2917
>                 URL: https://issues.apache.org/jira/browse/HDDS-2917
>             Project: Hadoop Distributed Data Store
>          Issue Type: Improvement
>          Components: Ozone Client
>            Reporter: Shashikant Banerjee
>            Assignee: Shashikant Banerjee
>            Priority: Major
>              Labels: Triaged, pull-request-available
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Currently, every request submitted to client is retried with a default retry policy in ozone.
> For watch requests , ideally the timeout is higher and there should be no retries. The idea is to address that.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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