Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
Date: Thu, 12 Nov 2015 18:36:11 +0000 (UTC)
From: "Valentin Kulichenko (JIRA)" <jira@apache.org>
To: dev@ignite.apache.org
Message-ID: <JIRA.12912563.1447353340000.52730.1447353371078@Atlassian.JIRA>
In-Reply-To: <JIRA.12912563.1447353340000@Atlassian.JIRA>
References: <JIRA.12912563.1447353340000@Atlassian.JIRA>
 <JIRA.12912563.1447353340332@arcas>
Subject: [jira] [Created] (IGNITE-1897) Add failover to write-behind cache
 store
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Valentin Kulichenko created IGNITE-1897:
-------------------------------------------

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


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)