Details
-
New Feature
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
Reviewed
Description
Currently, there are efforts to add support for various resource-types such as disk(YARN-2139), network(YARN-2140), and HDFS bandwidth(YARN-2681). These efforts all aim to add support for a new resource type and are fairly involved efforts. In addition, once support is added, it becomes harder for users to specify the resources they need. All existing jobs have to be modified, or have to use the minimum allocation.
This ticket is a proposal to extend the YARN resource model to a more flexible model which makes it easier to support additional resource-types. It also considers the related aspect of “resource profiles” which allow users to easily specify the various resources they need for any given container.
This feature is already merged to trunk, please go to YARN-7069 for all pending items.
Attachments
Attachments
Issue Links
- is depended upon by
-
YARN-6690 Consolidate NM overallocation thresholds with ResourceTypes
- Open
-
SPARK-20327 Add CLI support for YARN custom resources, like GPUs
- Resolved
- is related to
-
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-2681 Support bandwidth enforcement for containers while reading from HDFS
- Patch Available
-
YARN-7069 [Umbrella] YARN Resource Profiles phase#2 enhancements
- Open
- is required by
-
YARN-5983 [Umbrella] Support for FPGA as a Resource in YARN
- Resolved
-
YARN-6223 [Umbrella] Natively support GPU configuration/discovery/scheduling/isolation on YARN
- Resolved
- relates to
-
YARN-6720 Support updating FPGA related constraint node label after FPGA device re-configuration
- Open
-
YARN-6589 Recover all resources when NM restart
- Resolved
-
YARN-4122 Add support for GPU as a resource
- Resolved
-
YARN-8200 Backport resource types/GPU features to branch-3.0/branch-2
- Resolved