Uploaded image for project: 'Cassandra'
  1. Cassandra
  2. CASSANDRA-2554

Move gossip heartbeats [back] to its own thread

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Normal
    • Resolution: Fixed
    • 0.7.6
    • None
    • None
    • Normal

    Description

      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.

      Attachments

        1. 2554-0.7.txt
          6 kB
          Jonathan Ellis
        2. 2554-0.8.txt
          5 kB
          Jonathan Ellis

        Activity

          People

            jbellis Jonathan Ellis
            jbellis Jonathan Ellis
            Jonathan Ellis
            Sylvain Lebresne
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: