cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wei Deng (JIRA)" <>
Subject [jira] [Created] (CASSANDRA-12186) anticompaction log message doesn't include the parent repair session id
Date Wed, 13 Jul 2016 06:48:20 GMT
Wei Deng created CASSANDRA-12186:

             Summary: anticompaction log message doesn't include the parent repair session
                 Key: CASSANDRA-12186
             Project: Cassandra
          Issue Type: Bug
          Components: Observability
            Reporter: Wei Deng
            Priority: Minor

It appears that even though incremental repair is now enabled by default post C*-3.0 (which
means at the end of each repair session, there is an anti-compaction step that needs to be
executed), we don't include the parent repair session UUID in the log message of the anti-compaction
log entries. This makes observing all activities related to an incremental repair session
to be more difficult. See the following:

DEBUG [AntiEntropyStage:1] 2016-07-13 01:57:30,956 - Got
anticompaction request AnticompactionRequest{parentRepairSession=27103de0-489d-11e6-a6d6-cd06faa0aaa2}
INFO  [CompactionExecutor:5] 2016-07-13 02:07:47,512 - Starting
anticompaction for trivial_ks.weitest on 1/[BigTableReader(path='/var/lib/cassandra/data/trivial_ks/weitest-538b07d1489b11e6a9ef61c6ff848952/mb-1-big-Data.db')]
INFO  [CompactionExecutor:5] 2016-07-13 02:07:47,513 - SSTable
fully contained in range (-9223372036854775808,-9223372036854775808], mutating repairedAt
instead of anticompacting
INFO  [CompactionExecutor:5] 2016-07-13 02:07:47,570 - Completed
anticompaction successfully

The initial submission of the anti-compaction task to the CompactionManager still has reference
to the parent repair session UUID, but subsequent anti-compaction log entries are missing
this parent repair session UUID.

This message was sent by Atlassian JIRA

View raw message