[
https://issues.apache.org/jira/browse/HADOOP-17596?focusedWorklogId=608923&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-608923
]
ASF GitHub Bot logged work on HADOOP-17596:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 09/Jun/21 05:11
Start Date: 09/Jun/21 05:11
Worklog Time Spent: 10m
Work Description: surendralilhore commented on pull request #2795:
URL: https://github.com/apache/hadoop/pull/2795#issuecomment-857378838
@steveloughran , I updated the Jira.
> Are there any plans to backport to branch-3.3? A retest of the cherrypick
is all which should be needed
Yes, @sumangala-patki is working on backport and testing it for 3.2 and 3.3
branch.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 608923)
Time Spent: 3h 40m (was: 3.5h)
> ABFS: Change default Readahead Queue Depth from num(processors) to const
> ------------------------------------------------------------------------
>
> Key: HADOOP-17596
> URL: https://issues.apache.org/jira/browse/HADOOP-17596
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/azure
> Affects Versions: 3.3.1
> Reporter: Sumangala Patki
> Assignee: Sumangala Patki
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.4.0
>
> Time Spent: 3h 40m
> Remaining Estimate: 0h
>
> The default value of readahead queue depth is currently set to the number of
> available processors. However, this can result in one inputstream instance
> consuming more processor time. To ensure equal thread allocation during read
> for all inputstreams created in a session, we change the default readahead
> queue depth to a constant (2).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
