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 2016/12/13 22:22:58 UTC
[jira] [Updated] (AURORA-1829) Expose stats on preemptor BiCache
expirations
[ https://issues.apache.org/jira/browse/AURORA-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mehrdad Nurolahzade updated AURORA-1829:
----------------------------------------
Description:
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 preemptor {{BiCache}} ({{reservation_cache_size}}). We could additionally collect (a) cache expiration stats and (b) reservation entry removals in {{TaskSchedulerImpl.taskChanged()}} to monitor overall preemption effectiveness.
was:
We are currently collecting stats for the size of preemptor {{BiCache}} ({{reservation_cache_size}}). We could additionally collect cache expiration stats to monitor overall preemption effectiveness.
Currently, we have no visibility into whether reservations made by preemption are actually consumed or simply expire.
> 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
> 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 preemptor {{BiCache}} ({{reservation_cache_size}}). 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.4#6332)