Igniters, I want to bring community attention to the ticket [1] once again since it raises a lot of confusion among Ignite users [2] and I would like this to be addressed in 1.6.
The alternatives for the case when entry processor is used in CLOCK mode are: * Print a warning, but still allow to use invoke() since it will work if key access is synchronized by external means. * Throw an exception and force users to switch to PRIMARY mode when invoke() is used. Any thoughts / other suggestions? -- AG [1] https://issues.apache.org/jira/browse/IGNITE-2088 [2] http://apache-ignite-users.70518.x6.nabble.com/Version-issue-with-concurrent-cache-updates-EntryProcessor-td2896.html
