[jira] [Commented] (YARN-3214) Add non-exclusive node labels

[ https://issues.apache.org/jira/browse/YARN-3214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14379263#comment-14379263 ] Lohit Vijayarenu commented on YARN-3214: Thanks [~wangda] for reply. I feel

[jira] [Commented] (YARN-3214) Add non-exclusive node labels

[ https://issues.apache.org/jira/browse/YARN-3214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14378541#comment-14378541 ] Lohit Vijayarenu commented on YARN-3214: bq. (P0) A node can belong to at most one

[jira] [Commented] (YARN-2314) ContainerManagementProtocolProxy can create thousands of threads for a large cluster

[ https://issues.apache.org/jira/browse/YARN-2314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14131732#comment-14131732 ] Lohit Vijayarenu commented on YARN-2314: We hit same problem on one of our large

[jira] [Commented] (YARN-2314) ContainerManagementProtocolProxy can create thousands of threads for a large cluster

[ https://issues.apache.org/jira/browse/YARN-2314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14131920#comment-14131920 ] Lohit Vijayarenu commented on YARN-2314: Thanks [~jlowe]

[jira] [Commented] (YARN-796) Allow for (admin) labels on nodes and resource-requests

[ https://issues.apache.org/jira/browse/YARN-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14041128#comment-14041128 ] Lohit Vijayarenu commented on YARN-796: --- As [~tucu00] mentioned, label sounds closely

[jira] [Commented] (YARN-1692) ConcurrentModificationException in fair scheduler AppSchedulable

[ https://issues.apache.org/jira/browse/YARN-1692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13899506#comment-13899506 ] Lohit Vijayarenu commented on YARN-1692: +1 on the patch. Can anyone else review

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=13870908#comment-13870908 ] Lohit Vijayarenu commented on YARN-1530: Yes, proxy server inside library, but only

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=13868242#comment-13868242 ] Lohit Vijayarenu commented on YARN-1530: We might have also think about data

[jira] [Commented] (YARN-85) Allow per job log aggregation configuration

[ https://issues.apache.org/jira/browse/YARN-85?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13822192#comment-13822192 ] Lohit Vijayarenu commented on YARN-85: -- Patch looks good to me. Can anyone else also

[jira] [Resolved] (YARN-546) mapred.fairscheduler.eventlog.enabled removed from Hadoop 2.0

[ https://issues.apache.org/jira/browse/YARN-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lohit Vijayarenu resolved YARN-546. --- Resolution: Duplicate Resolving duplicate of YARN-1383 mapred.fairscheduler.eventlog.enabled

[jira] [Commented] (YARN-1383) Remove node updates from the Fair Scheduler event log

[ https://issues.apache.org/jira/browse/YARN-1383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13822210#comment-13822210 ] Lohit Vijayarenu commented on YARN-1383: On big clusters logging for each heartbeat

[jira] [Resolved] (YARN-290) Wrong cluster metrics on RM page with FairScheduler

[ https://issues.apache.org/jira/browse/YARN-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lohit Vijayarenu resolved YARN-290. --- Resolution: Duplicate Closing, duplicate of YARN-282 Wrong cluster metrics

[jira] [Commented] (YARN-1206) Container logs link is broken on RM web UI after application finished

[ https://issues.apache.org/jira/browse/YARN-1206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13769199#comment-13769199 ] Lohit Vijayarenu commented on YARN-1206: We have seen case where upon enabling log

[jira] [Updated] (YARN-305) Too many 'Node offerred to app:... messages in RM

[ https://issues.apache.org/jira/browse/YARN-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lohit Vijayarenu updated YARN-305: -- Attachment: YARN-305.2.patch Sorry, somehow missed review comments in email. These are the only

[jira] [Created] (YARN-1122) FairScheduler user-as-default-queue always defaults to 'default'

Lohit Vijayarenu created YARN-1122: -- Summary: FairScheduler user-as-default-queue always defaults to 'default' Key: YARN-1122 URL: https://issues.apache.org/jira/browse/YARN-1122 Project: Hadoop

[jira] [Updated] (YARN-1122) FairScheduler user-as-default-queue always defaults to 'default'

[ https://issues.apache.org/jira/browse/YARN-1122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lohit Vijayarenu updated YARN-1122: --- Attachment: YARN-1122.1.patch Simple patch to fix this. FairScheduler

[jira] [Updated] (YARN-305) Too many 'Node offerred to app:... messages in RM

[ https://issues.apache.org/jira/browse/YARN-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lohit Vijayarenu updated YARN-305: -- Attachment: YARN-305.1.patch Simple patch to change log level to debug and add node information.

[jira] [Updated] (YARN-305) Too many 'Node offerred to app:... messages in RM

[ https://issues.apache.org/jira/browse/YARN-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lohit Vijayarenu updated YARN-305: -- Attachment: (was: YARN-305.1.patch) Too many 'Node offerred to app:... messages in RM

[jira] [Updated] (YARN-305) Too many 'Node offerred to app:... messages in RM

[ https://issues.apache.org/jira/browse/YARN-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lohit Vijayarenu updated YARN-305: -- Attachment: YARN-305.1.patch Had generated diff from old branch. Reattaching diff.

[jira] [Created] (YARN-1032) NPE in RackResolve

Lohit Vijayarenu created YARN-1032: -- Summary: NPE in RackResolve Key: YARN-1032 URL: https://issues.apache.org/jira/browse/YARN-1032 Project: Hadoop YARN Issue Type: Bug Affects

[jira] [Commented] (YARN-1032) NPE in RackResolve

[ https://issues.apache.org/jira/browse/YARN-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13729977#comment-13729977 ] Lohit Vijayarenu commented on YARN-1032: Once we hit exception in RackResolver,

[jira] [Updated] (YARN-1032) NPE in RackResolve

[ https://issues.apache.org/jira/browse/YARN-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lohit Vijayarenu updated YARN-1032: --- Attachment: YARN-1032.1.patch Simple patch to catch NPE and return default-rack. Since it is

[jira] [Commented] (YARN-1032) NPE in RackResolve

[ https://issues.apache.org/jira/browse/YARN-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13730167#comment-13730167 ] Lohit Vijayarenu commented on YARN-1032: [~zjshen] Yes, documentation does not

[jira] [Commented] (YARN-666) [Umbrella] Support rolling upgrades in YARN

[ https://issues.apache.org/jira/browse/YARN-666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13659686#comment-13659686 ] Lohit Vijayarenu commented on YARN-666: --- This looks good. Few minor point/JIRAs

[jira] [Resolved] (YARN-356) Add YARN_NODEMANAGER_OPTS and YARN_RESOURCEMANAGER_OPTS to yarn.env

[ https://issues.apache.org/jira/browse/YARN-356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lohit Vijayarenu resolved YARN-356. --- Resolution: Invalid Add YARN_NODEMANAGER_OPTS and YARN_RESOURCEMANAGER_OPTS to yarn.env

[jira] [Resolved] (YARN-307) NodeManager should log container launch command.

[ https://issues.apache.org/jira/browse/YARN-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lohit Vijayarenu resolved YARN-307. --- Resolution: Invalid Resolving as wont invalid NodeManager should log

[jira] [Updated] (YARN-546) mapred.fairscheduler.eventlog.enabled removed from Hadoop 2.0

[ https://issues.apache.org/jira/browse/YARN-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lohit Vijayarenu updated YARN-546: -- Attachment: YARN-546.1.patch It looks like there is nothing much logged in event log and

[jira] [Commented] (YARN-451) Add more metrics to RM page

[ https://issues.apache.org/jira/browse/YARN-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13627203#comment-13627203 ] Lohit Vijayarenu commented on YARN-451: --- Tried to see if adding total number of

[jira] [Created] (YARN-502) RM crash with NPE on NODE_REMOVED event

Lohit Vijayarenu created YARN-502: - Summary: RM crash with NPE on NODE_REMOVED event Key: YARN-502 URL: https://issues.apache.org/jira/browse/YARN-502 Project: Hadoop YARN Issue Type: Bug

[jira] [Created] (YARN-451) Add more metrics to RM page

Lohit Vijayarenu created YARN-451: - Summary: Add more metrics to RM page Key: YARN-451 URL: https://issues.apache.org/jira/browse/YARN-451 Project: Hadoop YARN Issue Type: Improvement

[jira] [Created] (YARN-402) Dispatcher warn message is too late

Lohit Vijayarenu created YARN-402: - Summary: Dispatcher warn message is too late Key: YARN-402 URL: https://issues.apache.org/jira/browse/YARN-402 Project: Hadoop YARN Issue Type:

[jira] [Created] (YARN-356) Add YARN_NODEMANAGER_OPTS and YARN_RESOURCEMANAGER_OPTS to yarn.env

Lohit Vijayarenu created YARN-356: - Summary: Add YARN_NODEMANAGER_OPTS and YARN_RESOURCEMANAGER_OPTS to yarn.env Key: YARN-356 URL: https://issues.apache.org/jira/browse/YARN-356 Project: Hadoop YARN

[jira] [Created] (YARN-351) ResourceManager NPE during allocateNodeLocal

Lohit Vijayarenu created YARN-351: - Summary: ResourceManager NPE during allocateNodeLocal Key: YARN-351 URL: https://issues.apache.org/jira/browse/YARN-351 Project: Hadoop YARN Issue Type:

[jira] [Resolved] (YARN-351) ResourceManager NPE during allocateNodeLocal

[ https://issues.apache.org/jira/browse/YARN-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lohit Vijayarenu resolved YARN-351. --- Resolution: Duplicate Thanks [~sandyr]. It does looks like it is solved in YARN-335. I was

[jira] [Resolved] (YARN-287) NodeManager logs incorrect physical/virtual memory values

[ https://issues.apache.org/jira/browse/YARN-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lohit Vijayarenu resolved YARN-287. --- Resolution: Invalid Thanks for explanation. Closing as invalid NodeManager

[jira] [Updated] (YARN-324) Provide way to preserve container directories

[ https://issues.apache.org/jira/browse/YARN-324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lohit Vijayarenu updated YARN-324: -- Summary: Provide way to preserve container directories (was: Provide way to preserve )

[jira] [Created] (YARN-307) NodeManager should log container launch command.

Lohit Vijayarenu created YARN-307: - Summary: NodeManager should log container launch command. Key: YARN-307 URL: https://issues.apache.org/jira/browse/YARN-307 Project: Hadoop YARN Issue

[jira] [Commented] (YARN-307) NodeManager should log container launch command.

[ https://issues.apache.org/jira/browse/YARN-307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13542616#comment-13542616 ] Lohit Vijayarenu commented on YARN-307: --- For example I am seeing container launch

[jira] [Created] (YARN-290) Wrong cluster metrics on RM page

Lohit Vijayarenu created YARN-290: - Summary: Wrong cluster metrics on RM page Key: YARN-290 URL: https://issues.apache.org/jira/browse/YARN-290 Project: Hadoop YARN Issue Type: Bug