[
https://issues.apache.org/jira/browse/IGNITE-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-1605:
-------------------------------------
Description:
Need to provide stronger data loss check.
Currently node can fire event - EVT_CACHE_REBALANCE_PART_DATA_LOST
However, this is not enough since if there is strong requirement on application
behavior on data loss e.g. further cache updates should throw exception - this
requirement cannot currently be met even with use of cache interceptor.
Suggestions:
* Introduce CacheDataLossPolicy enum: FAIL_OPS, NOOP and put it to configuration
* If node fires PART_LOST_EVT then any update to lost partition will throw (or
will not throw) exception according to DataLossPolicy
* ForceKeysRequest should be completed with exception (if plc == FAIL) if all
nodes to request from are gone. So, all gets/puts/txs should fail.
We also may want to add a public API method in order to allow a recovery from a
failed state.
was:
Need to provide stronger data loss check.
Currently node can fire event - EVT_CACHE_REBALANCE_PART_DATA_LOST
However, this is not enough since if there is strong requirement on application
behavior on data loss e.g. further cache updates should throw exception - this
requirement cannot currently be met even with use of cache interceptor.
Suggestions:
* Introduce CacheDataLossPolicy enum: FAIL_OPS, NOOP and put it to configuration
* If node fires PART_LOST_EVT then any update to lost partition will throw (or
will not throw) exception according to DataLossPolicy
* ForceKeysRequest should be completed with exception (if plc == FAIL) if all
nodes to request from are gone. So, all gets/puts/txs should fail.
> Provide stronger data loss check
> --------------------------------
>
> Key: IGNITE-1605
> URL: https://issues.apache.org/jira/browse/IGNITE-1605
> Project: Ignite
> Issue Type: Task
> Reporter: Yakov Zhdanov
> Assignee: Alexey Goncharuk
>
> Need to provide stronger data loss check.
> Currently node can fire event - EVT_CACHE_REBALANCE_PART_DATA_LOST
> However, this is not enough since if there is strong requirement on
> application behavior on data loss e.g. further cache updates should throw
> exception - this requirement cannot currently be met even with use of cache
> interceptor.
> Suggestions:
> * Introduce CacheDataLossPolicy enum: FAIL_OPS, NOOP and put it to
> configuration
> * If node fires PART_LOST_EVT then any update to lost partition will throw
> (or will not throw) exception according to DataLossPolicy
> * ForceKeysRequest should be completed with exception (if plc == FAIL) if all
> nodes to request from are gone. So, all gets/puts/txs should fail.
> We also may want to add a public API method in order to allow a recovery from
> a failed state.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
