You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2011/06/23 18:19:47 UTC

[jira] [Commented] (CASSANDRA-2817) Expose number of threads blocked on submitting a memtable for flush

    [ https://issues.apache.org/jira/browse/CASSANDRA-2817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13053947#comment-13053947 ] 

Jonathan Ellis commented on CASSANDRA-2817:
-------------------------------------------

Very clever solution, I like it.

Can you add "currently blocked" to statuslogger and nodetool tpstats?

> Expose number of threads blocked on submitting a memtable for flush
> -------------------------------------------------------------------
>
>                 Key: CASSANDRA-2817
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2817
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.7.0
>            Reporter: Sylvain Lebresne
>            Assignee: Sylvain Lebresne
>            Priority: Minor
>             Fix For: 0.7.7
>
>         Attachments: 0001-Expose-threads-blocked-on-submission-to-executor.patch
>
>
> Writes can be blocked by a thread trying to submit a memtable while the flush queue is full. While this is the expected behavior (the goal being to prevent OOMing), it is worth exposing when that happens so that people can monitor it and modify settings accordingly if that happens too often.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira