从EntryProcessor访问IMap [英] accessing IMap from EntryProcessor

问题描述

是否可以从EntryProcessor的process()方法内访问IMap或其他Hazelcast分布式数据结构(如AtomicLong)?

Can IMap or other Hazelcast distributed data structures like AtomicLong be accessed from within process() method of an EntryProcessor?

我遇到以下异常:

java.util.concurrent.ExecutionException: java.lang.IllegalThreadStateException: Thread[hz.Alcatraz-ANP-Sys-HAZLE-2.actiance.local.partition-operation.thread-5,5,Alcatraz-ANP-Sys-HAZLE-2.actiance.local] cannot make remote call: com.hazelcast.concurrent.lock.operations.LockOperation@3229190f
at java.util.concurrent.FutureTask.report(FutureTask.java:122) ~[na:1.7.0_51]
at java.util.concurrent.FutureTask.get(FutureTask.java:188) ~[na:1.7.0_51]
at com.hazelcast.executor.impl.DistributedExecutorService$CallableProcessor.run(DistributedExecutorService.java:189) ~[hazelcast-3.3_actiance.jar:3.3]
at com.hazelcast.util.executor.CachedExecutorServiceDelegate$Worker.run(CachedExecutorServiceDelegate.java:209) [hazelcast-3.3_actiance.jar:3.3]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [na:1.7.0_51]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [na:1.7.0_51]
at java.lang.Thread.run(Thread.java:744) [na:1.7.0_51]
at com.hazelcast.util.executor.HazelcastManagedThread.executeRun(HazelcastManagedThread.java:76) [hazelcast-3.3_actiance.jar:3.3]
at com.hazelcast.util.executor.HazelcastManagedThread.run(HazelcastManagedThread.java:92) [hazelcast-3.3_actiance.jar:3.3]

我正在使用Hazelcast版本3.3

I'm using Hazelcast version 3.3

推荐答案

您可以访问其他数据结构，但需要确保它们与当前处理的条目位于同一数据分区中.这意味着您可以使用(例如)数据关联性将所有数据固定在同一分区中.

You can access other datastructures but you need to make sure they're in the same data partition as the currently processed entry. This means you can use (for example) data affinity to pin all data together in the same partition.

虽然无法在不同分区之间共享IAtomicLong.

Sharing an IAtomicLong between different partitions is not possible though.

PS:除了当前处理的条目外，您也不应突变其他数据，因为它可能最终会导致不同节点之间的死锁.

PS: You also shouldn't mutate other data than the current processed entry since it might end up in a deadlock between different nodes.

这篇关于从EntryProcessor访问IMap的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！