Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (athena.apache.org: domain of fabrice.facorat@gmail.com
 designates 209.85.220.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1393929450689-7593199.post@n2.nabble.com>
References: <1393856185355-7593189.post@n2.nabble.com>
	<OF63F27D56.752FD5AC-ONC1257C91.003637CD-C1257C91.00365B93@urssaf.fr>
	<1393929450689-7593199.post@n2.nabble.com>
Date: Tue, 4 Mar 2014 15:46:02 +0100
Message-ID: 
 <CAJgLgcgSHb7P-N5jHg73xWm5T9s_-oNwD1qX_oX7V=+Msrn6DQ@mail.gmail.com>
Subject: Re: Gossip intermittently marks node as DOWN
From: Fabrice Facorat <fabrice.facorat@gmail.com>
To: user@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1

>From what I understand, this can happen when having many nodes and
vnodes by node. How many vnodes did you configure on your nodes ?

2014-03-04 11:37 GMT+01:00 Phil Luckhurst <phil.luckhurst@powerassure.com>:
> The VMs are hosted on the same ESXi server and they are just running
> Cassandra. We seem to get this happen even if the nodes appear to be idle;
> about 2 to 4 times per hour.
>
> ----
> Phil
>
>
>
> --
> View this message in context: http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Gossip-intermittently-marks-node-as-DOWN-tp7593189p7593199.html
> Sent from the cassandra-user@incubator.apache.org mailing list archive at Nabble.com.


-- 
Close the World, Open the Net
http://www.linux-wizard.net