On Fri, Jan 6, 2017 at 6:45 PM, Sotirios Delimanolis
wrote:
> I forgot to check nodetool gossipinfo. Still, why does the first check
> think that the address exists, but the second doesn't?
>
>
> On Friday, January 6, 2017 1:11 PM, David Berry
> wrote:
>
>
> I’ve encountered this previously wher
I forgot to check nodetool gossipinfo. Still, why does the first check think
that the address exists, but the second doesn't?
On Friday, January 6, 2017 1:11 PM, David Berry
wrote:
#yiv4782259727 #yiv4782259727 -- _filtered #yiv4782259727 {panose-1:2 4 5 3 5
4 6 3 2 4;} _filtered #yiv
I’ve encountered this previously where after removing a node, gossip info is
retained for 72 hours which doesn’t allow the IP to be reused during that
period. You can check how long gossip will retain this information using
“nodetool gossipinfo” where the epoch time will be shown with status
We had a node go down in our cluster and its disk had to be wiped. During that
time, all nodes in the cluster have restarted at least once.
We want to add the bad node back to the ring. It has the same IP/hostname. I
follow the steps here for "Adding nodes to an existing cluster."
When the proces
yeah you should async writes also you cannot neglect data size so you might
want to let us know what your data size is?
On Thu, Jan 5, 2017 at 2:57 PM, kurt Greaves wrote:
> you should try switching to async writes and then perform the test. sync
> writes won't make much difference from a sing
