[jira] [Commented] (YARN-6050) AMs can't be scheduled on racks or nodes

[ https://issues.apache.org/jira/browse/YARN-6050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15810963#comment-15810963 ] Wangda Tan commented on YARN-6050: -- [~rkanter], thanks for explanation. I'm agree with most of your

[jira] [Commented] (YARN-6074) FlowRunEntity does not deserialize long values in efficient way.

[ https://issues.apache.org/jira/browse/YARN-6074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15810953#comment-15810953 ] Rohith Sharma K S commented on YARN-6074: - bq. I think this can go in trunk. Right ? Yup.. Need to

[jira] [Commented] (YARN-6074) FlowRunEntity does not deserialize long values in efficient way.

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

[jira] [Commented] (YARN-6074) FlowRunEntity does not deserialize long values in efficient way.

[ https://issues.apache.org/jira/browse/YARN-6074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15810884#comment-15810884 ] Varun Saxena commented on YARN-6074: I think this can go in trunk. Right ? > FlowRunEntity does not

[jira] [Commented] (YARN-6060) Linux container executor fails to run container on directories mounted as noexec

[ https://issues.apache.org/jira/browse/YARN-6060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15810878#comment-15810878 ] Varun Vasudev commented on YARN-6060: - [~miklos.szeg...@cloudera.com] - the patch attached will make

[jira] [Updated] (YARN-6074) FlowRunEntity does not deserialize long values in efficient way.

[ https://issues.apache.org/jira/browse/YARN-6074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-6074: Attachment: YARN-6074.patch Updated patch by type casting to Number and getting long value.

[jira] [Created] (YARN-6074) FlowRunEntity does not deserialize long values in efficient way.

Rohith Sharma K S created YARN-6074: --- Summary: FlowRunEntity does not deserialize long values in efficient way. Key: YARN-6074 URL: https://issues.apache.org/jira/browse/YARN-6074 Project: Hadoop

[jira] [Updated] (YARN-6072) RM unable to start in secure mode

[ https://issues.apache.org/jira/browse/YARN-6072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-6072: --- Affects Version/s: 3.0.0-alpha2 2.8.0 > RM unable to start in secure

[jira] [Commented] (YARN-6072) RM unable to start in secure mode

[ https://issues.apache.org/jira/browse/YARN-6072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15810834#comment-15810834 ] Sunil G commented on YARN-6072: --- + [~kasha] [~jianhe] too. > RM unable to start in secure mode >

[jira] [Commented] (YARN-5709) Cleanup leader election configs and pluggability

[ https://issues.apache.org/jira/browse/YARN-5709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15810832#comment-15810832 ] Sunil G commented on YARN-5709: --- Looks like EmbeddedElector is started earlier to AdminService and causing

[jira] [Updated] (YARN-6073) Misuse of format specifier in Preconditions.checkArgument

[ https://issues.apache.org/jira/browse/YARN-6073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuanbo Liu updated YARN-6073: - Attachment: YARN-6073.001.patch upload v1 patch for this JIRA. > Misuse of format specifier in

[jira] [Assigned] (YARN-6073) Misuse of format specifier in Preconditions.checkArgument

[ https://issues.apache.org/jira/browse/YARN-6073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuanbo Liu reassigned YARN-6073: Assignee: Yuanbo Liu > Misuse of format specifier in Preconditions.checkArgument >

[jira] [Updated] (YARN-3774) ZKRMStateStore should use Curator 3.0 and avail CuratorOp

[ https://issues.apache.org/jira/browse/YARN-3774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-3774: --- Description: YARN-2716 changes ZKRMStateStore to use Curator. Transactions added there are

[jira] [Updated] (YARN-3774) ZKRMStateStore should use Curator 3.0 and avail CuratorOp

[ https://issues.apache.org/jira/browse/YARN-3774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-3774: --- Target Version/s: 3.0.0-alpha2 (was: ) > ZKRMStateStore should use Curator 3.0 and avail

[jira] [Updated] (YARN-3774) ZKRMStateStore should use Curator 3.0 and avail CuratorOp

[ https://issues.apache.org/jira/browse/YARN-3774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-3774: --- Issue Type: Improvement (was: Bug) > ZKRMStateStore should use Curator 3.0 and avail

[jira] [Updated] (YARN-3774) ZKRMStateStore should use Curator 3.0 and avail CuratorOp

[ https://issues.apache.org/jira/browse/YARN-3774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-3774: --- Priority: Critical (was: Blocker) > ZKRMStateStore should use Curator 3.0 and avail CuratorOp

[jira] [Commented] (YARN-6073) Misuse of format specifier in Preconditions.checkArgument

[ https://issues.apache.org/jira/browse/YARN-6073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15810798#comment-15810798 ] Yongjun Zhang commented on YARN-6073: - Sure [~yuanbo], seems someone need to help to add your name to

[jira] [Commented] (YARN-6073) Misuse of format specifier in Preconditions.checkArgument

[ https://issues.apache.org/jira/browse/YARN-6073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15810780#comment-15810780 ] Yuanbo Liu commented on YARN-6073: -- This JIRA can be my good start of first patch for YARN. [~yzhangal]

[jira] [Assigned] (YARN-6072) RM unable to start in secure mode

[ https://issues.apache.org/jira/browse/YARN-6072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ajith S reassigned YARN-6072: - Assignee: Ajith S (was: Naganarasimha G R) > RM unable to start in secure mode >

[jira] [Assigned] (YARN-6072) RM unable to start in secure mode

[ https://issues.apache.org/jira/browse/YARN-6072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R reassigned YARN-6072: --- Assignee: Naganarasimha G R > RM unable to start in secure mode >

[jira] [Commented] (YARN-6068) Log aggregation get failed when NM restart even with recovery

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

[jira] [Commented] (YARN-6068) Log aggregation get failed when NM restart even with recovery

[ https://issues.apache.org/jira/browse/YARN-6068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15810560#comment-15810560 ] Varun Saxena commented on YARN-6068: Committed to trunk, branch-2 and branch-2.8 Thanks [~djp] for

[jira] [Commented] (YARN-5937) stop-yarn.sh is not able to gracefully stop node managers

[ https://issues.apache.org/jira/browse/YARN-5937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15810541#comment-15810541 ] Weiwei Yang commented on YARN-5937: --- Hello [~Naganarasimha] Thanks a lot for looking into this one, any

[jira] [Commented] (YARN-6068) Log aggregation get failed when NM restart even with recovery

[ https://issues.apache.org/jira/browse/YARN-6068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15810487#comment-15810487 ] Varun Saxena commented on YARN-6068: +1 LGTM. Will commit it shortly > Log aggregation get failed when

[jira] [Commented] (YARN-6068) Log aggregation get failed when NM restart even with recovery

[ https://issues.apache.org/jira/browse/YARN-6068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15810406#comment-15810406 ] Junping Du commented on YARN-6068: -- Mark this as blocker for 2.8 as the issue will break NM restart work

[jira] [Updated] (YARN-6068) Log aggregation get failed when NM restart even with recovery

[ https://issues.apache.org/jira/browse/YARN-6068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-6068: - Target Version/s: 2.8.0 (was: 2.8.1) > Log aggregation get failed when NM restart even with recovery >

[jira] [Updated] (YARN-6068) Log aggregation get failed when NM restart even with recovery

[ https://issues.apache.org/jira/browse/YARN-6068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-6068: - Priority: Blocker (was: Critical) > Log aggregation get failed when NM restart even with recovery >

[jira] [Created] (YARN-6073) Misuse of format specifier in Preconditions.checkArgument

Yongjun Zhang created YARN-6073: --- Summary: Misuse of format specifier in Preconditions.checkArgument Key: YARN-6073 URL: https://issues.apache.org/jira/browse/YARN-6073 Project: Hadoop YARN

[jira] [Commented] (YARN-3774) ZKRMStateStore should use Curator 3.0 and avail CuratorOp

[ https://issues.apache.org/jira/browse/YARN-3774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15809944#comment-15809944 ] Jordan Zimmerman commented on YARN-3774: FYI - this will be fixed in the next release of Curator

[jira] [Commented] (YARN-6066) Opportunistic containers minor fixes: API annotations and config parameter changes

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

[jira] [Commented] (YARN-5219) When an export var command fails in launch_container.sh, the full container launch should fail

[ https://issues.apache.org/jira/browse/YARN-5219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15809650#comment-15809650 ] Allen Wittenauer commented on YARN-5219: bq. After the export section in launch_container.sh, i

[jira] [Commented] (YARN-6066) Opportunistic containers minor fixes: API annotations and config parameter changes

[ https://issues.apache.org/jira/browse/YARN-6066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15809617#comment-15809617 ] Arun Suresh commented on YARN-6066: --- Committing this to branch-2 shortly since these changes have already

[jira] [Updated] (YARN-5219) When an export var command fails in launch_container.sh, the full container launch should fail

[ https://issues.apache.org/jira/browse/YARN-5219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-5219: -- Attachment: YARN-5219.004.patch Sorry for a lil long delay here. It fell off my radar. Yes, its correct. We can

[jira] [Commented] (YARN-6062) nodemanager memory leak

[ https://issues.apache.org/jira/browse/YARN-6062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15809326#comment-15809326 ] Rohith Sharma K S commented on YARN-6062: - It appears to be attached details are different from

[jira] [Commented] (YARN-5984) Refactor move application across queue's CS level implementation

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

[jira] [Updated] (YARN-5984) Refactor move application across queue's CS level implementation

[ https://issues.apache.org/jira/browse/YARN-5984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-5984: -- Attachment: YARN-5984.0002.patch Attaching new patch after rebase. [~leftnoteasy] [~rohithsharma] please help to

[jira] [Commented] (YARN-5988) RM unable to start in secure setup

[ https://issues.apache.org/jira/browse/YARN-5988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15809068#comment-15809068 ] Bibin A Chundatt commented on YARN-5988: [~rohithsharma] raised YARN-6072 to track the same. > RM

[jira] [Updated] (YARN-6072) RM unable to start in secure mode

[ https://issues.apache.org/jira/browse/YARN-6072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-6072: --- Attachment: hadoop-secureuser-resourcemanager-vm1.log Attaching logs for the same cc

[jira] [Created] (YARN-6072) RM unable to start in secure mode

Bibin A Chundatt created YARN-6072: -- Summary: RM unable to start in secure mode Key: YARN-6072 URL: https://issues.apache.org/jira/browse/YARN-6072 Project: Hadoop YARN Issue Type: Bug

[jira] [Comment Edited] (YARN-6062) nodemanager memory leak

[ https://issues.apache.org/jira/browse/YARN-6062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15809058#comment-15809058 ] gehaijiang edited comment on YARN-6062 at 1/8/17 9:19 AM: -- mat information:

[jira] [Commented] (YARN-6062) nodemanager memory leak

[ https://issues.apache.org/jira/browse/YARN-6062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15809058#comment-15809058 ] gehaijiang commented on YARN-6062: -- mat information: 类名称 (类ID)对象个数本身所占内存 本身加引用所占内存

[jira] [Commented] (YARN-6062) nodemanager memory leak

[ https://issues.apache.org/jira/browse/YARN-6062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15809052#comment-15809052 ] gehaijiang commented on YARN-6062: -- Already attached > nodemanager memory leak > ---

[jira] [Updated] (YARN-6062) nodemanager memory leak

[ https://issues.apache.org/jira/browse/YARN-6062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gehaijiang updated YARN-6062: - Attachment: smaps.84971.txt jstack.84971.txt jmap.84971.txt jmap、jstack、