[jira] [Updated] (YARN-1366) AM should implement Resync with the ApplicationMasterService instead of shutting down

[ https://issues.apache.org/jira/browse/YARN-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-1366: - Attachment: YARN-1366.12.patch Updating patch with below changes. 1. Making second allocate() call on resync comm

[jira] [Commented] (YARN-2242) Improve exception information on AM launch crashes

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

[jira] [Updated] (YARN-1767) Windows: Allow a way for users to augment classpath of YARN daemons

[ https://issues.apache.org/jira/browse/YARN-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1767: --- Target Version/s: 2.6.0 (was: 2.5.0) > Windows: Allow a way for users to augment classpath of

[jira] [Updated] (YARN-2032) Implement a scalable, available TimelineStore using HBase

[ https://issues.apache.org/jira/browse/YARN-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2032: --- Target Version/s: 2.6.0 (was: 2.5.0) > Implement a scalable, available TimelineStore using HB

[jira] [Updated] (YARN-2136) RMStateStore can explicitly handle store/update events when fenced

[ https://issues.apache.org/jira/browse/YARN-2136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2136: --- Target Version/s: 2.6.0 (was: 2.5.0) > RMStateStore can explicitly handle store/update events

[jira] [Updated] (YARN-1341) Recover NMTokens upon nodemanager restart

[ https://issues.apache.org/jira/browse/YARN-1341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1341: --- Target Version/s: 2.6.0 (was: 2.5.0) > Recover NMTokens upon nodemanager restart > --

[jira] [Updated] (YARN-2151) FairScheduler option for global preemption within hierarchical queues

[ https://issues.apache.org/jira/browse/YARN-2151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2151: --- Target Version/s: 2.6.0 (was: 2.5.0) > FairScheduler option for global preemption within hier

[jira] [Commented] (YARN-1515) Provide ContainerManagementProtocol#signalContainer processing a batch of signals

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

[jira] [Commented] (YARN-2229) Making ContainerId long type

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

[jira] [Updated] (YARN-2147) client lacks delegation token exception details when application submit fails

[ https://issues.apache.org/jira/browse/YARN-2147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2147: --- Target Version/s: 2.6.0 (was: 2.5.0) > client lacks delegation token exception details when a

[jira] [Updated] (YARN-2153) Ensure distributed shell work with RM work-preserving recovery

[ https://issues.apache.org/jira/browse/YARN-2153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2153: --- Target Version/s: 2.6.0 (was: 2.5.0) > Ensure distributed shell work with RM work-preserving

[jira] [Updated] (YARN-1515) Provide ContainerManagementProtocol#signalContainer processing a batch of signals

[ https://issues.apache.org/jira/browse/YARN-1515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1515: --- Target Version/s: 2.6.0 (was: 2.5.0) > Provide ContainerManagementProtocol#signalContainer pr

[jira] [Updated] (YARN-2010) RM can't transition to active if it can't recover an app attempt

[ https://issues.apache.org/jira/browse/YARN-2010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2010: --- Target Version/s: 2.6.0 (was: 2.5.0) > RM can't transition to active if it can't recover an a

[jira] [Updated] (YARN-1773) ShuffleHeader should have a format that can inform about errors

[ https://issues.apache.org/jira/browse/YARN-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1773: --- Target Version/s: 2.6.0 (was: 2.5.0) > ShuffleHeader should have a format that can inform abo

[jira] [Updated] (YARN-2000) Fix ordering of starting services inside the RM

[ https://issues.apache.org/jira/browse/YARN-2000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2000: --- Target Version/s: 2.6.0 (was: 2.5.0) > Fix ordering of starting services inside the RM >

[jira] [Updated] (YARN-2079) Recover NonAggregatingLogHandler state upon nodemanager restart

[ https://issues.apache.org/jira/browse/YARN-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2079: --- Target Version/s: 2.6.0 (was: 2.5.0) > Recover NonAggregatingLogHandler state upon nodemanage

[jira] [Updated] (YARN-2197) Add a link to YARN CHANGES.txt in the left side of doc

[ https://issues.apache.org/jira/browse/YARN-2197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2197: --- Target Version/s: 2.6.0 (was: 2.5.0) > Add a link to YARN CHANGES.txt in the left side of doc

[jira] [Updated] (YARN-1747) Better physical memory monitoring for containers

[ https://issues.apache.org/jira/browse/YARN-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1747: --- Target Version/s: 2.6.0 (was: 2.5.0) > Better physical memory monitoring for containers > ---

[jira] [Updated] (YARN-2037) Add restart support for Unmanaged AMs

[ https://issues.apache.org/jira/browse/YARN-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2037: --- Target Version/s: 2.6.0 (was: 2.5.0) > Add restart support for Unmanaged AMs > --

[jira] [Updated] (YARN-1813) Better error message for "yarn logs" when permission denied

[ https://issues.apache.org/jira/browse/YARN-1813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1813: --- Target Version/s: 2.6.0 (was: 2.5.0) > Better error message for "yarn logs" when permission d

[jira] [Commented] (YARN-2228) TimelineServer should load pseudo authentication filter when authentication = simple

[ https://issues.apache.org/jira/browse/YARN-2228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14051085#comment-14051085 ] Varun Vasudev commented on YARN-2228: - Looks good. Couple of things - 1. {noformat} -

[jira] [Updated] (YARN-2227) Move containerMgrProxy from RM's AMLaunch to get rid of issues that new client talking with old server

[ https://issues.apache.org/jira/browse/YARN-2227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2227: --- Target Version/s: 2.6.0 (was: 2.5.0) > Move containerMgrProxy from RM's AMLaunch to get rid o

[jira] [Updated] (YARN-2026) Fair scheduler : Fair share for inactive queues causes unfair allocation in some scenarios

[ https://issues.apache.org/jira/browse/YARN-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2026: --- Target Version/s: 2.6.0 (was: 2.5.0) > Fair scheduler : Fair share for inactive queues causes

[jira] [Updated] (YARN-1741) XInclude support broken for YARN ResourceManager

[ https://issues.apache.org/jira/browse/YARN-1741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1741: --- Target Version/s: 2.6.0 (was: 2.5.0) > XInclude support broken for YARN ResourceManager > ---

[jira] [Updated] (YARN-868) YarnClient should set the service address in tokens returned by getRMDelegationToken()

[ https://issues.apache.org/jira/browse/YARN-868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-868: -- Target Version/s: 2.6.0 (was: 2.5.0) > YarnClient should set the service address in tokens retur

[jira] [Updated] (YARN-570) Time strings are formated in different timezone

[ https://issues.apache.org/jira/browse/YARN-570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-570: -- Target Version/s: 2.6.0 (was: 2.5.0) > Time strings are formated in different timezone > ---

[jira] [Updated] (YARN-2034) Description for yarn.nodemanager.localizer.cache.target-size-mb is incorrect

[ https://issues.apache.org/jira/browse/YARN-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2034: --- Target Version/s: 2.6.0 (was: 2.5.0) > Description for yarn.nodemanager.localizer.cache.targe

[jira] [Updated] (YARN-1769) CapacityScheduler: Improve reservations

[ https://issues.apache.org/jira/browse/YARN-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1769: --- Target Version/s: 2.6.0 (was: 3.0.0, 2.4.0, 2.5.0) > CapacityScheduler: Improve reservations

[jira] [Updated] (YARN-2067) FairScheduler update/continuous-scheduling threads should start only when after the scheduler is started

[ https://issues.apache.org/jira/browse/YARN-2067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2067: --- Target Version/s: 2.6.0 (was: 2.5.0) > FairScheduler update/continuous-scheduling threads sho

[jira] [Updated] (YARN-2127) Move YarnUncaughtExceptionHandler into Hadoop common

[ https://issues.apache.org/jira/browse/YARN-2127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2127: --- Target Version/s: 2.6.0 (was: 2.5.0) > Move YarnUncaughtExceptionHandler into Hadoop common >

[jira] [Updated] (YARN-2162) Fair Scheduler :ability to optionally configure minResources and maxResources in terms of percentage

[ https://issues.apache.org/jira/browse/YARN-2162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2162: --- Target Version/s: 2.6.0 (was: 2.5.0) > Fair Scheduler :ability to optionally configure minRes

[jira] [Updated] (YARN-2209) Replace allocate#resync command with ApplicationMasterNotRegisteredException to indicate AM to re-register on RM restart

[ https://issues.apache.org/jira/browse/YARN-2209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2209: --- Target Version/s: 2.6.0 (was: 2.5.0) > Replace allocate#resync command with ApplicationMaster

[jira] [Updated] (YARN-2154) FairScheduler: Improve preemption to preempt only those containers that would satisfy the incoming request

[ https://issues.apache.org/jira/browse/YARN-2154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2154: --- Target Version/s: 2.6.0 (was: 2.5.0) > FairScheduler: Improve preemption to preempt only thos

[jira] [Updated] (YARN-2199) FairScheduler: Allow max-AM-share to be specified in the root queue

[ https://issues.apache.org/jira/browse/YARN-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2199: --- Target Version/s: 2.6.0 (was: 2.5.0) > FairScheduler: Allow max-AM-share to be specified in t

[jira] [Updated] (YARN-1848) Persist ClusterMetrics across RM HA transitions

[ https://issues.apache.org/jira/browse/YARN-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1848: --- Target Version/s: 2.6.0 (was: 2.5.0) > Persist ClusterMetrics across RM HA transitions >

[jira] [Updated] (YARN-2249) RM may receive container release request on AM resync before container is actually recovered

[ https://issues.apache.org/jira/browse/YARN-2249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2249: --- Target Version/s: 2.6.0 (was: 2.5.0) > RM may receive container release request on AM resync

[jira] [Updated] (YARN-1564) add some basic workflow YARN services

[ https://issues.apache.org/jira/browse/YARN-1564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1564: --- Target Version/s: 2.6.0 (was: 2.5.0) > add some basic workflow YARN services > --

[jira] [Updated] (YARN-1902) Allocation of too many containers when a second request is done with the same resource capability

[ https://issues.apache.org/jira/browse/YARN-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1902: --- Target Version/s: 2.6.0 (was: 2.5.0) > Allocation of too many containers when a second reques

[jira] [Updated] (YARN-2063) ZKRMStateStore: Better handling of operation failures

[ https://issues.apache.org/jira/browse/YARN-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2063: --- Target Version/s: 2.6.0 (was: 2.5.0) > ZKRMStateStore: Better handling of operation failures

[jira] [Updated] (YARN-1680) availableResources sent to applicationMaster in heartbeat should exclude blacklistedNodes free memory.

[ https://issues.apache.org/jira/browse/YARN-1680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1680: --- Target Version/s: 2.6.0 (was: 2.5.0) > availableResources sent to applicationMaster in heartb

[jira] [Updated] (YARN-2200) Rename related container start time to container creation time

[ https://issues.apache.org/jira/browse/YARN-2200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2200: --- Target Version/s: 2.6.0 (was: 2.5.0) > Rename related container start time to container creat

[jira] [Updated] (YARN-556) RM Restart phase 2 - Work preserving restart

[ https://issues.apache.org/jira/browse/YARN-556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-556: -- Target Version/s: 2.6.0 (was: 2.5.0) > RM Restart phase 2 - Work preserving restart > --

[jira] [Updated] (YARN-2076) Minor error in TestLeafQueue files

[ https://issues.apache.org/jira/browse/YARN-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2076: --- Target Version/s: 2.6.0 (was: 2.5.0) > Minor error in TestLeafQueue files > -

[jira] [Updated] (YARN-2035) FileSystemApplicationHistoryStore blocks RM and AHS while NN is in safemode

[ https://issues.apache.org/jira/browse/YARN-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2035: --- Target Version/s: 2.6.0 (was: 2.5.0) > FileSystemApplicationHistoryStore blocks RM and AHS wh

[jira] [Updated] (YARN-1874) Cleanup: Move RMActiveServices out of ResourceManager into its own file

[ https://issues.apache.org/jira/browse/YARN-1874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1874: --- Target Version/s: 2.6.0 (was: 2.5.0) > Cleanup: Move RMActiveServices out of ResourceManager

[jira] [Updated] (YARN-2243) Order of arguments for Preconditions.checkNotNull() is wrong in SchedulerApplicationAttempt ctor

[ https://issues.apache.org/jira/browse/YARN-2243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2243: --- Target Version/s: 2.6.0 (was: 2.5.0) > Order of arguments for Preconditions.checkNotNull() is

[jira] [Updated] (YARN-2131) Add a way to nuke the RMStateStore

[ https://issues.apache.org/jira/browse/YARN-2131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2131: --- Target Version/s: 2.6.0 (was: 2.5.0) > Add a way to nuke the RMStateStore > -

[jira] [Updated] (YARN-2045) Data persisted in NM should be versioned

[ https://issues.apache.org/jira/browse/YARN-2045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2045: --- Target Version/s: 2.6.0 (was: 2.5.0) > Data persisted in NM should be versioned > ---

[jira] [Updated] (YARN-2055) Preemption: Jobs are failing due to AMs are getting launched and killed multiple times

[ https://issues.apache.org/jira/browse/YARN-2055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2055: --- Target Version/s: 2.6.0 (was: 2.5.0) > Preemption: Jobs are failing due to AMs are getting la

[jira] [Updated] (YARN-2014) Performance: AM scaleability is 10% slower in 2.4 compared to 0.23.9

[ https://issues.apache.org/jira/browse/YARN-2014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2014: --- Target Version/s: 2.6.0 (was: 2.5.0) > Performance: AM scaleability is 10% slower in 2.4 comp

[jira] [Updated] (YARN-2038) Revisit how AMs learn of containers from previous attempts

[ https://issues.apache.org/jira/browse/YARN-2038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2038: --- Target Version/s: 2.6.0 (was: 2.5.0) > Revisit how AMs learn of containers from previous atte

[jira] [Updated] (YARN-2137) Add support for logaggregation to a path on non-default filecontext

[ https://issues.apache.org/jira/browse/YARN-2137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2137: --- Target Version/s: 2.6.0 (was: 2.5.0) > Add support for logaggregation to a path on non-defaul

[jira] [Updated] (YARN-1844) yarn.log.server.url should have a default value

[ https://issues.apache.org/jira/browse/YARN-1844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1844: --- Target Version/s: 2.6.0 (was: 2.5.0) > yarn.log.server.url should have a default value >

[jira] [Updated] (YARN-1681) When "banned.users" is not set in LCE's container-executor.cfg, submit job with user in DEFAULT_BANNED_USERS will receive unclear error message

[ https://issues.apache.org/jira/browse/YARN-1681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1681: --- Target Version/s: 2.6.0 (was: 2.5.0) > When "banned.users" is not set in LCE's container-exec

[jira] [Updated] (YARN-2157) Document YARN metrics

[ https://issues.apache.org/jira/browse/YARN-2157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2157: --- Target Version/s: 2.6.0 (was: 2.5.0) > Document YARN metrics > - > >

[jira] [Updated] (YARN-1480) RM web services getApps() accepts many more filters than ApplicationCLI "list" command

[ https://issues.apache.org/jira/browse/YARN-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1480: --- Target Version/s: 2.6.0 (was: 2.5.0) > RM web services getApps() accepts many more filters th

[jira] [Updated] (YARN-2062) Too many InvalidStateTransitionExceptions from NodeState.NEW on RM failover

[ https://issues.apache.org/jira/browse/YARN-2062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2062: --- Target Version/s: 2.6.0 (was: 2.5.0) > Too many InvalidStateTransitionExceptions from NodeSta

[jira] [Updated] (YARN-1354) Recover applications upon nodemanager restart

[ https://issues.apache.org/jira/browse/YARN-1354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1354: --- Target Version/s: 2.6.0 (was: 2.5.0) > Recover applications upon nodemanager restart > --

[jira] [Updated] (YARN-1342) Recover container tokens upon nodemanager restart

[ https://issues.apache.org/jira/browse/YARN-1342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1342: --- Target Version/s: 2.6.0 (was: 2.5.0) > Recover container tokens upon nodemanager restart > --

[jira] [Updated] (YARN-2110) TestAMRestart#testAMRestartWithExistingContainers assumes CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2110: --- Target Version/s: 2.6.0 (was: 2.5.0) > TestAMRestart#testAMRestartWithExistingContainers assu

[jira] [Updated] (YARN-1106) The RM should point the tracking url to the RM app page if its empty

[ https://issues.apache.org/jira/browse/YARN-1106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1106: --- Target Version/s: 2.6.0 (was: 3.0.0, 2.5.0) > The RM should point the tracking url to the RM

[jira] [Updated] (YARN-1408) Preemption caused Invalid State Event: ACQUIRED at KILLED and caused a task timeout for 30mins

[ https://issues.apache.org/jira/browse/YARN-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1408: --- Target Version/s: 2.6.0 (was: 2.5.0) > Preemption caused Invalid State Event: ACQUIRED at KIL

[jira] [Updated] (YARN-1856) cgroups based memory monitoring for containers

[ https://issues.apache.org/jira/browse/YARN-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1856: --- Target Version/s: 2.6.0 (was: 2.5.0) > cgroups based memory monitoring for containers > -

[jira] [Updated] (YARN-1809) Synchronize RM and Generic History Service Web-UIs

[ https://issues.apache.org/jira/browse/YARN-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1809: --- Target Version/s: 2.6.0 (was: 2.5.0) > Synchronize RM and Generic History Service Web-UIs > -

[jira] [Updated] (YARN-2242) Improve exception information on AM launch crashes

[ https://issues.apache.org/jira/browse/YARN-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-2242: Attachment: YARN-2242-070115-2.patch Add the missing period in the end of the diagnostic information. > Improve ex

[jira] [Commented] (YARN-2242) Improve exception information on AM launch crashes

[ https://issues.apache.org/jira/browse/YARN-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14051068#comment-14051068 ] Li Lu commented on YARN-2242: - Thanks [~djp]! > Improve exception information on AM launch cr

[jira] [Commented] (YARN-2242) Improve exception information on AM launch crashes

[ https://issues.apache.org/jira/browse/YARN-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14051066#comment-14051066 ] Junping Du commented on YARN-2242: -- bq. Zhijie Shen, thank you for the notification. I agr

[jira] [Commented] (YARN-2233) Implement web services to create, renew and cancel delegation tokens

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

[jira] [Updated] (YARN-2229) Making ContainerId long type

[ https://issues.apache.org/jira/browse/YARN-2229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA updated YARN-2229: - Attachment: YARN-2229.4.patch Updated a patch not to use Long.compare(long, long). > Making Conta

[jira] [Commented] (YARN-1366) AM should implement Resync with the ApplicationMasterService instead of shutting down

[ https://issues.apache.org/jira/browse/YARN-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14051049#comment-14051049 ] Jian He commented on YARN-1366: --- add java doc for AMRMClient#allocate(). should be enough. bq

[jira] [Commented] (YARN-2229) Making ContainerId long type

[ https://issues.apache.org/jira/browse/YARN-2229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14051045#comment-14051045 ] Tsuyoshi OZAWA commented on YARN-2229: -- Thanks you, Jian. I found that Long.compare(lo

[jira] [Commented] (YARN-2242) Improve exception information on AM launch crashes

[ https://issues.apache.org/jira/browse/YARN-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14051019#comment-14051019 ] Junping Du commented on YARN-2242: -- Patch looks good to me overall. Some minor fix is miss

[jira] [Commented] (YARN-1366) AM should implement Resync with the ApplicationMasterService instead of shutting down

[ https://issues.apache.org/jira/browse/YARN-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14051013#comment-14051013 ] Rohith commented on YARN-1366: -- bq. can you add some documentation about this Shall I add in

[jira] [Commented] (YARN-2229) Making ContainerId long type

[ https://issues.apache.org/jira/browse/YARN-2229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14050990#comment-14050990 ] Jian He commented on YARN-2229: --- it failed with cannot find symbol for this method "Long.com

[jira] [Commented] (YARN-1366) AM should implement Resync with the ApplicationMasterService instead of shutting down

[ https://issues.apache.org/jira/browse/YARN-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14050978#comment-14050978 ] Bikas Saha commented on YARN-1366: -- Does a null response make sense for the user? > AM sh

[jira] [Commented] (YARN-1366) AM should implement Resync with the ApplicationMasterService instead of shutting down

[ https://issues.apache.org/jira/browse/YARN-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14050977#comment-14050977 ] Jian He commented on YARN-1366: --- bq. in which case the returned allocate response should be n

[jira] [Commented] (YARN-1366) AM should implement Resync with the ApplicationMasterService instead of shutting down

[ https://issues.apache.org/jira/browse/YARN-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14050975#comment-14050975 ] Jian He commented on YARN-1366: --- bq. Should we make a second call to allocate (after re-regis

[jira] [Commented] (YARN-1366) AM should implement Resync with the ApplicationMasterService instead of shutting down

[ https://issues.apache.org/jira/browse/YARN-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14050965#comment-14050965 ] Bikas Saha commented on YARN-1366: -- Why are we returning the old allocateResponse to the u

[jira] [Commented] (YARN-2229) Making ContainerId long type

[ https://issues.apache.org/jira/browse/YARN-2229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14050961#comment-14050961 ] Tsuyoshi OZAWA commented on YARN-2229: -- [~jianhe], can you check whether trunk code wi

[jira] [Commented] (YARN-2069) Add cross-user preemption within CapacityScheduler's leaf-queue

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

[jira] [Commented] (YARN-2229) Making ContainerId long type

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

[jira] [Updated] (YARN-2229) Making ContainerId long type

[ https://issues.apache.org/jira/browse/YARN-2229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA updated YARN-2229: - Attachment: YARN-2229.3.patch > Making ContainerId long type > > >

[jira] [Commented] (YARN-1366) AM should implement Resync with the ApplicationMasterService instead of shutting down

[ https://issues.apache.org/jira/browse/YARN-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14050913#comment-14050913 ] Jian He commented on YARN-1366: --- looks good, +1 > AM should implement Resync with the Applic

[jira] [Updated] (YARN-2069) Add cross-user preemption within CapacityScheduler's leaf-queue

[ https://issues.apache.org/jira/browse/YARN-2069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal updated YARN-2069: Attachment: YARN-2069-trunk-3.patch Rebasing and Updating the patch. Thanks, Mayank > Add cross-us

[jira] [Updated] (YARN-2249) RM may receive container release request on AM resync before container is actually recovered

[ https://issues.apache.org/jira/browse/YARN-2249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-2249: -- Summary: RM may receive container release request on AM resync before container is actually recovered (was: AM

[jira] [Created] (YARN-2249) AM resync may send container release request before container is actually recovered

Jian He created YARN-2249: - Summary: AM resync may send container release request before container is actually recovered Key: YARN-2249 URL: https://issues.apache.org/jira/browse/YARN-2249 Project: Hadoop YAR

[jira] [Updated] (YARN-2249) AM resync may send container release request before container is actually recovered

[ https://issues.apache.org/jira/browse/YARN-2249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-2249: -- Description: AM resync on RM restart will send outstanding resource requests, container release list etc. back t

[jira] [Updated] (YARN-2229) Making ContainerId long type

[ https://issues.apache.org/jira/browse/YARN-2229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA updated YARN-2229: - Attachment: (was: YARN-2229.3.patch) > Making ContainerId long type >

[jira] [Commented] (YARN-2242) Improve exception information on AM launch crashes

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

[jira] [Commented] (YARN-2242) Improve exception information on AM launch crashes

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

[jira] [Commented] (YARN-2022) Preempting an Application Master container can be kept as least priority when multiple applications are marked for preemption by ProportionalCapacityPreemptionPolicy

[ https://issues.apache.org/jira/browse/YARN-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14050784#comment-14050784 ] Hudson commented on YARN-2022: -- SUCCESS: Integrated in Hadoop-trunk-Commit #5813 (See [https:

[jira] [Updated] (YARN-2242) Improve exception information on AM launch crashes

[ https://issues.apache.org/jira/browse/YARN-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-2242: Attachment: YARN-2242-070115-1.patch Better interface design for the private verification function on diagnostic in

[jira] [Updated] (YARN-2242) Improve exception information on AM launch crashes

[ https://issues.apache.org/jira/browse/YARN-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-2242: Attachment: YARN-2242-070115.patch Hi [~djp], in this new patch I modified an existing unit test, on testing alloca

[jira] [Commented] (YARN-2232) ClientRMService doesn't allow delegation token owner to cancel their own token in secure mode

[ https://issues.apache.org/jira/browse/YARN-2232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14050753#comment-14050753 ] Hudson commented on YARN-2232: -- SUCCESS: Integrated in Hadoop-trunk-Commit #5812 (See [https:

[jira] [Commented] (YARN-2232) ClientRMService doesn't allow delegation token owner to cancel their own token in secure mode

[ https://issues.apache.org/jira/browse/YARN-2232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14050738#comment-14050738 ] Vinod Kumar Vavilapalli commented on YARN-2232: --- Looks good, +1. Checking thi

[jira] [Assigned] (YARN-2248) Capacity Scheduler changes for moving apps between queues

[ https://issues.apache.org/jira/browse/YARN-2248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli reassigned YARN-2248: - Assignee: Janos Matyas [~matyix], tx for opening this. Assigning it to you

[jira] [Commented] (YARN-2248) Capacity Scheduler changes for moving apps between queues

[ https://issues.apache.org/jira/browse/YARN-2248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14050729#comment-14050729 ] Vinod Kumar Vavilapalli commented on YARN-2248: --- Do you mind attaching a patc

[jira] [Commented] (YARN-2241) ZKRMStateStore: On startup, show nicer messages if znodes already exist

[ https://issues.apache.org/jira/browse/YARN-2241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14050695#comment-14050695 ] Hudson commented on YARN-2241: -- SUCCESS: Integrated in Hadoop-trunk-Commit #5811 (See [https:

[jira] [Created] (YARN-2248) Capacity Scheduler changes for moving apps between queues

Janos Matyas created YARN-2248: -- Summary: Capacity Scheduler changes for moving apps between queues Key: YARN-2248 URL: https://issues.apache.org/jira/browse/YARN-2248 Project: Hadoop YARN Issue

[jira] [Updated] (YARN-2241) ZKRMStateStore: On startup, show nicer messages if znodes already exist

[ https://issues.apache.org/jira/browse/YARN-2241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2241: --- Summary: ZKRMStateStore: On startup, show nicer messages if znodes already exist (was: ZKRMSt

  1   2   >