[jira] [Comment Edited] (CASSANDRA-7511) Commit log grows infinitely after truncate

2014-07-30 Thread Jeremiah Jordan (JIRA) 

[ 
https://issues.apache.org/jira/browse/CASSANDRA-7511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14079403#comment-14079403
 ] 

Jeremiah Jordan edited comment on CASSANDRA-7511 at 7/30/14 4:01 PM:
-

-The unit test doesn't catch the problem.  If I revert all the changes in 
ColumnFamilyStore.java but keep the others the test still passes.-

Ignore that, I had a type in my -D


was (Author: jjordan):
The unit test doesn't catch the problem.  If I revert all the changes in 
ColumnFamilyStore.java but keep the others the test still passes.

 Commit log grows infinitely after truncate
 --

 Key: CASSANDRA-7511
 URL: https://issues.apache.org/jira/browse/CASSANDRA-7511
 Project: Cassandra
  Issue Type: Bug
 Environment: CentOS 6.5, Oracle Java 7u60, C* 2.0.6, 2.0.9, including 
 earlier 1.0.* versions.
Reporter: Viktor Jevdokimov
Assignee: Benedict
Priority: Minor
  Labels: commitlog
 Fix For: 2.0.10

 Attachments: 7511-2.0-v2.txt, 7511.txt


 Commit log grows infinitely after CF truncate operation via cassandra-cli, 
 regardless CF receives writes or not thereafter.
 CF's could be non-CQL Standard and Super column type. Creation of snapshots 
 after truncate is turned off.
 Commit log may start grow promptly, may start grow later, on a few only or on 
 all nodes at once.
 Nothing special in the system log. No idea how to reproduce.
 After rolling restart commit logs are cleared and back to normal. Just 
 annoying to do rolling restart after each truncate.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Comment Edited] (CASSANDRA-7511) Commit log grows infinitely after truncate

2014-07-30 Thread Benedict (JIRA) 

[ 
https://issues.apache.org/jira/browse/CASSANDRA-7511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14079532#comment-14079532
 ] 

Benedict edited comment on CASSANDRA-7511 at 7/30/14 5:06 PM:
--

I don't have a super-strong preference. It _is_ considerably faster this way, 
but I don't really mind.

-What does bug me at the moment is that truncate is completely broken for 
user-provided timestamps. I think we should have a warning somewhere about it. 
Hinted handoff and batchlog replay will potentially break badly after a 
truncate.-

Scratch that. Was remembering a maybe-problem I realised probably wasn't a 
problem. Should stop corresponding when not working...


was (Author: benedict):
I don't have a super-strong preference. It _is_ considerably faster this way, 
but I don't really mind.

What does bug me at the moment is that truncate is completely broken for 
user-provided timestamps. I think we should have a warning somewhere about it. 
Hinted handoff and batchlog replay will potentially break badly after a 
truncate.

 Commit log grows infinitely after truncate
 --

 Key: CASSANDRA-7511
 URL: https://issues.apache.org/jira/browse/CASSANDRA-7511
 Project: Cassandra
  Issue Type: Bug
 Environment: CentOS 6.5, Oracle Java 7u60, C* 2.0.6, 2.0.9, including 
 earlier 1.0.* versions.
Reporter: Viktor Jevdokimov
Assignee: Benedict
Priority: Minor
  Labels: commitlog
 Fix For: 2.0.10

 Attachments: 7511-2.0-v2.txt, 7511.txt


 Commit log grows infinitely after CF truncate operation via cassandra-cli, 
 regardless CF receives writes or not thereafter.
 CF's could be non-CQL Standard and Super column type. Creation of snapshots 
 after truncate is turned off.
 Commit log may start grow promptly, may start grow later, on a few only or on 
 all nodes at once.
 Nothing special in the system log. No idea how to reproduce.
 After rolling restart commit logs are cleared and back to normal. Just 
 annoying to do rolling restart after each truncate.



--
This message was sent by Atlassian JIRA
(v6.2#6252)