You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "Mehrdad Nurolahzade (JIRA)" <ji...@apache.org> on 2017/05/04 19:09:04 UTC
[jira] [Commented] (AURORA-1829) Expose stats on preemptor BiCache
expirations
[ https://issues.apache.org/jira/browse/AURORA-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15997258#comment-15997258 ]
Mehrdad Nurolahzade commented on AURORA-1829:
---------------------------------------------
Second attempt: https://reviews.apache.org/r/58636/
> Expose stats on preemptor BiCache expirations
> ---------------------------------------------
>
> Key: AURORA-1829
> URL: https://issues.apache.org/jira/browse/AURORA-1829
> Project: Aurora
> Issue Type: Task
> Components: Scheduler
> Reporter: Mehrdad Nurolahzade
> Assignee: Mehrdad Nurolahzade
> Priority: Minor
> Labels: newbie
>
> We have no visibility into whether reservations made by preemption are actually consumed or simply expire.
> We are currently collecting stats for the size of preemption/reservation {{BiCache}}. We could additionally collect (a) cache expiration stats and (b) reservation entry removals in {{TaskSchedulerImpl.taskChanged()}} to monitor overall preemption effectiveness.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)