[
https://issues.apache.org/jira/browse/CASSANDRA-10265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yuki Morishita updated CASSANDRA-10265:
---------------------------------------
Since Version: 2.2.1
So after CASSANDRA-9142, incremental repair is not working as expected due to
not running anti-compaction?
If we couldn't catch that in dtests, I think we need to fix incremental_repair
dtest as well.
> Properly deserialize PREPARE_GLOBAL_MESSAGE and update NEWS.txt about repair
> defaults in 2.2
> --------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-10265
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10265
> Project: Cassandra
> Issue Type: Bug
> Reporter: Marcus Eriksson
> Assignee: Marcus Eriksson
> Fix For: 2.2.x
>
>
> We deserialize all PREPARE_MESSAGE as non-global, meaning we don't do any
> anticompaction after incremental repairs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
