-caf375221684 1a
UN 10.4.68.221 137.12 GB 256 50.7%
37479ec3-7b6d-4537-975c-f9d95e92ee1d 1d
UN 10.4.68.222 141.89 GB 256 52.7%
8df87657-c39b-405a-ba54-d60b577c1429 1d
--
On Wed, Jul 27, 2016 at 2:04 PM, Farzad Panahi <farzad.
k with netstats if other nodes keep connections with the
> stopped node in the CLOSE_WAIT state? And also if the problem disappears if
> you run nodetool disablegossip before stopping the node?
>
> 2016-07-26 16:54 GMT-03:00 Farzad Panahi <farzad.pan...@gmail.com>:
>
>> I am new
I am new to Cassandra and trying to figure out how the cluster behaves when
things go south.
I have a 6-node cluster, RF=3.
I stop Cassandra service on a node for a while. All nodes see the node as
DN. After a while I start the Cassandra service on DN. Interesting point is
that all other nodes
our best bet.
>
> Julien Anguenot talks a little bit about migrating his cluster to 3.0
> here:
> http://planetcassandra.org/blog/this-week-in-cassandra-3-0-in-the-wild-5132016/
>
> On Wed, Jul 20, 2016 at 4:33 PM Farzad Panahi <farzad.pan...@gmail.com>
> wrote:
>
>> H
Hi,
I am new to Cassandra and a bit confused about how versioning works here.
I have recently started working on Cassandra clusters. I want to create a
Cassandra cluster and make it ready for production but I am not sure which
version is the right one. Some people mention that the most stable
