cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Jirsa (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-12296) system_auth can't be rebuilt by default
Date Wed, 12 Oct 2016 03:20:20 GMT


Jeff Jirsa commented on CASSANDRA-12296:

[~KurtG] - If you're running NTS with only one replica, the patch will advise you to consider
{{NetworkTopologyStrategy}}. Further, {{SimpleStrategy}} with a higher RF would also be adequate
to find a second replica for streaming - the datastax docs recommending {{NetworkTopologyStrategy}}
before {{nodetool rebuild}} are specifically referencing adding a new DC. The error message
above is not limited to ONLY adding a new DC, and could be hit in a number of other ways,
where the recommendation to switch to NTS isn't necessary.

I agree the message is difficult to understand now, but "please switch to NTS" isn't the right
fix here, either.

> system_auth can't be rebuilt by default
> ---------------------------------------
>                 Key: CASSANDRA-12296
>                 URL:
>             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
> {code}
> which suggests that a user should give up consistency guarantees when it's not necessary.

This message was sent by Atlassian JIRA

View raw message