Support jittering backoff strategies

[yuokada]

Exponential Backoff And Jitter | AWS Architecture Blog

According to the blog entry above, jittering backoffs are more effective than exponential backoff in view of retry count and completion time.

---

• FullJitterBackOff is used instead of ExponentialBackOff by default.

• We can select a backoff strategy as follows:

  client = TDClient.newBuilder()
          .setRetryStrategy(BackOffStrategy.Exponential)
          .build()
          .httpClient;

[miniway]

@yuokada jittering backoffs looks good to me. Then how we configure or switch to the jittering ?

[yuokada]

@miniway In our presto? I don't consider yet. But, for current user using ExponentialBackOff can easily switch to jittering backoffs since all backoffs extend BackOff abstract class.

[yuokada]

Ah... you mean that I need to improve the class below to support jittering backoffs. Right? https://github.com/treasure-data/td-client-java/blob/master/src/main/java/com/treasuredata/client/TDClientConfig.java

If so, I didn't completely notice.

[xerial]

TDClientBuilder is an entry point for configuring TDClient https://github.com/treasure-data/td-client-java/blob/master/src/main/java/com/treasuredata/client/AbstractTDClientBuilder.java

We already have parameters (max retry, multipliers, etc.) for retyring so we should be able to provide a custom Backoff factory (default will be generating FullJittering class). For example, create an interface like this:

interface BackoffFactory {
   Backoff newBackoff(TDClientConfig config); 
}

Then, support setting a custom BackoffFactory at TDClientBuilder.

We also need to change this part https://github.com/treasure-data/td-client-java/blob/c02b9bbd2d94e2b948cf6bde5f07448ca2f1a4a1/src/main/java/com/treasuredata/client/TDHttpClient.java#L345