[ https://issues.apache.org/jira/browse/CASSANDRA-3047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294710#comment-13294710 ]
David Alves commented on CASSANDRA-3047: ---------------------------------------- the test is separated from StorageServiceServerTest because other tests will hang when schemaloader is called on startup. this is the new output: {code} Datacenter: DC1 ========== Replicas: 1 Address DC Rack Status State Load Owns Token 127.0.0.1 DC1 RAC1 Up Normal 52.76 KB 100.00% 0 Datacenter: DC2 ========== Replicas: 1 Address DC Rack Status State Load Owns Token 85070591730234615865843651857942052864 127.0.0.2 DC2 RAC1 Up Normal 52.76 KB 50.00% 1 127.0.0.3 DC2 RAC2 Up Normal 54.46 KB 50.00% 85070591730234615865843651857942052864 Datacenter: DC3 ========== Replicas: 3 Address DC Rack Status State Load Owns Token 127605887595351923798765477786913079296 127.0.0.4 DC3 RAC1 Up Normal 52.76 KB 75.00% 2 127.0.0.5 DC3 RAC1 Up Normal 54.46 KB 75.00% 42535295865117307932921825928971026432 127.0.0.6 DC3 RAC2 Up Normal 52.78 KB 75.00% 85070591730234615865843651857942052865 127.0.0.7 DC3 RAC2 Up Normal 52.78 KB 75.00% 127605887595351923798765477786913079296 {code} > implementations of IPartitioner.describeOwnership() are not DC aware > -------------------------------------------------------------------- > > Key: CASSANDRA-3047 > URL: https://issues.apache.org/jira/browse/CASSANDRA-3047 > Project: Cassandra > Issue Type: Improvement > Components: Tools > Reporter: Aaron Morton > Assignee: David Alves > Priority: Trivial > Fix For: 1.1.2 > > Attachments: CASSANDRA-3047.patch > > > see http://www.mail-archive.com/user@cassandra.apache.org/msg16375.html > When a cluster the multiple rings approach to tokens the output from nodetool > ring is incorrect. > When it uses the interleaved token approach (e.g. dc1, dc2, dc1, dc2) it will > be correct. > It's a bit hacky but could we special case (RP) tokens that are off by 1 and > calculate the ownership per dc ? I guess another approach would be to add > some parameters so the partitioner can be told about the token assignment > strategy. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira