[
https://issues.apache.org/jira/browse/IGNITE-4587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15948419#comment-15948419
]
Denis Magda commented on IGNITE-4587:
-------------------------------------
[~dreamx], [~agura],
Looking at the benchmarking results produced by one of my colleagues I didn't
spot any performance degradation between 1.9 and 2.0 for PRIMARY write order
mode. So, we accept this contribution and wipe out {{CLOCK}} mode.
Even more, can we remove {{CacheAtomicWriteOrderMode}} enum from the public API
at all? I see no reason why we should preserve for a single option available -
{{PRIMARY}}. Asked the same in the related discussion on the dev list.
> 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)
