cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-2554) Move gossip heartbeats [back] to its own thread
Date Mon, 25 Apr 2011 17:31:03 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-2554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jonathan Ellis updated CASSANDRA-2554:
--------------------------------------

    Attachment: 2554-0.7.txt

> Move gossip heartbeats [back] to its own thread
> -----------------------------------------------
>
>                 Key: CASSANDRA-2554
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2554
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.7.0
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>             Fix For: 0.7.6
>
>         Attachments: 2554-0.7.txt
>
>
> Gossip heartbeat *really* needs to run every 1s or other nodes may mark us down. But
gossip currently shares an executor thread with other tasks.
> I see at least two of these could cause blocking: hint cleanup post-delivery and flush-expired-memtables,
both of which call forceFlush which will block if the flush queue + threads are full.
> We've run into this before (CASSANDRA-2253); we should move Gossip back to its own dedicated
executor or it will keep happening whenever someone accidentally puts something on the "shared"
executor that can block.

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

Mime
View raw message