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

cleanup + repair generates a lot of logs

    XMLWordPrintableJSON

Details

    • Normal

    Description

      One of our node generates a lot of cassandra logs (int the 10 MB/s) and CPU usage has increased (by a factor 2-3).
      This was most probably triggered by a "nodetool snapshot" while a cleanup was already running on this node.

      An example of those logs:
      2015-12-08 09:15:17,794 INFO [ValidationExecutor:689]ColumnFamilyStore.java:1923 Spinning trying to capture released readers [...]
      2015-12-08 09:15:17,794 INFO [ValidationExecutor:689]ColumnFamilyStore.java:1924 Spinning trying to capture all readers [...]
      2015-12-08 09:15:17,795 INFO [ValidationExecutor:689]ColumnFamilyStore.java:1923 Spinning trying to capture released readers [...]
      2015-12-08 09:15:17,795 INFO [ValidationExecutor:689]ColumnFamilyStore.java:1924 Spinning trying to capture all readers [...]
      (I removed SSTableReader information because it's rather long... I can share it privately if needed)
      Note that the date has not been changed (only 1ms between logs)

      It should not generate that gigantic amount of logs

      This is probably linked to: https://issues.apache.org/jira/browse/CASSANDRA-9637

      Attachments

        Activity

          People

            marcuse Marcus Eriksson
            frousseau Fabien Rousseau
            Marcus Eriksson
            Carl Yeksigian
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: