[jira] [Commented] (YARN-1041) Protocol changes for RM to bind and notify a restarted AM of existing containers

[ https://issues.apache.org/jira/browse/YARN-1041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13865223#comment-13865223 ] Steve Loughran commented on YARN-1041: -- Looks good as an API for an AM to work with #

[jira] [Moved] (YARN-1572) Lower chance to hit NPE in allocateNodeLocal

[ https://issues.apache.org/jira/browse/YARN-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G moved HDFS-5729 to YARN-1572: - Key: YARN-1572 (was: HDFS-5729) Project: Hadoop YARN

[jira] [Commented] (YARN-1409) NonAggregatingLogHandler can throw RejectedExecutionException

[ https://issues.apache.org/jira/browse/YARN-1409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13865310#comment-13865310 ] Hudson commented on YARN-1409: -- SUCCESS: Integrated in Hadoop-Yarn-trunk #446 (See

[jira] [Commented] (YARN-1482) WebApplicationProxy should be always-on w.r.t HA even if it is embedded in the RM

[ https://issues.apache.org/jira/browse/YARN-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13865311#comment-13865311 ] Hudson commented on YARN-1482: -- SUCCESS: Integrated in Hadoop-Yarn-trunk #446 (See

[jira] [Commented] (YARN-1293) TestContainerLaunch.testInvalidEnvSyntaxDiagnostics fails on trunk

[ https://issues.apache.org/jira/browse/YARN-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13865312#comment-13865312 ] Hudson commented on YARN-1293: -- SUCCESS: Integrated in Hadoop-Yarn-trunk #446 (See

[jira] [Commented] (YARN-1409) NonAggregatingLogHandler can throw RejectedExecutionException

[ https://issues.apache.org/jira/browse/YARN-1409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13865429#comment-13865429 ] Hudson commented on YARN-1409: -- SUCCESS: Integrated in Hadoop-Hdfs-trunk #1638 (See

[jira] [Commented] (YARN-1482) WebApplicationProxy should be always-on w.r.t HA even if it is embedded in the RM

[ https://issues.apache.org/jira/browse/YARN-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13865430#comment-13865430 ] Hudson commented on YARN-1482: -- SUCCESS: Integrated in Hadoop-Hdfs-trunk #1638 (See

[jira] [Commented] (YARN-1568) Rename clusterid to clusterId in ActiveRMInfoProto

[ https://issues.apache.org/jira/browse/YARN-1568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13865434#comment-13865434 ] Hudson commented on YARN-1568: -- SUCCESS: Integrated in Hadoop-Hdfs-trunk #1638 (See

[jira] [Commented] (YARN-1293) TestContainerLaunch.testInvalidEnvSyntaxDiagnostics fails on trunk

[ https://issues.apache.org/jira/browse/YARN-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13865431#comment-13865431 ] Hudson commented on YARN-1293: -- SUCCESS: Integrated in Hadoop-Hdfs-trunk #1638 (See

[jira] [Commented] (YARN-1293) TestContainerLaunch.testInvalidEnvSyntaxDiagnostics fails on trunk

[ https://issues.apache.org/jira/browse/YARN-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13865501#comment-13865501 ] Hudson commented on YARN-1293: -- SUCCESS: Integrated in Hadoop-Mapreduce-trunk #1663 (See

[jira] [Commented] (YARN-1568) Rename clusterid to clusterId in ActiveRMInfoProto

[ https://issues.apache.org/jira/browse/YARN-1568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13865504#comment-13865504 ] Hudson commented on YARN-1568: -- SUCCESS: Integrated in Hadoop-Mapreduce-trunk #1663 (See

[jira] [Commented] (YARN-1482) WebApplicationProxy should be always-on w.r.t HA even if it is embedded in the RM

[ https://issues.apache.org/jira/browse/YARN-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13865500#comment-13865500 ] Hudson commented on YARN-1482: -- SUCCESS: Integrated in Hadoop-Mapreduce-trunk #1663 (See

[jira] [Commented] (YARN-1409) NonAggregatingLogHandler can throw RejectedExecutionException

[ https://issues.apache.org/jira/browse/YARN-1409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13865499#comment-13865499 ] Hudson commented on YARN-1409: -- SUCCESS: Integrated in Hadoop-Mapreduce-trunk #1663 (See

[jira] [Commented] (YARN-888) clean up POM dependencies

[ https://issues.apache.org/jira/browse/YARN-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13865556#comment-13865556 ] Karthik Kambatla commented on YARN-888: --- Looks good to me. With the patch applied,

[jira] [Commented] (YARN-888) clean up POM dependencies

[ https://issues.apache.org/jira/browse/YARN-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13865564#comment-13865564 ] Karthik Kambatla commented on YARN-888: --- Actually, the test failures are related.

[jira] [Updated] (YARN-888) clean up POM dependencies

[ https://issues.apache.org/jira/browse/YARN-888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-888: -- Attachment: yarn-888-2.patch Changing the jersey test dependency from core to grizzly2 in NM

[jira] [Commented] (YARN-1463) Tests should avoid starting http-server where possible or creates spnego keytab/principals

[ https://issues.apache.org/jira/browse/YARN-1463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13865623#comment-13865623 ] Jason Lowe commented on YARN-1463: -- We run with security enabled but without SPNEGO on our

[jira] [Commented] (YARN-888) clean up POM dependencies

[ https://issues.apache.org/jira/browse/YARN-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13865674#comment-13865674 ] Karthik Kambatla commented on YARN-888: --- Ran tests in unmanaged-am-launcher locally

[jira] [Resolved] (YARN-1390) Provide a way to capture source of an application to be queried through REST or Java Client APIs

[ https://issues.apache.org/jira/browse/YARN-1390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla resolved YARN-1390. Resolution: Duplicate From the progress on YARN-1399, it doesn't look like there will be

[jira] [Commented] (YARN-1399) Allow users to annotate an application with multiple tags

[ https://issues.apache.org/jira/browse/YARN-1399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13865691#comment-13865691 ] Karthik Kambatla commented on YARN-1399: bq. Adding a field to

[jira] [Assigned] (YARN-1003) Add a maxContainersPerNode config to the Fair Scheduler

[ https://issues.apache.org/jira/browse/YARN-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla reassigned YARN-1003: -- Assignee: (was: Karthik Kambatla) Add a maxContainersPerNode config to the Fair

[jira] [Assigned] (YARN-1015) FS should watch resource utilization of containers and allocate speculative containers if appropriate

[ https://issues.apache.org/jira/browse/YARN-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla reassigned YARN-1015: -- Assignee: (was: Karthik Kambatla) FS should watch resource utilization of

[jira] [Created] (YARN-1574) When RM transit from Active to Standby, the same eventDispatcher should not be registered more than once

Xuan Gong created YARN-1574: --- Summary: When RM transit from Active to Standby, the same eventDispatcher should not be registered more than once Key: YARN-1574 URL: https://issues.apache.org/jira/browse/YARN-1574

[jira] [Commented] (YARN-415) Capture memory utilization at the app-level for chargeback

[ https://issues.apache.org/jira/browse/YARN-415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13865739#comment-13865739 ] Kendall Thrapp commented on YARN-415: - Thanks Andrey for all your work on this! I'm

[jira] [Updated] (YARN-1567) In Fair Scheduler, allow empty leaf queues to become parent queues on allocation file reload

[ https://issues.apache.org/jira/browse/YARN-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-1567: - Attachment: YARN-1567.patch In Fair Scheduler, allow empty leaf queues to become parent queues on

[jira] [Updated] (YARN-1399) Allow users to annotate an application with multiple tags

[ https://issues.apache.org/jira/browse/YARN-1399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-1399: -- Assignee: (was: Zhijie Shen) Mark the ticket Unassigned as more than one may work on it. Allow

[jira] [Commented] (YARN-1574) When RM transit from Active to Standby, the same eventDispatcher should not be registered more than once

[ https://issues.apache.org/jira/browse/YARN-1574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13865773#comment-13865773 ] Karthik Kambatla commented on YARN-1574: Good catch, [~xgong]. I see two ways of

[jira] [Commented] (YARN-1574) When RM transit from Active to Standby, the same eventDispatcher should not be registered more than once

[ https://issues.apache.org/jira/browse/YARN-1574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13865780#comment-13865780 ] Karthik Kambatla commented on YARN-1574: [~xgong], [~bikassaha] - what do you

[jira] [Commented] (YARN-1567) In Fair Scheduler, allow empty leaf queues to become parent queues on allocation file reload

[ https://issues.apache.org/jira/browse/YARN-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13865785#comment-13865785 ] Hadoop QA commented on YARN-1567: - {color:red}-1 overall{color}. Here are the results of

[jira] [Updated] (YARN-1138) yarn.application.classpath is set to point to $HADOOP_CONF_DIR etc., which does not work on Windows

[ https://issues.apache.org/jira/browse/YARN-1138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chuan Liu updated YARN-1138: Attachment: YARN-1138.patch The default value for yarn.application.classpath is already properly defined

[jira] [Commented] (YARN-1041) Protocol changes for RM to bind and notify a restarted AM of existing containers

[ https://issues.apache.org/jira/browse/YARN-1041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13865795#comment-13865795 ] Jian He commented on YARN-1041: --- bq. there's a lot of duplication across each scheduler's {{

[jira] [Commented] (YARN-888) clean up POM dependencies

[ https://issues.apache.org/jira/browse/YARN-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13865830#comment-13865830 ] Roman Shaposhnik commented on YARN-888: --- +1 clean up POM dependencies

[jira] [Updated] (YARN-888) clean up POM dependencies

[ https://issues.apache.org/jira/browse/YARN-888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Abdelnur updated YARN-888: Attachment: YARN-888.patch new patch adding missing hadoop-common test JARs in a few

[jira] [Commented] (YARN-888) clean up POM dependencies

[ https://issues.apache.org/jira/browse/YARN-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13865847#comment-13865847 ] Hadoop QA commented on YARN-888: {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-1138) yarn.application.classpath is set to point to $HADOOP_CONF_DIR etc., which does not work on Windows

[ https://issues.apache.org/jira/browse/YARN-1138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13865927#comment-13865927 ] Hadoop QA commented on YARN-1138: - {color:green}+1 overall{color}. Here are the results of

[jira] [Commented] (YARN-888) clean up POM dependencies

[ https://issues.apache.org/jira/browse/YARN-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13865953#comment-13865953 ] Hadoop QA commented on YARN-888: {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-1575) Public localizer crashes with Localized unkown resource

[ https://issues.apache.org/jira/browse/YARN-1575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13865956#comment-13865956 ] Jason Lowe commented on YARN-1575: -- I think there's a race condition in the public

[jira] [Updated] (YARN-1567) In Fair Scheduler, allow empty queues to change between leaf and parent on allocation file reload

[ https://issues.apache.org/jira/browse/YARN-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-1567: - Summary: In Fair Scheduler, allow empty queues to change between leaf and parent on allocation file

[jira] [Commented] (YARN-1567) In Fair Scheduler, allow empty leaf queues to become parent queues on allocation file reload

[ https://issues.apache.org/jira/browse/YARN-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13865958#comment-13865958 ] Sandy Ryza commented on YARN-1567: -- Test failure is unrelated In Fair Scheduler, allow

[jira] [Updated] (YARN-935) YARN-321 branch is broken due to applicationhistoryserver module's pom.xml

[ https://issues.apache.org/jira/browse/YARN-935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-935: - Attachment: YARN-935.2.patch Created an updated patch that applies to the latest trunk. With it, we don't

[jira] [Updated] (YARN-947) Defining the history data classes for the implementation of the reading/writing interface

[ https://issues.apache.org/jira/browse/YARN-947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-947: - Attachment: YARN-947.9.patch Created an updated patch that applies to the latest trunk. With it, we don't

[jira] [Updated] (YARN-1345) RMServerUtils#createApplicationAttemptState needs to add the mapping for FINAL_SAVING

[ https://issues.apache.org/jira/browse/YARN-1345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-1345: -- Attachment: YARN-1345.1.patch Upload a patch that updates the commit: {quote} git-svn-id:

[jira] [Commented] (YARN-888) clean up POM dependencies

[ https://issues.apache.org/jira/browse/YARN-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13866017#comment-13866017 ] Alejandro Abdelnur commented on YARN-888: - I've run the resourcemanager and

[jira] [Commented] (YARN-1345) RMServerUtils#createApplicationAttemptState needs to add the mapping for FINAL_SAVING

[ https://issues.apache.org/jira/browse/YARN-1345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13866018#comment-13866018 ] Hadoop QA commented on YARN-1345: - {color:red}-1 overall{color}. Here are the results of

[jira] [Updated] (YARN-979) [YARN-321] Add more APIs related to ApplicationAttempt and Container in ApplicationHistoryProtocol

[ https://issues.apache.org/jira/browse/YARN-979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-979: - Attachment: YARN-979.7.patch Created an updated patch that applies to the latest trunk. [YARN-321] Add

[jira] [Updated] (YARN-974) RMContainer should collect more useful information to be recorded in Application-History

[ https://issues.apache.org/jira/browse/YARN-974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-974: - Attachment: YARN-974.5.patch Created an updated patch that applies to the latest trunk. RMContainer

[jira] [Updated] (YARN-1567) In Fair Scheduler, allow empty queues to change between leaf and parent on allocation file reload

[ https://issues.apache.org/jira/browse/YARN-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-1567: - Attachment: YARN-1567-1.patch In Fair Scheduler, allow empty queues to change between leaf and parent on

[jira] [Commented] (YARN-888) clean up POM dependencies

[ https://issues.apache.org/jira/browse/YARN-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13866030#comment-13866030 ] Karthik Kambatla commented on YARN-888: --- Running all yarn tests locally to be on the

[jira] [Updated] (YARN-953) [YARN-321] Enable ResourceManager to write history data

[ https://issues.apache.org/jira/browse/YARN-953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-953: - Attachment: YARN-953.9.patch Created an updated patch that applies to the latest trunk. [YARN-321]

[jira] [Updated] (YARN-1574) When RM transit from Active to Standby, the same eventDispatcher should not be registered more than once

[ https://issues.apache.org/jira/browse/YARN-1574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-1574: Attachment: YARN-1574.1.patch When RM transit from Active to Standby, the same eventDispatcher should not

[jira] [Commented] (YARN-1574) When RM transit from Active to Standby, the same eventDispatcher should not be registered more than once

[ https://issues.apache.org/jira/browse/YARN-1574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13866042#comment-13866042 ] Xuan Gong commented on YARN-1574: - +1 on option2. But I think that the resetDispatcher

[jira] [Updated] (YARN-967) [YARN-321] Command Line Interface(CLI) for Reading Application History Storage Data

[ https://issues.apache.org/jira/browse/YARN-967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-967: - Attachment: YARN-967.15.patch Created an updated patch that applies to the latest trunk. [YARN-321]

[jira] [Commented] (YARN-1567) In Fair Scheduler, allow empty queues to change between leaf and parent on allocation file reload

[ https://issues.apache.org/jira/browse/YARN-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13866075#comment-13866075 ] Hadoop QA commented on YARN-1567: - {color:green}+1 overall{color}. Here are the results of

[jira] [Updated] (YARN-1530) [Umbrella] Store, manage and serve per-framework application-timeline data

[ https://issues.apache.org/jira/browse/YARN-1530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-1530: -- Attachment: application timeline design-20140108.pdf Attached is the designed

[jira] [Commented] (YARN-1574) When RM transit from Active to Standby, the same eventDispatcher should not be registered more than once

[ https://issues.apache.org/jira/browse/YARN-1574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13866089#comment-13866089 ] Hadoop QA commented on YARN-1574: - {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-1574) When RM transit from Active to Standby, the same eventDispatcher should not be registered more than once

[ https://issues.apache.org/jira/browse/YARN-1574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13866098#comment-13866098 ] Xuan Gong commented on YARN-1574: - [~kkambatl] Could you take a look ? When RM transit

[jira] [Updated] (YARN-1575) Public localizer crashes with Localized unkown resource

[ https://issues.apache.org/jira/browse/YARN-1575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-1575: -- Issue Type: Sub-task (was: Bug) Parent: YARN-543 Public localizer

[jira] [Commented] (YARN-1574) When RM transit from Active to Standby, the same eventDispatcher should not be registered more than once

[ https://issues.apache.org/jira/browse/YARN-1574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13866111#comment-13866111 ] Karthik Kambatla commented on YARN-1574: Approach looks reasonable. Comments: # It

[jira] [Commented] (YARN-888) clean up POM dependencies

[ https://issues.apache.org/jira/browse/YARN-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13866123#comment-13866123 ] Karthik Kambatla commented on YARN-888: --- Ran all Yarn tests locally without failures.

[jira] [Created] (YARN-1576) Allow setting RPC timeout in ApplicationClientProtocolPBClientImpl

Sandy Ryza created YARN-1576: Summary: Allow setting RPC timeout in ApplicationClientProtocolPBClientImpl Key: YARN-1576 URL: https://issues.apache.org/jira/browse/YARN-1576 Project: Hadoop YARN

[jira] [Commented] (YARN-888) clean up POM dependencies

[ https://issues.apache.org/jira/browse/YARN-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13866162#comment-13866162 ] Alejandro Abdelnur commented on YARN-888: - Karthik, thanks for the verification.

[jira] [Assigned] (YARN-1576) Allow setting RPC timeout in ApplicationClientProtocolPBClientImpl

[ https://issues.apache.org/jira/browse/YARN-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza reassigned YARN-1576: Assignee: Sandy Ryza Allow setting RPC timeout in ApplicationClientProtocolPBClientImpl

[jira] [Created] (YARN-1577) Unmanaged AM is broken because of YARN-1493

Jian He created YARN-1577: - Summary: Unmanaged AM is broken because of YARN-1493 Key: YARN-1577 URL: https://issues.apache.org/jira/browse/YARN-1577 Project: Hadoop YARN Issue Type: Sub-task

[jira] [Commented] (YARN-1568) Rename clusterid to clusterId in ActiveRMInfoProto

[ https://issues.apache.org/jira/browse/YARN-1568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13866254#comment-13866254 ] Vinod Kumar Vavilapalli commented on YARN-1568: --- Hey. I missed this before,

[jira] [Updated] (YARN-1490) RM should optionally not kill all containers when an ApplicationMaster exits

[ https://issues.apache.org/jira/browse/YARN-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-1490: -- Attachment: YARN-1490.4.patch Thanks Vinod for such detailed comments ! RM should optionally not kill all

[jira] [Commented] (YARN-1490) RM should optionally not kill all containers when an ApplicationMaster exits

[ https://issues.apache.org/jira/browse/YARN-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13866264#comment-13866264 ] Jian He commented on YARN-1490: --- Uploaded a new patch bq. Change it also transfer running

[jira] [Commented] (YARN-1166) YARN 'appsFailed' metric should be of type 'counter'

[ https://issues.apache.org/jira/browse/YARN-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13866266#comment-13866266 ] Vinod Kumar Vavilapalli commented on YARN-1166: --- One comment other than

[jira] [Commented] (YARN-1490) RM should optionally not kill all containers when an ApplicationMaster exits

[ https://issues.apache.org/jira/browse/YARN-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13866267#comment-13866267 ] Jian He commented on YARN-1490: --- bq. What about NMTokens? Imagine this. AM1 requests a

[jira] [Updated] (YARN-1574) When RM transit from Active to Standby, the same eventDispatcher should not be registered more than once

[ https://issues.apache.org/jira/browse/YARN-1574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-1574: Attachment: YARN-1574.2.patch When RM transit from Active to Standby, the same eventDispatcher should not

[jira] [Commented] (YARN-1574) When RM transit from Active to Standby, the same eventDispatcher should not be registered more than once

[ https://issues.apache.org/jira/browse/YARN-1574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13866271#comment-13866271 ] Hadoop QA commented on YARN-1574: - {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-1166) YARN 'appsFailed' metric should be of type 'counter'

[ https://issues.apache.org/jira/browse/YARN-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13866276#comment-13866276 ] Jian He commented on YARN-1166: --- @zhijie, last time I checked YARN-915 should be caused by

[jira] [Updated] (YARN-1574) When RM transit from Active to Standby, the same eventDispatcher should not be registered more than once

[ https://issues.apache.org/jira/browse/YARN-1574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-1574: Attachment: YARN-1574.2.patch When RM transit from Active to Standby, the same eventDispatcher should not

[jira] [Commented] (YARN-1345) RMServerUtils#createApplicationAttemptState needs to add the mapping for FINAL_SAVING

[ https://issues.apache.org/jira/browse/YARN-1345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13866281#comment-13866281 ] Vinod Kumar Vavilapalli commented on YARN-1345: --- I think [~jianhe]

[jira] [Commented] (YARN-1574) When RM transit from Active to Standby, the same eventDispatcher should not be registered more than once

[ https://issues.apache.org/jira/browse/YARN-1574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13866282#comment-13866282 ] Karthik Kambatla commented on YARN-1574: bq. I think that they are fine because all

[jira] [Commented] (YARN-1568) Rename clusterid to clusterId in ActiveRMInfoProto

[ https://issues.apache.org/jira/browse/YARN-1568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13866289#comment-13866289 ] Karthik Kambatla commented on YARN-1568: bq. our convention is to mark all fields

[jira] [Commented] (YARN-1496) Protocol additions to allow moving apps between queues

[ https://issues.apache.org/jira/browse/YARN-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13866288#comment-13866288 ] Vinod Kumar Vavilapalli commented on YARN-1496: --- 'ChangeApplicationQueue'

[jira] [Commented] (YARN-1490) RM should optionally not kill all containers when an ApplicationMaster exits

[ https://issues.apache.org/jira/browse/YARN-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13866294#comment-13866294 ] Hadoop QA commented on YARN-1490: - {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-1568) Rename clusterid to clusterId in ActiveRMInfoProto

[ https://issues.apache.org/jira/browse/YARN-1568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13866293#comment-13866293 ] Vinod Kumar Vavilapalli commented on YARN-1568: --- oh, there is a bit of

[jira] [Commented] (YARN-888) clean up POM dependencies

[ https://issues.apache.org/jira/browse/YARN-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13866301#comment-13866301 ] Vinod Kumar Vavilapalli commented on YARN-888: -- bq. We should normalize the

[jira] [Commented] (YARN-1574) When RM transit from Active to Standby, the same eventDispatcher should not be registered more than once

[ https://issues.apache.org/jira/browse/YARN-1574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13866304#comment-13866304 ] Hadoop QA commented on YARN-1574: - {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-1567) In Fair Scheduler, allow empty queues to change between leaf and parent on allocation file reload

[ https://issues.apache.org/jira/browse/YARN-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13866306#comment-13866306 ] Vinod Kumar Vavilapalli commented on YARN-1567: --- Empty queues or stopped

[jira] [Comment Edited] (YARN-1577) Unmanaged AM is broken because of YARN-1493

[ https://issues.apache.org/jira/browse/YARN-1577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13866308#comment-13866308 ] Alejandro Abdelnur edited comment on YARN-1577 at 1/9/14 4:34 AM:

[jira] [Commented] (YARN-1577) Unmanaged AM is broken because of YARN-1493

[ https://issues.apache.org/jira/browse/YARN-1577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13866308#comment-13866308 ] Alejandro Abdelnur commented on YARN-1577: -- this seems a serius regression,

[jira] [Updated] (YARN-1490) RM should optionally not kill all containers when an ApplicationMaster exits

[ https://issues.apache.org/jira/browse/YARN-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-1490: -- Attachment: YARN-1490.5.patch RM should optionally not kill all containers when an ApplicationMaster exits

[jira] [Commented] (YARN-1345) RMServerUtils#createApplicationAttemptState needs to add the mapping for FINAL_SAVING

[ https://issues.apache.org/jira/browse/YARN-1345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13866326#comment-13866326 ] Zhijie Shen commented on YARN-1345: --- bq. I think Jian He deliberately didn't add

[jira] [Updated] (YARN-1578) Fix how to handle ApplicationHistory about the container

[ https://issues.apache.org/jira/browse/YARN-1578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shinichi Yamashita updated YARN-1578: - Attachment: screenshot.png Fix how to handle ApplicationHistory about the container

[jira] [Created] (YARN-1578) Fix how to handle ApplicationHistory about the container

Shinichi Yamashita created YARN-1578: Summary: Fix how to handle ApplicationHistory about the container Key: YARN-1578 URL: https://issues.apache.org/jira/browse/YARN-1578 Project: Hadoop YARN

[jira] [Commented] (YARN-1490) RM should optionally not kill all containers when an ApplicationMaster exits

[ https://issues.apache.org/jira/browse/YARN-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13866333#comment-13866333 ] Hadoop QA commented on YARN-1490: - {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-1577) Unmanaged AM is broken because of YARN-1493

[ https://issues.apache.org/jira/browse/YARN-1577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13866335#comment-13866335 ] Zhijie Shen commented on YARN-1577: --- bq. We may need to introduce an attempt state report

[jira] [Updated] (YARN-1577) Unmanaged AM is broken because of YARN-1493

[ https://issues.apache.org/jira/browse/YARN-1577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-1577: -- Affects Version/s: 2.4.0 Unmanaged AM is broken because of YARN-1493

[jira] [Updated] (YARN-1577) Unmanaged AM is broken because of YARN-1493

[ https://issues.apache.org/jira/browse/YARN-1577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-1577: -- Priority: Blocker (was: Major) Unmanaged AM is broken because of YARN-1493

[jira] [Commented] (YARN-1577) Unmanaged AM is broken because of YARN-1493

[ https://issues.apache.org/jira/browse/YARN-1577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13866339#comment-13866339 ] Jian He commented on YARN-1577: --- yup, marked as blocker Unmanaged AM is broken because of

[jira] [Created] (YARN-1579) ActiveRMInfoProto fields should be optional

Karthik Kambatla created YARN-1579: -- Summary: ActiveRMInfoProto fields should be optional Key: YARN-1579 URL: https://issues.apache.org/jira/browse/YARN-1579 Project: Hadoop YARN Issue

[jira] [Commented] (YARN-1568) Rename clusterid to clusterId in ActiveRMInfoProto

[ https://issues.apache.org/jira/browse/YARN-1568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13866364#comment-13866364 ] Karthik Kambatla commented on YARN-1568: Thanks for the explanation, Vinod. I guess

[jira] [Commented] (YARN-1572) Lower chance to hit NPE in allocateNodeLocal

[ https://issues.apache.org/jira/browse/YARN-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13866384#comment-13866384 ] Junping Du commented on YARN-1572: -- Yes. It seems to be a YARN issue. I will take this.

[jira] [Assigned] (YARN-1572) Lower chance to hit NPE in allocateNodeLocal

[ https://issues.apache.org/jira/browse/YARN-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du reassigned YARN-1572: Assignee: Junping Du Lower chance to hit NPE in allocateNodeLocal

[jira] [Updated] (YARN-1572) Low chance to hit NPE issue in AppSchedulingInfo#allocateNodeLocal

[ https://issues.apache.org/jira/browse/YARN-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-1572: - Summary: Low chance to hit NPE issue in AppSchedulingInfo#allocateNodeLocal (was: Lower chance to hit

[jira] [Updated] (YARN-1572) Low chance to hit NPE issue in AppSchedulingInfo#allocateNodeLocal

[ https://issues.apache.org/jira/browse/YARN-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-1572: - Affects Version/s: 2.2.0 Low chance to hit NPE issue in AppSchedulingInfo#allocateNodeLocal

[jira] [Updated] (YARN-1572) Low chance to hit NPE issue in AppSchedulingInfo#allocateNodeLocal

[ https://issues.apache.org/jira/browse/YARN-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-1572: - Component/s: scheduler Low chance to hit NPE issue in AppSchedulingInfo#allocateNodeLocal

[jira] [Updated] (YARN-1572) Low chance to hit NPE issue in AppSchedulingInfo#allocateNodeLocal

[ https://issues.apache.org/jira/browse/YARN-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-1572: - Target Version/s: 2.4.0 Low chance to hit NPE issue in AppSchedulingInfo#allocateNodeLocal

  1   2   >