Abstract

It is common to deploy multiple workloads in one cluster to achieve high resource utilization, which tends to bring more resource contentions and performance interferences. If the allocable resources cannot satisfy the resource requirements of a task, the task should wait for resources, significantly increasing its scheduling latency. The inappropriate resource requirements may make a running task become a swollen task or a straggler task, which makes many allocated resources underutilized or the task be processed slowly. Therefore, how to guarantee the QoS of various services in the mixed workload deployment cluster is a challenge. Existing solutions preempt the resources from batch jobs to guarantee the resource requirements of latency-sensitive tasks without taking into account the underutilized resources in swollen tasks, which inevitably compromises the performance of batch jobs. Thus, we try to meet the resource requirements of newly incoming latency-sensitive tasks and straggler tasks with the underutilized resources instead of directly preempting the resources of batch jobs. This paper presents CERES, which tries to ensure the QoS of latency-sensitive services and reduce the performance impact on batch jobs. Firstly, CERES periodically screens out swollen tasks from batch jobs and straggler tasks from latency-sensitive services. Secondly, CERES reclaims resources from the swollen tasks and even preempts resources from common batch tasks when the idle resources in the cluster cannot meet the resource requirements of newly incoming latency-sensitive tasks and the straggler tasks. If there are sufficient allocable resources in the cluster, CERES expands the resources of the straggler tasks. We have implemented CERES based on Hadoop YARN and conducted comprehensive experiments. The results show that compared with the state-of-the-art approach, CERES can decrease the task completion time of latency-sensitive services by 20.77%, reduce performance losses to batch jobs by 15.46%, and improve the cluster resource utilization by 27.06%.

Full Text
Paper version not known

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.