[jira] [Updated] (IGNITE-1897) Add failover to write-behind cache store
[ https://issues.apache.org/jira/browse/IGNITE-1897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-1897: Issue Type: New Feature (was: Improvement) > Add failover to write-behind cache store > > > Key: IGNITE-1897 > URL: https://issues.apache.org/jira/browse/IGNITE-1897 > Project: Ignite > Issue Type: New Feature > Components: cache >Reporter: Valentin Kulichenko > > 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.4.14#64029)
[jira] [Updated] (IGNITE-1897) Add failover to write-behind cache store
[ https://issues.apache.org/jira/browse/IGNITE-1897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-1897: Fix Version/s: (was: 2.0) 2.1 > 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 > Fix For: 2.1 > > > 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.15#6346)
[jira] [Updated] (IGNITE-1897) Add failover to write-behind cache store
[ https://issues.apache.org/jira/browse/IGNITE-1897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-1897: Fix Version/s: (was: 1.8) 2.0 > 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 > Fix For: 2.0 > > > 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)
[jira] [Updated] (IGNITE-1897) Add failover to write-behind cache store
[ https://issues.apache.org/jira/browse/IGNITE-1897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-1897: --- Fix Version/s: (was: 1.7) 1.8 > 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 > Fix For: 1.8 > > > 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)
[jira] [Updated] (IGNITE-1897) Add failover to write-behind cache store
[ https://issues.apache.org/jira/browse/IGNITE-1897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-1897: Assignee: (was: Valentin Kulichenko) > 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 > 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)
[jira] [Updated] (IGNITE-1897) Add failover to write-behind cache store
[ 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)
