ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dmitry Lazurkin <dila...@gmail.com>
Subject Exception on node startup: Attempted to release write lock while not holding it
Date Tue, 05 Mar 2019 15:48:43 GMT
Hello.

I have exception on node startup:

java.lang.IllegalMonitorStateException: Attempted to release write lock
while not holding it [lock=00007fa721ec8610, state=0000000000010000
    at
org.apache.ignite.internal.util.OffheapReadWriteLock.writeUnlock(OffheapReadWriteLock.java:266)
    at
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.writeUnlockPage(PageMemoryImpl.java:1536)
    at
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.writeUnlock(PageMemoryImpl.java:470)
    at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.restoreMemory(GridCacheDatabaseSharedManager.java:2067)
    at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.restoreMemory(GridCacheDatabaseSharedManager.java:1970)
    at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.readCheckpointAndRestoreMemory(GridCacheDatabaseSharedManager.java:826)
    at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onClusterStateChangeRequest(GridDhtPartitionsExchangeFuture.java:1099)
    at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:733)
    at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2667)
    at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2539)
    at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
    at java.lang.Thread.run(Thread.java:748)

WAL has record PAGE_RECORD with pageId 72340207180973833(offset=1,
flags=1, partId=265, index=1801) in fullPageId. But that record has
pageData with pageId 282613143045897(offset=0, flags=1, partId=265,
index=1801). And GridCacheDatabaseSharedManager#restoreMemory uses
pageId (tag) from record fullPageId for writeLock and uses pageId (tag)
from pageData for writeUnlock. Why are offsets different?

I saw this issue only once and don't known how to reproduce it.


Thank you.



Mime
View raw message