Hmm, doing the same but with:
atomicWriteOrderMode=PRIMARY
writeSynchronizationMode=PRIMARY_SYNC
causes:
[atomic.GridDhtAtomicCache] - <testCache> Unexpected exception during cache
update
java.lang.AssertionError: Invalid version for inner update
[entry=GridDhtAtomicCacheEntry [super=GridDhtCacheEntry [rdrs=[],
locPart=GridDhtLocalPartition [id=351, mapPubSize=1,
rmvQueue=GridCircularBuffer [sizeMask=511, idxGen=0], cntr=0, state=OWNING,
reservations=0, empty=false, createTime=02/09/2016 14:52:05, mapPubSize=1],
super=GridDistributedCacheEntry [super=GridCacheMapEntry
[key=KeyCacheObjectImpl [val=<myKey>, hasValBytes=true],
val=CacheObjectImpl [val=[1.0], hasValBytes=true], startVer=1455022325067,
ver=GridCacheVersion [topVer=66502326, nodeOrderDrId=1,
globalTime=1455022348434, order=1455022325392], hash=1026268892,
extras=null, flags=0]]]], newVer=GridCacheVersion [topVer=66502326,
nodeOrderDrId=1, globalTime=1455022348422, order=1455022325391]]
at
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerUpdate(GridCacheMapEntry.java:2018)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updatePartialBatch(GridDhtAtomicCache.java:2189)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateWithBatch(GridDhtAtomicCache.java:1747)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1299)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1194)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.mapSingle(GridNearAtomicUpdateFuture.java:457)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.access$1400(GridNearAtomicUpdateFuture.java:72)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$UpdateState.map(GridNearAtomicUpdateFuture.java:931)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.mapOnTopology(GridNearAtomicUpdateFuture.java:417)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.map(GridNearAtomicUpdateFuture.java:283)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$18.apply(GridDhtAtomicCache.java:925)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$18.apply(GridDhtAtomicCache.java:923)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.asyncOp(GridDhtAtomicCache.java:700)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsync0(GridDhtAtomicCache.java:923)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.invokeAllAsync(GridDhtAtomicCache.java:815)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.invokeAll(GridDhtAtomicCache.java:739)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.invokeAll(IgniteCacheProxy.java:1537)
2016-02-09 13:18 GMT+02:00 Myron Chelyada <[email protected]>:
> Hi Alexey,
>
> Thanks for reply.
>
> Are there any other similar limitations with modes related to entry
> processor?
> Perhaps there is some detailed documentation (more detailed than I see on
> site)?
>
> 2016-02-09 12:09 GMT+02:00 Alexey Goncharuk <[email protected]>:
>
>> Myron,
>>
>> This is a known usability issue, see [1]. You need to set
>> atomicWriterOrderMode to PRIMARY in order to make entry processors to work
>> correctly. I will cross-post this mail to devlist in order to raise the
>> ticket priority.
>>
>> [1] https://issues.apache.org/jira/browse/IGNITE-2088
>>
>> --AG
>>
>
>