s
previously. From: Sotirios Delimanolis [mailto:sotodel...@yahoo.com]
Sent: Friday, January 6, 2017 2:38 PM
To: User
Subject: Logs appear to contradict themselves during bootstrap steps We had
a node go down in our cluster and its disk had to be wiped. During that time,
all nodes in the
rn101:~$ date -d @$((1483995662276/1000))
> Mon Jan 9 21:01:02 UTC 2017
>
> At the time we waited the 72 hour period before reusing the IP, I’ve not
> used replace_address previously.
>
>
> *From:* Sotirios Delimanolis [mailto:sotodel...@yahoo.com]
> *Sent:* Friday, January 6
Sent: Friday, January 6, 2017 2:38 PM
To: User
Subject: Logs appear to contradict themselves during bootstrap steps 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
before reusing the IP, I’ve not used
replace_address previously.
From: Sotirios Delimanolis [mailto:sotodel...@yahoo.com]
Sent: Friday, January 6, 2017 2:38 PM
To: User
Subject: Logs appear to contradict themselves during bootstrap steps
We had a node go down in our cluster and its disk had to be
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
