Joel Knighton commented on CASSANDRA-12485:

I don't have too many useful suggestions here. That branch builds and runs 
stress fine on my machines. It is clear that either the CLASSPATH isn't being 
set correctly in the cassandra-stress script (which sets it by sourcing 
cassandra.in.sh) or the stress files aren't being built (which seems very 
unlikely to me). If I were you, I would add some debugging to the scripts to 
print CLASSPATH/CASSANDRA_HOME/other variables before the final step of trying 
to run stress and see if there is something about your environment or shell 
that prevents the scripts from executing correctly. There may be a bug there, 
but it isn't one I can reproduce or have seen.

> Always require replace_address to replace existing token
> --------------------------------------------------------
>                 Key: CASSANDRA-12485
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12485
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Distributed Metadata
>            Reporter: Paulo Motta
>            Priority: Minor
>              Labels: lhf
> CASSANDRA-10134 prevented replace an existing node unless 
> {{\-Dcassandra.replace_address}} or 
> {{\-Dcassandra.allow_unsafe_replace=true}} is specified.
> We should extend this behavior to tokens, preventing a node from joining the 
> ring if another node with the same token already existing in the ring, unless 
> {{\-Dcassandra.replace_address}} or 
> {{\-Dcassandra.allow_unsafe_replace=true}} is specified in order to avoid 
> catastrophic scenarios.
> One scenario where this can easily happen is if you replace a node with 
> another node with a different IP, and after some time you restart the 
> original node by mistake. The original node will then take over the tokens of 
> the replaced node (since it has a newer gossip generation).

This message was sent by Atlassian JIRA

Reply via email to