[
https://issues.apache.org/jira/browse/IGNITE-13593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladislav Pyatkov updated IGNITE-13593:
---------------------------------------
Description:
[https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=749390831986783178&tab=testDetails&branch_IgniteTests24Java8=%3Cdefault%3E]
Flaky rate is 14%
There are two kinds of fails in this test (as a TC says):
# Exception on MVCC cache, because tests adds identical keys in one moment.
This exception will fix here.
# Assertion error, because size of cache as different as expected.
This behavior is difficulty reproduced and happened very rare in TC. It will
be fixed in another ticket if it appears again after this issue would be closed.
The reason of flacking of this test is an exception on MVCC cache:
{noformat}
javax.cache.CacheException: class
org.apache.ignite.transactions.TransactionSerializationException: Cannot
serialize transaction due to write conflict (transaction is marked for rollback)
at
org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1265)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:2077)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.put(IgniteCacheProxyImpl.java:1313)
at
org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.put(GatewayProtectedCacheProxy.java:817)
at
org.apache.ignite.internal.processors.cache.IgniteClientCacheStartFailoverTest$8.call(IgniteClientCacheStartFailoverTest.java:399)
at
org.apache.ignite.internal.processors.cache.IgniteClientCacheStartFailoverTest$8.call(IgniteClientCacheStartFailoverTest.java:375)
at
org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:87)
Caused by: class
org.apache.ignite.transactions.TransactionSerializationException: Cannot
serialize transaction due to write conflict (transaction is marked for rollback)
at
org.apache.ignite.internal.util.IgniteUtils$16.apply(IgniteUtils.java:1011)
at
org.apache.ignite.internal.util.IgniteUtils$16.apply(IgniteUtils.java:1009)
... 7 more
Caused by: class
org.apache.ignite.internal.transactions.IgniteTxSerializationCheckedException:
Cannot serialize transaction due to write conflict (transaction is marked for
rollback)
at
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.serializationError(GridCacheMapEntry.java:7123)
at
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.access$700(GridCacheMapEntry.java:136)
at
org.apache.ignite.internal.processors.cache.GridCacheMapEntry$MvccUpdateLockListener.apply(GridCacheMapEntry.java:5629)
at
org.apache.ignite.internal.processors.cache.GridCacheMapEntry$MvccUpdateLockListener.apply(GridCacheMapEntry.java:5482)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:407)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.unblock(GridFutureAdapter.java:355)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.unblockAll(GridFutureAdapter.java:343)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:520)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:498)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:464)
at
org.apache.ignite.internal.processors.cache.mvcc.MvccProcessorImpl$LockFuture.run(MvccProcessorImpl.java:1952)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
{noformat}
was:
[https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=749390831986783178&tab=testDetails&branch_IgniteTests24Java8=%3Cdefault%3E]
Flaky rate is 14%
There are two kinds of fails in this test (as a TC says):
# Exception on MVCC cache, because tests adds identical keys in one moment.
This exception will fix here.
# Assertion error, because size of cache as different as expected.
This behavior is difficulty reproduced and happened very rare in TC. It will
be fixed in another ticket if it appears again after this issue would be closed.
The reason of flacking of this test is an exception on MVCC cache:
{noformat}
javax.cache.CacheException: class
org.apache.ignite.transactions.TransactionSerializationException: Cannot
serialize transaction due to write conflict (transaction is marked for
rollback) at
org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1265)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:2077)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.put(IgniteCacheProxyImpl.java:1313)
at
org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.put(GatewayProtectedCacheProxy.java:817)
at
org.apache.ignite.internal.processors.cache.IgniteClientCacheStartFailoverTest$8.call(IgniteClientCacheStartFailoverTest.java:399)
at
org.apache.ignite.internal.processors.cache.IgniteClientCacheStartFailoverTest$8.call(IgniteClientCacheStartFailoverTest.java:375)
at org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:87)
Caused by: class
org.apache.ignite.transactions.TransactionSerializationException: Cannot
serialize transaction due to write conflict (transaction is marked for
rollback) at
org.apache.ignite.internal.util.IgniteUtils$16.apply(IgniteUtils.java:1011) at
org.apache.ignite.internal.util.IgniteUtils$16.apply(IgniteUtils.java:1009) ...
7 more Caused by: class
org.apache.ignite.internal.transactions.IgniteTxSerializationCheckedException:
Cannot serialize transaction due to write conflict (transaction is marked for
rollback) at
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.serializationError(GridCacheMapEntry.java:7123)
at
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.access$700(GridCacheMapEntry.java:136)
at
org.apache.ignite.internal.processors.cache.GridCacheMapEntry$MvccUpdateLockListener.apply(GridCacheMapEntry.java:5629)
at
org.apache.ignite.internal.processors.cache.GridCacheMapEntry$MvccUpdateLockListener.apply(GridCacheMapEntry.java:5482)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:407)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.unblock(GridFutureAdapter.java:355)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.unblockAll(GridFutureAdapter.java:343)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:520)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:498)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:464)
at
org.apache.ignite.internal.processors.cache.mvcc.MvccProcessorImpl$LockFuture.run(MvccProcessorImpl.java:1952)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
{noformat}
> IgniteClientCacheStartFailoverTest.testRebalanceStateConcurrentStart (Cache
> 2) is flaky
> ---------------------------------------------------------------------------------------
>
> Key: IGNITE-13593
> URL: https://issues.apache.org/jira/browse/IGNITE-13593
> Project: Ignite
> Issue Type: Bug
> Reporter: Vladislav Pyatkov
> Assignee: Vladislav Pyatkov
> Priority: Major
>
> [https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=749390831986783178&tab=testDetails&branch_IgniteTests24Java8=%3Cdefault%3E]
> Flaky rate is 14%
>
> There are two kinds of fails in this test (as a TC says):
> # Exception on MVCC cache, because tests adds identical keys in one moment.
> This exception will fix here.
> # Assertion error, because size of cache as different as expected.
> This behavior is difficulty reproduced and happened very rare in TC. It will
> be fixed in another ticket if it appears again after this issue would be
> closed.
> The reason of flacking of this test is an exception on MVCC cache:
> {noformat}
> javax.cache.CacheException: class
> org.apache.ignite.transactions.TransactionSerializationException: Cannot
> serialize transaction due to write conflict (transaction is marked for
> rollback)
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1265)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:2077)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.put(IgniteCacheProxyImpl.java:1313)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.put(GatewayProtectedCacheProxy.java:817)
> at
> org.apache.ignite.internal.processors.cache.IgniteClientCacheStartFailoverTest$8.call(IgniteClientCacheStartFailoverTest.java:399)
> at
> org.apache.ignite.internal.processors.cache.IgniteClientCacheStartFailoverTest$8.call(IgniteClientCacheStartFailoverTest.java:375)
> at
> org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:87)
> Caused by: class
> org.apache.ignite.transactions.TransactionSerializationException: Cannot
> serialize transaction due to write conflict (transaction is marked for
> rollback)
> at
> org.apache.ignite.internal.util.IgniteUtils$16.apply(IgniteUtils.java:1011)
> at
> org.apache.ignite.internal.util.IgniteUtils$16.apply(IgniteUtils.java:1009)
> ... 7 more
> Caused by: class
> org.apache.ignite.internal.transactions.IgniteTxSerializationCheckedException:
> Cannot serialize transaction due to write conflict (transaction is marked
> for rollback)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.serializationError(GridCacheMapEntry.java:7123)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.access$700(GridCacheMapEntry.java:136)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry$MvccUpdateLockListener.apply(GridCacheMapEntry.java:5629)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry$MvccUpdateLockListener.apply(GridCacheMapEntry.java:5482)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:407)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblock(GridFutureAdapter.java:355)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblockAll(GridFutureAdapter.java:343)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:520)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:498)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:464)
> at
> org.apache.ignite.internal.processors.cache.mvcc.MvccProcessorImpl$LockFuture.run(MvccProcessorImpl.java:1952)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
>
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
