You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Panagiotis Garefalakis (Jira)" <ji...@apache.org> on 2021/05/26 13:24:00 UTC
[jira] [Resolved] (HIVE-24537) Optimise locking in
LlapTaskSchedulerService
[ https://issues.apache.org/jira/browse/HIVE-24537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Panagiotis Garefalakis resolved HIVE-24537.
-------------------------------------------
Resolution: Fixed
> Optimise locking in LlapTaskSchedulerService
> --------------------------------------------
>
> Key: HIVE-24537
> URL: https://issues.apache.org/jira/browse/HIVE-24537
> Project: Hive
> Issue Type: Sub-task
> Components: llap
> Reporter: Rajesh Balamohan
> Assignee: Panagiotis Garefalakis
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.0.0
>
> Attachments: Screenshot 2020-12-15 at 11.41.49 AM.png
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> 1. Read lock should suffice for "notifyStarted()".
> 2. Locking in "allocateTask()" can be optimised.
> 3. Optimize preemptTasks() & preemptTasksFromMap(). This would help in reducing the codepath with writeLock. Currently, it iterates through all tasks.
>
> !Screenshot 2020-12-15 at 11.41.49 AM.png|width=847,height=446!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)