Not sure if it's the best/intended behavior, but you should see it go back to 100% if you run: nodetool -h 127.0.0.1 -p 8080 ring <keyspace>.
I think the rationale for showing 33% is that different keyspaces might have different RFs, so it's unclear what to show for ownership. However, if you include the keyspace as part of your query, you'll get it weighted by the RF of that keyspace. I believe the same logic applies for nodetool status. Andrew On Thu, Jul 11, 2013 at 12:58 PM, Jason Tyler <jaty...@yahoo-inc.com> wrote: > Thanks Rob! I was able to confirm with getendpoints. > > Cheers, > > ~Jason > > From: Robert Coli <rc...@eventbrite.com> > Reply-To: "user@cassandra.apache.org" <user@cassandra.apache.org> > Date: Wednesday, July 10, 2013 4:09 PM > To: "user@cassandra.apache.org" <user@cassandra.apache.org> > Cc: Francois Richard <frich...@yahoo-inc.com> > Subject: Re: node tool ring displays 33.33% owns on 3 node cluster with > replication > > On Wed, Jul 10, 2013 at 4:04 PM, Jason Tyler <jaty...@yahoo-inc.com>wrote: > >> Is this simply a display issue, or have I lost replication? >> > > Almost certainly just a display issue. Do "nodetool -h localhost > getendpoints <keyspace> <columnfamily> 0", which will tell you the > endpoints for the non-transformed key "0." It should give you 3 endpoints. > You could also do this test with a known existing key and then go to those > nodes and verify that they have that data on disk via sstable2json. > > (FWIW, it is an odd display issue/bug if it is one. Because it has > reverted to pre-1.1 behavior...) > > =Rob >
