[ https://issues.apache.org/jira/browse/CASSANDRA-12296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sam Tunnicliffe updated CASSANDRA-12296: ---------------------------------------- Summary: Better error message when streaming with insufficient sources in DC (was: Better error message when rebuilding) > Better error message when streaming with insufficient sources in DC > ------------------------------------------------------------------- > > Key: CASSANDRA-12296 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12296 > Project: Cassandra > Issue Type: Bug > Reporter: Jim Witschey > Assignee: Kurt Greaves > Priority: Minor > Labels: lhf > Fix For: 3.0.10, 3.10 > > Attachments: 12296-3.0.patch, 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 (v6.3.4#6332)