Question

我们在启用持久性和对等类加载的情况下运行2节点Ignite群集。我们遇到了同级课程加载问题，可以简化为：

IgniteCache存储类A，B，C的值。它们都实现相同的接口X。该缓存中的任何ScanQuery都尝试像在接口X上进行操作

 val cache: IgniteCache<UUID, X> 
.....
 val query = ScanQuery<UUID, X> { _, entry ->  .... }
 cache.query(query, { it.key }).use { keys ->
            for (key in keys) {
                 ........

失败：

Caused by: java.lang.ClassCastException: A cannot be cast to X

    at ….Scheduler$poll$dueQuery$1.apply(Scheduler:61)

    at org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager$ScanQueryIterator.advance(GridCacheQueryManager.java:3089)

    at org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager$ScanQueryIterator.onHasNext(GridCacheQueryManager.java:2982)

    at org.apache.ignite.internal.util.GridCloseableIteratorAdapter.hasNextX(GridCloseableIteratorAdapter.java:53)

    at org.apache.ignite.internal.util.lang.GridIteratorAdapter.hasNext(GridIteratorAdapter.java:45)

at org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.runQuery(GridCacheQueryManager.java:1164)

    at org.apache.ignite.internal.processors.cache.query.GridCacheDistributedQueryManager.processQueryRequest(GridCacheDistributedQueryManager.java:230)

    at org.apache.ignite.internal.processors.cache.query.GridCacheDistributedQueryManager$2.apply(GridCacheDistributedQueryManager.java:108)

    at org.apache.ignite.internal.processors.cache.query.GridCacheDistributedQueryManager$2.apply(GridCacheDistributedQueryManager.java:106)

    at org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1054)

    at org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:579)

    at org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:378)

    at org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:304)

    at org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:99)

    at org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:293)

    at org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1556)

    at org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1184)

    at org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:125)

    at org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1091)

    ... 3 common frames omitted

如果我们在该缓存中仅保留一个特定的类A并让ScanQuery在该缓存中进行操作，则一切正常。

A，B，C类由于使用Externalizable进行自定义序列化而被OptimizedMarshaller封送。

是否支持此方案？我们在做错什么吗？

有没有一种方法可以对缓存值的接口使用ScanQuery？

0 个答案: