Igniters, I noted strange behavior of IgniteCache.invoke() in async mode. If exception is thrown from entry processor, sometimes it lands in future as expected, but sometimes it is thrown right-away as if it was a synchronous call. Behavior depends on topology and may be key affinity. Test case is provided in the ticket: https://issues.apache.org/jira/browse/IGNITE-1098
As I understand, IgniteCache.invoke() must never throw processor exceptions according to our "async" contract (as well as ny other async-supported operations). Can anyone throw a glance on the problem? Vladimir.
