[MTCGA]: new failures in builds [3391876] needs to be handled
Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. If your changes can lead to this failure(s): We're grateful that you were a volunteer to make the contribution to this project, but things change and you may no longer be able to finalize your contribution. Could you respond to this email and indicate if you wish to continue and fix test failures or step down and some committer may revert you commit. *New stable failure of a flaky test in master GridVersionSelfTest.testVersions https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=2028128591644736718&branch=%3Cdefault%3E&tab=testDetails No changes in the build - Here's a reminder of what contributors were agreed to do https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute - Should you have any questions please contact dev@ignite.apache.org Best Regards, Apache Ignite TeamCity Bot https://github.com/apache/ignite-teamcity-bot Notification generated at 08:58:26 24-03-2019
[jira] [Created] (IGNITE-11618) Assertion got removed exception on entry with dht local candidate on transaction timeout
Alexey Goncharuk created IGNITE-11618: - Summary: Assertion got removed exception on entry with dht local candidate on transaction timeout Key: IGNITE-11618 URL: https://issues.apache.org/jira/browse/IGNITE-11618 Project: Ignite Issue Type: Bug Reporter: Alexey Goncharuk -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11617) New exchange coordinator skips client fast reply for previous exchange
Alexey Goncharuk created IGNITE-11617: - Summary: New exchange coordinator skips client fast reply for previous exchange Key: IGNITE-11617 URL: https://issues.apache.org/jira/browse/IGNITE-11617 Project: Ignite Issue Type: Bug Reporter: Alexey Goncharuk -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11616) NPE in MvccProcessorImpl when stopping a starting node
Alexey Goncharuk created IGNITE-11616:
-
Summary: NPE in MvccProcessorImpl when stopping a starting node
Key: IGNITE-11616
URL: https://issues.apache.org/jira/browse/IGNITE-11616
Project: Ignite
Issue Type: Test
Components: sql
Reporter: Alexey Goncharuk
Fix For: 2.8
I observe the following NPE in IgniteBaselineAffinityTopologyActivationTest.
It happens because we shutdown when MVCC coordinator is not assigned yet
{code}
java.lang.NullPointerException
at
java.util.concurrent.ConcurrentHashMap.replaceNode(ConcurrentHashMap.java:1106)
at
java.util.concurrent.ConcurrentHashMap.remove(ConcurrentHashMap.java:1097)
at
org.apache.ignite.internal.processors.cache.mvcc.MvccProcessorImpl.onCoordinatorFailed(MvccProcessorImpl.java:527)
at
org.apache.ignite.internal.processors.cache.mvcc.MvccProcessorImpl.onKernalStop(MvccProcessorImpl.java:459)
at org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:2335)
at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:2283)
at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1194)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1992)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1683)
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1109)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:607)
at
org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:984)
at
org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:925)
at
org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:913)
at
org.apache.ignite.internal.processors.cache.persistence.IgniteBaselineAffinityTopologyActivationTest.startGridWithConsistentId(IgniteBaselineAffinityTopologyActivationTest.java:729)
at
org.apache.ignite.internal.processors.cache.persistence.IgniteBaselineAffinityTopologyActivationTest.testNodeWithBltIsNotAllowedToJoinClusterDuringFirstActivation(IgniteBaselineAffinityTopologyActivationTest.java:532)
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:47)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at
org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2102)
at java.lang.Thread.run(Thread.java:745)
{code}
>From the first glance it looks like we can simply ignore the {{null}} node ID,
>however, there is a race - in {{onKernalStop}} we block a busy lock and remove
>discovery listener, then do a coordinator cleanup. However, the discovery
>notification worker is only stopped in {{stop}} phase, but MVCC manager does a
>cleanup in {{onKernalStop}} phase - so listener can execute some code after
>the {{onKernalStop}} is executed because there is no busy lock protection in
>the discovery listener itself.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11615) IgniteBaselineAffinityTopologyActivationTest sometimes fails due to NPE on node stop
Alexey Goncharuk created IGNITE-11615:
-
Summary: IgniteBaselineAffinityTopologyActivationTest sometimes
fails due to NPE on node stop
Key: IGNITE-11615
URL: https://issues.apache.org/jira/browse/IGNITE-11615
Project: Ignite
Issue Type: Test
Reporter: Alexey Goncharuk
Assignee: Alexey Goncharuk
Fix For: 2.8
I observe two kind of NPEs in the test:
The first one happens because we shutdown when MVCC coordinator is not assigned
yet
{code}
java.lang.NullPointerException
at
java.util.concurrent.ConcurrentHashMap.replaceNode(ConcurrentHashMap.java:1106)
at
java.util.concurrent.ConcurrentHashMap.remove(ConcurrentHashMap.java:1097)
at
org.apache.ignite.internal.processors.cache.mvcc.MvccProcessorImpl.onCoordinatorFailed(MvccProcessorImpl.java:527)
at
org.apache.ignite.internal.processors.cache.mvcc.MvccProcessorImpl.onKernalStop(MvccProcessorImpl.java:459)
at org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:2335)
at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:2283)
at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1194)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1992)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1683)
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1109)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:607)
at
org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:984)
at
org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:925)
at
org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:913)
at
org.apache.ignite.internal.processors.cache.persistence.IgniteBaselineAffinityTopologyActivationTest.startGridWithConsistentId(IgniteBaselineAffinityTopologyActivationTest.java:729)
at
org.apache.ignite.internal.processors.cache.persistence.IgniteBaselineAffinityTopologyActivationTest.testNodeWithBltIsNotAllowedToJoinClusterDuringFirstActivation(IgniteBaselineAffinityTopologyActivationTest.java:532)
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:47)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at
org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2102)
at java.lang.Thread.run(Thread.java:745)
{code}
The second one happens because we shutdown before the preloader was initialized:
{code}
[13:24:30]W: [org.apache.ignite:ignite-core]
java.lang.NullPointerException
[13:24:30]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.internal.processors.cache.CacheGroupContext.onKernalStop(CacheGroupContext.java:742)
[13:24:30]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStop(GridCacheProcessor.java:1158)
[13:24:30]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:2335)
[13:24:30]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:2283)
[13:24:30]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2570)
[13:24:30]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2533)
[13:24:30]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.internal.IgnitionEx.stop(IgnitionEx.java:330)
[13:24:30]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.Ignition.stop(Ignition.java:223)
[13:24:30]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.testframework.junits.GridAbstractTest.stopGrid(GridAbstractTest.java:1187)
[13:24:30]W: [org.apache.ignite:ignite-core]
