cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-9917) MVs should validate gc grace seconds on the tables involved
Date Thu, 13 Aug 2015 21:26:46 GMT


Aleksey Yeschenko commented on CASSANDRA-9917:

Yes, CREATE MV, ALTER TABLE, ALTER MV. More generally, batchlog writes should warn if any
involved tables have extremely low gc gs - whatever extremely low actually is - with or without

That said, I have no idea what {{MIN_GC_GRACE_SECONDS}} should be. Just bringing up the issue
that batchlog is completely useless for such writes. 

> MVs should validate gc grace seconds on the tables involved
> -----------------------------------------------------------
>                 Key: CASSANDRA-9917
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Aleksey Yeschenko
>            Assignee: Paulo Motta
>              Labels: materializedviews
>             Fix For: 3.0.0 rc1
> For correctness reasons (potential resurrection of dropped values), batchlog entries
are TTLs with the lowest gc grace second of all the tables involved in a batch.
> It means that if gc gs is set to 0 in one of the tables, the batchlog entry will be dead
on arrival, and never replayed.
> We should probably warn against such LOGGED writes taking place, in general, but for
MVs, we must validate that gc gs on the base table (and on the MV table, if we should allow
altering gc gs there at all), is never set too low, or else.

This message was sent by Atlassian JIRA

View raw message