[
https://issues.apache.org/jira/browse/IGNITE-2378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ershov updated IGNITE-2378:
------------------------------------
Description:
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.
# ResetLostPartsMsg should affect only topology with specified version.
was:
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.
> 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
> Labels: 1.6
> Original Estimate: 40h
> Remaining Estimate: 40h
>
> 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.
> # ResetLostPartsMsg should affect only topology with specified version.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
