[ Rustam Aliyev ]
Hi,
After upgrading to the vnodes I created and enabled shuffle
operation as suggested. After running for a couple of hours I had to
disable it because nodes were not catching up with compactions. I
repeated this process 3 times (enable/disable).
I have 5 nodes and each
So, you're saying that deleted rows can come back even if the node is always up
or down for less than max_hint_window_in_ms, right ?
--
Cyril SCETBON
On Apr 5, 2013, at 11:59 PM, Edward Capriolo
edlinuxg...@gmail.commailto:edlinuxg...@gmail.com wrote:
There are a series of edge cases that
Because cassandra is eventually consistent, and there are many settings
QUORUM, ONE, hint windows, disk failures, cosmic rays, node joins, there
are few absolutes.
On Mon, Apr 8, 2013 at 10:15 AM, cscetbon@orange.com wrote:
So, you're saying that deleted rows can come back even if the node
Hi,
I have a use case that sounds like storing data associated with files. So, I
store them with the CF:
rowkey = (folder_id, file_id)
colname = property name (about the file corresponding to file_id)
colvalue = property value
And I have CF for manual indexing:
rowkey = (folder_id, indexed
After 2 days of endless compactions and streaming I had to stop this and
cancel shuffle. One of the nodes even complained that there's no free
disk space (grew from 30GB to 400GB). After all these problems number of
the moved tokens were less than 40 (out of 1280!).
Now, when nodes start they
You need to increase the JVM heap, cassandra picks sensible defaults if you
have enough server memory.
Reset all changed config files to default settings and make sure cassandra has
at least 4GB of JVM heap. The heap size is calculated in cassandra-env.sh.
Cheers
-
Aaron
If you create a reverse index on all column names, where the single row has a
key something like the_index and each column name is the column name that has
been used else where, you are approaching the twitter global timeline anti
pattern(™).
Basically you will end up with a hot row that has
Look in the logs for messages from the SecondaryIndexManager
starts with Submitting index build of
end with Index build of
Cheers
-
Aaron Morton
Freelance Cassandra Consultant
New Zealand
@aaronmorton
http://www.thelastpickle.com
On 7/04/2013, at 12:55 AM, Kais Ahmed
For #1 Storage Proxy (server wide) metrics are per request, so 1 in your
example. CF level metrics are per row, so 5 in your example.
Not sure what graph you were looking at in ops centre, probably best to ask on
here http://www.datastax.com/support-forums/
Cheers
-
Aaron
Do not heve any manner to limit the usage of heap by setting some attribute
in cassandra.yalm file?
2013/4/9 aaron morton aa...@thelastpickle.com
You need to increase the JVM heap, cassandra picks sensible defaults if
you have enough server memory.
Reset all changed config files to default
10 matches
Mail list logo
