You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Viraj Jasani (Jira)" <ji...@apache.org> on 2022/09/01 00:36:00 UTC

[jira] [Created] (HADOOP-18435) Remove usage of fs.s3a.executor.capacity

Viraj Jasani created HADOOP-18435:
-------------------------------------

             Summary: Remove usage of fs.s3a.executor.capacity
                 Key: HADOOP-18435
                 URL: https://issues.apache.org/jira/browse/HADOOP-18435
             Project: Hadoop Common
          Issue Type: Sub-task
          Components: fs/s3
            Reporter: Viraj Jasani
            Assignee: Viraj Jasani


When s3guard was part of s3a, DynamoDBMetadataStore was the only consumer of StoreContext that used throttled executor provided by StoreContext, which internally uses fs.s3a.executor.capacity to determine executor capacity for SemaphoredDelegatingExecutor. With the removal of s3guard from s3a, we should also remove fs.s3a.executor.capacity and it's usages as it's no longer being used by any StoreContext consumers. The config's existence and its description can be really confusing for the users.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org