You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2012/08/14 18:32:38 UTC
[jira] [Created] (CASSANDRA-4543) batchlog replay
Jonathan Ellis created CASSANDRA-4543:
-----------------------------------------
Summary: batchlog replay
Key: CASSANDRA-4543
URL: https://issues.apache.org/jira/browse/CASSANDRA-4543
Project: Cassandra
Issue Type: Sub-task
Reporter: Jonathan Ellis
Assignee: Aleksey Yeschenko
--
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] [Resolved] (CASSANDRA-4543) batchlog replay
Posted by "Aleksey Yeschenko (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aleksey Yeschenko resolved CASSANDRA-4543.
------------------------------------------
Resolution: Fixed
This has already been implemented in 4542.
> batchlog replay
> ---------------
>
> Key: CASSANDRA-4543
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4543
> Project: Cassandra
> Issue Type: Sub-task
> Reporter: Jonathan Ellis
> Assignee: Aleksey Yeschenko
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-4543) batchlog replay
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13434257#comment-13434257 ]
Jonathan Ellis commented on CASSANDRA-4543:
-------------------------------------------
After a batchlog entry (CASSANDRA-4542) is written, if it isn't removed within 2*rpc_write_timeout, we should be fairly safe in assuming that the coordinator failed and the batch will need to be replayed. (If in fact the coordinator is still alive but degraded, replaying it will be idempotent and harmless.)
Suggest leveraging the existing hint mechanism for replay: turn the batch entry into its component mutations, hint those, and let HHOM replay when the target is alive.
> batchlog replay
> ---------------
>
> Key: CASSANDRA-4543
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4543
> Project: Cassandra
> Issue Type: Sub-task
> Reporter: Jonathan Ellis
> Assignee: Aleksey Yeschenko
>
--
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