[
https://issues.apache.org/jira/browse/IGNITE-4587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15939187#comment-15939187
]
Denis Magda commented on IGNITE-4587:
-------------------------------------
Guys, in any case, after we see benchmarking results for 1.9 and 2.0 (both in
PRIMARY synchronization mode) then the final decision will be done. If 2.0
outperforms 1.9 in PRIMARY synchronization mode then there is no sense to
preserve harmful CLOCK mode. Even more, we might need to remove
{{CacheWriteSynchMode}} from the public API at all, since there is no need to
have it for a single parameter.
> 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)
