[
https://issues.apache.org/jira/browse/AURORA-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13883483#comment-13883483
]
Hudson commented on AURORA-122:
-------------------------------
SUCCESS: Integrated in Aurora #73 (See
[https://builds.apache.org/job/Aurora/73/])
AURORA-122: Add an abstraction for secondary indices, introduce an index on
slave host. (wfarner: rev 4efa6748c949d76ea1c118fc7b19bb2490398219)
* src/main/java/org/apache/aurora/scheduler/async/Preemptor.java
* src/main/java/org/apache/aurora/scheduler/storage/mem/MemTaskStore.java
* src/main/java/org/apache/aurora/scheduler/http/Maintenance.java
* src/test/java/org/apache/aurora/scheduler/storage/mem/MemTaskStoreTest.java
* src/main/java/org/apache/aurora/scheduler/base/Tasks.java
> Introduce a task store secondary index on slave host
> ----------------------------------------------------
>
> Key: AURORA-122
> URL: https://issues.apache.org/jira/browse/AURORA-122
> Project: Aurora
> Issue Type: Story
> Components: Reliability, Scheduler
> Reporter: Bill Farner
> Assignee: Bill Farner
> Labels: O2
>
> We've observed the {{resourceOffers}} callback taking longer than desired in
> large clusters. Timing has indicated that they take as long as 100ms
> regularly, with occasional calls taking as long as a minute. We've narrowed
> down the majority of time spent to be performing expensive task store queries
> by slave host (in {{GcExecutorLauncher}}. When lots of hosts and tasks are
> present, these calls should be considerably faster if we maintain a index on
> slave host to avoid full task store scans.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
