I'm facing the same issue. It's also reported by @aholmberg in: Incorrect output in "nodetool status -r" <https://issues.apache.org/jira/browse/CASSANDRA-16283?focusedCommentId=17259947&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17259947> [image: image.png]
On Wed, Feb 10, 2021 at 4:21 PM Shalom Sagges <shalomsag...@gmail.com> wrote: > Ah, missed the keyspace name there. > My bad :-) > > On Wed, Feb 10, 2021 at 4:13 PM Bowen Song <bo...@bso.ng.invalid> wrote: > >> In your example, the nodetool output depends on whether the keyspace name >> is present in the "nodetool status" command line parameters. "nodetool >> status" command without a keyspace name may not show the effective >> ownerships, but it should always show the effective ownership information >> when you use "nodetool status keyspace_name". >> On 10/02/2021 13:12, Shalom Sagges wrote: >> >> I don't think it's related specifically to 4.0 >> I can see this issue on 3.11 and even on previous versions as well. >> It occurs when the replication factor is not similar on all keyspaces. >> For example, if you have a cluster with 2 DCs and one of the keyspaces >> has a RF of DC1: 3 whie other keyspaces have DC1: 3, DC2 : 3, you will see >> the reported behaviour. >> >> Hope this helps! >> >> On Wed, Feb 10, 2021 at 2:24 PM Erick Ramirez <erick.rami...@datastax.com> >> wrote: >> >>> This appears to be the same issue reported in CASSANDRA-16273 >>> <https://issues.apache.org/jira/browse/CASSANDRA-16273> affecting 4.0 >>> and is currently open/unresolved. Cheers! >>> >>>> -- *בברכה,* *יקיר גיברלטר*
