[
https://issues.apache.org/jira/browse/IGNITE-11729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Plekhanov updated IGNITE-11729:
---------------------------------------
Fix Version/s: (was: 2.9)
2.10
> Low description for lost policy functional
> ------------------------------------------
>
> Key: IGNITE-11729
> URL: https://issues.apache.org/jira/browse/IGNITE-11729
> Project: Ignite
> Issue Type: Improvement
> Components: documentation
> Affects Versions: 2.7
> Reporter: ARomantsov
> Priority: Major
> Fix For: 2.10
>
>
> Current description in
> https://apacheignite.readme.io/docs/partition-loss-policies seems not covered
> persistence case and text description is not clear
> Probably we need to transform it into two tables (in-memory, persistence)
> Rows - cache_write, cache_read, cache_remove,sql_read, sql_write
> Columns - READ_ONLY_SAFE ,READ_ONLY_ALL, READ_WRITE_SAFE, etc
> {code:java}
> Policies
> Ignite supports the following PartitionLossPolicies:
> READ_ONLY_SAFE - all writes to a cache/table will fail with an exception.
> Reads will only be allowed for entries belonging to survived/alive
> partitions. Reads from lost partitions will fail with an exception.
> READ_ONLY_ALL - reads are allowed from any partition including the lost ones.
> An exception is thrown in an attempt to write to any partition. The result of
> reading from a lost partition is undefined and may be different on different
> nodes in the cluster.
> READ_WRITE_SAFE - all reads and writes are allowed for entries in
> survived/alive partitions. All reads and writes of entries belonging to the
> lost partitions will fail with an exception.
> READ_WRITE_ALL - all reads and writes will proceed as if all partitions were
> in a consistent state (as if no partition loss happened). The result of
> reading from a lost partition is undefined and may be different on different
> nodes in the cluster.
> IGNORE - this mode never marks a lost partition as lost, pretending that no
> partition loss has happened and clearing the partition loss state right away.
> Technically, the partition will not be added to the collection of
> lostPartitions which is the main difference from READ_WRITE_ALL mode. IGNORE
> mode is used by default.
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
