You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Shashikant Banerjee (Jira)" <ji...@apache.org> on 2020/06/03 15:24:00 UTC
[jira] [Resolved] (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 ]
Shashikant Banerjee resolved HDDS-1504.
---------------------------------------
Fix Version/s: 0.6.0
Resolution: Fixed
This has been fixed with https://issues.apache.org/jira/browse/RATIS-796.
> 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
> Labels: TriagePending
> Fix For: 0.6.0
>
>
> 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.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-issues-help@hadoop.apache.org