Export - CSV (All fields)
Export - CSV (Current fields)
YARN-1742
Fix javadoc of parameter DEFAULT_NM_MIN_HEALTHY_DISKS_FRACTION
TestRMAdminService assumes CapacityScheduler
YarnConfiguration is missing a default for yarn.nodemanager.log.retain-secondsYARN-2020
observeOnly should be checked before any preemption computation started inside containerBasedPreemptOrKill() of ProportionalCapacityPreemptionPolicy.javaYARN-1789
ApplicationSummary does not escape newlines in the app name
Fix wrong MockLocalizerStatus#equals implementation
yarn kill non-existent application is too verbose
Need to log the blacklist additions/removals when YarnSchedule#allocate
Deprecate/ mark private few methods from YarnConfiguration
Formatting the lines within 80 chars in YarnCommands.apt.vm
Cleanup: Get rid of ResourceManager#get*SecretManager() methods and use the RMContext methods instead
NodeManager should identify failed disks becoming good again
yarn client fails when RM is killed within 5s of job submission
TestRMRestart.testQueueMetricsOnRMRestart failure
Write test cases to verify that killApplication API works in RM HA
Unexpected Unregistered event at Attempt Launched state
Handle RM fail overs after the submitApplication call.
RMAdminCLI should check whether HA is enabled before executes transitionToActive/transitionToStandby
TestRM#testNMTokenSentForNormalContainer assumes CapacityScheduler
FairScheduler treats app lookup failures as ERRORs
Job stays in PREP state for long time after RM Restarts
RM HA: AM link broken if the AM is on nodes other than RM
Document the REST APIs of timeline and generic history services
Create SMAPBasedProcessTree to get PSS information
renewDelegationToken should survive RM failover
Revisit RMApp transitions from NEW on RECOVER
Reset cluster-metrics on transition to standby
Replace MemoryApplicationTimelineStore with LeveldbApplicationTimelineStore as default
Replace MemoryApplicationTimelineStore with LeveldbApplicationTimelineStore as default
Bugs around log URL
Handle RM fails over after getApplicationID() and before submitApplication().
RM logs get filled with scheduler monitor logs when we enable scheduler monitoring
Lost node list should be identify by NodeId
ApplicationClientProtocol and ApplicationHistoryProtocol should expose analogous APIs
Replace set resource change on RMNode/SchedulerNode directly with event notification.
Webservice should redirect to active RM when HA is enabled.
RM API and RM changes to handle tags for running jobsYARN-1452
Document the usage of the generic application history and the timeline data service
RM cannot write the final state of RMApp/RMAppAttempt to the application history store in the transition to the final state
Enhance CS to decouple scheduling from node heartbeats
Do not use HttpConfig.isSecure() in YARN
Application recovery throws InvalidStateTransitonException for FAILED and KILLED jobs
Make Windows client work with Linux/Unix cluster
Succeeded application remains in accepted after RM restartYARN-149
[Umbrella] ResourceManager (RM) Fail-over
AppsCompleted/AppsKilled metric is incorrect when MR job is killed with yarn application -kill
yarn application does not make any progress even when no other application is running when RM is being restarted in the background
many getFileStatus calls made from node manager for localizing a public distributed cache resource
aggregated log writer can write more log data then it says is the log length
ResourceManager can exit unexpectedly if DNS is unavailable