anton-vinogradov commented on PR #13447:
URL: https://github.com/apache/ignite/pull/13447#issuecomment-5246801943
Follow-up on the `assert initTime > 0` above: it is worse than a failing
test, it hangs.
The AssertionError is thrown inside a future listener and swallowed there,
so the near lock future never completes:
```
(err) Failed to notify listener: GridEmbeddedFuture$1@7be5697c
java.lang.AssertionError
at
org.apache.ignite.internal.processors.cache.GridCacheEntryInfo.expireTime(GridCacheEntryInfo.java:131)
at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearCacheEntry.initializeFromDht(GridNearCacheEntry.java:156)
at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearCacheAdapter.entryEx(GridNearCacheAdapter.java:147)
at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearCacheAdapter.entryExx(GridNearCacheAdapter.java:164)
at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearLockFuture$1.apply(GridNearLockFuture.java:1265)
```
`GridCacheNearPrimarySyncSelfTest` on `f95cc504` runs into it and then sits
there:
```
[21:41:13] >>> Future [startTime=21:39:13, curTime=21:41:13,
fut=GridNearLockFuture [...
[21:57:13] First 10 long running transactions [total=2]
[21:57:13] >>> Transaction [startTime=21:39:13, curTime=21:57:13,
systemTime=1079633, ...
```
18 minutes, then I killed it. The reason is that
`GridNearCacheAdapter.entryEx(key, topVer)` calls `initializeFromDht` on every
near entry lookup, so any near cache without an expiry policy hits it.
With `initTime` set unconditionally the same test finishes in 0.25 s and the
log has no assertion errors at all. That one line, the overflow guard and the
cases are in https://github.com/Vladsz83/ignite/pull/1.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
