Repository: ignite Updated Branches: refs/heads/ignite-4587 [created] 0bfb5851c
Delete CLOCK mode in CacheAtomicWriteOrderMode. Project: http://git-wip-us.apache.org/repos/asf/ignite/repo Commit: http://git-wip-us.apache.org/repos/asf/ignite/commit/f0dcbbde Tree: http://git-wip-us.apache.org/repos/asf/ignite/tree/f0dcbbde Diff: http://git-wip-us.apache.org/repos/asf/ignite/diff/f0dcbbde Branch: refs/heads/ignite-4587 Commit: f0dcbbdecd10ee9afee3cb0c5a96bb1540d0c06a Parents: 4e1fc40 Author: Max Kozlov <[email protected]> Authored: Mon Feb 13 12:20:51 2017 +0300 Committer: Max Kozlov <[email protected]> Committed: Mon Feb 13 12:20:51 2017 +0300 ---------------------------------------------------------------------- .../ignite/cache/CacheAtomicWriteOrderMode.java | 18 +----------------- 1 file changed, 1 insertion(+), 17 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/ignite/blob/f0dcbbde/modules/core/src/main/java/org/apache/ignite/cache/CacheAtomicWriteOrderMode.java ---------------------------------------------------------------------- diff --git a/modules/core/src/main/java/org/apache/ignite/cache/CacheAtomicWriteOrderMode.java b/modules/core/src/main/java/org/apache/ignite/cache/CacheAtomicWriteOrderMode.java index 38b4556..2595d29 100644 --- a/modules/core/src/main/java/org/apache/ignite/cache/CacheAtomicWriteOrderMode.java +++ b/modules/core/src/main/java/org/apache/ignite/cache/CacheAtomicWriteOrderMode.java @@ -23,27 +23,11 @@ import org.jetbrains.annotations.Nullable; * Cache write ordering mode. This enumeration is taken into account only in {@link CacheAtomicityMode#ATOMIC} * atomicity mode. Write ordering mode determines which node assigns the write version, sender or the primary node. * <p> - * For example, {@link #CLOCK} mode assigns write versions on a sender node which generally leads to better - * performance in {@link CacheWriteSynchronizationMode#FULL_SYNC} synchronization mode, since in this case - * sender can send write requests to primary and backups at the same time. Otherwise, if ordering mode is - * {@link #PRIMARY}, it would only send request to primary node, which in turn will assign write version + * For example, {@link #PRIMARY} mode would only send request to primary node, which in turn will assign write version * and forward it to backups. - * <p> - * {@link #CLOCK} mode will be automatically configured only with {@link CacheWriteSynchronizationMode#FULL_SYNC} - * write synchronization mode, as for other synchronization modes it does not render better performance. */ public enum CacheAtomicWriteOrderMode { /** - * In this mode, write versions are assigned on a sender node which generally leads to better - * performance in {@link CacheWriteSynchronizationMode#FULL_SYNC} synchronization mode, since in this case - * sender can send write requests to primary and backups at the same time. - * <p> - * This mode will be automatically configured only with {@link CacheWriteSynchronizationMode#FULL_SYNC} - * write synchronization mode, as for other synchronization modes it does not render better performance. - */ - CLOCK, - - /** * Cache version is assigned only on primary node. This means that sender will only send write request * to primary node, which in turn will assign write version and forward it to backups. */
