[jira] [Updated] (YARN-9834) Allow using a pool of local users to run Yarn Secure Container in secure mode

[ https://issues.apache.org/jira/browse/YARN-9834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] shanyu zhao updated YARN-9834: -- Description: Yarn Secure Container in secure mode allows separation of different user's local files

[jira] [Commented] (YARN-9834) Allow using a pool of local users to run Yarn Secure Container in secure mode

[ https://issues.apache.org/jira/browse/YARN-9834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16932085#comment-16932085 ] shanyu zhao commented on YARN-9834: --- Thanks for the review [~eyang]. If you see any security hole in

[jira] [Comment Edited] (YARN-9834) Allow using a pool of local users to run Yarn Secure Container in secure mode

[ https://issues.apache.org/jira/browse/YARN-9834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16932009#comment-16932009 ] shanyu zhao edited comment on YARN-9834 at 9/18/19 5:45 AM: {quote}Given the

[jira] [Commented] (YARN-9839) NodeManager java.lang.OutOfMemoryError unable to create new native thread

[ https://issues.apache.org/jira/browse/YARN-9839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16932064#comment-16932064 ] Chandni Singh commented on YARN-9839: - Another issue is that the error from the {{LocalizerRunner}}

[jira] [Commented] (YARN-9834) Allow using a pool of local users to run Yarn Secure Container in secure mode

[ https://issues.apache.org/jira/browse/YARN-9834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16932041#comment-16932041 ] Eric Yang commented on YARN-9834: - Sorry, this design looks too risky for me to consider. I will let

[jira] [Issue Comment Deleted] (YARN-9839) NodeManager java.lang.OutOfMemoryError unable to create new native thread

[ https://issues.apache.org/jira/browse/YARN-9839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandni Singh updated YARN-9839: Comment: was deleted (was: Caching {{LocalizerRunner}} which is a {{Thread}} is not a good idea.

[jira] [Commented] (YARN-9814) JobHistoryServer can't delete aggregated files, if remote app root directory is created by NodeManager

[ https://issues.apache.org/jira/browse/YARN-9814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16932026#comment-16932026 ] Sunil Govindan commented on YARN-9814: -- I have committed this to trunk, thanks . [~adam.antal] If

[jira] [Comment Edited] (YARN-9839) NodeManager java.lang.OutOfMemoryError unable to create new native thread

[ https://issues.apache.org/jira/browse/YARN-9839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16932017#comment-16932017 ] Chandni Singh edited comment on YARN-9839 at 9/18/19 3:58 AM: -- Caching

[jira] [Commented] (YARN-9814) JobHistoryServer can't delete aggregated files, if remote app root directory is created by NodeManager

[ https://issues.apache.org/jira/browse/YARN-9814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16932025#comment-16932025 ] Hudson commented on YARN-9814: -- FAILURE: Integrated in Jenkins build Hadoop-trunk-Commit #17321 (See

[jira] [Commented] (YARN-9814) JobHistoryServer can't delete aggregated files, if remote app root directory is created by NodeManager

[ https://issues.apache.org/jira/browse/YARN-9814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16932022#comment-16932022 ] Sunil Govindan commented on YARN-9814: -- +1 Committing shortly > JobHistoryServer can't delete

[jira] [Updated] (YARN-9833) Race condition when DirectoryCollection.checkDirs() runs during container launch

[ https://issues.apache.org/jira/browse/YARN-9833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Govindan updated YARN-9833: - Fix Version/s: 3.1.4 3.2.2 > Race condition when

[jira] [Comment Edited] (YARN-9839) NodeManager java.lang.OutOfMemoryError unable to create new native thread

[ https://issues.apache.org/jira/browse/YARN-9839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16932017#comment-16932017 ] Chandni Singh edited comment on YARN-9839 at 9/18/19 3:51 AM: -- Caching

[jira] [Commented] (YARN-9839) NodeManager java.lang.OutOfMemoryError unable to create new native thread

[ https://issues.apache.org/jira/browse/YARN-9839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16932017#comment-16932017 ] Chandni Singh commented on YARN-9839: - Caching {{LocalizerRunner}} which is a {{Thread}} is not a good

[jira] [Created] (YARN-9839) NodeManager java.lang.OutOfMemoryError unable to create new native thread

Chandni Singh created YARN-9839: --- Summary: NodeManager java.lang.OutOfMemoryError unable to create new native thread Key: YARN-9839 URL: https://issues.apache.org/jira/browse/YARN-9839 Project: Hadoop

[jira] [Comment Edited] (YARN-9834) Allow using a pool of local users to run Yarn Secure Container in secure mode

[ https://issues.apache.org/jira/browse/YARN-9834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16932009#comment-16932009 ] shanyu zhao edited comment on YARN-9834 at 9/18/19 3:23 AM: {quote}Given the

[jira] [Commented] (YARN-9834) Allow using a pool of local users to run Yarn Secure Container in secure mode

[ https://issues.apache.org/jira/browse/YARN-9834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16932009#comment-16932009 ] shanyu zhao commented on YARN-9834: --- {quote}Given the reasoning of node manager running in Docker

[jira] [Commented] (YARN-9834) Allow using a pool of local users to run Yarn Secure Container in secure mode

[ https://issues.apache.org/jira/browse/YARN-9834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931975#comment-16931975 ] Eric Yang commented on YARN-9834: - {quote}"host" in this scenario is the Docker container running node

[jira] [Commented] (YARN-9834) Allow using a pool of local users to run Yarn Secure Container in secure mode

[ https://issues.apache.org/jira/browse/YARN-9834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931953#comment-16931953 ] shanyu zhao commented on YARN-9834: --- {quote}I think host joining AD is required to keep authorized

[jira] [Commented] (YARN-2255) YARN Audit logging not added to log4j.properties

[ https://issues.apache.org/jira/browse/YARN-2255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931952#comment-16931952 ] Weiwei Yang commented on YARN-2255: --- I have committed this to trunk, 3.2 and 3.1. 3.0 is skipped because

[jira] [Commented] (YARN-2255) YARN Audit logging not added to log4j.properties

[ https://issues.apache.org/jira/browse/YARN-2255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931947#comment-16931947 ] Weiwei Yang commented on YARN-2255: --- Sorry for the late response [~aihuaxu], this got slipped away from

[jira] [Commented] (YARN-2255) YARN Audit logging not added to log4j.properties

[ https://issues.apache.org/jira/browse/YARN-2255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931949#comment-16931949 ] Hudson commented on YARN-2255: -- FAILURE: Integrated in Jenkins build Hadoop-trunk-Commit #17320 (See

[jira] [Commented] (YARN-9834) Allow using a pool of local users to run Yarn Secure Container in secure mode

[ https://issues.apache.org/jira/browse/YARN-9834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931946#comment-16931946 ] Eric Yang commented on YARN-9834: - {quote}For SSSD to work it needs to have credentials to talk to LDAP,

[jira] [Commented] (YARN-8849) DynoYARN: A simulation and testing infrastructure for YARN clusters

[ https://issues.apache.org/jira/browse/YARN-8849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931752#comment-16931752 ] Zhe Zhang commented on YARN-8849: - [~jhung] has been continuing this work internally. We plan to share an

[jira] [Assigned] (YARN-8849) DynoYARN: A simulation and testing infrastructure for YARN clusters

[ https://issues.apache.org/jira/browse/YARN-8849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe Zhang reassigned YARN-8849: --- Assignee: Jonathan Hung (was: Keqiu Hu) > DynoYARN: A simulation and testing infrastructure for

[jira] [Commented] (YARN-9837) YARN Service fails to fetch status for Stopped apps with bigger spec files

[ https://issues.apache.org/jira/browse/YARN-9837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931730#comment-16931730 ] Hudson commented on YARN-9837: -- FAILURE: Integrated in Jenkins build Hadoop-trunk-Commit #17314 (See

[jira] [Commented] (YARN-9834) Allow using a pool of local users to run Yarn Secure Container in secure mode

[ https://issues.apache.org/jira/browse/YARN-9834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931725#comment-16931725 ] shanyu zhao commented on YARN-9834: --- [~eyang] {quote}The mechanism doesn't need to be different between

[jira] [Commented] (YARN-9838) Using the CapacityScheduler,Apply "movetoqueue" on the application which CS reserved containers for,will cause "Num Container" and "Used Resource" in ResourceUsage metri

[ https://issues.apache.org/jira/browse/YARN-9838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931698#comment-16931698 ] Hadoop QA commented on YARN-9838: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Commented] (YARN-9768) RM Renew Delegation token thread should timeout and retry

[ https://issues.apache.org/jira/browse/YARN-9768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931643#comment-16931643 ] Manikandan R commented on YARN-9768: [~elgoiri] [~crh] Can you review? > RM Renew Delegation token

[jira] [Comment Edited] (YARN-9772) CapacitySchedulerQueueManager has incorrect list of queues

[ https://issues.apache.org/jira/browse/YARN-9772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931577#comment-16931577 ] Manikandan R edited comment on YARN-9772 at 9/17/19 4:17 PM: - True,

[jira] [Commented] (YARN-9833) Race condition when DirectoryCollection.checkDirs() runs during container launch

[ https://issues.apache.org/jira/browse/YARN-9833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931612#comment-16931612 ] Hudson commented on YARN-9833: -- FAILURE: Integrated in Jenkins build Hadoop-trunk-Commit #17313 (See

[jira] [Commented] (YARN-9772) CapacitySchedulerQueueManager has incorrect list of queues

[ https://issues.apache.org/jira/browse/YARN-9772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931577#comment-16931577 ] Manikandan R commented on YARN-9772: True, [~tarunparimi] but I think those situations are very

[jira] [Commented] (YARN-9834) Allow using a pool of local users to run Yarn Secure Container in secure mode

[ https://issues.apache.org/jira/browse/YARN-9834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931554#comment-16931554 ] Eric Yang commented on YARN-9834: - [~shanyu] {quote}You are talking about Docker container executor. What

[jira] [Commented] (YARN-9833) Race condition when DirectoryCollection.checkDirs() runs during container launch

[ https://issues.apache.org/jira/browse/YARN-9833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931493#comment-16931493 ] Sunil Govindan commented on YARN-9833: -- +1. Committing this now. > Race condition when

[jira] [Updated] (YARN-9838) Using the CapacityScheduler,Apply "movetoqueue" on the application which CS reserved containers for,will cause "Num Container" and "Used Resource" in ResourceUsage metrics

[ https://issues.apache.org/jira/browse/YARN-9838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jiulongzhu updated YARN-9838: - Attachment: YARN-9838.0001.patch > Using the CapacityScheduler,Apply "movetoqueue" on the application

[jira] [Updated] (YARN-9838) Using the CapacityScheduler,Apply "movetoqueue" on the application which CS reserved containers for,will cause "Num Container" and "Used Resource" in ResourceUsage metrics

[ https://issues.apache.org/jira/browse/YARN-9838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jiulongzhu updated YARN-9838: - Attachment: (was: YARN-9838.0001.patch) > Using the CapacityScheduler,Apply "movetoqueue" on the

[jira] [Commented] (YARN-9836) General usability improvements in showSimulationTrace.html

[ https://issues.apache.org/jira/browse/YARN-9836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931384#comment-16931384 ] Hadoop QA commented on YARN-9836: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Commented] (YARN-4029) Update LogAggregationStatus to store on finish

[ https://issues.apache.org/jira/browse/YARN-4029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931377#comment-16931377 ] Adam Antal commented on YARN-4029: -- Seems like there wasn't any updates on this issue lately. Are you

[jira] [Commented] (YARN-9838) Using the CapacityScheduler,Apply "movetoqueue" on the application which CS reserved containers for,will cause "Num Container" and "Used Resource" in ResourceUsage metri

[ https://issues.apache.org/jira/browse/YARN-9838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931302#comment-16931302 ] Hadoop QA commented on YARN-9838: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Updated] (YARN-9836) General usability improvements in showSimulationTrace.html

[ https://issues.apache.org/jira/browse/YARN-9836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Antal updated YARN-9836: - Attachment: YARN-9836.001.patch > General usability improvements in showSimulationTrace.html >

[jira] [Commented] (YARN-9838) Using the CapacityScheduler,Apply "movetoqueue" on the application which CS reserved containers for,will cause "Num Container" and "Used Resource" in ResourceUsage metri

[ https://issues.apache.org/jira/browse/YARN-9838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931239#comment-16931239 ] jiulongzhu commented on YARN-9838: -- [~sunilg]  Sorry for that, it wouldn't happen again. # I checked

[jira] [Updated] (YARN-9838) Using the CapacityScheduler,Apply "movetoqueue" on the application which CS reserved containers for,will cause "Num Container" and "Used Resource" in ResourceUsage metrics

[ https://issues.apache.org/jira/browse/YARN-9838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jiulongzhu updated YARN-9838: - Attachment: (was: bug_fix_capacityScheduler_moveApplication.patch) > Using the

[jira] [Commented] (YARN-9826) Blocked threads at EntityGroupFSTimelineStore#getCachedStore

[ https://issues.apache.org/jira/browse/YARN-9826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931218#comment-16931218 ] Harunobu Daikoku commented on YARN-9826: [~Prabhu Joseph] Although multiple threads could indeed

[jira] [Reopened] (YARN-9838) Using the CapacityScheduler,Apply "movetoqueue" on the application which CS reserved containers for,will cause "Num Container" and "Used Resource" in ResourceUsage metric

[ https://issues.apache.org/jira/browse/YARN-9838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jiulongzhu reopened YARN-9838: -- > Using the CapacityScheduler,Apply "movetoqueue" on the application which CS > reserved containers

[jira] [Commented] (YARN-9838) Using the CapacityScheduler,Apply "movetoqueue" on the application which CS reserved containers for,will cause "Num Container" and "Used Resource" in ResourceUsage metri

[ https://issues.apache.org/jira/browse/YARN-9838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931192#comment-16931192 ] Sunil Govindan commented on YARN-9838: -- [~jiulongZhu] Thanks for reporting this issues. Few general

[jira] [Commented] (YARN-9838) Using the CapacityScheduler,Apply "movetoqueue" on the application which CS reserved containers for,will cause "Num Container" and "Used Resource" in ResourceUsage metri

[ https://issues.apache.org/jira/browse/YARN-9838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931184#comment-16931184 ] jiulongzhu commented on YARN-9838: -- I need a review.Thanks! [~genericqa] [~lavkesh] [~aaron.hadoop] 

[jira] [Assigned] (YARN-9748) Allow capacity-scheduler configuration on HDFS and support reload from HDFS

[ https://issues.apache.org/jira/browse/YARN-9748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhoukang reassigned YARN-9748: -- Assignee: zhoukang (was: Prabhu Joseph) > Allow capacity-scheduler configuration on HDFS and support

[jira] [Resolved] (YARN-9838) Using the CapacityScheduler,Apply "movetoqueue" on the application which CS reserved containers for,will cause "Num Container" and "Used Resource" in ResourceUsage metric

[ https://issues.apache.org/jira/browse/YARN-9838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jiulongzhu resolved YARN-9838. -- Resolution: Resolved > Using the CapacityScheduler,Apply "movetoqueue" on the application which CS >

[jira] [Resolved] (YARN-9835) 官网代码片段错误

[ https://issues.apache.org/jira/browse/YARN-9835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka resolved YARN-9835. - Resolution: Duplicate > 官网代码片段错误 > > > Key: YARN-9835 >

[jira] [Commented] (YARN-9835) 官网代码片段错误

[ https://issues.apache.org/jira/browse/YARN-9835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931167#comment-16931167 ] Akira Ajisaka commented on YARN-9835: - Hi [~lijianfeng], please use English to file an issue. Anyway,

[jira] [Reopened] (YARN-9838) Using the CapacityScheduler,Apply "movetoqueue" on the application which CS reserved containers for,will cause "Num Container" and "Used Resource" in ResourceUsage metric

[ https://issues.apache.org/jira/browse/YARN-9838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jiulongzhu reopened YARN-9838: -- > Using the CapacityScheduler,Apply "movetoqueue" on the application which CS > reserved containers

[jira] [Updated] (YARN-9838) Using the CapacityScheduler,Apply "movetoqueue" on the application which CS reserved containers for,will cause "Num Container" and "Used Resource" in ResourceUsage metrics

[ https://issues.apache.org/jira/browse/YARN-9838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jiulongzhu updated YARN-9838: - Attachment: (was: bug_fix_capacityScheduler_moveApplication.patch) > Using the

[jira] [Updated] (YARN-9838) Using the CapacityScheduler,Apply "movetoqueue" on the application which CS reserved containers for,will cause "Num Container" and "Used Resource" in ResourceUsage metrics

[ https://issues.apache.org/jira/browse/YARN-9838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jiulongzhu updated YARN-9838: - Description:       In some clusters of ours, we are seeing "Used Resource","Used Capacity","Absolute

[jira] [Created] (YARN-9838) Using the CapacityScheduler,Apply "movetoqueue" on the application which CS reserved containers for,will cause "Num Container" and "Used Resource" in ResourceUsage metrics

jiulongzhu created YARN-9838: Summary: Using the CapacityScheduler,Apply "movetoqueue" on the application which CS reserved containers for,will cause "Num Container" and "Used Resource" in ResourceUsage metrics error Key: YARN-9838