[
https://issues.apache.org/jira/browse/CASSANDRA-3465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13148569#comment-13148569
]
Alain RODRIGUEZ commented on CASSANDRA-3465:
--------------------------------------------
Hi, I was not able to reproduce this bug with the source built from github, so
I have no logs for you. I decided to make a new cluster with the new version of
Cassandra (1.0.2). I had exactly the same problem. So I thought it definitely
comes from my configuration. I turned off my entire cluster, removed all the
keyspaces and all the files inside the data/system directory to completly reset
the cluster.
Now it works like a charm... I don't exactly know where this problem came from.
If you're going to continue investigating, you should know I configured my
cluster by installing & configuring one EC2 instance that I cloned twice.
Before launching Cassandra on the 2 new nodes I changed there listen_address
and tokens in cassandra.yaml and rm .../data/system/Location* .../commitlog/*.
Maybe shouldn't I have used clones or should I have removed all from the system
directory directly, I don't know.
If something in my configuration was wrong I may have been noticed of it.
> Wrong counters values when RF > 1
> ---------------------------------
>
> Key: CASSANDRA-3465
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3465
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.0.0
> Environment: Amazon EC2 (cluster of 5 t1.micro), phpCassa 0.8.a.2
> Reporter: Alain RODRIGUEZ
> Assignee: Sylvain Lebresne
> Priority: Critical
> Attachments: 0001-add-debug-infos.patch, logServer0.log,
> logServer0_cl_all.log, logServer1.log, logServer1_cl_all.log, logServer2.log,
> logServer2_cl_all.log
>
>
> I have got a CF that contains many counters of some events. When I'm at RF =
> 1 and simulate 10 events, they are well counted.
> However, when I switch to a RF = 3, my counter show a wrong value that
> sometimes change when requested twice (it can return 7, then 5 instead of 10
> all the time).
> I first thought that it was a problem of CL because I seem to remember that I
> read once that I had to use CL.One for reads and writes with counters. So I
> tried with CL.One, without success...
> /*-------------------------------------------------- CODE
> -------------------------------------------------------*/
> $servers = array("ec2-xxx-xxx-xxx-xxx.eu-west-1.compute.amazonaws.com",
> "ec2-yyy-yyy-yyy-yyy.eu-west-1.compute.amazonaws.com",
> "ec2-zzz-zzz-zzz-zzz.eu-west-1.compute.amazonaws.com",
> "ec2-aaa-aaa-aaa-aaa.eu-west-1.compute.amazonaws.com",
> "ec2-bbb-bbb-bbb-bbb.eu-west-1.compute.amazonaws.com");
> $pool = new ConnectionPool("mykeyspace", $servers);
> $stats_test = new ColumnFamily($pool, 'stats_test',
> $read_consistency_level=cassandra_ConsistencyLevel::ONE,
> $write_consistency_level=cassandra_ConsistencyLevel::ONE);
>
> $time = date( 'YmdH', time());
>
> for($i=0; $i<10; $i++){
> for($c=1; $c<=3; $c++){
> $stats_test->add($c, $time.':test');
> }
> $counts = $stats_test->multiget(array(1,2,3));
> echo('Counter1: '.$counts[1][$time.':test']."\n");
> echo('Counter2: '.$counts[2][$time.':test']."\n");
> echo('Counter3: '.$counts[3][$time.':test']."\n\n");
> }
> /*-------------------------------- END OF CODE
> -------------------------------------------------------------------------*/
> /*-------------------------------------------------- OUTPUT
> ------------------------------------------------------------*/
> Counter1: 1
> Counter2: 1
> Counter3: 1
> Counter1: 2
> Counter2: 2
> Counter3: 2
> Counter1: 3
> Counter2: 3
> Counter3: 3
> Counter1: 3
> Counter2: 4
> Counter3: 4
> Counter1: 4
> Counter2: 5
> Counter3: 3
> Counter1: 5
> Counter2: 6
> Counter3: 3
> Counter1: 6
> Counter2: 7
> Counter3: 4
> Counter1: 4
> Counter2: 8
> Counter3: 7
> Counter1: 5
> Counter2: 9
> Counter3: 8
> Counter1: 8
> Counter2: 4
> Counter3: 9
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
