[jira] [Updated] (YARN-5216) Expose configurable preemption policy for OPPORTUNISTIC containers running on the NM

[ https://issues.apache.org/jira/browse/YARN-5216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-5216: - Fix Version/s: 3.1.0 2.9.0 > Expose configurable preemption policy for OPPORTUNISTIC

[jira] [Updated] (YARN-5292) NM Container lifecycle and state transitions to support for PAUSED container state.

[ https://issues.apache.org/jira/browse/YARN-5292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-5292: - Fix Version/s: 3.1.0 2.9.0 > NM Container lifecycle and state transitions to support

[jira] [Commented] (YARN-7244) ShuffleHandler is not aware of disks that are added

[ https://issues.apache.org/jira/browse/YARN-7244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16183000#comment-16183000 ] Jason Lowe commented on YARN-7244: -- bq. Only potential issue which I see is that, once a set of dirs are

[jira] [Commented] (YARN-7244) ShuffleHandler is not aware of disks that are added

[ https://issues.apache.org/jira/browse/YARN-7244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16182678#comment-16182678 ] Jason Lowe commented on YARN-7244: -- Thanks for the patch! The core issue here is that the NM is handing

[jira] [Updated] (YARN-7260) yarn.router.pipeline.cache-max-size is missing in yarn-default.xml

[ https://issues.apache.org/jira/browse/YARN-7260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-7260: - Attachment: YARN-7260-branch-2.001.patch Attaching a patch that fixes the missed rename in

[jira] [Updated] (YARN-7260) yarn.router.pipeline.cache-max-size is missing in yarn-default.xml

[ https://issues.apache.org/jira/browse/YARN-7260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-7260: - Affects Version/s: 2.9.0 Target Version/s: 2.9.0 Summary:

[jira] [Assigned] (YARN-7260) yarn.router,.

[ https://issues.apache.org/jira/browse/YARN-7260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe reassigned YARN-7260: Assignee: Jason Lowe Summary: yarn.router,. (was: TestYarnConfigurationFields fails in

[jira] [Updated] (YARN-7226) Whitelisted variables do not support delayed variable expansion

[ https://issues.apache.org/jira/browse/YARN-7226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-7226: - Attachment: YARN-7226.004.patch Thanks for the review, Eric! bq. Is there a reason for us to catch the

[jira] [Moved] (YARN-7257) AggregatedLogsBlock reports a bad 'end' value as a bad 'start' value

[ https://issues.apache.org/jira/browse/YARN-7257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe moved MAPREDUCE-6969 to YARN-7257: - Affects Version/s: (was: 3.0.0-beta1) (was:

[jira] [Commented] (YARN-7256) Giving Yarn Application the Option to Black Out Certain Nodes On the Fly

[ https://issues.apache.org/jira/browse/YARN-7256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16181416#comment-16181416 ] Jason Lowe commented on YARN-7256: -- YARN already allows application-level blacklisting since YARN-750. Is

[jira] [Commented] (YARN-7248) NM returns new SCHEDULED container status to older clients

[ https://issues.apache.org/jira/browse/YARN-7248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16181278#comment-16181278 ] Jason Lowe commented on YARN-7248: -- Thanks for the patch! It no longer applies and needs to be rebased.

[jira] [Updated] (YARN-6570) No logs were found for running application, running container

[ https://issues.apache.org/jira/browse/YARN-6570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-6570: - Fix Version/s: (was: 3.1.0) (was: 3.0.0-beta1) (was:

[jira] [Reopened] (YARN-6570) No logs were found for running application, running container

[ https://issues.apache.org/jira/browse/YARN-6570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe reopened YARN-6570: -- I missed the NEW state exposure in the trunk/branch-2 patch which will also be problematic. This not only

[jira] [Updated] (YARN-7226) Whitelisted variables do not support delayed variable expansion

[ https://issues.apache.org/jira/browse/YARN-7226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-7226: - Attachment: YARN-7226.003.patch Attaching a patch that implements the ignore-whitelist-vars-for-Docker

[jira] [Commented] (YARN-7248) NM returns new SCHEDULED container status to older clients

[ https://issues.apache.org/jira/browse/YARN-7248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16179469#comment-16179469 ] Jason Lowe commented on YARN-7248: -- Sounds good. We'll be all set until someone comes along in Hadoop 3.4

[jira] [Commented] (YARN-6570) No logs were found for running application, running container

[ https://issues.apache.org/jira/browse/YARN-6570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16179408#comment-16179408 ] Jason Lowe commented on YARN-6570: -- Yes, which is why I didn't revert this from branch-2 or trunk, just

[jira] [Commented] (YARN-7248) NM returns new SCHEDULED container status to older clients

[ https://issues.apache.org/jira/browse/YARN-7248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16179401#comment-16179401 ] Jason Lowe commented on YARN-7248: -- bq. Is it ok if for the fix, we check and return RUNNING to the client

[jira] [Commented] (YARN-7248) NM returns new SCHEDULED container status to older clients

[ https://issues.apache.org/jira/browse/YARN-7248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16179392#comment-16179392 ] Jason Lowe commented on YARN-7248: -- Maybe I'm missing something, but it looks like containers can be in

[jira] [Updated] (YARN-6570) No logs were found for running application, running container

[ https://issues.apache.org/jira/browse/YARN-6570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-6570: - Fix Version/s: (was: 2.8.3) I reverted this from branch-2.8 and also filed YARN-7248 to address the

[jira] [Commented] (YARN-6570) No logs were found for running application, running container

[ https://issues.apache.org/jira/browse/YARN-6570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16179240#comment-16179240 ] Jason Lowe commented on YARN-6570: -- -1 for the branch-2.8 patch. This broke a lot of things since nobody,

[jira] [Commented] (YARN-7248) NM returns new SCHEDULED container status to older clients

[ https://issues.apache.org/jira/browse/YARN-7248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16179231#comment-16179231 ] Jason Lowe commented on YARN-7248: -- Clients should pass a version flag or something similar to indicate

[jira] [Commented] (YARN-4597) Introduce ContainerScheduler and a SCHEDULED state to NodeManager container lifecycle

[ https://issues.apache.org/jira/browse/YARN-4597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16179233#comment-16179233 ] Jason Lowe commented on YARN-4597: -- Sorry to arrive late here, but this has backwards-compatibility

[jira] [Created] (YARN-7248) NM returns new SCHEDULED container status to older clients

Jason Lowe created YARN-7248: Summary: NM returns new SCHEDULED container status to older clients Key: YARN-7248 URL: https://issues.apache.org/jira/browse/YARN-7248 Project: Hadoop YARN Issue

[jira] [Commented] (YARN-7226) Whitelisted variables do not support delayed variable expansion

[ https://issues.apache.org/jira/browse/YARN-7226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16179115#comment-16179115 ] Jason Lowe commented on YARN-7226: -- bq. If the user doesn't override the env vars, it is expected that

[jira] [Commented] (YARN-7226) Whitelisted variables do not support delayed variable expansion

[ https://issues.apache.org/jira/browse/YARN-7226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16176987#comment-16176987 ] Jason Lowe commented on YARN-7226: -- bq. So my vote would be for putting this patch in and then filing a

[jira] [Commented] (YARN-7102) NM heartbeat stuck when responseId overflows MAX_INT

[ https://issues.apache.org/jira/browse/YARN-7102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16176821#comment-16176821 ] Jason Lowe commented on YARN-7102: -- Ah sorry, so maybe we're OK with this scenario in the current code as

[jira] [Commented] (YARN-7102) NM heartbeat stuck when responseId overflows MAX_INT

[ https://issues.apache.org/jira/browse/YARN-7102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16176461#comment-16176461 ] Jason Lowe commented on YARN-7102: -- Forgot to mention that the above scenario is probably happening a lot

[jira] [Commented] (YARN-7102) NM heartbeat stuck when responseId overflows MAX_INT

[ https://issues.apache.org/jira/browse/YARN-7102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16176421#comment-16176421 ] Jason Lowe commented on YARN-7102: -- Not a fan of that approach either. It has a corner case with the same

[jira] [Commented] (YARN-7226) Whitelisted variables do not support delayed variable expansion

[ https://issues.apache.org/jira/browse/YARN-7226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16176376#comment-16176376 ] Jason Lowe commented on YARN-7226: -- bq. For example, an image used for running MR tasks could specify its

[jira] [Commented] (YARN-5195) RM intermittently crashed with NPE while handling APP_ATTEMPT_REMOVED event when async-scheduling enabled in CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-5195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16175395#comment-16175395 ] Jason Lowe commented on YARN-5195: -- The unit test failures are similar to the branch-2.7 case -- known

[jira] [Updated] (YARN-5195) RM intermittently crashed with NPE while handling APP_ATTEMPT_REMOVED event when async-scheduling enabled in CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-5195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-5195: - Attachment: YARN-5195-branch-2.8.001.patch Attaching the branch-2.8 patch again so the QA bot can comment

[jira] [Commented] (YARN-7226) Whitelisted variables do not support delayed variable expansion

[ https://issues.apache.org/jira/browse/YARN-7226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16174846#comment-16174846 ] Jason Lowe commented on YARN-7226: -- Pinging [~sidharta-s] and [~vvasudev] since the {{var=var:-value}}

[jira] [Commented] (YARN-4266) Allow users to enter containers as UID:GID pair instead of by username

[ https://issues.apache.org/jira/browse/YARN-4266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16174786#comment-16174786 ] Jason Lowe commented on YARN-4266: -- Thanks for updating the patch! +1 lgtm. I'll commit this later today

[jira] [Commented] (YARN-7226) Whitelisted variables do not support delayed variable expansion

[ https://issues.apache.org/jira/browse/YARN-7226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16173930#comment-16173930 ] Jason Lowe commented on YARN-7226: -- Test failures appear to be unrelated, but unfortunately the details

[jira] [Commented] (YARN-7102) NM heartbeat stuck when responseId overflows MAX_INT

[ https://issues.apache.org/jira/browse/YARN-7102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16173875#comment-16173875 ] Jason Lowe commented on YARN-7102: -- Sorry for the delay. bq. After a more strict responseId check in NM

[jira] [Updated] (YARN-6968) Hardcoded absolute pathname in DockerLinuxContainerRuntime

[ https://issues.apache.org/jira/browse/YARN-6968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-6968: - Summary: Hardcoded absolute pathname in DockerLinuxContainerRuntime (was: Hard coded reference to an

[jira] [Updated] (YARN-7226) Whitelisted variables do not support delayed variable expansion

[ https://issues.apache.org/jira/browse/YARN-7226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-7226: - Attachment: YARN-7226.002.patch Updated the patch to remove the unused imports. > Whitelisted variables

[jira] [Updated] (YARN-7226) Whitelisted variables do not support delayed variable expansion

[ https://issues.apache.org/jira/browse/YARN-7226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-7226: - Attachment: YARN-7226.001.patch Attaching a patch that takes the approach described above.

[jira] [Commented] (YARN-7226) Whitelisted variables do not support delayed variable expansion

[ https://issues.apache.org/jira/browse/YARN-7226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16173232#comment-16173232 ] Jason Lowe commented on YARN-7226: -- Maybe I'm missing something, but the whitelisted variable support

[jira] [Created] (YARN-7226) Whitelisted variables do not support delayed variable expansion

Jason Lowe created YARN-7226: Summary: Whitelisted variables do not support delayed variable expansion Key: YARN-7226 URL: https://issues.apache.org/jira/browse/YARN-7226 Project: Hadoop YARN

[jira] [Commented] (YARN-6968) Hard coded reference to an absolute pathname in org.apache.hadoop.yarn.server.nodemanager.containermanager.linux.runtime.DockerLinuxContainerRuntime.launchContainer(Cont

[ https://issues.apache.org/jira/browse/YARN-6968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16172229#comment-16172229 ] Jason Lowe commented on YARN-6968: -- Any update on this? It would be nice to have Yetus stop complaining

[jira] [Commented] (YARN-4266) Allow users to enter containers as UID:GID pair instead of by username

[ https://issues.apache.org/jira/browse/YARN-4266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16172217#comment-16172217 ] Jason Lowe commented on YARN-4266: -- Thanks for updating the patch! The YarnConfigurationFields and

[jira] [Commented] (YARN-4266) Allow users to enter containers as UID:GID pair instead of by username

[ https://issues.apache.org/jira/browse/YARN-4266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16170762#comment-16170762 ] Jason Lowe commented on YARN-4266: -- Apologies for arriving late on this. Comments on the 003 patch:

[jira] [Commented] (YARN-7192) Add a pluggable StateMachine Listener that is notified of NM Container State changes

[ https://issues.apache.org/jira/browse/YARN-7192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16170141#comment-16170141 ] Jason Lowe commented on YARN-7192: -- Thanks for updating the patch! The test failure is unrelated and

[jira] [Commented] (YARN-7192) Add a pluggable StateMachine Listener that is notified of NM Container State changes

[ https://issues.apache.org/jira/browse/YARN-7192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16168606#comment-16168606 ] Jason Lowe commented on YARN-7192: -- +1 lgtm. I'd rather see the multi-listener support added up front.

[jira] [Commented] (YARN-7190) Ensure only NM classpath in 2.x gets TSv2 related hbase jars, not the user classpath

[ https://issues.apache.org/jira/browse/YARN-7190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16168272#comment-16168272 ] Jason Lowe commented on YARN-7190: -- I wasn't referring specifically to that JIRA, more to the fact that

[jira] [Commented] (YARN-7190) Ensure only NM classpath in 2.x gets TSv2 related hbase jars, not the user classpath

[ https://issues.apache.org/jira/browse/YARN-7190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16166452#comment-16166452 ] Jason Lowe commented on YARN-7190: -- Yes, many tasks probably do not need YARN jars, but some do. Oozie

[jira] [Commented] (YARN-5972) Support Pausing/Freezing of opportunistic containers

[ https://issues.apache.org/jira/browse/YARN-5972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16166368#comment-16166368 ] Jason Lowe commented on YARN-5972: -- I'm OK with this being added to trunk as separate JIRAs. The entire

[jira] [Commented] (YARN-7190) Ensure only NM classpath in 2.x gets TSv2 related hbase jars, not the user classpath

[ https://issues.apache.org/jira/browse/YARN-7190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16166359#comment-16166359 ] Jason Lowe commented on YARN-7190: -- Separate directory for these that's only pulled into the classpath

[jira] [Commented] (YARN-7192) Add a pluggable StateMachine Listener that is notified of NM Container State changes

[ https://issues.apache.org/jira/browse/YARN-7192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16166341#comment-16166341 ] Jason Lowe commented on YARN-7192: -- Took a quick look at the patch, some initial comments: Would it make

[jira] [Commented] (YARN-7190) Ensure only NM classpath in 2.x gets TSv2 related hbase jars, not the user classpath

[ https://issues.apache.org/jira/browse/YARN-7190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16166271#comment-16166271 ] Jason Lowe commented on YARN-7190: -- This could be an issue in 3.x as well. I suspect the HBase project

[jira] [Assigned] (YARN-7084) TestSchedulingMonitor#testRMStarts fails sporadically

[ https://issues.apache.org/jira/browse/YARN-7084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe reassigned YARN-7084: Assignee: Jason Lowe Affects Version/s: 2.8.2 2.9.0

[jira] [Updated] (YARN-7084) TestSchedulingMonitor#testRMStarts fails sporadically

[ https://issues.apache.org/jira/browse/YARN-7084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-7084: - Attachment: YARN-7084.001.patch Saw this fail again, and I had a bit of time to take a deeper look. The

[jira] [Commented] (YARN-6726) Fix issues with docker commands executed by container-executor

[ https://issues.apache.org/jira/browse/YARN-6726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16163702#comment-16163702 ] Jason Lowe commented on YARN-6726: -- The branch-2 patch also has the off-by-one error in it, see YARN-7014.

[jira] [Updated] (YARN-4727) Unable to override the $HADOOP_CONF_DIR env variable for container

[ https://issues.apache.org/jira/browse/YARN-4727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-4727: - Attachment: YARN-4727.002.patch Updating the patch to fix the checkstyle issue. The findbugs warning is

[jira] [Updated] (YARN-4727) Unable to override the $HADOOP_CONF_DIR env variable for container

[ https://issues.apache.org/jira/browse/YARN-4727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-4727: - Attachment: YARN-4727.001.patch Attaching a patch that changes the {{putEnvIfNotNull}} to

[jira] [Assigned] (YARN-4727) Unable to override the $HADOOP_CONF_DIR env variable for container

[ https://issues.apache.org/jira/browse/YARN-4727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe reassigned YARN-4727: Assignee: Jason Lowe Affects Version/s: 2.8.1 Target Version/s: 2.8.3, 2.7.5

[jira] [Commented] (YARN-6992) Kill application button is visible even if the application is FINISHED in RM UI

[ https://issues.apache.org/jira/browse/YARN-6992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16158986#comment-16158986 ] Jason Lowe commented on YARN-6992: -- Shouldn't this bugfix be committed to branch-3.0 as well? > Kill

[jira] [Updated] (YARN-6219) NM web server related UT fails with "NMWebapps failed to start."

[ https://issues.apache.org/jira/browse/YARN-6219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-6219: - Attachment: YARN-6219-branch-2.001.patch Attaching a patch which is just the TestNMWebServer fix from

[jira] [Resolved] (YARN-7078) TestNMWebServer fails on branch-2

[ https://issues.apache.org/jira/browse/YARN-7078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe resolved YARN-7078. -- Resolution: Duplicate > TestNMWebServer fails on branch-2 > - > >

[jira] [Commented] (YARN-7078) TestNMWebServer fails on branch-2

[ https://issues.apache.org/jira/browse/YARN-7078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16158831#comment-16158831 ] Jason Lowe commented on YARN-7078: -- This is a duplicate of YARN-6219. > TestNMWebServer fails on branch-2

[jira] [Assigned] (YARN-6219) NM web server related UT fails with "NMWebapps failed to start."

[ https://issues.apache.org/jira/browse/YARN-6219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe reassigned YARN-6219: Assignee: Jason Lowe Affects Version/s: 2.9.0 This is no longer occurring on trunk

[jira] [Commented] (YARN-7130) ATSv2 documentation changes post merge

[ https://issues.apache.org/jira/browse/YARN-7130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16158795#comment-16158795 ] Jason Lowe commented on YARN-7130: -- Shouldn't this go into branch-3.0 as well? > ATSv2 documentation

[jira] [Commented] (YARN-7140) CollectorInfo should have Public visibility

[ https://issues.apache.org/jira/browse/YARN-7140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16158796#comment-16158796 ] Jason Lowe commented on YARN-7140: -- I think this needs to go into branch-3.0 as well. > CollectorInfo

[jira] [Commented] (YARN-6930) Admins should be able to explicitly enable specific LinuxContainerRuntime in the NodeManager

[ https://issues.apache.org/jira/browse/YARN-6930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16157659#comment-16157659 ] Jason Lowe commented on YARN-6930: -- +1 for the branch-2 patch as well. The TestNMWebServer failure is

[jira] [Commented] (YARN-7149) Cross-queue preemption sometimes starves an underserved queue

[ https://issues.apache.org/jira/browse/YARN-7149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16157213#comment-16157213 ] Jason Lowe commented on YARN-7149: -- bq. after each container allocation, we can get a new UL, and because

[jira] [Commented] (YARN-7148) TestLogsCLI fails in trunk and branch-2 and javadoc error

[ https://issues.apache.org/jira/browse/YARN-7148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16155997#comment-16155997 ] Jason Lowe commented on YARN-7148: -- [~djp], this needs to go into branch-3.0 as well since trunk was

[jira] [Commented] (YARN-7164) TestAMRMClientOnRMRestart fails sporadically with bind address in use

[ https://issues.apache.org/jira/browse/YARN-7164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16155976#comment-16155976 ] Jason Lowe commented on YARN-7164: -- Thanks for the review, Kihwal! Committing this. >

[jira] [Commented] (YARN-7164) TestAMRMClientOnRMRestart fails sporadically with bind address in use

[ https://issues.apache.org/jira/browse/YARN-7164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16155946#comment-16155946 ] Jason Lowe commented on YARN-7164: -- The TestLogsCLI failure is unrelated and tracked by YARN-7148. >

[jira] [Updated] (YARN-7164) TestAMRMClientOnRMRestart fails sporadically with bind address in use

[ https://issues.apache.org/jira/browse/YARN-7164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-7164: - Affects Version/s: 3.0.0-beta1 2.9.0 Target Version/s: 2.9.0, 3.0.0-beta1,

[jira] [Updated] (YARN-7164) TestAMRMClientOnRMRestart fails sporadically with bind address in use

[ https://issues.apache.org/jira/browse/YARN-7164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-7164: - Attachment: YARN-7164.001.patch Patch that configures the scheduler address to an ephemeral port to

[jira] [Commented] (YARN-7164) TestAMRMClientOnRMRestart fails sporadically with bind address in use

[ https://issues.apache.org/jira/browse/YARN-7164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16155606#comment-16155606 ] Jason Lowe commented on YARN-7164: -- Stacktrace: {noformat}

[jira] [Created] (YARN-7164) TestAMRMClientOnRMRestart fails sporadically with bind address in use

Jason Lowe created YARN-7164: Summary: TestAMRMClientOnRMRestart fails sporadically with bind address in use Key: YARN-7164 URL: https://issues.apache.org/jira/browse/YARN-7164 Project: Hadoop YARN

[jira] [Commented] (YARN-7144) Log Aggregation controller should not swallow the exceptions when it calls closeWriter and closeReader.

[ https://issues.apache.org/jira/browse/YARN-7144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16155505#comment-16155505 ] Jason Lowe commented on YARN-7144: -- Thanks, Xuan! +1 lgtm as well. > Log Aggregation controller should

[jira] [Commented] (YARN-7149) Cross-queue preemption sometimes starves an underserved queue

[ https://issues.apache.org/jira/browse/YARN-7149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16155474#comment-16155474 ] Jason Lowe commented on YARN-7149: -- Thanks for the report and analysis, Eric! So it appears YARN-5889's

[jira] [Commented] (YARN-7136) Additional Performance Improvement for Resource Profile Feature

[ https://issues.apache.org/jira/browse/YARN-7136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16154325#comment-16154325 ] Jason Lowe commented on YARN-7136: -- Thanks for updating the patch and addressing my comments! +1 lgtm

[jira] [Commented] (YARN-7136) Additional Performance Improvement for Resource Profile Feature

[ https://issues.apache.org/jira/browse/YARN-7136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16154255#comment-16154255 ] Jason Lowe commented on YARN-7136: -- bq. Do you think is it fine according to the perf report for 3+

[jira] [Commented] (YARN-7136) Additional Performance Improvement for Resource Profile Feature

[ https://issues.apache.org/jira/browse/YARN-7136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16153762#comment-16153762 ] Jason Lowe commented on YARN-7136: -- Apologies for the delay, as I was offline during the long weekend.

[jira] [Commented] (YARN-7070) some of local cache files for yarn can't be deleted

[ https://issues.apache.org/jira/browse/YARN-7070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16153633#comment-16153633 ] Jason Lowe commented on YARN-7070: -- Those warnings are "normal" and are a result of the container being

[jira] [Commented] (YARN-7120) CapacitySchedulerPage NPE in "Aggregate scheduler counts" section

[ https://issues.apache.org/jira/browse/YARN-7120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16150757#comment-16150757 ] Jason Lowe commented on YARN-7120: -- Ah sorry, I misread the patch. We're not setting the container ID to

[jira] [Commented] (YARN-7147) ATS1.5 crash due to OOM

[ https://issues.apache.org/jira/browse/YARN-7147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16150709#comment-16150709 ] Jason Lowe commented on YARN-7147: -- Rolling leveldb doesn't make sense for an entity group caching. That

[jira] [Commented] (YARN-7136) Additional Performance Improvement for Resource Profile Feature

[ https://issues.apache.org/jira/browse/YARN-7136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16150699#comment-16150699 ] Jason Lowe commented on YARN-7136: -- So patch 005 addresses the volatile-in-a-loop issue, although I'm

[jira] [Commented] (YARN-7136) Additional Performance Improvement for Resource Profile Feature

[ https://issues.apache.org/jira/browse/YARN-7136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16150691#comment-16150691 ] Jason Lowe commented on YARN-7136: -- Sorry, comment race. My comments above were for patch 004, I'll have

[jira] [Commented] (YARN-7136) Additional Performance Improvement for Resource Profile Feature

[ https://issues.apache.org/jira/browse/YARN-7136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16150688#comment-16150688 ] Jason Lowe commented on YARN-7136: -- Thanks for updating the patch! The findbugs exclusion entry should

[jira] [Commented] (YARN-7120) CapacitySchedulerPage NPE in "Aggregate scheduler counts" section

[ https://issues.apache.org/jira/browse/YARN-7120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16150577#comment-16150577 ] Jason Lowe commented on YARN-7120: -- Thanks for the patch! If I understand the patch correctly, this won't

[jira] [Commented] (YARN-7147) ATS1.5 crash due to OOM

[ https://issues.apache.org/jira/browse/YARN-7147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16150563#comment-16150563 ] Jason Lowe commented on YARN-7147: -- Isn't this solved by changing

[jira] [Commented] (YARN-7136) Additional Performance Improvement for Resource Profile Feature

[ https://issues.apache.org/jira/browse/YARN-7136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16149144#comment-16149144 ] Jason Lowe commented on YARN-7136: -- Thanks for the patch! In the Resource equals method, is there a need

[jira] [Commented] (YARN-6930) Admins should be able to explicitly enable specific LinuxContainerRuntime in the NodeManager

[ https://issues.apache.org/jira/browse/YARN-6930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16147912#comment-16147912 ] Jason Lowe commented on YARN-6930: -- Thanks for updating the patch! +1 lgtm as well.

[jira] [Commented] (YARN-6479) TestDistributedShell.testDSShellWithoutDomainV1_5 fails

[ https://issues.apache.org/jira/browse/YARN-6479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16147402#comment-16147402 ] Jason Lowe commented on YARN-6479: -- I saw another case of this, and it fails because

[jira] [Commented] (YARN-7117) Capacity Scheduler: Support Auto Creation of Leaf Queues While Doing Queue Mapping

[ https://issues.apache.org/jira/browse/YARN-7117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16147241#comment-16147241 ] Jason Lowe commented on YARN-7117: -- bq. This is a valid concern, instead of deleting queue, how about

[jira] [Commented] (YARN-6876) Create an abstract log writer for extendability

[ https://issues.apache.org/jira/browse/YARN-6876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16146032#comment-16146032 ] Jason Lowe commented on YARN-6876: -- Previously the IOUtils.cleanup calls were passed a logger that would

[jira] [Commented] (YARN-7117) Capacity Scheduler: Support Auto Creation of Leaf Queues While Doing Queue Mapping

[ https://issues.apache.org/jira/browse/YARN-7117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16145976#comment-16145976 ] Jason Lowe commented on YARN-7117: -- bq. Adding queue with zero guaranteed resource is one possible

[jira] [Commented] (YARN-6930) Admins should be able to explicitly enable specific LinuxContainerRuntime in the NodeManager

[ https://issues.apache.org/jira/browse/YARN-6930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16145597#comment-16145597 ] Jason Lowe commented on YARN-6930: -- Thanks for updating the patch! In addition to Eric's comment, it

[jira] [Commented] (YARN-5816) TestDelegationTokenRenewer#testCancelWithMultipleAppSubmissions is still flakey

[ https://issues.apache.org/jira/browse/YARN-5816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16145419#comment-16145419 ] Jason Lowe commented on YARN-5816: -- Thanks for the patch! +1 lgtm. Committing this. >

[jira] [Commented] (YARN-7112) TestAMRMProxy is failing with invalid request

[ https://issues.apache.org/jira/browse/YARN-7112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16145343#comment-16145343 ] Jason Lowe commented on YARN-7112: -- I committed this to branch-2.8.2 as well since YARN-6640 was committed

[jira] [Commented] (YARN-7117) Capacity Scheduler: Support Auto Creation of Leaf Queues While Doing Queue Mapping

[ https://issues.apache.org/jira/browse/YARN-7117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16145335#comment-16145335 ] Jason Lowe commented on YARN-7117: -- The main issue I see is that it could end up creating what previously

[jira] [Commented] (YARN-7083) Log aggregation deletes/renames while file is open

[ https://issues.apache.org/jira/browse/YARN-7083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16144420#comment-16144420 ] Jason Lowe commented on YARN-7083: -- I'm OK with fixing in 2.8.x and filing a followup JIRA. If that

[jira] [Commented] (YARN-6876) Create an abstract log writer for extendability

[ https://issues.apache.org/jira/browse/YARN-6876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16144402#comment-16144402 ] Jason Lowe commented on YARN-6876: -- Sorry for the late comment, but I was just looking at the code in

[jira] [Resolved] (YARN-7110) NodeManager always crash for spark shuffle service out of memory

[ https://issues.apache.org/jira/browse/YARN-7110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe resolved YARN-7110. -- Resolution: Duplicate > NodeManager always crash for spark shuffle service out of memory >

[jira] [Commented] (YARN-7110) NodeManager always crash for spark shuffle service out of memory

[ https://issues.apache.org/jira/browse/YARN-7110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16144360#comment-16144360 ] Jason Lowe commented on YARN-7110: -- Looks like Varun was driving that effort but may be busy with other

<    2   3   4   5   6   7   8   9   10   11   >