Export - CSV (All fields)
Export - CSV (Current fields)
YARN-8977
Remove unnecessary type casting when calling AbstractYarnScheduler#getSchedulerNodeYARN-8801
javadoc comments in docker-util.h is confusingYARN-8810
Yarn Service: discrepancy between hashcode and equals of ConfigFile
Misleading log statement in NM when max retries is -1
publish all exposed ports to random ports when using bridge network
RM UI progress column is of wrong type
Update documentation and yarn-default related to the Docker runtime
Create healthcheck REST endpoint for ATSv2
[UI2] Handle ATSv2 server down or failures cases gracefully in YARN UI v2
Support getting PreemptionMessage when using AMRMClientAsync
Improve the error message when a bind mount is not whitelisted
YARN service example is out-dated
DockerLinuxContainerRuntime prevents access to distributed cache entries on a full disk
Validate service principal format prior to launching yarn service
Document best practice for user management
Expose mutable-conf scheduler's configuration in RM /scheduler-conf endpoint
Add support for tmpfs mounts with the Docker runtime
Logging improvements for better debuggability
Add version attribute to site doc examples and quickstart
YARN Service keytab does not support s3, wasb, gs and is restricted to HDFS and local filesystem only
TestRMEmbeddedElector#testCallbackSynchronization is flakey
Yarn Service Upgrade: Support express upgrade of a service
Race condition in NM container launched after done
NodeManager metrics may return wrong negative values when NM restart
Service Upgrade: With default readiness check, the status of upgrade is reported to be successful prematurely
Carriage Return character in launch command cause node manager to become unhealthy
YARN Resource Manager is running OOM because of leak of Configuration Object
LevelDBCacheTimelineStore in ATS 1.5 leaks native memory
Container launch exception in AM log should be printed in ERROR level
CapacityScheduler should respect maximum node resource when per-queue maximum-allocation is being used.
Support bind propagation options for mounts in docker runtimeYARN-8488
YARN service/components/instances should have SUCCEEDED/FAILED states
官网代码片段错误
SchedulingRequests can be wrong when multiple containers stopped at the same time
resourceLimits may be wrongly calculated when leaf-queue is blocked in cluster with 3+ level queues
RM fails to recover finished unmanaged AM
Container-executor permission check errors cause the NM to be marked unhealthy
YARN RegistryDNS throws NPE when Kerberos tgt expires
On NodeManager container gets cleaned up before its pid file is created
Container cleanup fails while trying to delete Cgroups
New AM attempt could not retrieve previous attempt component data
YARN native service should return container if launch failed
When using custom resource type, application will fail to run due to the CapacityScheduler throws InvalidResourceRequestException(GREATER_THEN_MAX_ALLOCATION)
NPE in CapacityScheduler#tryCommit when handling allocate/reserve proposal whose allocatedOrReservedContainer is null
Yarn service conflict between restart policy and NM configuration
YARN NM: OOM error while reading back the state store on recovery
NM and service AM don't have updated status for reinitialized containers
Yarn Service Upgrade: Instance state changes from UPGRADING to READY without performing a readiness check
sleeper service fails to launch with "Authentication Required"
[DS] AM registration fails when hadoop authorization is enabled