Re: Does recovery continue after truncating a table?

Thanks Ben and Hiro, I've reported it at https://issues.apache.org/jira/browse/CASSANDRA-12960. I'll use `truncatehints` or DROP command after this. On Sun, Nov 27, 2016 at 12:33 PM, Ben Slater wrote: > By “undocumented limitation”, I meant “TRUNCATE” is mainly

Re: Does recovery continue after truncating a table?

By “undocumented limitation”, I meant “TRUNCATE” is mainly only used in development and testing, not production scenarios so a sufficient fix (and certainly a better than nothing fix) might be just to document that if you issue a TRUNCATE while there are still hinted hand-offs pending the hinted

Re: Does recovery continue after truncating a table?

Hi Yuji and Ben, I tried out this revised script and the same issue occurred to me, too. I think it's definitely a bug to be solved asap. >Ben What do you mean "an undocumented limitation" ? Thanks, Hiro On Sat, Nov 26, 2016 at 3:13 PM, Ben Slater wrote: > Nice

Re: Does recovery continue after truncating a table?

Nice detective work! Seems to me that it’s a best an undocumented limitation and potentially could be viewed as a bug - maybe log another JIRA? One node - there is a nodetool truncatehints command that could be used to clear out the hints (

Re: Does recovery continue after truncating a table?

Hi all, I revised the script to reproduce the issue. I think the issue happens more frequently than before. Killing another node is added to the previous script. [script] #!/bin/sh node1_ip= node2_ip= node3_ip= node2_user= node3_user= rows=1 echo "consistency quorum;" >

Re: Does recovery continue after truncating a table?

I investigated source code and logs of killed node. I guess that unexpected writes are executed when truncation is being executed. Some writes were executed after flush (the first flush) in truncation and these writes could be read. These writes were requested as MUTATION by another node for

Does recovery continue after truncating a table?

Hi, I could find stale data after truncating a table. It seems that truncating starts while recovery is being executed just after a node restarts. After the truncating finishes, recovery still continues? Is it expected? I use C* 2.2.8 and can reproduce it as below. [create table]