cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (Commented) (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3455) Pending tasks should probably not include active tasks
Date Fri, 04 Nov 2011 17:11:51 GMT


Jonathan Ellis commented on CASSANDRA-3455:

Hmm.  The existing definition makes sense if you think of it as "not yet completed" instead
of "waiting."  Which is more useful, because otherwise you can have a bunch of executors saying
"zero pending tasks" but there is nothing to tell whether that is because the system isn't
busy or you just haven't maxed out on executor threads yet.

TLDR: splitting into getActiveTasks/getQueueSize may make sense for 1.1, but we shouldn't
break things before then.
> Pending tasks should probably not include active tasks
> ------------------------------------------------------
>                 Key: CASSANDRA-3455
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 0.8.0, 1.0.0
>            Reporter: Sylvain Lebresne
>            Assignee: Sylvain Lebresne
>            Priority: Minor
>             Fix For: 0.8.8, 1.0.3
>         Attachments: 0001-Update-pending-task-count.patch
> In our TheadExecutor JMX metrics, 'pending tasks' includes 'active tasks' (because it's
taskCount-completedTaskCount). I think this is counter-intuitive for most people (of course
you could define 'pending tasks' as the 'pending of being fully executed' but you usually
want pending to indicate if there is tasks that have to wait to be executed). Besides, I believe
the initial intention was not to have pending to include active given the following comment:
> {noformat}
>     /**
>      * Get the number of tasks waiting to be executed
>      */
>     public long getPendingTasks()
> {noformat}
> This ticket propose to fix that.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message