The datastax documentation was fixed after the initial confusion with
vnodes vs non-vnodes, so you should be safe to follow the procedure
described there. Make sure to set the
-Dcassandra.replace_address=address_of_dead_node JVM option (don't worry
about the initial token).
2015-09-17 21:21 GMT-03
This seems like an apt time to quote [1]:
> Remember that you get 1 point for making a backup and 10,000 points for
restoring one.
Restoring from backups is my goal.
The commonly recommended tools (tablesnap, cassandra_snapshotter) all seem
to leave the restore operation as a pretty complicated
Hi all,
Could someone please let me know if the following modeling is on the right way
?
Te requirement is to query by user_id the summarized data of
transaction_status_per_user.
-
### UDT
CREATE TYPE core_analytics.status_summary (
name text,
count int,
hexcolor t
Hi
Can the community help to confirm that
http://docs.datastax.com/en/cassandra/1.2/cassandra/operations/ops_replace_node_t.html
will work for non-vnode cluster in Cassandra 1.2.
It looks like I don't have to set the initial token for the replacement
node (but same IP) at all if I run the JVM opt
Some more info,
Looking at the Java Memory Dump file.
I see about 400 SSTableScanners - one for each of our column Families.
Each is about 200MB in size.
And (from what I can see) all of them are reading from a
"compactions_in_progress-ka-00-Data.db" file
dfile org.apache.cassandra.io.com
Hey all, I was hoping someone had a similar issue.
We're using 2.1.6 and shutdown a testbed in AWS thinking we were finished with
it,
We started it backup today and saw that only 2 of 4 nodes came up.
Seems there was a lot of compaction happening at the time it was shutdown,
cassandra tries to s
Thank you very much for pointing this out Victor. Really useful to know.
On Wed, Sep 16, 2015 at 4:55 PM, Victor Chen
wrote:
> Yes, you can examine the actual sstables in your cassandra data dir. That
> will tell you what version sstables you have on that node.
>
> You can refer to this link:
>
