You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Peter Schuller (Created) (JIRA)" <ji...@apache.org> on 2012/02/16 07:18:59 UTC

[jira] [Created] (CASSANDRA-3922) streaming from all (not one) neighbors during rebuild/bootstrap

streaming from all (not one) neighbors during rebuild/bootstrap
---------------------------------------------------------------

                 Key: CASSANDRA-3922
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3922
             Project: Cassandra
          Issue Type: Bug
          Components: Core
            Reporter: Peter Schuller
            Assignee: Peter Schuller
            Priority: Blocker
         Attachments: CASSANDRA-3922-1.1.txt

The last round of changes that happened in CASSANDRA-3483 before it went in actually changed behavior - we now stream from *ALL* neighbors that have a range, rather than just one. This leads to data size explosion.

Attaching patch to revert to intended behavior.

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

        

[jira] [Updated] (CASSANDRA-3922) streaming from all (not one) neighbors during rebuild/bootstrap

Posted by "Peter Schuller (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CASSANDRA-3922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Peter Schuller updated CASSANDRA-3922:
--------------------------------------

    Attachment: CASSANDRA-3922-1.1.txt
    
> streaming from all (not one) neighbors during rebuild/bootstrap
> ---------------------------------------------------------------
>
>                 Key: CASSANDRA-3922
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3922
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Peter Schuller
>            Assignee: Peter Schuller
>            Priority: Blocker
>             Fix For: 1.1.0
>
>         Attachments: CASSANDRA-3922-1.1.txt
>
>
> The last round of changes that happened in CASSANDRA-3483 before it went in actually changed behavior - we now stream from *ALL* neighbors that have a range, rather than just one. This leads to data size explosion.
> Attaching patch to revert to intended behavior.

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

        

[jira] [Updated] (CASSANDRA-3922) streaming from all (not one) neighbors during rebuild/bootstrap

Posted by "Peter Schuller (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CASSANDRA-3922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Peter Schuller updated CASSANDRA-3922:
--------------------------------------

    Fix Version/s: 1.1.0
    
> streaming from all (not one) neighbors during rebuild/bootstrap
> ---------------------------------------------------------------
>
>                 Key: CASSANDRA-3922
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3922
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Peter Schuller
>            Assignee: Peter Schuller
>            Priority: Blocker
>             Fix For: 1.1.0
>
>         Attachments: CASSANDRA-3922-1.1.txt
>
>
> The last round of changes that happened in CASSANDRA-3483 before it went in actually changed behavior - we now stream from *ALL* neighbors that have a range, rather than just one. This leads to data size explosion.
> Attaching patch to revert to intended behavior.

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