No snapshots.
I restarted the node and now the Load in ring is in sync with the disk
usage. Not sure what caused it to go out of sync. However, the Live SStable
count doesn't match exactly with the number of data files on disk.
I am going through the Cassandra code to understand what could be the
Do you have any snapshots on the nodes where you are seeing this issue?
Snapshots will link to sstables which will cause them not be deleted.
-Arindam
From: Narendra Sharma [mailto:narendra.sha...@gmail.com]
Sent: Sunday, December 15, 2013 1:15 PM
To: user@cassandra.apache.org
Subject: Cassandra
Datstax recently started offering free virtual training. You may want to
try that first:
http://www.datastax.com/what-we-offer/products-services/training/virtual-training
There are also many Cassandra meetups around the world:
http://cassandra.meetup.com/
Datstax also offers classroom training,
the cassandra-env.sh has option
JVM_OPTS="$JVM_OPTS -Xss180k"
it will give this error if you start cassandra with java 7. So increase the
value, or remove option.
Regards,
Maciej
On Mon, Dec 16, 2013 at 2:37 PM, srmore wrote:
> What is your thread stack size (xss) ? try increasing that, that
What is your thread stack size (xss) ? try increasing that, that could
help. Sometimes the limitation is imposed by the host provider (e.g.
amazon ec2 etc.)
Thanks,
Sandeep
On Mon, Dec 16, 2013 at 6:53 AM, Oleg Dulin wrote:
> Hi guys!
>
> I beleive my limits settings are correct. Here is the o
If you want sequential numbers, you can't trust distributed counters
from Cassandra. However, you could use Redis for this.
Additionally, you can also use a random UUID and only show the customer
first 6 characters -- it is unique enough...
Oleg
On 2013-12-16 09:33:39 +, Jacob Rhoden sai
Hi guys!
I beleive my limits settings are correct. Here is the output of "ulimits -a":
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i)
Artur Kronenberg openmarket.com> writes:
>
> It's been a while since I tried that but here are some things I can
> think of:
>
> * the .log.out seems wrong. Unless your cassandra commitlogs don't end
> in .log.out. I tried this locally with your script and my commitlogs get
> extracted to .l
Andrey Ilinykh gmail.com> writes:
>
>
> As someone told you this feature was added by Netflix to work with Priam
(cassandra management tool). Priam itself uses it for several months only,
so I doubt if anybody uses this feature in production. Any way, you can ping
guys working on Priam. This is
Hi Guys,
As per the subject, is there any way at all to easily associate small numbers
in systems where users traditionally associate “bug/request” tickets with short
numbers?
In this use case I imagine the requirements would be as follows:
The numbers don’t necessary need to be sequential, jus
10 matches
Mail list logo