The commitlog_total_space_in_mb was not set, I set it to avoid having the
same problem in the future.
I am aware of the over-counting problem introduced by the counters. The
point is that I use them to make statistics per hours. I can understand
having some wrong counts in the column corresponding
It sounds like the commitlog has been replayed however I have really no
idea whether this could have happened. Anyone?
2012/4/13 Alain RODRIGUEZ
> The commitlog_total_space_in_mb was not set, I set it to avoid having the
> same problem in the future.
>
> I am aware of the over-counting problem i
Thanks everybody! Appreciate it.
From: Watanabe Maki [mailto:watanabe.m...@gmail.com]
Sent: Wednesday, April 11, 2012 5:40 PM
To: user@cassandra.apache.org
Subject: Re: Initial token - newbie question (version 1.0.8)
auto_bootstrap parameter has been removed and always enabled since 1.0.
The Cassandra team is pleased to announce the release of the first release
candidate for the future Apache Cassandra 1.1.
Please first note that this is a release candidate, *not* the final release
yet.
All help in testing this release candidate will be greatly appreciated. Please
report any prob
Hi Guys,
Sorry for posting this here, but I figured there should be a lot of smart
Network/System Admins on this list which can recommend a good mailing
list/forum for questions related to networking and rack/datacenter setups.
Best,
Drew
Hello
We have 6 node cluster (cassandra 0.8.10). On one node i increase java heap
size to 6GB, and now at this node begin grows swap, but system have about
3GB of free memory:
root@6wd003:~# free
total used free sharedbuffers cached
Mem: 24733664 21702
I forgot to say that system have 24GB of phis memory
2012/4/14 ruslan usifov
> Hello
>
> We have 6 node cluster (cassandra 0.8.10). On one node i increase java
> heap size to 6GB, and now at this node begin grows swap, but system have
> about 3GB of free memory:
>
>
> root@6wd003:~# free
>
Hi!
What is the difference between 'repair' and '-pr repair'? Simple repair
touch all token ranges (for all nodes) and -pr touch only range for
which given node responsible?
On 04/12/2012 05:59 PM, Sylvain Lebresne wrote:
On Thu, Apr 12, 2012 at 4:06 PM, Frank Ng wrote:
I also noticed tha
On Sat, Apr 14, 2012 at 1:57 PM, Igor wrote:
> Hi!
>
> What is the difference between 'repair' and '-pr repair'? Simple repair
> touch all token ranges (for all nodes) and -pr touch only range for which
> given node responsible?
>
>
-pr only touches the primary range of the node. If you executes
