You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by "Vladislav Pyatkov (Jira)" <ji...@apache.org> on 2021/01/27 11:21:00 UTC

[jira] [Created] (IGNITE-14073) False alarm to lose all transaction nodes

Vladislav Pyatkov created IGNITE-14073:
------------------------------------------

             Summary: False alarm to lose all transaction nodes
                 Key: IGNITE-14073
                 URL: https://issues.apache.org/jira/browse/IGNITE-14073
             Project: Ignite
          Issue Type: Bug
            Reporter: Vladislav Pyatkov
            Assignee: Vladislav Pyatkov


This exception will happen when losing a primary and other one node during the transaction.
But it may not be truth, because the transaction will be able to continue on backups (if they are still alive).

{noformat}
 [2021-01-23 22:32:50,584][ERROR][test-runner-#1%near.IgniteTxExceptionNodeFailTest%][root] Transaction was not committed.
class org.apache.ignite.IgniteException: Failed to commit a transaction (all partition owners have left the grid, partition data has been lost) [cacheName=default, partition=3, key=386050343]
	at org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:1096)
	at org.apache.ignite.internal.processors.cache.transactions.TransactionProxyImpl.commit(TransactionProxyImpl.java:323)
	at org.apache.ignite.internal.processors.cache.distributed.near.IgniteTxExceptionNodeFailTest.cacheWithBackups(IgniteTxExceptionNodeFailTest.java:280)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
	at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
	at org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2367)
	at java.lang.Thread.run(Thread.java:748)
Caused by: class org.apache.ignite.internal.processors.cache.CacheInvalidStateException: Failed to commit a transaction (all partition owners have left the grid, partition data has been lost) [cacheName=default, partition=3, key=386050343]
	at org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxFinishFuture$FinishMiniFuture.onNodeLeft(GridNearTxFinishFuture.java:993)
	at org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxFinishFuture.onNodeLeft(GridNearTxFinishFuture.java:167)
	at org.apache.ignite.internal.processors.cache.GridCacheMvccManager$4.onEvent(GridCacheMvccManager.java:265)
	at org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager$LocalListenerWrapper.onEvent(GridEventStorageManager.java:1393)
	at org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.notifyListeners(GridEventStorageManager.java:888)
	at org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.notifyListeners(GridEventStorageManager.java:873)
	at org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.record0(GridEventStorageManager.java:349)
	at org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.record(GridEventStorageManager.java:312)
	at org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.recordEvent(GridDiscoveryManager.java:2948)
	at org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body0(GridDiscoveryManager.java:3164)
	at org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body(GridDiscoveryManager.java:2968)
	at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
	... 1 more
{noformat}
It will frighten a client, because it looks like a data lose.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)