[
https://issues.apache.org/jira/browse/IGNITE-1897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-1897:
----------------------------------------
Description:
Currently there is a possibility of losing database updates if primary node
fails. We should maintain updates queue on backup node as well and flush it if
needed.
The implementation should be similar to what is done with continuous queries in
scope of this ticket: https://issues.apache.org/jira/browse/IGNITE-426
Corresponding user@ thread:
http://apache-ignite-users.70518.x6.nabble.com/Write-behind-question-td1936.html
was:
Currently there is a possibility of losing database updates if primary node
fails. We should maintain updates queue on backup node as well and flush it if
needed.
The implementation should be similar to what is done with continuous queries in
scope of this ticket: https://issues.apache.org/jira/browse/IGNITE-426
> Add failover to write-behind cache store
> ----------------------------------------
>
> Key: IGNITE-1897
> URL: https://issues.apache.org/jira/browse/IGNITE-1897
> Project: Ignite
> Issue Type: Improvement
> Components: cache
> Reporter: Valentin Kulichenko
> Assignee: Valentin Kulichenko
> Priority: Critical
> Fix For: 1.6
>
>
> Currently there is a possibility of losing database updates if primary node
> fails. We should maintain updates queue on backup node as well and flush it
> if needed.
> The implementation should be similar to what is done with continuous queries
> in scope of this ticket: https://issues.apache.org/jira/browse/IGNITE-426
> Corresponding user@ thread:
> http://apache-ignite-users.70518.x6.nabble.com/Write-behind-question-td1936.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
