You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2017/06/15 21:13:02 UTC
[jira] [Created] (IGNITE-5513) WalRecoveryTxLogicalRecordsTest is
broken, probably due to "inactive" cluster state
Vladimir Ozerov created IGNITE-5513:
---------------------------------------
Summary: WalRecoveryTxLogicalRecordsTest is broken, probably due to "inactive" cluster state
Key: IGNITE-5513
URL: https://issues.apache.org/jira/browse/IGNITE-5513
Project: Ignite
Issue Type: Bug
Components: cache
Reporter: Vladimir Ozerov
Assignee: Dmitriy Govorukhin
Fix For: 2.1
The following tests hang:
{{WalRecoveryTxLogicalRecordsTest.testRecoveryNoPageLost1}}
{{WalRecoveryTxLogicalRecordsTest.testRecoveryNoPageLost2}}
{{WalRecoveryTxLogicalRecordsTest.testRecoveryRandomPutRemove}}
{{WalRecoveryTxLogicalRecordsTest.testWalAfterPreloading}}
The following exception is seen nearby, most probably this is the root cause
{code}
[16:47:05]W: [org.apache.ignite:ignite-indexing] class org.apache.ignite.IgniteException: can not perform operation, because cluster inactive
[16:47:05]W: [org.apache.ignite:ignite-indexing] at org.apache.ignite.internal.IgniteKernal.checkClusterState(IgniteKernal.java:3666)
[16:47:05]W: [org.apache.ignite:ignite-indexing] at org.apache.ignite.internal.IgniteKernal.cache(IgniteKernal.java:2712)
[16:47:05]W: [org.apache.ignite:ignite-indexing] at org.apache.ignite.internal.processors.cache.persistence.db.wal.WalRecoveryTxLogicalRecordsTest.testFreeListRecovery(WalRecoveryTxLogicalRecordsTest.java:775)
[16:47:05]W: [org.apache.ignite:ignite-indexing] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[16:47:05]W: [org.apache.ignite:ignite-indexing] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
{code}:
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)