[jira] [Created] (YARN-672) Consider Localizing Resources within the NM process itself in non-secure deployments

Siddharth Seth created YARN-672: --- Summary: Consider Localizing Resources within the NM process itself in non-secure deployments Key: YARN-672 URL: https://issues.apache.org/jira/browse/YARN-672

[jira] [Created] (YARN-673) Remove yarn-default.xml

Siddharth Seth created YARN-673: --- Summary: Remove yarn-default.xml Key: YARN-673 URL: https://issues.apache.org/jira/browse/YARN-673 Project: Hadoop YARN Issue Type: Improvement

[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=13656331#comment-13656331 ] Siddharth Seth commented on YARN-666: - bq. Steps to upgrade a YARN cluster: do you think

[jira] [Commented] (YARN-673) Remove yarn-default.xml

[ https://issues.apache.org/jira/browse/YARN-673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13656343#comment-13656343 ] Siddharth Seth commented on YARN-673: - The documentation will be part of the source

[jira] [Commented] (YARN-672) Consider Localizing Resources within the NM process itself in non-secure deployments

[ https://issues.apache.org/jira/browse/YARN-672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13656344#comment-13656344 ] Siddharth Seth commented on YARN-672: - bq. Should be careful while doing this. What I'd

[jira] [Commented] (YARN-615) ContainerLaunchContext.containerTokens should simply be called tokens

[ https://issues.apache.org/jira/browse/YARN-615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13656631#comment-13656631 ] Siddharth Seth commented on YARN-615: - +1. Will commit this in a bit.

[jira] [Commented] (YARN-673) Remove yarn-default.xml

[ https://issues.apache.org/jira/browse/YARN-673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13656641#comment-13656641 ] Siddharth Seth commented on YARN-673: - [~hitesh] That works as well. We can then defer

[jira] [Assigned] (YARN-628) Fix YarnException unwrapping

[ https://issues.apache.org/jira/browse/YARN-628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth reassigned YARN-628: --- Assignee: Siddharth Seth Fix YarnException unwrapping

[jira] [Updated] (YARN-628) Fix YarnException unwrapping

[ https://issues.apache.org/jira/browse/YARN-628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated YARN-628: Attachment: YARN-628.txt The patch makes the following changes - Changes

[jira] [Resolved] (YARN-669) ContainerTokens sent from the RM to NM via the AM should be a byte field

[ https://issues.apache.org/jira/browse/YARN-669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth resolved YARN-669. - Resolution: Invalid ContainerTokens sent from the RM to NM via the AM should be a byte field

[jira] [Updated] (YARN-628) Fix YarnException unwrapping

[ https://issues.apache.org/jira/browse/YARN-628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated YARN-628: Attachment: YARN-628.txt.2 Updated patch to handle client side exceptions from the RPC layer.

[jira] [Updated] (YARN-628) Fix YarnException unwrapping

[ https://issues.apache.org/jira/browse/YARN-628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated YARN-628: Attachment: YARN-628.txt Fixes the unit test failure. Fix YarnException unwrapping

[jira] [Commented] (YARN-628) Fix YarnException unwrapping

[ https://issues.apache.org/jira/browse/YARN-628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13660118#comment-13660118 ] Siddharth Seth commented on YARN-628: - I agree; mentioned that along with the first

[jira] [Commented] (YARN-628) Fix YarnException unwrapping

[ https://issues.apache.org/jira/browse/YARN-628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13660411#comment-13660411 ] Siddharth Seth commented on YARN-628: - Good catch on the javadoc. That should be fixed.

[jira] [Commented] (YARN-702) minicluster classpath construction requires user to set yarn.is.minicluster in the job conf

[ https://issues.apache.org/jira/browse/YARN-702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13662227#comment-13662227 ] Siddharth Seth commented on YARN-702: - When using the MiniCluster, users should be using

[jira] [Created] (YARN-708) Move RecordFactory classes to hadoop-yarn-api, miscellaneous fixes to the interfaces

Siddharth Seth created YARN-708: --- Summary: Move RecordFactory classes to hadoop-yarn-api, miscellaneous fixes to the interfaces Key: YARN-708 URL: https://issues.apache.org/jira/browse/YARN-708

[jira] [Updated] (YARN-708) Move RecordFactory classes to hadoop-yarn-api, miscellaneous fixes to the interfaces

[ https://issues.apache.org/jira/browse/YARN-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated YARN-708: Attachment: YARN-708.1.txt Initial patch. Submitting this for jenkins. Will update this with a move

[jira] [Updated] (YARN-708) Move RecordFactory classes to hadoop-yarn-api, miscellaneous fixes to the interfaces

[ https://issues.apache.org/jira/browse/YARN-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated YARN-708: Attachment: YARN-708_postMvScript.1.txt move_YARN_708.1.sh Move scripts and a follow

[jira] [Updated] (YARN-708) Move RecordFactory classes to hadoop-yarn-api, miscellaneous fixes to the interfaces

[ https://issues.apache.org/jira/browse/YARN-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated YARN-708: Attachment: YARN-708.full.1.txt Complete patch after using the move script and incremental patch.

[jira] [Commented] (YARN-710) Add to ser/deser methods to RecordFactory

[ https://issues.apache.org/jira/browse/YARN-710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13663479#comment-13663479 ] Siddharth Seth commented on YARN-710: - Post YARN-711, RecordFactory and Record will

[jira] [Commented] (YARN-710) Add to ser/deser methods to RecordFactory

[ https://issues.apache.org/jira/browse/YARN-710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13663536#comment-13663536 ] Siddharth Seth commented on YARN-710: - bq. Sid, what would be 'relevant' Yarn records? I

[jira] [Created] (YARN-715) TestDistributedShell and TestUnmanagedAMLauncher are failing

Siddharth Seth created YARN-715: --- Summary: TestDistributedShell and TestUnmanagedAMLauncher are failing Key: YARN-715 URL: https://issues.apache.org/jira/browse/YARN-715 Project: Hadoop YARN

[jira] [Commented] (YARN-710) Add to ser/deser methods to RecordFactory

[ https://issues.apache.org/jira/browse/YARN-710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13663649#comment-13663649 ] Siddharth Seth commented on YARN-710: - Wider base to support in terms of compatibility.

[jira] [Created] (YARN-716) Make ApplicationID immutable

Siddharth Seth created YARN-716: --- Summary: Make ApplicationID immutable Key: YARN-716 URL: https://issues.apache.org/jira/browse/YARN-716 Project: Hadoop YARN Issue Type: Task Affects

[jira] [Updated] (YARN-716) Make ApplicationID immutable

[ https://issues.apache.org/jira/browse/YARN-716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated YARN-716: Attachment: YARN-716.txt Patch to make AppId immutable, and associated changes. Includes MR changes.

[jira] [Commented] (YARN-710) Add to ser/deser methods to RecordFactory

[ https://issues.apache.org/jira/browse/YARN-710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13664384#comment-13664384 ] Siddharth Seth commented on YARN-710: - bq. Regardless of that, the ser/deser mechanism

[jira] [Commented] (YARN-710) Add to ser/deser methods to RecordFactory

[ https://issues.apache.org/jira/browse/YARN-710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13664665#comment-13664665 ] Siddharth Seth commented on YARN-710: - bq. bq. Vinod, Sid, given the discussion, are we

[jira] [Commented] (YARN-715) TestDistributedShell and TestUnmanagedAMLauncher are failing

[ https://issues.apache.org/jira/browse/YARN-715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13664883#comment-13664883 ] Siddharth Seth commented on YARN-715: - +1. Thanks Vinod.

[jira] [Created] (YARN-720) container-log4j.properties should not refer to mapreduce properties

Siddharth Seth created YARN-720: --- Summary: container-log4j.properties should not refer to mapreduce properties Key: YARN-720 URL: https://issues.apache.org/jira/browse/YARN-720 Project: Hadoop YARN

[jira] [Created] (YARN-1892) Excessive logging in RM

Siddharth Seth created YARN-1892: Summary: Excessive logging in RM Key: YARN-1892 URL: https://issues.apache.org/jira/browse/YARN-1892 Project: Hadoop YARN Issue Type: Bug

[jira] [Commented] (YARN-766) TestNodeManagerShutdown should use Shell to form the output path

[ https://issues.apache.org/jira/browse/YARN-766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13974450#comment-13974450 ] Siddharth Seth commented on YARN-766: - [~djp], The 2.x patch is only required to fix a

[jira] [Created] (YARN-2264) Race in DrainDispatcher can cause random test failures

Siddharth Seth created YARN-2264: Summary: Race in DrainDispatcher can cause random test failures Key: YARN-2264 URL: https://issues.apache.org/jira/browse/YARN-2264 Project: Hadoop YARN

[jira] [Commented] (YARN-1131) $ yarn logs should return a message log aggregation is during progress if YARN application is running

[ https://issues.apache.org/jira/browse/YARN-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13784613#comment-13784613 ] Siddharth Seth commented on YARN-1131: -- [~djp], if you don't mind, I'd like to take

[jira] [Updated] (YARN-1131) $ yarn logs should return a message log aggregation is during progress if YARN application is running

[ https://issues.apache.org/jira/browse/YARN-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated YARN-1131: - Attachment: YARN-1131.1.txt Changes in the patch Adds a YARN application status check based on

[jira] [Commented] (YARN-1131) $ yarn logs should return a message log aggregation is during progress if YARN application is running

[ https://issues.apache.org/jira/browse/YARN-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13784841#comment-13784841 ] Siddharth Seth commented on YARN-1131: -- Thanks for the review. bq. why not use

[jira] [Commented] (YARN-1131) $yarn logs command should return an appropriate error message if YARN application is still running

[ https://issues.apache.org/jira/browse/YARN-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13784850#comment-13784850 ] Siddharth Seth commented on YARN-1131: -- Will open the followup jiras. Running this

[jira] [Commented] (YARN-890) The roundup for memory values on resource manager UI is misleading

[ https://issues.apache.org/jira/browse/YARN-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13784864#comment-13784864 ] Siddharth Seth commented on YARN-890: - +1. Resources should not be rounded up. Is there

[jira] [Updated] (YARN-1131) $yarn logs command should return an appropriate error message if YARN application is still running

[ https://issues.apache.org/jira/browse/YARN-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated YARN-1131: - Attachment: YARN-1131.3.txt Updated the patch to get the tests working, also added one more test

[jira] [Commented] (YARN-1131) $yarn logs command should return an appropriate error message if YARN application is still running

[ https://issues.apache.org/jira/browse/YARN-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13785718#comment-13785718 ] Siddharth Seth commented on YARN-1131: -- If another state does get added to the

[jira] [Commented] (YARN-1274) LCE fails to run containers that don't have resources to localize

[ https://issues.apache.org/jira/browse/YARN-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13786910#comment-13786910 ] Siddharth Seth commented on YARN-1274: -- I'm in favour of chanigng the LCE as well. it

[jira] [Assigned] (YARN-1274) LCE fails to run containers that don't have resources to localize

[ https://issues.apache.org/jira/browse/YARN-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth reassigned YARN-1274: Assignee: Siddharth Seth (was: Alejandro Abdelnur) LCE fails to run containers that don't

[jira] [Updated] (YARN-1274) LCE fails to run containers that don't have resources to localize

[ https://issues.apache.org/jira/browse/YARN-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated YARN-1274: - Attachment: YARN-1274.1.txt Updated launch_container to create the app level local and log

[jira] [Updated] (YARN-1274) LCE fails to run containers that don't have resources to localize

[ https://issues.apache.org/jira/browse/YARN-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated YARN-1274: - Attachment: YARN-1274.trunk.1.txt Patch for trunk and branch-2. The previous patch applies to

[jira] [Created] (YARN-1503) Support making additional 'LocalResources' available to running containers

Siddharth Seth created YARN-1503: Summary: Support making additional 'LocalResources' available to running containers Key: YARN-1503 URL: https://issues.apache.org/jira/browse/YARN-1503 Project:

[jira] [Commented] (YARN-1503) Support making additional 'LocalResources' available to running containers

[ https://issues.apache.org/jira/browse/YARN-1503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13848111#comment-13848111 ] Siddharth Seth commented on YARN-1503: -- bq. A slightly more detailed explanation of

[jira] [Updated] (YARN-1517) AMFilterInitializer with configurable AMIpFilter

[ https://issues.apache.org/jira/browse/YARN-1517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated YARN-1517: - Assignee: Pramod Immaneni AMFilterInitializer with configurable AMIpFilter

[jira] [Created] (YARN-1664) Add a utility to retrieve the RM Principal (renewer for tokens)

Siddharth Seth created YARN-1664: Summary: Add a utility to retrieve the RM Principal (renewer for tokens) Key: YARN-1664 URL: https://issues.apache.org/jira/browse/YARN-1664 Project: Hadoop YARN

[jira] [Commented] (YARN-2698) Move getClusterNodeLabels and getNodeToLabels to YarnClient instead of AdminService

[ https://issues.apache.org/jira/browse/YARN-2698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14191562#comment-14191562 ] Siddharth Seth commented on YARN-2698: -- FWIW, this can break downstream components

[jira] [Commented] (YARN-2698) Move getClusterNodeLabels and getNodeToLabels to YarnClient instead of AdminService

[ https://issues.apache.org/jira/browse/YARN-2698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14191569#comment-14191569 ] Siddharth Seth commented on YARN-2698: -- Actually, it'll help downstream projects if

[jira] [Created] (YARN-2789) Re-instate the NodeReport.newInstance API modified in YARN-2968

Siddharth Seth created YARN-2789: Summary: Re-instate the NodeReport.newInstance API modified in YARN-2968 Key: YARN-2789 URL: https://issues.apache.org/jira/browse/YARN-2789 Project: Hadoop YARN

[jira] [Commented] (YARN-2698) Move getClusterNodeLabels and getNodeToLabels to YarnClient instead of AdminService

[ https://issues.apache.org/jira/browse/YARN-2698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14192203#comment-14192203 ] Siddharth Seth commented on YARN-2698: -- Created YARN-2789 Move getClusterNodeLabels

[jira] [Commented] (YARN-2830) Add backwords compatible ContainerId.newInstance constructor for use within Tez Local Mode

[ https://issues.apache.org/jira/browse/YARN-2830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14202758#comment-14202758 ] Siddharth Seth commented on YARN-2830: -- +1 for retaining the old newInstance method.

[jira] [Commented] (YARN-1723) AMRMClientAsync missing blacklist addition and removal functionality

[ https://issues.apache.org/jira/browse/YARN-1723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14304189#comment-14304189 ] Siddharth Seth commented on YARN-1723: -- +1. The patch looks good. Will commit after

[jira] [Updated] (YARN-1723) AMRMClientAsync missing blacklist addition and removal functionality

[ https://issues.apache.org/jira/browse/YARN-1723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated YARN-1723: - Assignee: Bartosz Ługowski AMRMClientAsync missing blacklist addition and removal functionality

[jira] [Updated] (YARN-671) Add an interface on the RM to move NMs into a maintenance state

[ https://issues.apache.org/jira/browse/YARN-671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated YARN-671: Assignee: (was: Siddharth Seth) Add an interface on the RM to move NMs into a maintenance state

[jira] [Commented] (YARN-671) Add an interface on the RM to move NMs into a maintenance state

[ https://issues.apache.org/jira/browse/YARN-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14312917#comment-14312917 ] Siddharth Seth commented on YARN-671: - The intent was to have an interface to

[jira] [Commented] (YARN-886) make APPLICATION_STOP consistent with APPLICATION_INIT

[ https://issues.apache.org/jira/browse/YARN-886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14524210#comment-14524210 ] Siddharth Seth commented on YARN-886: - [~djp] - this looks like it's still valid. START

[jira] [Updated] (YARN-1503) Support making additional 'LocalResources' available to running containers

[ https://issues.apache.org/jira/browse/YARN-1503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated YARN-1503: - Assignee: (was: Siddharth Seth) Support making additional 'LocalResources' available to

[jira] [Resolved] (YARN-575) ContainerManager APIs should be user accessible

[ https://issues.apache.org/jira/browse/YARN-575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth resolved YARN-575. - Resolution: Won't Fix Assignee: (was: Vinod Kumar Vavilapalli) Closing as Won't Fix based

[jira] [Updated] (YARN-670) Add an Exception to indicate 'Maintenance' for NMs and add this to the JavaDoc for appropriate protocols

[ https://issues.apache.org/jira/browse/YARN-670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated YARN-670: Assignee: (was: Siddharth Seth) Add an Exception to indicate 'Maintenance' for NMs and add this

[jira] [Updated] (YARN-3310) MR-279: Log info about the location of dist cache

[ https://issues.apache.org/jira/browse/YARN-3310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated YARN-3310: - Assignee: (was: Siddharth Seth) MR-279: Log info about the location of dist cache

[jira] [Resolved] (YARN-197) Add a separate log server

[ https://issues.apache.org/jira/browse/YARN-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth resolved YARN-197. - Resolution: Won't Fix Resolving due to the presence of additional services which can be used for

[jira] [Commented] (YARN-3674) YARN application disappears from view

[ https://issues.apache.org/jira/browse/YARN-3674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14549858#comment-14549858 ] Siddharth Seth commented on YARN-3674: -- Clicking on a specific queue on the scheduler

[jira] [Commented] (YARN-197) Add a separate log server

[ https://issues.apache.org/jira/browse/YARN-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14481525#comment-14481525 ] Siddharth Seth commented on YARN-197: - Yes, as long as the logs are being served out by

[jira] [Commented] (YARN-1462) AHS API and other AHS changes to handle tags for completed MR jobs

[ https://issues.apache.org/jira/browse/YARN-1462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14569648#comment-14569648 ] Siddharth Seth commented on YARN-1462: -- ApplicationReport.newInstance is used by

[jira] [Commented] (YARN-1197) Support changing resources of an allocated container

[ https://issues.apache.org/jira/browse/YARN-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14588847#comment-14588847 ] Siddharth Seth commented on YARN-1197: -- bq. I would argue that waiting for an NM-RM

[jira] [Commented] (YARN-4207) Add a non-judgemental YARN app completion status

[ https://issues.apache.org/jira/browse/YARN-4207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14955334#comment-14955334 ] Siddharth Seth commented on YARN-4207: -- [~rhaase] - thanks for taking this up. Along with the change

[jira] [Updated] (YARN-4207) Add a non-judgemental YARN app completion status

[ https://issues.apache.org/jira/browse/YARN-4207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated YARN-4207: - Assignee: Rich Haase > Add a non-judgemental YARN app completion status >

[jira] [Commented] (YARN-162) nodemanager log aggregation has scaling issues with namenode

[ https://issues.apache.org/jira/browse/YARN-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14933751#comment-14933751 ] Siddharth Seth commented on YARN-162: - Go ahead. > nodemanager log aggregation has scaling issues with

[jira] [Resolved] (YARN-4208) Support additional values for FinalApplicationStatus

[ https://issues.apache.org/jira/browse/YARN-4208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth resolved YARN-4208. -- Resolution: Duplicate Looks like [~sershe] already filed YARN-4207. Closing this as a dupe. >

[jira] [Updated] (YARN-4207) Add a non-judgemental YARN app completion status

[ https://issues.apache.org/jira/browse/YARN-4207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated YARN-4207: - Issue Type: Improvement (was: Bug) > Add a non-judgemental YARN app completion status >

[jira] [Created] (YARN-4208) Support additional values for FinalApplicationStatus

Siddharth Seth created YARN-4208: Summary: Support additional values for FinalApplicationStatus Key: YARN-4208 URL: https://issues.apache.org/jira/browse/YARN-4208 Project: Hadoop YARN Issue

[jira] [Commented] (YARN-4207) Add a non-judgemental YARN app completion status

[ https://issues.apache.org/jira/browse/YARN-4207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14907140#comment-14907140 ] Siddharth Seth commented on YARN-4207: -- cc [~vinodkv] > Add a non-judgemental YARN app completion

[jira] [Commented] (YARN-4207) Add a non-judgemental YARN app completion status

[ https://issues.apache.org/jira/browse/YARN-4207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15060611#comment-15060611 ] Siddharth Seth commented on YARN-4207: -- +1. This looks good. Thanks [~rhaase] > Add a non-judgemental

[jira] [Created] (YARN-4554) ApplicationReport.getDiagnostics does not return diagnostics from individual attempts

Siddharth Seth created YARN-4554: Summary: ApplicationReport.getDiagnostics does not return diagnostics from individual attempts Key: YARN-4554 URL: https://issues.apache.org/jira/browse/YARN-4554

[jira] [Commented] (YARN-4554) ApplicationReport.getDiagnostics does not return diagnostics from individual attempts

[ https://issues.apache.org/jira/browse/YARN-4554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15089794#comment-15089794 ] Siddharth Seth commented on YARN-4554: -- Please go ahead. Separating the diagnostics per appAttempt in

[jira] [Commented] (YARN-5193) For long running services, aggregate logs when a container completes instead of when the app completes

[ https://issues.apache.org/jira/browse/YARN-5193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15313121#comment-15313121 ] Siddharth Seth commented on YARN-5193: -- bq. I don't think long-running necessarily means low container

[jira] [Created] (YARN-5205) yarn logs for live applications does not provide log files which may have already been aggregated

Siddharth Seth created YARN-5205: Summary: yarn logs for live applications does not provide log files which may have already been aggregated Key: YARN-5205 URL: https://issues.apache.org/jira/browse/YARN-5205

[jira] [Commented] (YARN-5194) Avoid adding yarn-site to all Configuration instances created by the JVM

[ https://issues.apache.org/jira/browse/YARN-5194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15316909#comment-15316909 ] Siddharth Seth commented on YARN-5194: -- This will likely break a bunch of things - hence targeted at

[jira] [Created] (YARN-5224) Logs for a completed container are not available in the yarn logs output for a live application

Siddharth Seth created YARN-5224: Summary: Logs for a completed container are not available in the yarn logs output for a live application Key: YARN-5224 URL: https://issues.apache.org/jira/browse/YARN-5224

[jira] [Created] (YARN-5194) Avoid adding yarn-site to all Configuration instances created by the JVM

Siddharth Seth created YARN-5194: Summary: Avoid adding yarn-site to all Configuration instances created by the JVM Key: YARN-5194 URL: https://issues.apache.org/jira/browse/YARN-5194 Project: Hadoop

[jira] [Created] (YARN-5193) For long running services, aggregate logs when a container completes instead of when the app completes

Siddharth Seth created YARN-5193: Summary: For long running services, aggregate logs when a container completes instead of when the app completes Key: YARN-5193 URL:

[jira] [Commented] (YARN-5193) For long running services, aggregate logs when a container completes instead of when the app completes

[ https://issues.apache.org/jira/browse/YARN-5193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15312822#comment-15312822 ] Siddharth Seth commented on YARN-5193: -- Log rolling should help. I'm yet to try it out. Do you happen

[jira] [Commented] (YARN-5270) Solve miscellaneous issues caused by YARN-4844

[ https://issues.apache.org/jira/browse/YARN-5270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15340336#comment-15340336 ] Siddharth Seth commented on YARN-5270: -- Not sure why the NotImplementedYet exceptions are required. Is

[jira] [Created] (YARN-5297) Avoid printing a stack trace when recovering an app after the RM restarts

Siddharth Seth created YARN-5297: Summary: Avoid printing a stack trace when recovering an app after the RM restarts Key: YARN-5297 URL: https://issues.apache.org/jira/browse/YARN-5297 Project:

[jira] [Created] (YARN-4816) SystemClock API broken in 2.9.0

Siddharth Seth created YARN-4816: Summary: SystemClock API broken in 2.9.0 Key: YARN-4816 URL: https://issues.apache.org/jira/browse/YARN-4816 Project: Hadoop YARN Issue Type: Bug

[jira] [Assigned] (YARN-4816) SystemClock API broken in 2.9.0

[ https://issues.apache.org/jira/browse/YARN-4816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth reassigned YARN-4816: Assignee: Siddharth Seth > SystemClock API broken in 2.9.0 >

[jira] [Commented] (YARN-4816) SystemClock API broken in 2.9.0

[ https://issues.apache.org/jira/browse/YARN-4816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15194673#comment-15194673 ] Siddharth Seth commented on YARN-4816: -- Thanks for the review [~kasha] - committing to master and

[jira] [Updated] (YARN-4816) SystemClock API broken in 2.9.0

[ https://issues.apache.org/jira/browse/YARN-4816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated YARN-4816: - Attachment: YARN-4816.1.txt Trivial patch. Re-introduces the public constructor and marks it as

[jira] [Created] (YARN-5418) When partial log aggregation is enabled, display the list of aggregated files on the container log page

Siddharth Seth created YARN-5418: Summary: When partial log aggregation is enabled, display the list of aggregated files on the container log page Key: YARN-5418 URL:

[jira] [Created] (YARN-5738) Allow services to release/kill specific containers

Siddharth Seth created YARN-5738: Summary: Allow services to release/kill specific containers Key: YARN-5738 URL: https://issues.apache.org/jira/browse/YARN-5738 Project: Hadoop YARN Issue

[jira] [Commented] (YARN-3427) Remove deprecated methods from ResourceCalculatorProcessTree

[ https://issues.apache.org/jira/browse/YARN-3427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15947786#comment-15947786 ] Siddharth Seth commented on YARN-3427: -- >From a Tez perspective, would prefer if the methods were left

[jira] [Commented] (YARN-6509) Add a size threshold beyond which yarn logs will require a force option

[ https://issues.apache.org/jira/browse/YARN-6509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15981703#comment-15981703 ] Siddharth Seth commented on YARN-6509: -- Is the current proposal to change the default to fetch the

<    1   2   3