[
https://issues.apache.org/jira/browse/CASSANDRA-13405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
T Jake Luciani updated CASSANDRA-13405:
---------------------------------------
Description:
The view builder for one MV is restarted when other MVs are added on the same
keyspace. There is an issue if compactions are running between these restarts
that can cause the view builder to skip data, 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).
was:
The view builder for one MV is restarted when other MVs are added on the same
keyspace. There is an issue if compactions 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).
> 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
> Components: Local Write-Read Paths
> Reporter: T Jake Luciani
> Assignee: T Jake Luciani
> Labels: materializedviews
> 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 compactions are running between these
> restarts that can cause the view builder to skip data, 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)
