Overview
Many of you would have faced these error during nodetool repair -
Repair session 2a703be0-7722-11e5-ac24-c5a3c7c6e3cf for range (5995916511884239066,6033116056473427945] failed with error java.io.IOException: Cannot proceed on repair because a neighbor (/<node IP>) is dead: session failed.
Repair session 28c63560-7722-11e5-ac24-c5a3c7c6e3cf for range (-135025182178679597,-28481663575762586] failed with error java.io.IOException: Endpoint /<IP of node> died
and By looking at this error...
Sunday, January 31, 2016
Cassandra - Cannot proceed on repair because a neighbor is dead: session failed/Endpoint Died
Monday, January 18, 2016
Cassandra Cluster Migration to a New Cluster V2.2.4
Overview
This page describe how to migrate from an existing cluster to a new cluster. Several times we have a situations where we want to move the entire cluster to a new cluster (reason could be anything; better hardware, moving away from existing data center etc.) without taking any downtime and ensuring all data gets migrated to new cluster, we had the same requirement and we decided to go with below mentioned strategy which worked like a charm.
This whole process is online and without impacting client, Old DC...
Monday, January 11, 2016
Role Based Access Control (RBAC) Cassandra 2.2.4 Explained with Example
Overview
Cassandra has recently launced most awaiting feature "Role based access control (RBAC)" but there are very limited information available on web and people actually stuck at practicle scenarios viz.
1. How to migrate from legacy authentication to RBAC.
2. Is there any changes need to be made in cassandra.yaml file.
3. What table structure changes been made to system_auth keyspaces.
4. What about legacy table.
5. We have legacy table as well as new table also and creating a new user doesnt work.
6. What...
Subscribe to:
Posts (Atom)