Greetings,
Matt brought to my attention that I shared the document at "view only"
mode. My apologies for that. I corrected permissions and shared the
document personally with everybody, who indicated he/she would review it.
Thanks,
Oleg
On Fri, Feb 12, 2016 at 10:33 PM, oleg yusim wrote:
> Gr
hi;
we have a 12 node cluster across 2 datacenters. We are currently using
cassandra 2.1.12 version.
SNITCH : GossipingPropertyFileSnitch
When we decommissioned few nodes in a particular datacenter and observed
the following :
nodetool status shows only the live nodes in the cluster.
nodeto
On Sat, Feb 13, 2016 at 4:30 PM, Branton Davis
wrote:
> We use SizeTieredCompaction. The nodes were about 67% full and we were
> planning on adding new nodes (doubling the cluster to 6) soon.
>
Be sure to add those new nodes one at a time.
Have you checked for, and cleared, old snapshots? Snap
+1 on what Alain said, but I do think if you are high enough on a 2.1.x
(will look later) version you don't need to follow the documentation. It is
outdated. Run a full repair, the you can start incremental repairs since
the SSTables will have the metadata on them about the last repair.
Wait some
Hi,
I am testing repairs repairs -inc -par and I can see that in all my nodes
> the numbers of sstables explode to 5k from 5 sstables.
This looks like a known issue, see
https://issues.apache.org/jira/browse/CASSANDRA-10422
Make sure your version is higher than 2.1.12, 2.2.4, 3.0.1, 3.1 to avoid
Hi Brian,
Did you noticed this error: "CF 9733d050-d0ed-11e5-904a-5574a0c0fd2a was
dropped during streaming" ?
Are you dropping keyspaces or tables (old name Column Family, CF) during
the bootstrap (maybe as a client app action ?)
Or are you creating KS / CF on both DataCenters before connecting
Yes you are right Anishek. If you write with LOCAL_ONE, values will be the same.
