Jeff Jirsa commented on CASSANDRA-12296:

you still get an incorrect error message if you try and rebuild from the same 
DC using NTS from a DC that doesn't contain the keyspace. When I was testing 
this case apparently the error got masked by another keyspace which makes me 
think there may be another bug here 

Glad you found a way to trigger it with NTS (good work there). Would personally 
vote for a more generic error rather than multiple different error messages for 
each possible failure situation. [~brandon.williams] - you deal with a lot of 
end users, are you good with what he proposed ( {{Ensure this keyspace has 
replicas in the source datacentre}} )? 

> system_auth can't be rebuilt by default
> ---------------------------------------
>                 Key: CASSANDRA-12296
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12296
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Jim Witschey
>            Priority: Minor
>              Labels: lhf
>         Attachments: 12296.patch
> This came up in discussion of CASSANDRA-11687. {{nodetool rebuild}} was 
> failing in a dtest. [~pauloricardomg] explained:
> bq. before [CASSANDRA-11848] the local node could be considered a source, 
> while now sources are restricted only to dc2, so since {{system_auth}} uses 
> {{SimpleStrategy}} depending on the token arrangement there could or not be 
> sources from dc2. Fix is to either use 
> {{-Dcassandra.consistent.rangemovement=false}} or update {{system_auth}} to 
> use {{NetworkTopologyStrategy}} with 2 dcs..
> This is, at the very least, a UX bug. When {{rebuild}} fails, it fails with
> {code}
> nodetool: Unable to find sufficient sources for streaming range 
> (-3287869951390391138,-1624006824486474209] in keyspace system_auth with 
> RF=1.If you want to ignore this, consider using system property 
> -Dcassandra.consistent.rangemovement=false.
> {code}
> which suggests that a user should give up consistency guarantees when it's 
> not necessary.

This message was sent by Atlassian JIRA

Reply via email to