[jira] [Commented] (YARN-11399) Make ResourceManager DelegationTokenRenewer timeout feature configurable

[ https://issues.apache.org/jira/browse/YARN-11399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17648869#comment-17648869 ] ASF GitHub Bot commented on YARN-11399: --- Daniel-009497 opened a new pull request, #

[jira] [Updated] (YARN-11399) Make ResourceManager DelegationTokenRenewer timeout feature configurable

[ https://issues.apache.org/jira/browse/YARN-11399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated YARN-11399: -- Labels: pull-request-available (was: ) > Make ResourceManager DelegationTokenRenewer timeout f

[jira] [Updated] (YARN-11399) Make ResourceManager DelegationTokenRenewer timeout feature configurable

[ https://issues.apache.org/jira/browse/YARN-11399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Ma updated YARN-11399: - Description: ResourceManager Delegation token renew timeout and retry mechanism is introduced in Hadoop

[jira] [Updated] (YARN-11399) Make ResourceManager DelegationTokenRenewer timeout feature configurable

[ https://issues.apache.org/jira/browse/YARN-11399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Ma updated YARN-11399: - Description: ResourceManager Delegation token renew timeout and retry mechanism is introduced in Hadoop

[jira] [Commented] (YARN-11398) ResourceManager DelegationTokenRenewer timeout feature may cause high utilization of CPU and object leak.

[ https://issues.apache.org/jira/browse/YARN-11398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17648864#comment-17648864 ] ASF GitHub Bot commented on YARN-11398: --- hadoop-yetus commented on PR #5233: URL: h

[jira] [Created] (YARN-11399) Make ResourceManager DelegationTokenRenewer timeout feature configurable

Daniel Ma created YARN-11399: Summary: Make ResourceManager DelegationTokenRenewer timeout feature configurable Key: YARN-11399 URL: https://issues.apache.org/jira/browse/YARN-11399 Project: Hadoop YARN

[jira] [Updated] (YARN-11398) ResourceManager DelegationTokenRenewer timeout feature may cause high utilization of CPU and object leak.

[ https://issues.apache.org/jira/browse/YARN-11398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Ma updated YARN-11398: - Description: ResourceManager DelegationTokenRenewer timeout feature may cause high utilization of CPU an

[jira] [Commented] (YARN-11398) ResourceManager DelegationTokenRenewer timeout feature may cause high utilization of CPU and object leak.

[ https://issues.apache.org/jira/browse/YARN-11398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17648851#comment-17648851 ] Daniel Ma commented on YARN-11398: -- PR link: github.com/apache/hadoop/pull/5233 > Resou

[jira] [Commented] (YARN-11398) ResourceManager DelegationTokenRenewer timeout feature may cause high utilization of CPU and object leak.

[ https://issues.apache.org/jira/browse/YARN-11398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17648849#comment-17648849 ] ASF GitHub Bot commented on YARN-11398: --- Daniel-009497 opened a new pull request, #

[jira] [Updated] (YARN-11398) ResourceManager DelegationTokenRenewer timeout feature may cause high utilization of CPU and object leak.

[ https://issues.apache.org/jira/browse/YARN-11398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated YARN-11398: -- Labels: pull-request-available (was: ) > ResourceManager DelegationTokenRenewer timeout featur

[jira] [Created] (YARN-11398) ResourceManager DelegationTokenRenewer timeout feature may cause high utilization of CPU and object leak.

Daniel Ma created YARN-11398: Summary: ResourceManager DelegationTokenRenewer timeout feature may cause high utilization of CPU and object leak. Key: YARN-11398 URL: https://issues.apache.org/jira/browse/YARN-11398

[jira] [Commented] (YARN-11397) Memory leak when reading aggregated logs from s3 (LogAggregationTFileController::readAggregatedLogs)

[ https://issues.apache.org/jira/browse/YARN-11397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17648770#comment-17648770 ] Chris Nauroth commented on YARN-11397: -- Is this the same {{S3AInstrumentation}} leak

[jira] [Commented] (YARN-11320) [Federation] Add getSchedulerInfo REST APIs for Router

[ https://issues.apache.org/jira/browse/YARN-11320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17648719#comment-17648719 ] ASF GitHub Bot commented on YARN-11320: --- hadoop-yetus commented on PR #5217: URL: h

[jira] [Commented] (YARN-10896) RM fail over is not reporting the nodes DECOMMISSIONED

[ https://issues.apache.org/jira/browse/YARN-10896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17648716#comment-17648716 ] Anoop Sam John commented on YARN-10896: --- [~Sushil-K-S] As per the patch, for every

[jira] [Commented] (YARN-10879) Incorrect WARN text in ACL check for application tag based placement

[ https://issues.apache.org/jira/browse/YARN-10879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17648704#comment-17648704 ] ASF GitHub Bot commented on YARN-10879: --- hadoop-yetus commented on PR #5231: URL: h

[jira] [Updated] (YARN-11397) Memory leak when reading aggregated logs from s3 (LogAggregationTFileController::readAggregatedLogs)

[ https://issues.apache.org/jira/browse/YARN-11397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maciej Smole��ski updated YARN-11397: - Description: Reproduction code in the attachment. When collecting aggregated logs from s

[jira] [Updated] (YARN-11397) Memory leak when reading aggregated logs from s3 (LogAggregationTFileController::readAggregatedLogs)

[ https://issues.apache.org/jira/browse/YARN-11397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maciej Smole��ski updated YARN-11397: - Description: Reproduction code in the attachment. When collecting aggregated logs from s

[jira] [Commented] (YARN-10879) Incorrect WARN text in ACL check for application tag based placement

[ https://issues.apache.org/jira/browse/YARN-10879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17648601#comment-17648601 ] ASF GitHub Bot commented on YARN-10879: --- susheel-gupta opened a new pull request, #

[jira] [Updated] (YARN-10879) Incorrect WARN text in ACL check for application tag based placement

[ https://issues.apache.org/jira/browse/YARN-10879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated YARN-10879: -- Labels: pull-request-available (was: ) > Incorrect WARN text in ACL check for application tag

[jira] [Updated] (YARN-11397) Memory leak when reading aggregated logs from s3 (LogAggregationTFileController::readAggregatedLogs)

[ https://issues.apache.org/jira/browse/YARN-11397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maciej Smole��ski updated YARN-11397: - Description: Reproduction code in the attachment. When collecting aggregated logs from s

[jira] [Created] (YARN-11397) Memory leak when reading aggregated logs from s3 (LogAggregationTFileController::readAggregatedLogs)

Maciej Smole��ski created YARN-11397: Summary: Memory leak when reading aggregated logs from s3 (LogAggregationTFileController::readAggregatedLogs) Key: YARN-11397 URL: https://issues.apache.org/jira/browse/YA