[
https://issues.apache.org/jira/browse/IGNITE-4587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15863413#comment-15863413
]
ASF GitHub Bot commented on IGNITE-4587:
----------------------------------------
GitHub user dream-x opened a pull request:
https://github.com/apache/ignite/pull/1521
IGNITE-4587: Discontinue and remove CacheAtomicWriteOrderMode.CLOCK mode
[Jira ticket](https://issues.apache.org/jira/browse/IGNITE-4587).
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dream-x/ignite ignite-4587
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/1521.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1521
----
commit f0dcbbdecd10ee9afee3cb0c5a96bb1540d0c06a
Author: Max Kozlov <[email protected]>
Date: 2017-02-13T09:20:51Z
Delete CLOCK mode in CacheAtomicWriteOrderMode.
commit a37ff76168613007d3ca09c06688bc6456e4c330
Author: Max Kozlov <[email protected]>
Date: 2017-02-13T09:27:28Z
Delete use CLOCK for ignite-core.
commit 25d4ea5003773b739baba2c2d5c3e7be2194ba7a
Author: Max Kozlov <[email protected]>
Date: 2017-02-13T09:43:59Z
Fix tests CLOCK change to PRIMARY and delete same test.
----
> Discontinue and remove CacheAtomicWriteOrderMode.CLOCK mode
> -----------------------------------------------------------
>
> Key: IGNITE-4587
> URL: https://issues.apache.org/jira/browse/IGNITE-4587
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Reporter: Denis Magda
> Assignee: Maksim Kozlov
> Fix For: 2.0
>
>
> {{CacheAtomicWriteOrderMode.CLOCK}} proved to be harmful in production due to
> timing issues.
> It makes sense to remove it completely in 2.0 release. Migration guide has be
> updated:
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0+Migration+Guide
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
