In our case, we need to execute "unsafeAssassinateEndpoint" from
https://issues.apache.org/jira/browse/CASSANDRA-3337.How do we go about
applying the patch attached to CASSANDRA-3337? We always used the binary
distribution; never had to compile cassandra; so we are not sure of the
proper way t
On Thu, Dec 1, 2011 at 1:10 PM, huyle wrote:
> The clocks are very sync'ed between the nodes as they have ntp running
> hitting our time servers.
Maybe they weren't 3 days after the token left, which
https://issues.apache.org/jira/browse/CASSANDRA-2961 requires.
If a node sees the token you can
The clocks are very sync'ed between the nodes as they have ntp running
hitting our time servers.
Huy
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/decommissioned-nodes-still-being-gossipped-tp7051526p7051701.html
Sent from the cassandra-u...@
On Thu, Dec 1, 2011 at 12:26 PM, huyle wrote:
> Hi,
>
> We have 2 nodes have been decommissioned from the cluster running 1.0.3.
> However, the live nodes still making references to the decommissioned nodes
> 3 days after the nodes were decommissioned. Nodetool does not show the
> decommissioned
https://issues.apache.org/jira/browse/CASSANDRA-3243?
Thanks!
Huy
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/decommissioned-not-show-being-gossipped-tp7051526p7051526.html
Sent from the cassandra-u...@incubator.apache.org mailing list
