0

Chronicle Map の v3.10.1 を使用しています。私のマップには、約 77,000 のエントリがあります。entrySet()メソッドを使用してこのマップを反復処理しようとしています。正常に繰り返されず、その間に Chronicle 固有の例外がスローされます。クロニクル マップから生成されたログは次のとおりです。

016-09-17 06:39:15 [ERROR] n.o.c.m.i.CompiledMapIterationContext - Contexts locked on this segment:
net.openhft.chronicle.map.impl.CompiledMapIterationContext@205cd34b: used, segment 62, local state: UNLOCKED, read lock count: 0, update lock count: 0, write lock count: 0
Current thread contexts:
net.openhft.chronicle.map.impl.CompiledMapIterationContext@205cd34b: used, segment 62, local state: UNLOCKED, read lock count: 0, update lock count: 0, write lock count: 0

および例外:

2016-09-17 06:39:15 [ERROR] akka.dispatch.TaskInvocation - Failed to acquire the lock in 60 seconds.
Possible reasons:
 - The lock was not released by the previous holder. If you use contexts API,
 for example map.queryContext(key), in a try-with-resources block.
 - This Chronicle Map (or Set) instance is persisted to disk, and the previous
 process (or one of parallel accessing processes) has crashed while holding
 this lock. In this case you should use ChronicleMapBuilder.recoverPersistedTo() procedure
 to access the Chronicle Map instance.
 - A concurrent thread or process, currently holding this lock, spends
 unexpectedly long time (more than 60 seconds) in
 the context (try-with-resource block) or one of overridden interceptor
 methods (or MapMethods, or MapEntryOperations, or MapRemoteOperations)
 while performing an ordinary Map operation or replication. You should either
 redesign your logic to spend less time in critical sections (recommended) or
 acquire this lock with tryLock(time, timeUnit) method call, with sufficient
 time specified.
 - Segment(s) in your Chronicle Map are very large, and iteration over them
 takes more than 60 seconds. In this case you should
 acquire this lock with tryLock(time, timeUnit) method call, with longer
 timeout specified.
 - This is a dead lock. If you perform multi-key queries, ensure you acquire
 segment locks in the order (ascending by segmentIndex()), you can find
 an example here: https://github.com/OpenHFT/Chronicle-Map#multi-key-queries

java.lang.RuntimeException: Failed to acquire the lock in 60 seconds.
Possible reasons:
 - The lock was not released by the previous holder. If you use contexts API,
 for example map.queryContext(key), in a try-with-resources block.
 - This Chronicle Map (or Set) instance is persisted to disk, and the previous
 process (or one of parallel accessing processes) has crashed while holding
 this lock. In this case you should use ChronicleMapBuilder.recoverPersistedTo() procedure
 to access the Chronicle Map instance.
 - A concurrent thread or process, currently holding this lock, spends
 unexpectedly long time (more than 60 seconds) in
 the context (try-with-resource block) or one of overridden interceptor
 methods (or MapMethods, or MapEntryOperations, or MapRemoteOperations)
 while performing an ordinary Map operation or replication. You should either
 redesign your logic to spend less time in critical sections (recommended) or
 acquire this lock with tryLock(time, timeUnit) method call, with sufficient
 time specified.
 - Segment(s) in your Chronicle Map are very large, and iteration over them
 takes more than 60 seconds. In this case you should
 acquire this lock with tryLock(time, timeUnit) method call, with longer
 timeout specified.
 - This is a dead lock. If you perform multi-key queries, ensure you acquire
 segment locks in the order (ascending by segmentIndex()), you can find
 an example here: https://github.com/OpenHFT/Chronicle-Map#multi-key-queries

    at net.openhft.chronicle.hash.impl.BigSegmentHeader.deadLock(BigSegmentHeader.java:59)
    at net.openhft.chronicle.hash.impl.BigSegmentHeader.updateLock(BigSegmentHeader.java:231)
    at net.openhft.chronicle.map.impl.CompiledMapIterationContext$UpdateLock.lock(CompiledMapIterationContext.java:768)
    at net.openhft.chronicle.map.impl.CompiledMapIterationContext.forEachSegmentEntryWhile(CompiledMapIterationContext.java:3810)
    at net.openhft.chronicle.map.impl.CompiledMapIterationContext.forEachSegmentEntry(CompiledMapIterationContext.java:3816)
    at net.openhft.chronicle.map.ChronicleMapIterator.fillEntryBuffer(ChronicleMapIterator.java:61)
    at net.openhft.chronicle.map.ChronicleMapIterator.hasNext(ChronicleMapIterator.java:77)
    at java.lang.Iterable.forEach(Iterable.java:74)

これは、シングルスレッドの永続的なマップです。

4

0 に答える 0