[ 
https://issues.apache.org/jira/browse/HADOOP-14971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16221350#comment-16221350
 ] 

ASF GitHub Bot commented on HADOOP-14971:
-----------------------------------------

Github user ajfabbri commented on a diff in the pull request:

    https://github.com/apache/hadoop/pull/282#discussion_r147284720
  
    --- Diff: 
hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/s3guard/DynamoDBMetadataStore.java
 ---
    @@ -306,12 +338,15 @@ public void initialize(Configuration config) throws 
IOException {
        * between each attempt of {@link #MIN_RETRY_SLEEP_MSEC} milliseconds.
        * @param config
        */
    -  private void setMaxRetries(Configuration config) {
    +  private void initDataAccessRetries(Configuration config) {
         int maxRetries = config.getInt(S3GUARD_DDB_MAX_RETRIES,
             S3GUARD_DDB_MAX_RETRIES_DEFAULT);
         dataAccessRetryPolicy = RetryPolicies
             .exponentialBackoffRetry(maxRetries, MIN_RETRY_SLEEP_MSEC,
                 TimeUnit.MILLISECONDS);
    +    dataAccess = new Invoker(dataAccessRetryPolicy,
    +        this::retryEvent
    +    );
    --- End diff --
    
    Doesn't look like this is ever used.


> Merge S3A committers into trunk
> -------------------------------
>
>                 Key: HADOOP-14971
>                 URL: https://issues.apache.org/jira/browse/HADOOP-14971
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>    Affects Versions: 3.0.0
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>
> Merge the HADOOP-13786 committer into trunk. This branch is being set up as a 
> github PR for review there & to keep it out the mailboxes of the watchers on 
> the main JIRA



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to