Details
-
New Feature
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
Description
YARN is intended to be general purpose, but it is missing some features to be able to truly support long lived applications and long lived containers.
This ticket is intended to
- discuss what is needed to support long lived processes
- track the resulting JIRA.
Attachments
Issue Links
- contains
-
HADOOP-6959 Provisioning of long running Services via HOD
- Resolved
- depends upon
-
YARN-173 Page navigation support for container logs page and the logs web-service on NMs
- Open
-
YARN-624 Support gang scheduling in the AM RM protocol
- Open
-
YARN-1042 add ability to specify affinity/anti-affinity in container requests
- Open
-
YARN-1394 RM to inform AMs when a container completed due to NM going offline -planned or unplanned
- Resolved
-
YARN-611 Add an AM retry count reset window to YARN RM
- Closed
-
YARN-1111 NM containerlogs servlet can't handle logs of more than a GB
- Closed
-
YARN-2648 need mechanism for updating HDFS delegation tokens associated with container launch contexts
- Open
-
YARN-1489 [Umbrella] Work-preserving ApplicationMaster restart
- Resolved
-
YARN-913 Umbrella: Add a way to register long-lived services in a YARN cluster
- Open
-
YARN-2084 YARN to support REST APIs in AMs
- Open
-
YARN-5907 [Umbrella] [YARN-1042] add ability to specify affinity/anti-affinity in container requests
- Open
-
YARN-1105 RM or YarnClient to notify AMs if resource requests cannot be satisfied
- Open
-
YARN-326 Add multi-resource scheduling to the fair scheduler
- Closed
-
YARN-4080 Capacity planning for long running services on YARN
- Open
-
YARN-1160 allow admins to force app deployment on a specific host
- Open
-
YARN-1200 Provide a central view for rack topologies
- Resolved
-
YARN-2005 Blacklisting support for scheduling AMs
- Resolved
-
YARN-614 Separate AM failures from hardware failure or YARN error and do not count them to AM retry count
- Closed
-
YARN-445 Ability to signal containers
- Open
-
YARN-1197 Support changing resources of an allocated container
- Open
- is blocked by
-
YARN-796 Allow for (admin) labels on nodes and resource-requests
- Open
-
YARN-1041 Protocol changes for RM to bind and notify a restarted AM of existing containers
- Closed
-
YARN-3417 AM to be able to exit with a request saying "restart me with these (possibly updated) resource requirements"
- Open
-
YARN-3418 AM to be able to set/update web URL and IPC ports post-registration
- Open
- is depended upon by
-
YARN-4407 Support Resource oversubscription in YARN scheduler
- Resolved
- is related to
-
AMBARI-17353 First class support for YARN hosted services
- Open
-
YARN-3057 Need update apps' runnability when reloading allocation files for FairScheduler
- Resolved
-
YARN-2139 [Umbrella] Support for Disk as a Resource in YARN
- Open
-
YARN-2140 Add support for network IO isolation/scheduling for containers
- Open
-
YARN-679 add an entry point that can start any Yarn service
- Resolved
-
YARN-1151 Ability to configure auxiliary services from HDFS-based JAR files
- Resolved
-
SLIDER-183 Long lived application support
- Resolved
- relates to
-
YARN-5025 Container move (relocation) between nodes
- Open
-
YARN-810 Support CGroup ceiling enforcement on CPU
- Open
- requires
-
YARN-2443 Handling logs of long-running services on YARN
- Open