Details
-
Bug
-
Status: Closed
-
Critical
-
Resolution: Fixed
-
2.1.0-beta
-
None
-
Reviewed
Description
As discussed in MAPREDUCE-5261, there's a possibility that a DNS outage could lead to an unhandled exception in the ResourceManager's AsyncDispatcher, and that ultimately would cause the RM to exit. The RM should not exit during DNS hiccups.
Attachments
Attachments
Issue Links
- blocks
-
YARN-1417 RM may issue expired container tokens to AM while issuing new containers.
- Closed
- breaks
-
YARN-1795 After YARN-713, using FairScheduler can cause an InvalidToken Exception for NMTokens
- Resolved
- duplicates
-
YARN-1694 RM is shutting down when an NM is added to cluster without updating the hostname in /etc/hosts
- Resolved
-
YARN-768 RM crashes due to DNS issue
- Resolved
-
YARN-1114 Resource Manager Failure Due to Unreachable DNS
- Resolved
-
YARN-1894 RM shutdown due to java.net.UnknownHostException
- Closed
- is blocked by
-
YARN-957 Capacity Scheduler tries to reserve the memory more than what node manager reports.
- Closed
- is related to
-
MAPREDUCE-4295 RM crashes due to DNS issue
- Closed
- relates to
-
YARN-617 In unsercure mode, AM can fake resource requirements
- Closed
-
YARN-1839 Capacity scheduler preempts an AM out. AM attempt 2 fails to launch task container with SecretManager$InvalidToken: No NMToken sent
- Closed
-
MAPREDUCE-5261 TestRMContainerAllocator is exiting and failing the build
- Closed