aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Farner (JIRA)" <>
Subject [jira] [Resolved] (AURORA-871) Use optimistic locking when scheduling tasks
Date Fri, 13 Mar 2015 17:15:40 GMT


Bill Farner resolved AURORA-871.
    Resolution: Won't Fix

I suggest we hold off on this optimization until we determine whether AURORA-1158 bears sufficient

> Use optimistic locking when scheduling tasks
> --------------------------------------------
>                 Key: AURORA-871
>                 URL:
>             Project: Aurora
>          Issue Type: Task
>          Components: Scheduler
>            Reporter: Bill Farner
>            Assignee: Bill Farner
> The action of finding a resource offer that matches a task is the most compute-intensive
operation in the scheduler, and in busy clusters it can tend to dominate the global write
lock.  This has the side-effect of starving other writers, which include status updates and
user RPCs.
> Since the majority of the work done to find a matching resource offer is read-only, we
could hold only a read lock during this operation.  We should even be able to perform a weakly-consistent
read, so long as we avoid parallel scheduling of tasks within the same job.

This message was sent by Atlassian JIRA

View raw message