[jira] [Assigned] (YARN-1948) Expose utility methods in Apps.java publically

[ https://issues.apache.org/jira/browse/YARN-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel reassigned YARN-1948: --- Assignee: (was: nijel) > Expose utility methods in Apps.java publically >

[jira] [Assigned] (YARN-4303) Confusing help message if AM logs cant be retrieved via yarn logs command

[ https://issues.apache.org/jira/browse/YARN-4303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel reassigned YARN-4303: --- Assignee: (was: nijel) > Confusing help message if AM logs cant be retrieved via yarn logs command >

[jira] [Assigned] (YARN-4110) RMappImpl and RmAppAttemptImpl should override hashcode() & equals()

[ https://issues.apache.org/jira/browse/YARN-4110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel reassigned YARN-4110: --- Assignee: (was: nijel) > RMappImpl and RmAppAttemptImpl should override hashcode() & equals() >

[jira] [Assigned] (YARN-4249) Many options in "yarn application" command is not documented

[ https://issues.apache.org/jira/browse/YARN-4249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel reassigned YARN-4249: --- Assignee: (was: nijel) > Many options in "yarn application" command is not documented >

[jira] [Commented] (YARN-2934) Improve handling of container's stderr

[ https://issues.apache.org/jira/browse/YARN-2934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14991374#comment-14991374 ] nijel commented on YARN-2934: - thanks [~Naganarasimha] for the patch Few minor comments/doubts 1. {code}

[jira] [Commented] (YARN-4246) NPE while listing app attempt

[ https://issues.apache.org/jira/browse/YARN-4246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14978231#comment-14978231 ] nijel commented on YARN-4246: - thanks [~varun_saxena] and [~rohithsharma] for the review and commit. > NPE

[jira] [Assigned] (YARN-4303) Confusing help message if AM logs cant be retrieved via yarn logs command

[ https://issues.apache.org/jira/browse/YARN-4303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel reassigned YARN-4303: --- Assignee: nijel > Confusing help message if AM logs cant be retrieved via yarn logs command >

[jira] [Updated] (YARN-4246) NPE while listing app attempt

[ https://issues.apache.org/jira/browse/YARN-4246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel updated YARN-4246: Attachment: YARN-4246_2.patch Thanks [~steve_l] for pointing out the mistake. Updated the patch with the comment

[jira] [Commented] (YARN-4246) NPE while listing app attempt

[ https://issues.apache.org/jira/browse/YARN-4246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14955054#comment-14955054 ] nijel commented on YARN-4246: - bq. -1 yarn tests as per my analysis test fails are not related to this patch.

[jira] [Updated] (YARN-4246) NPE while listing app attempt

[ https://issues.apache.org/jira/browse/YARN-4246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel updated YARN-4246: Attachment: YARN-4246_1.patch patch. Please review > NPE while listing app attempt > -

[jira] [Updated] (YARN-4249) Many options in "yarn application" command is not documented

[ https://issues.apache.org/jira/browse/YARN-4249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel updated YARN-4249: Summary: Many options in "yarn application" command is not documented (was: Many options in "yarn application"

[jira] [Created] (YARN-4249) Many options in "yarn application" command is not documents

nijel created YARN-4249: --- Summary: Many options in "yarn application" command is not documents Key: YARN-4249 URL: https://issues.apache.org/jira/browse/YARN-4249 Project: Hadoop YARN Issue Type: Bug

[jira] [Commented] (YARN-4246) NPE while listing app attempt

[ https://issues.apache.org/jira/browse/YARN-4246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14950215#comment-14950215 ] nijel commented on YARN-4246: - thanks [~varun_saxena] for reporting the same issue is there in

[jira] [Updated] (YARN-4205) Add a service for monitoring application life time out

[ https://issues.apache.org/jira/browse/YARN-4205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel updated YARN-4205: Attachment: YARN-4205_03.patch > Add a service for monitoring application life time out >

[jira] [Commented] (YARN-4205) Add a service for monitoring application life time out

[ https://issues.apache.org/jira/browse/YARN-4205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14933513#comment-14933513 ] nijel commented on YARN-4205: - Thanks [~rohithsharma] for the comments Updated the patch. > Add a service for

[jira] [Commented] (YARN-4111) Killed application diagnostics message should be set rather having static mesage

[ https://issues.apache.org/jira/browse/YARN-4111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14909120#comment-14909120 ] nijel commented on YARN-4111: - Thanks [~rohithsharma] and [~sunilg] for the comments If we add the new

[jira] [Commented] (YARN-4205) Add a service for monitoring application life time out

[ https://issues.apache.org/jira/browse/YARN-4205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14909121#comment-14909121 ] nijel commented on YARN-4205: - Test cases failing as "method not found" for the method added in api project.

[jira] [Updated] (YARN-4205) Add a service for monitoring application life time out

[ https://issues.apache.org/jira/browse/YARN-4205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel updated YARN-4205: Description: This JIRA intend to provide a lifetime monitor service. The service will monitor the applications

[jira] [Commented] (YARN-4205) Add a service for monitoring application life time out

[ https://issues.apache.org/jira/browse/YARN-4205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14908204#comment-14908204 ] nijel commented on YARN-4205: - Thanks [~leftnoteasy] for the comments Sorry for the small mistakes Updated the

[jira] [Updated] (YARN-4205) Add a service for monitoring application life time out

[ https://issues.apache.org/jira/browse/YARN-4205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel updated YARN-4205: Attachment: YARN-4205_02.patch > Add a service for monitoring application life time out >

[jira] [Created] (YARN-4206) Add life time value in Application report and web UI

nijel created YARN-4206: --- Summary: Add life time value in Application report and web UI Key: YARN-4206 URL: https://issues.apache.org/jira/browse/YARN-4206 Project: Hadoop YARN Issue Type: Sub-task

[jira] [Updated] (YARN-4205) Add a service for monitoring application life time out

[ https://issues.apache.org/jira/browse/YARN-4205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel updated YARN-4205: Attachment: YARN-4205_01.patch Uploading initial version. > Add a service for monitoring application life time out

[jira] [Commented] (YARN-3813) Support Application timeout feature in YARN.

[ https://issues.apache.org/jira/browse/YARN-3813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14904688#comment-14904688 ] nijel commented on YARN-3813: - thanks [~rohithsharma] and [~sunilg] for the comments Updated patch with the

[jira] [Updated] (YARN-3813) Support Application timeout feature in YARN.

[ https://issues.apache.org/jira/browse/YARN-3813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel updated YARN-3813: Attachment: 0002_YARN-3813.patch > Support Application timeout feature in YARN. >

[jira] [Created] (YARN-4192) Add YARN metric logging periodically to a seperate file

nijel created YARN-4192: --- Summary: Add YARN metric logging periodically to a seperate file Key: YARN-4192 URL: https://issues.apache.org/jira/browse/YARN-4192 Project: Hadoop YARN Issue Type:

[jira] [Commented] (YARN-4135) Improve the assertion message in MockRM while failing after waiting for the state.

[ https://issues.apache.org/jira/browse/YARN-4135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14877467#comment-14877467 ] nijel commented on YARN-4135: - thanks [~rohithsharma] and [~adhoot] > Improve the assertion message in MockRM

[jira] [Commented] (YARN-4135) Improve the assertion message in MockRM while failing after waiting for the state.

[ https://issues.apache.org/jira/browse/YARN-4135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14747106#comment-14747106 ] nijel commented on YARN-4135: - bq.-1 yarn tests 54m 15s Tests failed in

[jira] [Updated] (YARN-4135) Improve the assertion message in MockRM while failing after waiting for the state.

[ https://issues.apache.org/jira/browse/YARN-4135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel updated YARN-4135: Attachment: YARN-4135_2.patch > Improve the assertion message in MockRM while failing after waiting for the >

[jira] [Commented] (YARN-4135) Improve the assertion message in MockRM while failing after waiting for the state.

[ https://issues.apache.org/jira/browse/YARN-4135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14746870#comment-14746870 ] nijel commented on YARN-4135: - thanks [~adhoot] for the comment Updated the patch. Please review > Improve the

[jira] [Commented] (YARN-4111) Killed application diagnostics message should be set rather having static mesage

[ https://issues.apache.org/jira/browse/YARN-4111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14740313#comment-14740313 ] nijel commented on YARN-4111: - Thanks [~sunilg] for the comments bq. RMAppKilledAttemptEvent is used for both

[jira] [Updated] (YARN-4111) Killed application diagnostics message should be set rather having static mesage

[ https://issues.apache.org/jira/browse/YARN-4111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel updated YARN-4111: Attachment: YARN-4111_3.patch Updated javadoc comments > Killed application diagnostics message should be set

[jira] [Created] (YARN-4146) getServiceState command is missing in yarnadmin command help

nijel created YARN-4146: --- Summary: getServiceState command is missing in yarnadmin command help Key: YARN-4146 URL: https://issues.apache.org/jira/browse/YARN-4146 Project: Hadoop YARN Issue Type:

[jira] [Updated] (YARN-4111) Killed application diagnostics message should be set rather having static mesage

[ https://issues.apache.org/jira/browse/YARN-4111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel updated YARN-4111: Attachment: YARN-4111_4.patch updated the javadoc for missing "." Test skip is not related to patch > Killed

[jira] [Resolved] (YARN-4146) getServiceState command is missing in yarnadmin command help

[ https://issues.apache.org/jira/browse/YARN-4146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel resolved YARN-4146. - Resolution: Invalid Sorry. My env was in non HA mode ! > getServiceState command is missing in yarnadmin

[jira] [Assigned] (YARN-4146) getServiceState command is missing in yarnadmin command help

[ https://issues.apache.org/jira/browse/YARN-4146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel reassigned YARN-4146: --- Assignee: (was: nijel) > getServiceState command is missing in yarnadmin command help >

[jira] [Updated] (YARN-4111) Killed application diagnostics message should be set rather having static mesage

[ https://issues.apache.org/jira/browse/YARN-4111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel updated YARN-4111: Attachment: YARN-4111_2.patch Updated the patch with checkstyle fix. The test failures are not related. Tried

[jira] [Updated] (YARN-4135) Improve the assertion message in MockRM while failing after waiting for the state.

[ https://issues.apache.org/jira/browse/YARN-4135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel updated YARN-4135: Attachment: YARN-4135_1.patch attached the patch please review > Improve the assertion message in MockRM while

[jira] [Created] (YARN-4135) Improve the assertion message in MockRM while failing after waiting for the state.

nijel created YARN-4135: --- Summary: Improve the assertion message in MockRM while failing after waiting for the state. Key: YARN-4135 URL: https://issues.apache.org/jira/browse/YARN-4135 Project: Hadoop YARN

[jira] [Updated] (YARN-4111) Killed application diagnostics message should be set rather having static mesage

[ https://issues.apache.org/jira/browse/YARN-4111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel updated YARN-4111: Attachment: YARN-4111_1.patch Attaching the patch Please review > Killed application diagnostics message should be

[jira] [Commented] (YARN-3771) "final" behavior is not honored for YarnConfiguration.DEFAULT_YARN_APPLICATION_CLASSPATH since it is a String[]

[ https://issues.apache.org/jira/browse/YARN-3771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14734602#comment-14734602 ] nijel commented on YARN-3771: - hi all, any comment on this change ? > "final" behavior is not honored for >

[jira] [Updated] (YARN-4110) RMappImpl and RmAppAttemptImpl should override hashcode() & equals()

[ https://issues.apache.org/jira/browse/YARN-4110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel updated YARN-4110: Attachment: YARN-4110_1.patch Attached the patch Please review > RMappImpl and RmAppAttemptImpl should override

[jira] [Commented] (YARN-4110) RMappImpl and RmAppAttemptImpl should override hashcode() & equals()

[ https://issues.apache.org/jira/browse/YARN-4110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14729078#comment-14729078 ] nijel commented on YARN-4110: - Sorry attached wrong patch so deleting the same > RMappImpl and

[jira] [Updated] (YARN-4110) RMappImpl and RmAppAttemptImpl should override hashcode() & equals()

[ https://issues.apache.org/jira/browse/YARN-4110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel updated YARN-4110: Attachment: (was: 01-YARN-4110.patch) > RMappImpl and RmAppAttemptImpl should override hashcode() & equals() >

[jira] [Assigned] (YARN-3813) Support Application timeout feature in YARN.

[ https://issues.apache.org/jira/browse/YARN-3813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel reassigned YARN-3813: --- Assignee: nijel > Support Application timeout feature in YARN. >

[jira] [Updated] (YARN-3813) Support Application timeout feature in YARN.

[ https://issues.apache.org/jira/browse/YARN-3813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel updated YARN-3813: Attachment: 0001-YARN-3813.patch Sorry for the long delay.. Adding an initial patch. The action on timeout is

[jira] [Commented] (YARN-3813) Support Application timeout feature in YARN.

[ https://issues.apache.org/jira/browse/YARN-3813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14728898#comment-14728898 ] nijel commented on YARN-3813: - This patch will address the initial issue. But this will kill the application

[jira] [Updated] (YARN-4110) RMappImpl and RmAppAttemptImpl should override hashcode() & equals()

[ https://issues.apache.org/jira/browse/YARN-4110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel updated YARN-4110: Attachment: 01-YARN-4110.patch Thanks [~rohithsharma] for reporting Attached the patch > RMappImpl and

[jira] [Assigned] (YARN-3869) Add app name to RM audit log

[ https://issues.apache.org/jira/browse/YARN-3869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel reassigned YARN-3869: --- Assignee: (was: nijel) Keeping it open for further comments and opinion > Add app name to RM audit log >

[jira] [Commented] (YARN-3813) Support Application timeout feature in YARN.

[ https://issues.apache.org/jira/browse/YARN-3813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14619984#comment-14619984 ] nijel commented on YARN-3813: - Thanks [~sunilg] and [~devaraj.k] for the comments bq.How

[jira] [Commented] (YARN-3813) Support Application timeout feature in YARN.

[ https://issues.apache.org/jira/browse/YARN-3813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14618432#comment-14618432 ] nijel commented on YARN-3813: - Attached initial draft for work details. Please share your

[jira] [Updated] (YARN-3813) Support Application timeout feature in YARN.

[ https://issues.apache.org/jira/browse/YARN-3813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel updated YARN-3813: Attachment: (was: YARN Application Timeout -3.pdf) Support Application timeout feature in YARN.

[jira] [Updated] (YARN-3813) Support Application timeout feature in YARN.

[ https://issues.apache.org/jira/browse/YARN-3813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel updated YARN-3813: Attachment: YARN Application Timeout -3.pdf Support Application timeout feature in YARN.

[jira] [Updated] (YARN-3813) Support Application timeout feature in YARN.

[ https://issues.apache.org/jira/browse/YARN-3813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel updated YARN-3813: Attachment: YARN Application Timeout .pdf Support Application timeout feature in YARN.

[jira] [Commented] (YARN-3869) Add app name to RM audit log

[ https://issues.apache.org/jira/browse/YARN-3869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14616363#comment-14616363 ] nijel commented on YARN-3869: - In Web it is shown as truncate. But if the names are similar,

[jira] [Commented] (YARN-3869) Add app name to RM audit log

[ https://issues.apache.org/jira/browse/YARN-3869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14616282#comment-14616282 ] nijel commented on YARN-3869: - hi i started working on this. One observation is in some cases

[jira] [Assigned] (YARN-2953) TestWorkPreservingRMRestart fails on trunk

[ https://issues.apache.org/jira/browse/YARN-2953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel reassigned YARN-2953: --- Assignee: nijel TestWorkPreservingRMRestart fails on trunk --

[jira] [Commented] (YARN-2953) TestWorkPreservingRMRestart fails on trunk

[ https://issues.apache.org/jira/browse/YARN-2953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14609771#comment-14609771 ] nijel commented on YARN-2953: - Hi [~rohithsharma] This test cases is passing in recent code and

[jira] [Updated] (YARN-3830) AbstractYarnScheduler.createReleaseCache may try to clean a null attempt

[ https://issues.apache.org/jira/browse/YARN-3830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel updated YARN-3830: Attachment: YARN-3830_4.patch Thanks [~devaraj.k] for the suggestion Updated patch with test case Please review

[jira] [Commented] (YARN-3869) Add app name to RM audit log

[ https://issues.apache.org/jira/browse/YARN-3869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14609812#comment-14609812 ] nijel commented on YARN-3869: - hi [~roji] i would like to work on this improvement. Please let

[jira] [Assigned] (YARN-3869) Add app name to RM audit log

[ https://issues.apache.org/jira/browse/YARN-3869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel reassigned YARN-3869: --- Assignee: nijel Add app name to RM audit log Key: YARN-3869

[jira] [Commented] (YARN-3830) AbstractYarnScheduler.createReleaseCache may try to clean a null attempt

[ https://issues.apache.org/jira/browse/YARN-3830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14611374#comment-14611374 ] nijel commented on YARN-3830: - Thanks [~devaraj.k] for the review and committing the patch.

[jira] [Commented] (YARN-3830) AbstractYarnScheduler.createReleaseCache may try to clean a null attempt

[ https://issues.apache.org/jira/browse/YARN-3830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14608093#comment-14608093 ] nijel commented on YARN-3830: - Thanks [~devaraj.k] for the review Test case looks bit tricky :)

[jira] [Updated] (YARN-3830) AbstractYarnScheduler.createReleaseCache may try to clean a null attempt

[ https://issues.apache.org/jira/browse/YARN-3830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel updated YARN-3830: Attachment: YARN-3830_2.patch Thanks [~xgong] for the comment. Updated the patch Please review

[jira] [Updated] (YARN-3830) AbstractYarnScheduler.createReleaseCache may try to clean a null attempt

[ https://issues.apache.org/jira/browse/YARN-3830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel updated YARN-3830: Attachment: YARN-3830_3.patch Sorry for the small mistake Line limit is corrected Test fail is not related to this

[jira] [Created] (YARN-3830) AbstractYarnScheduler.createReleaseCache may try to clean a null attempt

nijel created YARN-3830: --- Summary: AbstractYarnScheduler.createReleaseCache may try to clean a null attempt Key: YARN-3830 URL: https://issues.apache.org/jira/browse/YARN-3830 Project: Hadoop YARN

[jira] [Updated] (YARN-3830) AbstractYarnScheduler.createReleaseCache may try to clean a null attempt

[ https://issues.apache.org/jira/browse/YARN-3830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel updated YARN-3830: Attachment: YARN-3830_1.patch Updated the patch. Please review AbstractYarnScheduler.createReleaseCache may try to

[jira] [Created] (YARN-3813) Support Application timeout feature in YARN.

nijel created YARN-3813: --- Summary: Support Application timeout feature in YARN. Key: YARN-3813 URL: https://issues.apache.org/jira/browse/YARN-3813 Project: Hadoop YARN Issue Type: New Feature

[jira] [Commented] (YARN-1948) Expose utility methods in Apps.java publically

[ https://issues.apache.org/jira/browse/YARN-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14589782#comment-14589782 ] nijel commented on YARN-1948: - thanks [~vinodkv] for the comment I am thinking of changing both

[jira] [Updated] (YARN-1948) Expose utility methods in Apps.java publically

[ https://issues.apache.org/jira/browse/YARN-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel updated YARN-1948: Attachment: YARN-1948-1.patch Attached the file with modification Please review Expose utility methods in

[jira] [Created] (YARN-3796) Support User level Quota for space and Name (count)

nijel created YARN-3796: --- Summary: Support User level Quota for space and Name (count) Key: YARN-3796 URL: https://issues.apache.org/jira/browse/YARN-3796 Project: Hadoop YARN Issue Type: New Feature

[jira] [Moved] (YARN-3771) final behavior is not honored for YarnConfiguration.DEFAULT_YARN_APPLICATION_CLASSPATH since it is a String[]

[ https://issues.apache.org/jira/browse/YARN-3771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel moved HDFS-8526 to YARN-3771: --- Key: YARN-3771 (was: HDFS-8526) Project: Hadoop YARN (was: Hadoop HDFS) final

[jira] [Updated] (YARN-3771) final behavior is not honored for YarnConfiguration.DEFAULT_YARN_APPLICATION_CLASSPATH since it is a String[]

[ https://issues.apache.org/jira/browse/YARN-3771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel updated YARN-3771: Attachment: 0001-YARN-3771.patch Attached the patch. Please review final behavior is not honored for

[jira] [Assigned] (YARN-3693) Duplicate parameters on service start for NM and RM

[ https://issues.apache.org/jira/browse/YARN-3693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel reassigned YARN-3693: --- Assignee: nijel Duplicate parameters on service start for NM and RM

[jira] [Assigned] (YARN-1948) Expose utility methods in Apps.java publically

[ https://issues.apache.org/jira/browse/YARN-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel reassigned YARN-1948: --- Assignee: nijel Expose utility methods in Apps.java publically

[jira] [Commented] (YARN-3639) It takes too long time for RM to recover all apps if the original active RM and namenode is deployed on the same node.

[ https://issues.apache.org/jira/browse/YARN-3639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14541697#comment-14541697 ] nijel commented on YARN-3639: - hi [~xinxianyin] Thanks for reporting this issue. Can you attach

[jira] [Created] (YARN-3629) NodeID is always printed as null in node manager initialization log.

nijel created YARN-3629: --- Summary: NodeID is always printed as null in node manager initialization log. Key: YARN-3629 URL: https://issues.apache.org/jira/browse/YARN-3629 Project: Hadoop YARN Issue

[jira] [Commented] (YARN-3629) NodeID is always printed as null in node manager initialization log.

[ https://issues.apache.org/jira/browse/YARN-3629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14539495#comment-14539495 ] nijel commented on YARN-3629: - Moving the logs message is bit tricky since it logs some

[jira] [Updated] (YARN-3629) NodeID is always printed as null in node manager initialization log.

[ https://issues.apache.org/jira/browse/YARN-3629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel updated YARN-3629: Attachment: YARN-3629-1.patch Please review NodeID is always printed as null in node manager initialization log.

[jira] [Commented] (YARN-3629) NodeID is always printed as null in node manager initialization log.

[ https://issues.apache.org/jira/browse/YARN-3629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14541225#comment-14541225 ] nijel commented on YARN-3629: - Thanks [~devaraj.k] for the reviewing and committing the patch

[jira] [Commented] (YARN-3613) TestContainerManagerSecurity should init and start Yarn cluster in setup instead of individual methods

[ https://issues.apache.org/jira/browse/YARN-3613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14541223#comment-14541223 ] nijel commented on YARN-3613: - Thanks [~kasha] for reviewing and committing the patch

[jira] [Commented] (YARN-3629) NodeID is always printed as null in node manager initialization log.

[ https://issues.apache.org/jira/browse/YARN-3629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14539788#comment-14539788 ] nijel commented on YARN-3629: - bq.-1 tests included This is a log message change. So tests

[jira] [Commented] (YARN-3614) FileSystemRMStateStore throw exception when failed to remove application, that cause resourcemanager to crash

[ https://issues.apache.org/jira/browse/YARN-3614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14541306#comment-14541306 ] nijel commented on YARN-3614: - One possible cause is discussed in YARN-868 Can you try the

[jira] [Commented] (YARN-3614) FileSystemRMStateStore throw exception when failed to remove application, that cause resourcemanager to crash

[ https://issues.apache.org/jira/browse/YARN-3614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14537837#comment-14537837 ] nijel commented on YARN-3614: - hi @lachisis bq.when standby resourcemanager try to

[jira] [Updated] (YARN-3613) TestContainerManagerSecurity should init and start Yarn cluster in setup instead of individual methods

[ https://issues.apache.org/jira/browse/YARN-3613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel updated YARN-3613: Attachment: YARN-3613-1.patch Please review the patch. Removed 2 unused imports. Test time reduced from ~130 to ~80

[jira] [Commented] (YARN-3613) TestContainerManagerSecurity should init and start Yarn cluster in setup instead of individual methods

[ https://issues.apache.org/jira/browse/YARN-3613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14537514#comment-14537514 ] nijel commented on YARN-3613: - i will update the patch. TestContainerManagerSecurity should

[jira] [Assigned] (YARN-3613) TestContainerManagerSecurity should init and start Yarn cluster in setup instead of individual methods

[ https://issues.apache.org/jira/browse/YARN-3613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel reassigned YARN-3613: --- Assignee: nijel TestContainerManagerSecurity should init and start Yarn cluster in setup instead of

[jira] [Updated] (YARN-3018) Unify the default value for yarn.scheduler.capacity.node-locality-delay in code and default xml file

[ https://issues.apache.org/jira/browse/YARN-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel updated YARN-3018: Attachment: YARN-3018-5.patch Thanks [~vinodkv]. I completely missed this JIRA. Updated the patch to keep the value

[jira] [Updated] (YARN-3584) [Log mesage correction] : MIssing space in Diagnostics message

[ https://issues.apache.org/jira/browse/YARN-3584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel updated YARN-3584: Attachment: YARN-3584-2.patch Thanks [~jianhe] Updated patch to fix the comment. [Log mesage correction] : MIssing

[jira] [Commented] (YARN-3584) [Log mesage correction] : MIssing space in Diagnostics message

[ https://issues.apache.org/jira/browse/YARN-3584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14530149#comment-14530149 ] nijel commented on YARN-3584: - Test failures are not related to this patch Checkstyle is

[jira] [Updated] (YARN-3018) Unify the default value for yarn.scheduler.capacity.node-locality-delay in code and default xml file

[ https://issues.apache.org/jira/browse/YARN-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel updated YARN-3018: Attachment: YARN-3018-4.patch Thanks [~jianhe] for the comment Agree with you. Updated the patch with the changes

[jira] [Updated] (YARN-3271) FairScheduler: Move tests related to max-runnable-apps from TestFairScheduler to TestAppRunnability

[ https://issues.apache.org/jira/browse/YARN-3271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel updated YARN-3271: Attachment: YARN-3271.4.patch Thanks [~kasha] for the comments bq.tearDown need not explicitly stop the scheduler.

[jira] [Commented] (YARN-3018) Unify the default value for yarn.scheduler.capacity.node-locality-delay in code and default xml file

[ https://issues.apache.org/jira/browse/YARN-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14530699#comment-14530699 ] nijel commented on YARN-3018: - The test failure can be solved by changing the following lines

[jira] [Created] (YARN-3584) [Log mesage correction] : MIssing space in Diagnostics message

nijel created YARN-3584: --- Summary: [Log mesage correction] : MIssing space in Diagnostics message Key: YARN-3584 URL: https://issues.apache.org/jira/browse/YARN-3584 Project: Hadoop YARN Issue Type:

[jira] [Updated] (YARN-3584) [Log mesage correction] : MIssing space in Diagnostics message

[ https://issues.apache.org/jira/browse/YARN-3584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel updated YARN-3584: Attachment: YARN-3584-1.patch Attached the change. Please review [Log mesage correction] : MIssing space in

[jira] [Updated] (YARN-3584) [Log mesage correction] : MIssing space in Diagnostics message

[ https://issues.apache.org/jira/browse/YARN-3584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel updated YARN-3584: Attachment: YARN-3584-1.patch updated patch [Log mesage correction] : MIssing space in Diagnostics message

[jira] [Updated] (YARN-3584) [Log mesage correction] : MIssing space in Diagnostics message

[ https://issues.apache.org/jira/browse/YARN-3584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel updated YARN-3584: Attachment: (was: YARN-3584-1.patch) [Log mesage correction] : MIssing space in Diagnostics message

[jira] [Updated] (YARN-3018) Unify the default value for yarn.scheduler.capacity.node-locality-delay in code and default xml file

[ https://issues.apache.org/jira/browse/YARN-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel updated YARN-3018: Attachment: YARN-3018-1.patch Unify the default value for yarn.scheduler.capacity.node-locality-delay in code and

[jira] [Commented] (YARN-3018) Unify the default value for yarn.scheduler.capacity.node-locality-delay in code and default xml file

[ https://issues.apache.org/jira/browse/YARN-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14526307#comment-14526307 ] nijel commented on YARN-3018: - Thanks [~leftnoteasy] Uploaded the patch Unify the default

[jira] [Updated] (YARN-3018) Unify the default value for yarn.scheduler.capacity.node-locality-delay in code and default xml file

[ https://issues.apache.org/jira/browse/YARN-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel updated YARN-3018: Attachment: YARN-3018-2.patch Updated the patch to remove the white spaces Unify the default value for

[jira] [Updated] (YARN-3018) Unify the default value for yarn.scheduler.capacity.node-locality-delay in code and default xml file

[ https://issues.apache.org/jira/browse/YARN-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel updated YARN-3018: Attachment: YARN-3018-3.patch Re trigger the CIS. Patch was wrongly generated sorry for the noise Unify the

  1   2   >