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] [Updated] (CASSANDRA-2714) Throttle migration replay
Date Thu, 26 May 2011 20:13:47 GMT

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

Jonathan Ellis updated CASSANDRA-2714:
--------------------------------------

    Attachment: 2714.txt

patch mitigates this two ways:

- cuts chunk-of-migrations-to-push to 100 from 1000
- waits for target to apply the last set of migrations pushed, before sending it the next

> Throttle migration replay
> -------------------------
>
>                 Key: CASSANDRA-2714
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2714
>             Project: Cassandra
>          Issue Type: Improvement
>    Affects Versions: 0.7.0
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>            Priority: Minor
>             Fix For: 0.7.7, 0.8.1
>
>         Attachments: 2714.txt
>
>
> As reported on the mailing list,
> {noformat}
> - I have a lot of schema updates (there are 2067 rows in the system.Schema CF).
> - The live node loads migrations 1-1000, and sends them to the recovering node (Migration.getLocalMigrations())
> - Soon afterwards, the live node checks the schema version on the recovering node and
finds it has moved by a little - say it has applied the first 3 migrations. It then loads
migrations 3-1003, and sends them to the node.
> - This process is repeated very quickly (sends migrations 6-1006, 9-1009, etc).
> {noformat}
> The source of the problem is that MigrationManager.onChange will send out a full (up
to 1000 migrations) replay, every time the target's schema version changes.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message