Re: Convert single node C* to cluster (rebalancing problem)

So now the data is evenly balanced in both nodes? Refer to the following documentation to get a better understanding of the roc_address and the broadcast_rpc_address https://www.instaclustr.com/demystifying-cassandras-broadcast_address/

Re: How to avoid flush if the data can fit into memtable

Great explanation and the blog post, Akhil. Sorry for the delayed response (somehow didn't notice the email in my inbox), but this is what I concluded as well. In addition to compression, I believe the sstable is serialized as well and the combination of both results into much smaller sstable siz

Re: Information on Cassandra

On 2017-06-01 09:09 (-0700), "Harper, Paul" wrote: > Hello All, > > I'm about 3 months into support several clusters of Cassandra databases. I > recently subscribed to this email list and I receive lots of interesting > emails most of which I don't understand. I feel like I have a pretty goo

Re: How to avoid flush if the data can fit into memtable

On 2017-05-24 17:42 (-0700), preetika tyagi wrote: > Hi, > > I'm running Cassandra with a very small dataset so that the data can exist > on memtable only. Below are my configurations: > > In jvm.options: > > -Xms4G > -Xmx4G > > In cassandra.yaml, > > memtable_cleanup_threshold: 0.50 > mem

Re: Restarting nodes and reported load

Thanks for the info, this provides a lot to go through, especially Al Tobey's guide.  I'm running java version "1.8.0_121" and using G1GC for the gc type. On Jun 1 2017, at 2:32 pm, Victor Chen wrote: Regarding mtime, I'm

Re: Convert single node C* to cluster (rebalancing problem)

I am able to get it working. I added a new node with following changes #rpc_address:0.0.0.0 rpc_address: 10.128.1.11 #rpc_broadcast_address:10.128.1.11 rpc_address was set to 0.0.0.0, (I ran into a problem previously regarding remote connection and made these changes https://stackoverflow.com/que