cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (CASSANDRA-1577) Split gossiped load into 'primary' and 'total'
Date Tue, 05 Oct 2010 20:51:33 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-1577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12918167#action_12918167
] 

Jonathan Ellis edited comment on CASSANDRA-1577 at 10/5/10 4:49 PM:
--------------------------------------------------------------------

Let's either do this backwards-compatibly in 0.7.1 or break it in 0.8.

      was (Author: jbellis):
    Let's either do this backwards-compatibly in 0.7 or break it in 0.8.
  
> Split gossiped load into 'primary' and 'total'
> ----------------------------------------------
>
>                 Key: CASSANDRA-1577
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1577
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Stu Hood
>            Assignee: Stu Hood
>             Fix For: 0.8
>
>
> Bootstrap and load balancing decisions are currently made using the total load on a node,
as opposed to data the node is primarily responsible for due to a token hashing to its local
range. The latter number is the only reasonable number to be load balancing on, since ReplicationStrategies
can make arbitrary numbers of hops on the ring to find additional places to put replicas.
> To find the primary load efficiently, we can use the SSTableReader.getPositionsForRanges
method, although we should probably move the load calculation outside of the atomic swap in
SSTableTracker.
> The format of the serialized 'LOAD' gossip state will need to change in a backwards incompatible
fashion.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message