Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
Date: Thu, 14 Jan 2016 12:37:39 +0000 (UTC)
From: "Vladimir Ershov (JIRA)" <jira@apache.org>
To: dev@ignite.apache.org
Message-ID: <JIRA.12930130.1452775022000.109258.1452775059945@Atlassian.JIRA>
In-Reply-To: <JIRA.12930130.1452775022000@Atlassian.JIRA>
References: <JIRA.12930130.1452775022000@Atlassian.JIRA>
 <JIRA.12930130.1452775022472@arcas>
Subject: [jira] [Created] (IGNITE-2378) Data loss Part 2. Add flexible
 DataLoss Policy. Improve dataLoss event with batch.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Vladimir Ershov created IGNITE-2378:
---------------------------------------

             Summary: Data loss Part 2. Add flexible DataLoss Policy. Improve dataLoss event with batch.
                 Key: IGNITE-2378
                 URL: https://issues.apache.org/jira/browse/IGNITE-2378
             Project: Ignite
          Issue Type: Improvement
    Affects Versions: 1.6
            Reporter: Vladimir Ershov
            Assignee: Vladimir Ershov


Next steps for the data loss check functionality development:
# Introduce new DataLossPolicy, like read-only and others.
# Think of data restoration and implement if needed.
# Design solution for the reduce of the amount of EVT_CACHE_REBALANCE_PART_DATA_LOST. (Now it is possible to implement batching for those events). One has to be careful with backward compatibility here.


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