[jira] [Updated] (YARN-846) Move pb Impl from yarn-api to yarn-common

[ https://issues.apache.org/jira/browse/YARN-846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-846: - Attachment: move_pbImpls.sh upload the mv script Move pb Impl from yarn-api to yarn-common

[jira] [Commented] (YARN-846) Move pb Impl from yarn-api to yarn-common

[ https://issues.apache.org/jira/browse/YARN-846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13686388#comment-13686388 ] Jian He commented on YARN-846: -- This patch moved protocol records , api records, protocol pb to

[jira] [Updated] (YARN-846) Move pb Impl from yarn-api to yarn-common

[ https://issues.apache.org/jira/browse/YARN-846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-846: - Attachment: YARN-846.full.patch resubmit the patch to kick jenkins Move pb Impl from yarn-api to

[jira] [Updated] (YARN-846) Move pb Impl from yarn-api to yarn-common

[ https://issues.apache.org/jira/browse/YARN-846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-846: - Attachment: YARN-846.full.1.patch rebased on latest trunk Move pb Impl from yarn-api to

[jira] [Created] (YARN-849) YARN should figure out the hostname instead of expecting it in the Application Register call

Jian He created YARN-849: Summary: YARN should figure out the hostname instead of expecting it in the Application Register call Key: YARN-849 URL: https://issues.apache.org/jira/browse/YARN-849 Project:

[jira] [Updated] (YARN-849) YARN should figure out the App hostname instead of expecting it in the Application Register call

[ https://issues.apache.org/jira/browse/YARN-849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-849: - Summary: YARN should figure out the App hostname instead of expecting it in the Application Register call (was:

[jira] [Created] (YARN-850) Rename AMRMClient#getClusterAvailableResources, AMRMClientAsync#getClusterAvailableResources to getAvailableResources

Jian He created YARN-850: Summary: Rename AMRMClient#getClusterAvailableResources, AMRMClientAsync#getClusterAvailableResources to getAvailableResources Key: YARN-850 URL: https://issues.apache.org/jira/browse/YARN-850

[jira] [Updated] (YARN-850) Rename AMRMClient#getClusterAvailableResources, AMRMClientAsync#getClusterAvailableResources to getAvailableResources

[ https://issues.apache.org/jira/browse/YARN-850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-850: - Attachment: YARN-850.patch trivial rename patch Rename AMRMClient#getClusterAvailableResources,

[jira] [Updated] (YARN-818) YARN application classpath should add $PWD/* in addition to $PWD

[ https://issues.apache.org/jira/browse/YARN-818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-818: - Attachment: YARN-818.patch Add $PWD/* to YarnConfiguration.DEFAULT_YARN_APPLICATION_CLASSPATH and

[jira] [Created] (YARN-858) Move Resources and the caculators to a new package util.resource in yarn-common

Jian He created YARN-858: Summary: Move Resources and the caculators to a new package util.resource in yarn-common Key: YARN-858 URL: https://issues.apache.org/jira/browse/YARN-858 Project: Hadoop YARN

[jira] [Updated] (YARN-858) Move Resources and the caculators to a new package util.resource in yarn-common

[ https://issues.apache.org/jira/browse/YARN-858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-858: - Description: For userland use Move Resources and the caculators to a new package util.resource in

[jira] [Updated] (YARN-858) Move Resources and the calculators to a new package util.resource in yarn-common

[ https://issues.apache.org/jira/browse/YARN-858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-858: - Attachment: YARN-858.patch Moved DefaultResourceCalculator, DominantResourceCalculator, ResourceCalculator,

[jira] [Commented] (YARN-858) Move Resources and the calculators to a new package util.resource in yarn-common

[ https://issues.apache.org/jira/browse/YARN-858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13688669#comment-13688669 ] Jian He commented on YARN-858: -- Looks like this is duplicative as YARN-827

[jira] [Commented] (YARN-858) Move Resources and the calculators to a new package util.resource in yarn-common

[ https://issues.apache.org/jira/browse/YARN-858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13688674#comment-13688674 ] Jian He commented on YARN-858: -- close this Move Resources and the calculators

[jira] [Resolved] (YARN-858) Move Resources and the calculators to a new package util.resource in yarn-common

[ https://issues.apache.org/jira/browse/YARN-858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He resolved YARN-858. -- Resolution: Duplicate Move Resources and the calculators to a new package util.resource in yarn-common

[jira] [Updated] (YARN-827) Need to make Resource arithmetic methods public

[ https://issues.apache.org/jira/browse/YARN-827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-827: - Attachment: YARN-827.patch upload a patch to attract attentions. Moved DefaultResourceCalculator,

[jira] [Assigned] (YARN-827) Need to make Resource arithmetic methods public

[ https://issues.apache.org/jira/browse/YARN-827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He reassigned YARN-827: Assignee: Jian He (was: Zhijie Shen) Need to make Resource arithmetic methods public

[jira] [Updated] (YARN-827) Need to make Resource arithmetic methods public

[ https://issues.apache.org/jira/browse/YARN-827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-827: - Attachment: YARN-827.1.patch mark all as Private, and also modified capacity-scheduler.xml to point to the moved

[jira] [Updated] (YARN-827) Need to make Resource arithmetic methods public

[ https://issues.apache.org/jira/browse/YARN-827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-827: - Attachment: YARN-827.2.patch Findbug -1 is because of unused field in DefaultResourceCalculator

[jira] [Commented] (YARN-864) YARN NM leaking containers with CGroups

[ https://issues.apache.org/jira/browse/YARN-864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13690506#comment-13690506 ] Jian He commented on YARN-864: -- This might be related to YARN-688. YARN NM

[jira] [Updated] (YARN-688) Containers not cleaned up when NM received SHUTDOWN event from NodeStatusUpdater

[ https://issues.apache.org/jira/browse/YARN-688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-688: - Attachment: YARN-688-2.0.5-alpha.patch patch for 2.0.5-alpha for YARN-864 Containers not cleaned

[jira] [Commented] (YARN-864) YARN NM leaking containers with CGroups

[ https://issues.apache.org/jira/browse/YARN-864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13690602#comment-13690602 ] Jian He commented on YARN-864: -- Hi Chris Uploaded two patches there one for 2.0.5-alpha and one

[jira] [Assigned] (YARN-814) Difficult to diagnose a failed container launch when error due to invalid environment variable

[ https://issues.apache.org/jira/browse/YARN-814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He reassigned YARN-814: Assignee: Jian He Difficult to diagnose a failed container launch when error due to invalid

[jira] [Commented] (YARN-814) Difficult to diagnose a failed container launch when error due to invalid environment variable

[ https://issues.apache.org/jira/browse/YARN-814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13690966#comment-13690966 ] Jian He commented on YARN-814: -- After investigation shExec.getOutput() is returning empty

[jira] [Updated] (YARN-814) Difficult to diagnose a failed container launch when error due to invalid environment variable

[ https://issues.apache.org/jira/browse/YARN-814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-814: - Attachment: YARN-814.patch upload a patch Difficult to diagnose a failed container launch when

[jira] [Updated] (YARN-864) YARN NM leaking containers with CGroups

[ https://issues.apache.org/jira/browse/YARN-864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-864: - Attachment: YARN-864.1.patch patch for NM clean up containers on SHUTDOWN and REBOOT event. YARN

[jira] [Commented] (YARN-864) YARN NM leaking containers with CGroups

[ https://issues.apache.org/jira/browse/YARN-864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13691344#comment-13691344 ] Jian He commented on YARN-864: -- Hi Chris Yes, the log shows its on REBOOT event. The earlier

[jira] [Created] (YARN-881) Priority#compareTo method seems to be wrong.

Jian He created YARN-881: Summary: Priority#compareTo method seems to be wrong. Key: YARN-881 URL: https://issues.apache.org/jira/browse/YARN-881 Project: Hadoop YARN Issue Type: Bug

[jira] [Updated] (YARN-864) YARN NM leaking containers with CGroups

[ https://issues.apache.org/jira/browse/YARN-864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-864: - Attachment: YARN-864.2.patch YARN NM leaking containers with CGroups ---

[jira] [Commented] (YARN-864) YARN NM leaking containers with CGroups

[ https://issues.apache.org/jira/browse/YARN-864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13692388#comment-13692388 ] Jian He commented on YARN-864: -- Hi Chris that failure was due to reboot starts even before

[jira] [Commented] (YARN-864) YARN NM leaking containers with CGroups

[ https://issues.apache.org/jira/browse/YARN-864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13693528#comment-13693528 ] Jian He commented on YARN-864: -- Hi Chris YARN-495 was already committed which deals with

[jira] [Commented] (YARN-814) Difficult to diagnose a failed container launch when error due to invalid environment variable

[ https://issues.apache.org/jira/browse/YARN-814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13695678#comment-13695678 ] Jian He commented on YARN-814: -- kick the jenkins Difficult to diagnose a

[jira] [Updated] (YARN-513) Create common proxy client for communicating with RM

[ https://issues.apache.org/jira/browse/YARN-513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-513: - Attachment: YARN-513.13.patch rebased on latest trunk Create common proxy client for

[jira] [Updated] (YARN-814) Difficult to diagnose a failed container launch when error due to invalid environment variable

[ https://issues.apache.org/jira/browse/YARN-814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-814: - Attachment: YARN-814.2.patch Difficult to diagnose a failed container launch when error due to invalid

[jira] [Updated] (YARN-814) Difficult to diagnose a failed container launch when error due to invalid environment variable

[ https://issues.apache.org/jira/browse/YARN-814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-814: - Attachment: (was: YARN-814.3.patch) Difficult to diagnose a failed container launch when error due to

[jira] [Updated] (YARN-814) Difficult to diagnose a failed container launch when error due to invalid environment variable

[ https://issues.apache.org/jira/browse/YARN-814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-814: - Attachment: YARN-814.3.patch Difficult to diagnose a failed container launch when error due to invalid

[jira] [Commented] (YARN-353) Add Zookeeper-based store implementation for RMStateStore

[ https://issues.apache.org/jira/browse/YARN-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13697224#comment-13697224 ] Jian He commented on YARN-353: -- I'm taking this over Add Zookeeper-based

[jira] [Updated] (YARN-353) Add Zookeeper-based store implementation for RMStateStore

[ https://issues.apache.org/jira/browse/YARN-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-353: - Attachment: YARN-353.2.patch rebased the patch and added RMDelegationToken restore implementation for the

[jira] [Updated] (YARN-353) Add Zookeeper-based store implementation for RMStateStore

[ https://issues.apache.org/jira/browse/YARN-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-353: - Attachment: YARN-353.3.patch Devaraj, thanks for your review new patch, fixed the findbug and comments.

[jira] [Updated] (YARN-814) Difficult to diagnose a failed container launch when error due to invalid environment variable

[ https://issues.apache.org/jira/browse/YARN-814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-814: - Attachment: YARN-814.4.patch new patch ,account for both stdout and stderr. Difficult to

[jira] [Commented] (YARN-814) Difficult to diagnose a failed container launch when error due to invalid environment variable

[ https://issues.apache.org/jira/browse/YARN-814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13698250#comment-13698250 ] Jian He commented on YARN-814: -- ran on single node, see the log messages

[jira] [Created] (YARN-895) If NameNode is in safemode when RM restarts, RM should wait instead of crashing.

Jian He created YARN-895: Summary: If NameNode is in safemode when RM restarts, RM should wait instead of crashing. Key: YARN-895 URL: https://issues.apache.org/jira/browse/YARN-895 Project: Hadoop YARN

[jira] [Updated] (YARN-353) Add Zookeeper-based store implementation for RMStateStore

[ https://issues.apache.org/jira/browse/YARN-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-353: - Attachment: YARN-353.4.patch right, thanks for pointing that out. Updated the patch, made some changes along with

[jira] [Commented] (YARN-523) Container localization failures aren't reported from NM to RM

[ https://issues.apache.org/jira/browse/YARN-523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13699470#comment-13699470 ] Jian He commented on YARN-523: -- Looked at the code and tried on single node cluster, it turns

[jira] [Updated] (YARN-523) Container localization failures aren't reported from NM to RM

[ https://issues.apache.org/jira/browse/YARN-523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-523: - Attachment: YARN-523.patch added a test case to verify the diagnostics is reported Container

[jira] [Commented] (YARN-353) Add Zookeeper-based store implementation for RMStateStore

[ https://issues.apache.org/jira/browse/YARN-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13700395#comment-13700395 ] Jian He commented on YARN-353: -- bq. I dont think it makes sense to have default value for this.

[jira] [Commented] (YARN-353) Add Zookeeper-based store implementation for RMStateStore

[ https://issues.apache.org/jira/browse/YARN-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13700422#comment-13700422 ] Jian He commented on YARN-353: -- Any downside of doing that ? Add

[jira] [Commented] (YARN-353) Add Zookeeper-based store implementation for RMStateStore

[ https://issues.apache.org/jira/browse/YARN-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13700465#comment-13700465 ] Jian He commented on YARN-353: -- sorry, I meant downside of giving a default ZK address. yeah,

[jira] [Commented] (YARN-513) Create common proxy client for communicating with RM

[ https://issues.apache.org/jira/browse/YARN-513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702443#comment-13702443 ] Jian He commented on YARN-513: -- bq.Does ResourceTrackerClientPBImpl still need a close method

[jira] [Commented] (YARN-513) Create common proxy client for communicating with RM

[ https://issues.apache.org/jira/browse/YARN-513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702452#comment-13702452 ] Jian He commented on YARN-513: -- bq. Does this need an @VisibleForTesting flag? Yes, we need to

[jira] [Commented] (YARN-763) AMRMClientAsync should stop heartbeating after receiving shutdown from RM

[ https://issues.apache.org/jira/browse/YARN-763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13703016#comment-13703016 ] Jian He commented on YARN-763: -- The test is only testing the heartbeat thread is cancelled

[jira] [Updated] (YARN-353) Add Zookeeper-based store implementation for RMStateStore

[ https://issues.apache.org/jira/browse/YARN-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-353: - Attachment: YARN-353.5.patch New patch. Talked with Bikas offline, still remove default zk address as its out of

[jira] [Updated] (YARN-513) Create common proxy client for communicating with RM

[ https://issues.apache.org/jira/browse/YARN-513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-513: - Attachment: YARN-513.14.patch Upload a patch which fixed the comments Create common proxy client

[jira] [Updated] (YARN-814) Difficult to diagnose a failed container launch when error due to invalid environment variable

[ https://issues.apache.org/jira/browse/YARN-814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-814: - Attachment: YARN-814.5.patch New patch fixed the comments and added one test for invalid env diagnostics

[jira] [Commented] (YARN-523) Container localization failures aren't reported from NM to RM

[ https://issues.apache.org/jira/browse/YARN-523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13704910#comment-13704910 ] Jian He commented on YARN-523: -- tested on single node cluster to throw

[jira] [Created] (YARN-915) Apps Completed metrics on web UI is not correct after RM restart

Jian He created YARN-915: Summary: Apps Completed metrics on web UI is not correct after RM restart Key: YARN-915 URL: https://issues.apache.org/jira/browse/YARN-915 Project: Hadoop YARN Issue

[jira] [Updated] (YARN-915) Apps Completed metrics on web UI is not correct after RM restart

[ https://issues.apache.org/jira/browse/YARN-915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-915: - Attachment: screen shot.png Attach an image which shows the incorrect App complemented metrics.

[jira] [Updated] (YARN-915) Apps Completed metrics on web UI is not correct after RM restart

[ https://issues.apache.org/jira/browse/YARN-915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-915: - Description: negative Apps completed metrics can show on web UI Apps Completed metrics on web UI is not

[jira] [Commented] (YARN-763) AMRMClientAsync should stop heartbeating after receiving shutdown from RM

[ https://issues.apache.org/jira/browse/YARN-763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13705464#comment-13705464 ] Jian He commented on YARN-763: -- testCallAMRMClientAsyncStopFromCallbackHandler: In the test

[jira] [Created] (YARN-917) RM restart can fail when it restarts after staging dir is cleaned but before MR successfully unregister with RM

Jian He created YARN-917: Summary: RM restart can fail when it restarts after staging dir is cleaned but before MR successfully unregister with RM Key: YARN-917 URL: https://issues.apache.org/jira/browse/YARN-917

[jira] [Updated] (YARN-917) Job can fail when RM restarts after staging dir is cleaned but before MR successfully unregister with RM

[ https://issues.apache.org/jira/browse/YARN-917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-917: - Summary: Job can fail when RM restarts after staging dir is cleaned but before MR successfully unregister with RM

[jira] [Created] (YARN-920) List of applications at NM web UI is inconsistent with applications at RM UI after RM restart

Jian He created YARN-920: Summary: List of applications at NM web UI is inconsistent with applications at RM UI after RM restart Key: YARN-920 URL: https://issues.apache.org/jira/browse/YARN-920 Project:

[jira] [Updated] (YARN-920) List of applications at NM web UI is inconsistent with applications at RM UI after RM restart

[ https://issues.apache.org/jira/browse/YARN-920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-920: - Description: e.g. After RM restarts, previously running applications show finished on RM UI, but NM UI still

[jira] [Updated] (YARN-920) List of applications at NM web UI is inconsistent with applications at RM UI after RM restart

[ https://issues.apache.org/jira/browse/YARN-920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-920: - Attachment: NM UI.png RM UI.png Attached two images, one for RM web UI and the other for NM UI

[jira] [Created] (YARN-922) Change FileSystemRMStateStore to use directories

Jian He created YARN-922: Summary: Change FileSystemRMStateStore to use directories Key: YARN-922 URL: https://issues.apache.org/jira/browse/YARN-922 Project: Hadoop YARN Issue Type: Sub-task

[jira] [Updated] (YARN-922) Change FileSystemRMStateStore to use directories

[ https://issues.apache.org/jira/browse/YARN-922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-922: - Attachment: YARN-922.patch Patch to add directory support to FileSystemRMStateStore Change

[jira] [Commented] (YARN-513) Create common proxy client for communicating with RM

[ https://issues.apache.org/jira/browse/YARN-513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13708194#comment-13708194 ] Jian He commented on YARN-513: -- bq. ClientRMProxy.createRMProxy doesnt even take 3 arguments.

[jira] [Commented] (YARN-513) Create common proxy client for communicating with RM

[ https://issues.apache.org/jira/browse/YARN-513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13708696#comment-13708696 ] Jian He commented on YARN-513: -- bq. Why does YARNClient need to accept the rmaddress as a

[jira] [Commented] (YARN-353) Add Zookeeper-based store implementation for RMStateStore

[ https://issues.apache.org/jira/browse/YARN-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13708734#comment-13708734 ] Jian He commented on YARN-353: -- Thanks for the review, Karthik bq.YarnConfiguration: how about

[jira] [Updated] (YARN-353) Add Zookeeper-based store implementation for RMStateStore

[ https://issues.apache.org/jira/browse/YARN-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-353: - Attachment: YARN-353.6.patch Add Zookeeper-based store implementation for RMStateStore

[jira] [Updated] (YARN-353) Add Zookeeper-based store implementation for RMStateStore

[ https://issues.apache.org/jira/browse/YARN-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-353: - Attachment: YARN-353.7.patch Add Zookeeper-based store implementation for RMStateStore

[jira] [Updated] (YARN-513) Create common proxy client for communicating with RM

[ https://issues.apache.org/jira/browse/YARN-513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-513: - Attachment: YARN-513.15.patch Create common proxy client for communicating with RM

[jira] [Commented] (YARN-513) Create common proxy client for communicating with RM

[ https://issues.apache.org/jira/browse/YARN-513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13709063#comment-13709063 ] Jian He commented on YARN-513: -- New patch removed rmaddress as a parameter from YARNClient

[jira] [Updated] (YARN-513) Create common proxy client for communicating with RM

[ https://issues.apache.org/jira/browse/YARN-513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-513: - Attachment: YARN-513.16.patch Create common proxy client for communicating with RM

[jira] [Commented] (YARN-922) Change FileSystemRMStateStore to use directories

[ https://issues.apache.org/jira/browse/YARN-922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13709311#comment-13709311 ] Jian He commented on YARN-922: -- existing test cases covers this, no need to add more tests

[jira] [Updated] (YARN-513) Create common proxy client for communicating with RM

[ https://issues.apache.org/jira/browse/YARN-513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-513: - Attachment: YARN-513.17.patch rebased the patch Create common proxy client for communicating

[jira] [Updated] (YARN-922) Change FileSystemRMStateStore to use directories

[ https://issues.apache.org/jira/browse/YARN-922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-922: - Attachment: YARN-922.1.patch Change FileSystemRMStateStore to use directories

[jira] [Updated] (YARN-922) Change FileSystemRMStateStore to use directories

[ https://issues.apache.org/jira/browse/YARN-922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-922: - Attachment: YARN-922.2.patch fixed test failure. Change FileSystemRMStateStore to use

[jira] [Commented] (YARN-513) Create common proxy client for communicating with RM

[ https://issues.apache.org/jira/browse/YARN-513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13709457#comment-13709457 ] Jian He commented on YARN-513: -- The above test failures is not related to this patch,

[jira] [Updated] (YARN-922) Change FileSystemRMStateStore to use directories

[ https://issues.apache.org/jira/browse/YARN-922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-922: - Attachment: YARN-922.3.patch New patch addressed the comments Change FileSystemRMStateStore to

[jira] [Assigned] (YARN-926) ContainerManagerProtcol APIs should take in requests for multiple containers

[ https://issues.apache.org/jira/browse/YARN-926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He reassigned YARN-926: Assignee: Jian He (was: Vinod Kumar Vavilapalli) ContainerManagerProtcol APIs should take in requests

[jira] [Commented] (YARN-926) ContainerManagerProtcol APIs should take in requests for multiple containers

[ https://issues.apache.org/jira/browse/YARN-926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13711642#comment-13711642 ] Jian He commented on YARN-926: -- bq. should stopContainer take the request of multiple

[jira] [Updated] (YARN-814) Difficult to diagnose a failed container launch when error due to invalid environment variable

[ https://issues.apache.org/jira/browse/YARN-814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-814: - Attachment: YARN-814.6.patch Difficult to diagnose a failed container launch when error due to invalid

[jira] [Commented] (YARN-814) Difficult to diagnose a failed container launch when error due to invalid environment variable

[ https://issues.apache.org/jira/browse/YARN-814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13711828#comment-13711828 ] Jian He commented on YARN-814: -- bq. When an exception happens in

[jira] [Updated] (YARN-814) Difficult to diagnose a failed container launch when error due to invalid environment variable

[ https://issues.apache.org/jira/browse/YARN-814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-814: - Attachment: YARN-814.7.patch new patch fixed the warnings and added test case for stdout/stderr diagnostics

[jira] [Updated] (YARN-353) Add Zookeeper-based store implementation for RMStateStore

[ https://issues.apache.org/jira/browse/YARN-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-353: - Attachment: YARN-353.8.patch New patch made NUM_RETRIES configurable. Changed removeApplicationState to use multi

[jira] [Updated] (YARN-926) ContainerManagerProtcol APIs should take in requests for multiple containers

[ https://issues.apache.org/jira/browse/YARN-926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-926: - Attachment: YARN-926.1.patch Upload a patch: 1. Add 3 bulk api to ContainerManagementProtol

[jira] [Updated] (YARN-926) ContainerManagerProtcol APIs should take in requests for multiple containers

[ https://issues.apache.org/jira/browse/YARN-926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-926: - Attachment: YARN-926.2.patch New patch fixed the warnings ContainerManagerProtcol APIs should

[jira] [Updated] (YARN-926) ContainerManagerProtcol APIs should take in requests for multiple containers

[ https://issues.apache.org/jira/browse/YARN-926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-926: - Attachment: YARN-926.3.patch ContainerManagerProtcol APIs should take in requests for multiple containers

[jira] [Resolved] (YARN-459) DefaultContainerExecutor doesn't log stderr from container launch

[ https://issues.apache.org/jira/browse/YARN-459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He resolved YARN-459. -- Resolution: Fixed DefaultContainerExecutor doesn't log stderr from container launch

[jira] [Commented] (YARN-459) DefaultContainerExecutor doesn't log stderr from container launch

[ https://issues.apache.org/jira/browse/YARN-459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13714225#comment-13714225 ] Jian He commented on YARN-459: -- This should be fixed along with YARN-814

[jira] [Commented] (YARN-926) ContainerManagerProtcol APIs should take in requests for multiple containers

[ https://issues.apache.org/jira/browse/YARN-926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13714251#comment-13714251 ] Jian He commented on YARN-926: -- the findbug -1 is reporting SerializedException is not derived

[jira] [Commented] (YARN-926) ContainerManagerProtcol APIs should take in requests for multiple containers

[ https://issues.apache.org/jira/browse/YARN-926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13716687#comment-13716687 ] Jian He commented on YARN-926: -- bq. Otherwise, all the callers of them need to be modified,

[jira] [Updated] (YARN-926) ContainerManagerProtcol APIs should take in requests for multiple containers

[ https://issues.apache.org/jira/browse/YARN-926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-926: - Attachment: YARN-926.4.patch ContainerManagerProtcol APIs should take in requests for multiple containers

[jira] [Updated] (YARN-926) ContainerManagerProtcol APIs should take in requests for multiple containers

[ https://issues.apache.org/jira/browse/YARN-926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-926: - Attachment: YARN-926.5.patch New patch with a minor fix ContainerManagerProtcol APIs should take

[jira] [Updated] (YARN-926) ContainerManagerProtcol APIs should take in requests for multiple containers

[ https://issues.apache.org/jira/browse/YARN-926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-926: - Attachment: YARN-926.8.patch Uploaded a new patch fixing the find bug -1.

[jira] [Resolved] (YARN-564) Job history logs do not log anything when JVM fails to start

[ https://issues.apache.org/jira/browse/YARN-564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He resolved YARN-564. -- Resolution: Fixed Assignee: Jian He Job history logs do not log anything when JVM fails to start

[jira] [Commented] (YARN-564) Job history logs do not log anything when JVM fails to start

[ https://issues.apache.org/jira/browse/YARN-564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13718642#comment-13718642 ] Jian He commented on YARN-564: -- This was fixed along with YARN-814 reproduced as mentioned

[jira] [Commented] (YARN-926) ContainerManagerProtcol APIs should take in requests for multiple containers

[ https://issues.apache.org/jira/browse/YARN-926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13718698#comment-13718698 ] Jian He commented on YARN-926: -- I also tried, it should work. can you do mvn clean

[jira] [Updated] (YARN-688) Containers not cleaned up when NM received SHUTDOWN event from NodeStatusUpdater

[ https://issues.apache.org/jira/browse/YARN-688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-688: - Attachment: YARN-688.4.patch updated patch Containers not cleaned up when NM received SHUTDOWN

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