[
https://issues.apache.org/jira/browse/IGNITE-1840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14986187#comment-14986187
]
Alexey Goncharuk commented on IGNITE-1840:
------------------------------------------
It looks like eviction thread starts earlier than initial exchange is complete
and node has obtained a valid topology version.
I believe this line added before {{primaryParts.addAll(...)}} should fix the
issue:
{code}
cctx.preloader().startFuture().get();
{code}
> Exception in eviction manager on startup
> ----------------------------------------
>
> Key: IGNITE-1840
> URL: https://issues.apache.org/jira/browse/IGNITE-1840
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: ignite-1.4
> Reporter: Valentin Kulichenko
>
> It's rarely reproduced and looks like a race condition on startup. In some
> cases eviction backup worker start to work too early which leads to this
> exception on first iterations:
> {noformat}
> Exception in thread "cache-eviction-backup-worker-#40%null%"
> java.lang.AssertionError: AffinityTopologyVersion [topVer=-1, minorTopVer=0]
> at
> org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.cachedAffinity(GridAffinityAssignmentCache.java:423)
> at
> org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.primaryPartitions(GridAffinityAssignmentCache.java:397)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAffinityManager.primaryPartitions(GridCacheAffinityManager.java:352)
> at
> org.apache.ignite.internal.processors.cache.GridCacheEvictionManager$BackupWorker.body(GridCacheEvictionManager.java:1478)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
