Apache
/
druid
mirror of https://github.com/apache/druid.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Better defaults for Retry policy for task actions 

This PR changes the retry of task actions to be a bit more aggressive
by reducing the maxWait. Current defaults were 1 min to 10 mins, which
lead to a very delayed recovery in case there are any transient network
issues between the overlord and the peons.

doc changes.
This commit is contained in:
Nishant 2016-03-18 10:30:38 -07:00
parent 011efbfca7
commit ed8f39fcfe
2 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/content/configuration/indexing-service.md
View File

@ -298,6 +298,6 @@ If the peon is running in remote mode, there must be an overlord up and running.
|Property|Description|Default|
|--------|-----------|-------|
|`druid.peon.taskActionClient.retry.minWait`|The minimum retry time to communicate with overlord.|PT1M|
|`druid.peon.taskActionClient.retry.maxWait`|The maximum retry time to communicate with overlord.|PT10M|
|`druid.peon.taskActionClient.retry.maxRetryCount`|The maximum number of retries to communicate with overlord.|10|
|`druid.peon.taskActionClient.retry.minWait`|The minimum retry time to communicate with overlord.|PT5S|
|`druid.peon.taskActionClient.retry.maxWait`|The maximum retry time to communicate with overlord.|PT1M|
|`druid.peon.taskActionClient.retry.maxRetryCount`|The maximum number of retries to communicate with overlord.|60|

6
indexing-service/src/main/java/io/druid/indexing/common/RetryPolicyConfig.java
View File

@ -27,13 +27,13 @@ import org.joda.time.Period;
public class RetryPolicyConfig
{
@JsonProperty
private Period minWait = new Period("PT1M");
private Period minWait = new Period("PT5S");
@JsonProperty
private Period maxWait = new Period("PT10M");
private Period maxWait = new Period("PT1M");
@JsonProperty
private long maxRetryCount = 10;
private long maxRetryCount = 60;
public Period getMinWait()
{