[
https://issues.apache.org/jira/browse/CASSANDRA-13405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
T Jake Luciani updated CASSANDRA-13405:
---------------------------------------
Status: Patch Available (was: Open)
Fix with test to repro.
Basically ignore the generation value...
I've also added some better debug logging to help operators and us see what's
happening.
[3.0|https://github.com/tjake/cassandra/tree/13405-3.0]
[testall|cassci.datastax.com/view/Dev/view/tjake/job/tjake-13405-3.0-testall/]
[dtest|cassci.datastax.com/view/Dev/view/tjake/job/tjake-13405-3.0-dtest/]
[3.11|https://github.com/tjake/cassandra/tree/13405-3.11]
[testall|cassci.datastax.com/view/Dev/view/tjake/job/tjake-13405-3.11-testall/]
[dtest|cassci.datastax.com/view/Dev/view/tjake/job/tjake-13405-3.11-dtest/]
> ViewBuilder can miss data due to sstable generation filter
> ----------------------------------------------------------
>
> Key: CASSANDRA-13405
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13405
> Project: Cassandra
> Issue Type: Bug
> Reporter: T Jake Luciani
> Assignee: T Jake Luciani
> Fix For: 3.0.13
>
>
> The view builder for one MV is restarted when other MVs are added on the same
> keyspace. There is an issue if compaction are running between these restarts
> that can cause the view build is lost since the builder tracks the max
> sstable generation to filter by when it starts back up.
> I don't see a need for this generation tracking across restarts, it only
> needs to be tracked during a builders life (to avoid adding in newly
> compacted data).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
