You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Vijay (Updated) (JIRA)" <ji...@apache.org> on 2012/01/22 04:31:44 UTC

[jira] [Updated] (CASSANDRA-3768) Implement VNode to improve bootstrapping

     [ https://issues.apache.org/jira/browse/CASSANDRA-3768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vijay updated CASSANDRA-3768:
-----------------------------

    Description: 
Implementation of vnode will provide us with lot of advantages in bootstrapping and operating a big cluster.

Some Problems which VNodes can solve:
* When we have a balanced large cluster doubling a live cluster is not an very good option and often this makes us to over provision.
* The above is true when we want to shrink a cluster too.
* Currently in my organization often we have use cases where we have to refresh production cluster's into a dev clusters. There is a strong need where we can have different sized clusters and data' can be fork lift data's into and out of it without over engineering or complicating the recovery process.
* In some cases bootstrapping a node which which has a large amount of data might take longer than needed and it might cause the neighbors to be over loaded.

I am not sure if i know all the changes which needs to be performed to get to that state, but this ticket will get us started.


  was:
Implementation of vnode will provide us with lot of advantages automatically balancing the cluster when 1 node is added to the cluster.

Some Problems which VNodes can solve:
When we have a balanced large cluster doubling a live cluster is not an very good option and often this makes us to over provision.
The above is true when we want to shrink a cluster too.
Currently in my organization often we have use cases where we have to refresh production cluster's into a dev clusters. There is a strong need where we can have different sized clusters and data' can be fork lift data's into and out of it without over engineering or complicating the recovery process.
In some cases bootstrapping a node which which has a large amount of data might take longer than needed and it might cause the neighbors to be over loaded.

I am not sure if i know all the changes which needs to be performed to get to that state, but this ticket will get us started.


    
> Implement VNode to improve bootstrapping
> ----------------------------------------
>
>                 Key: CASSANDRA-3768
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3768
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>    Affects Versions: 1.2
>         Environment: JVM
>            Reporter: Vijay
>            Assignee: Vijay
>            Priority: Minor
>             Fix For: 1.2
>
>
> Implementation of vnode will provide us with lot of advantages in bootstrapping and operating a big cluster.
> Some Problems which VNodes can solve:
> * When we have a balanced large cluster doubling a live cluster is not an very good option and often this makes us to over provision.
> * The above is true when we want to shrink a cluster too.
> * Currently in my organization often we have use cases where we have to refresh production cluster's into a dev clusters. There is a strong need where we can have different sized clusters and data' can be fork lift data's into and out of it without over engineering or complicating the recovery process.
> * In some cases bootstrapping a node which which has a large amount of data might take longer than needed and it might cause the neighbors to be over loaded.
> I am not sure if i know all the changes which needs to be performed to get to that state, but this ticket will get us started.

--
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