[
https://issues.apache.org/jira/browse/CASSANDRA-12960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16074244#comment-16074244
]
ZhaoYang commented on CASSANDRA-12960:
--------------------------------------
because hints are not stored based on columnfamilies and it's based on
endpoints..
one possible way is to store a {{truncate/drop time}} for each table metadata
at each node.
when replaying hints, if hint_time older than {{truncate time}}, ignore hints
> Pending hinted hand-offs are replayed after TRUNCATE
> ----------------------------------------------------
>
> Key: CASSANDRA-12960
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12960
> Project: Cassandra
> Issue Type: Bug
> Components: Streaming and Messaging
> Environment: Cassandra 2.2.8
> Amazon Linux AMI 2016.03
> Reporter: Yuji Ito
> Priority: Minor
> Attachments: stale_data.sh
>
>
> I could read stale data after truncating a table.
> The issue happens when the truncation is executed while a node is starting.
> According to logs, pending hinted hand-offs were replayed after the
> truncation.
> *cluster*:
> - C* 2.2.8
> - a cluster has 3 nodes
> - replication_factor: 3
> *steps to reproduce* (the attached script):
> # kill a node
> # insert/update some records
> # restart the killed node
> # truncate the table (not to wait for the killed node's startup)
> # kill another node (this step isn't essential)
> # read all data
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
