[
https://issues.apache.org/jira/browse/AURORA-871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Lambert updated AURORA-871:
---------------------------------
Sprint: Aurora Q4 Sprint 2
> Use optimistic locking when scheduling tasks
> --------------------------------------------
>
> Key: AURORA-871
> URL: https://issues.apache.org/jira/browse/AURORA-871
> 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
(v6.3.4#6332)
