[ https://issues.apache.org/jira/browse/HDDS-3234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arpit Agarwal updated HDDS-3234: -------------------------------- Target Version/s: 0.6.0 Description: {code:java} <name>dfs.ratis.client.request.retry.interval</name> <value>1000ms</value> {code} Change the default value to 15s. As with 1s sleep, we will see retry happening at a very fast interval. In the billion object test, we see after changing the value to 15s, queue limit has never reached the limit. was: {code:java} <name>dfs.ratis.client.request.retry.interval</name> <value>1000ms</value> {code} Change the default value to 15s. As with 1s sleep, we will see retry happening at a very fast interval. In the billion object test, we see after changing the value to 15s, queue limit has never reached the limit. Labels: TriagePending billiontest pull-request-available (was: billiontest pull-request-available) > Fix retry interval default in Ozone client > ------------------------------------------ > > Key: HDDS-3234 > URL: https://issues.apache.org/jira/browse/HDDS-3234 > Project: Hadoop Distributed Data Store > Issue Type: Bug > Reporter: Bharat Viswanadham > Assignee: Bharat Viswanadham > Priority: Major > Labels: TriagePending, billiontest, pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > > {code:java} > <name>dfs.ratis.client.request.retry.interval</name> > <value>1000ms</value> > {code} > Change the default value to 15s. As with 1s sleep, we will see retry > happening at a very fast interval. > In the billion object test, we see after changing the value to 15s, queue > limit has never reached the limit. -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org