[jira] [Updated] (PHOENIX-6251) Fix ConcurrentMutationsExtendedIT.testConcurrentUpsertsWithNoIndexedColumns timout issue
[ https://issues.apache.org/jira/browse/PHOENIX-6251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viraj Jasani updated PHOENIX-6251: -- Attachment: PHOENIX-6251.master.000.patch > Fix ConcurrentMutationsExtendedIT.testConcurrentUpsertsWithNoIndexedColumns > timout issue > > > Key: PHOENIX-6251 > URL: https://issues.apache.org/jira/browse/PHOENIX-6251 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 5.0.0, 4.15.0 >Reporter: Xinyi Yan >Assignee: Viraj Jasani >Priority: Major > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-6251.4.x.000.patch, PHOENIX-6251.master.000.patch > > > ConcurrentMutationsExtendedIT.testConcurrentUpsertsWithNoIndexedColumns > failed 3 out last 10 runs. > > [https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-mulitbranch/job/4.x/134/testReport/org.apache.phoenix.end2end/ConcurrentMutationsExtendedIT/MatrixBuild___Matrix___HBASE_PROFILE1_6BuildAndTest___testConcurrentUpsertsWithNoIndexedColumns/] > > https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-mulitbranch/job/4.x/137/testReport/org.apache.phoenix.end2end/ConcurrentMutationsExtendedIT/MatrixBuild___Matrix___HBASE_PROFILE1_3BuildAndTest___testConcurrentUpsertsWithNoIndexedColumns/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6251) Fix ConcurrentMutationsExtendedIT.testConcurrentUpsertsWithNoIndexedColumns timout issue
[ https://issues.apache.org/jira/browse/PHOENIX-6251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viraj Jasani updated PHOENIX-6251: -- Attachment: PHOENIX-6251.4.x.000.patch > Fix ConcurrentMutationsExtendedIT.testConcurrentUpsertsWithNoIndexedColumns > timout issue > > > Key: PHOENIX-6251 > URL: https://issues.apache.org/jira/browse/PHOENIX-6251 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 5.0.0, 4.15.0 >Reporter: Xinyi Yan >Assignee: Viraj Jasani >Priority: Major > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-6251.4.x.000.patch > > > ConcurrentMutationsExtendedIT.testConcurrentUpsertsWithNoIndexedColumns > failed 3 out last 10 runs. > > [https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-mulitbranch/job/4.x/134/testReport/org.apache.phoenix.end2end/ConcurrentMutationsExtendedIT/MatrixBuild___Matrix___HBASE_PROFILE1_6BuildAndTest___testConcurrentUpsertsWithNoIndexedColumns/] > > https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-mulitbranch/job/4.x/137/testReport/org.apache.phoenix.end2end/ConcurrentMutationsExtendedIT/MatrixBuild___Matrix___HBASE_PROFILE1_3BuildAndTest___testConcurrentUpsertsWithNoIndexedColumns/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6251) Fix ConcurrentMutationsExtendedIT.testConcurrentUpsertsWithNoIndexedColumns timout issue
[ https://issues.apache.org/jira/browse/PHOENIX-6251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viraj Jasani updated PHOENIX-6251: -- Affects Version/s: 5.0.0 > Fix ConcurrentMutationsExtendedIT.testConcurrentUpsertsWithNoIndexedColumns > timout issue > > > Key: PHOENIX-6251 > URL: https://issues.apache.org/jira/browse/PHOENIX-6251 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 5.0.0, 4.15.0 >Reporter: Xinyi Yan >Assignee: Viraj Jasani >Priority: Major > Fix For: 5.1.0, 4.16.0 > > > ConcurrentMutationsExtendedIT.testConcurrentUpsertsWithNoIndexedColumns > failed 3 out last 10 runs. > > [https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-mulitbranch/job/4.x/134/testReport/org.apache.phoenix.end2end/ConcurrentMutationsExtendedIT/MatrixBuild___Matrix___HBASE_PROFILE1_6BuildAndTest___testConcurrentUpsertsWithNoIndexedColumns/] > > https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-mulitbranch/job/4.x/137/testReport/org.apache.phoenix.end2end/ConcurrentMutationsExtendedIT/MatrixBuild___Matrix___HBASE_PROFILE1_3BuildAndTest___testConcurrentUpsertsWithNoIndexedColumns/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6256) Fix MaxConcurrentConnectionsIT test flapper
[ https://issues.apache.org/jira/browse/PHOENIX-6256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-6256: -- Fix Version/s: (was: 5.1.0) > Fix MaxConcurrentConnectionsIT test flapper > --- > > Key: PHOENIX-6256 > URL: https://issues.apache.org/jira/browse/PHOENIX-6256 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 5.0.0, 4.15.0 >Reporter: Xinyi Yan >Assignee: Chinmay Kulkarni >Priority: Major > Fix For: 4.16.0 > > > MaxConcurrentConnectionsIT failed 3 out of last 10 runs. > > h3. Error Message > Found 1 connections still open. expected:<0> but was:<1> > h3. Stacktrace > java.lang.AssertionError: Found 1 connections still open. expected:<0> but > was:<1> at org.junit.Assert.fail(Assert.java:89) at > org.junit.Assert.failNotEquals(Assert.java:835) at > org.junit.Assert.assertEquals(Assert.java:647) at > org.apache.phoenix.query.MaxConcurrentConnectionsIT.testDeleteRuntimeFailureClosesConnections(MaxConcurrentConnectionsIT.java:122) > 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:59) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56) > at > org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306) at > org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366) at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63) > at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331) at > org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79) at > org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329) at > org.junit.runners.ParentRunner.access$100(ParentRunner.java:66) at > org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293) at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at > org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:54) at > org.junit.rules.RunRules.evaluate(RunRules.java:20) at > org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306) at > org.junit.runners.ParentRunner.run(ParentRunner.java:413) at > org.junit.runners.Suite.runChild(Suite.java:128) at > org.junit.runners.Suite.runChild(Suite.java:27) at > org.junit.runners.ParentRunner$4.run(ParentRunner.java:331) at > org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79) at > org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329) at > org.junit.runners.ParentRunner.access$100(ParentRunner.java:66) at > org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293) at > org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306) at > org.junit.runners.ParentRunner.run(ParentRunner.java:413) at > org.apache.maven.surefire.junitcore.JUnitCore.run(JUnitCore.java:55) at > org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:137) > at > org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107) > at > org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:83) > at > org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75) > at > org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:158) > at > org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:383) > at > org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:344) > at > org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:125) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:417) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6256) Fix MaxConcurrentConnectionsIT test flapper
[ https://issues.apache.org/jira/browse/PHOENIX-6256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-6256: -- Affects Version/s: (was: 5.0.0) > Fix MaxConcurrentConnectionsIT test flapper > --- > > Key: PHOENIX-6256 > URL: https://issues.apache.org/jira/browse/PHOENIX-6256 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 4.15.0 >Reporter: Xinyi Yan >Assignee: Chinmay Kulkarni >Priority: Major > Fix For: 4.16.0 > > > MaxConcurrentConnectionsIT failed 3 out of last 10 runs. > > h3. Error Message > Found 1 connections still open. expected:<0> but was:<1> > h3. Stacktrace > java.lang.AssertionError: Found 1 connections still open. expected:<0> but > was:<1> at org.junit.Assert.fail(Assert.java:89) at > org.junit.Assert.failNotEquals(Assert.java:835) at > org.junit.Assert.assertEquals(Assert.java:647) at > org.apache.phoenix.query.MaxConcurrentConnectionsIT.testDeleteRuntimeFailureClosesConnections(MaxConcurrentConnectionsIT.java:122) > 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:59) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56) > at > org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306) at > org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366) at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63) > at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331) at > org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79) at > org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329) at > org.junit.runners.ParentRunner.access$100(ParentRunner.java:66) at > org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293) at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at > org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:54) at > org.junit.rules.RunRules.evaluate(RunRules.java:20) at > org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306) at > org.junit.runners.ParentRunner.run(ParentRunner.java:413) at > org.junit.runners.Suite.runChild(Suite.java:128) at > org.junit.runners.Suite.runChild(Suite.java:27) at > org.junit.runners.ParentRunner$4.run(ParentRunner.java:331) at > org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79) at > org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329) at > org.junit.runners.ParentRunner.access$100(ParentRunner.java:66) at > org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293) at > org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306) at > org.junit.runners.ParentRunner.run(ParentRunner.java:413) at > org.apache.maven.surefire.junitcore.JUnitCore.run(JUnitCore.java:55) at > org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:137) > at > org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107) > at > org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:83) > at > org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75) > at > org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:158) > at > org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:383) > at > org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:344) > at > org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:125) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:417) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6256) Fix MaxConcurrentConnectionsIT test flapper
[ https://issues.apache.org/jira/browse/PHOENIX-6256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-6256: -- Affects Version/s: 5.0.0 4.15.0 > Fix MaxConcurrentConnectionsIT test flapper > --- > > Key: PHOENIX-6256 > URL: https://issues.apache.org/jira/browse/PHOENIX-6256 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 5.0.0, 4.15.0 >Reporter: Xinyi Yan >Assignee: Chinmay Kulkarni >Priority: Major > Fix For: 4.16.0 > > > MaxConcurrentConnectionsIT failed 3 out of last 10 runs. > > h3. Error Message > Found 1 connections still open. expected:<0> but was:<1> > h3. Stacktrace > java.lang.AssertionError: Found 1 connections still open. expected:<0> but > was:<1> at org.junit.Assert.fail(Assert.java:89) at > org.junit.Assert.failNotEquals(Assert.java:835) at > org.junit.Assert.assertEquals(Assert.java:647) at > org.apache.phoenix.query.MaxConcurrentConnectionsIT.testDeleteRuntimeFailureClosesConnections(MaxConcurrentConnectionsIT.java:122) > 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:59) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56) > at > org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306) at > org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366) at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63) > at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331) at > org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79) at > org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329) at > org.junit.runners.ParentRunner.access$100(ParentRunner.java:66) at > org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293) at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at > org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:54) at > org.junit.rules.RunRules.evaluate(RunRules.java:20) at > org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306) at > org.junit.runners.ParentRunner.run(ParentRunner.java:413) at > org.junit.runners.Suite.runChild(Suite.java:128) at > org.junit.runners.Suite.runChild(Suite.java:27) at > org.junit.runners.ParentRunner$4.run(ParentRunner.java:331) at > org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79) at > org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329) at > org.junit.runners.ParentRunner.access$100(ParentRunner.java:66) at > org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293) at > org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306) at > org.junit.runners.ParentRunner.run(ParentRunner.java:413) at > org.apache.maven.surefire.junitcore.JUnitCore.run(JUnitCore.java:55) at > org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:137) > at > org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107) > at > org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:83) > at > org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75) > at > org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:158) > at > org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:383) > at > org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:344) > at > org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:125) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:417) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6256) Fix MaxConcurrentConnectionsIT test flapper
[ https://issues.apache.org/jira/browse/PHOENIX-6256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-6256: -- Fix Version/s: 5.1.0 > Fix MaxConcurrentConnectionsIT test flapper > --- > > Key: PHOENIX-6256 > URL: https://issues.apache.org/jira/browse/PHOENIX-6256 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 5.0.0, 4.15.0 >Reporter: Xinyi Yan >Assignee: Chinmay Kulkarni >Priority: Major > Fix For: 5.1.0, 4.16.0 > > > MaxConcurrentConnectionsIT failed 3 out of last 10 runs. > > h3. Error Message > Found 1 connections still open. expected:<0> but was:<1> > h3. Stacktrace > java.lang.AssertionError: Found 1 connections still open. expected:<0> but > was:<1> at org.junit.Assert.fail(Assert.java:89) at > org.junit.Assert.failNotEquals(Assert.java:835) at > org.junit.Assert.assertEquals(Assert.java:647) at > org.apache.phoenix.query.MaxConcurrentConnectionsIT.testDeleteRuntimeFailureClosesConnections(MaxConcurrentConnectionsIT.java:122) > 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:59) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56) > at > org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306) at > org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366) at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63) > at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331) at > org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79) at > org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329) at > org.junit.runners.ParentRunner.access$100(ParentRunner.java:66) at > org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293) at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at > org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:54) at > org.junit.rules.RunRules.evaluate(RunRules.java:20) at > org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306) at > org.junit.runners.ParentRunner.run(ParentRunner.java:413) at > org.junit.runners.Suite.runChild(Suite.java:128) at > org.junit.runners.Suite.runChild(Suite.java:27) at > org.junit.runners.ParentRunner$4.run(ParentRunner.java:331) at > org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79) at > org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329) at > org.junit.runners.ParentRunner.access$100(ParentRunner.java:66) at > org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293) at > org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306) at > org.junit.runners.ParentRunner.run(ParentRunner.java:413) at > org.apache.maven.surefire.junitcore.JUnitCore.run(JUnitCore.java:55) at > org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:137) > at > org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107) > at > org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:83) > at > org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75) > at > org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:158) > at > org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:383) > at > org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:344) > at > org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:125) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:417) -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: IndexExtendedIT always failed on 4.x and master
Thanks Geoffrey (and Chenglei once again). On Thu, Dec 10, 2020 at 12:46 PM Geoffrey Jacoby wrote: > I already reverted the patch from both branches earlier this afternoon. > Sorry for the noise. > > Geoffrey > > On Thu, Dec 10, 2020 at 2:44 PM Ankit Singhal > wrote: > > > Please free to revert from 4.x (and master) and re-open the corresponding > > JIRA. > > > > On Thu, Dec 10, 2020 at 5:50 AM 程磊 wrote: > > > > > > > > > > > > > > Yes， when I revert the 4.x before PHOENIX-5140, the IndexExtendedIT > and > > > IndexScrutinyToolIT are sucess. > > > but after applying PHOENIX-5140,both IndexExtendedIT and > > > IndexScrutinyToolIT are always failed. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > At 2020-12-10 16:51:27, "Ankit Singhal" > > wrote: > > > >Thanks Chenglei for bringing the failures to the notice. Have you > > > confirmed > > > >that reverting PHOENIX-5140 fixes the problem? if yes then I would > > suggest > > > >reverting the fix and re-open the JIRA to be worked upon separately > for > > > the > > > >new fix. > > > > > > > >On Wed, Dec 9, 2020 at 7:14 PM cheng...@apache.org < > cheng...@apache.org > > > > > > >wrote: > > > > > > > >> I noticed IndexExtendedIT always failed on 4.x and master now, It > may > > be > > > >> caused by PHOENIX-5140 , for 4.x , the stack is : > > > >> java.lang.AssertionError: expected:<0> but was:<-1> > > > >> at org.junit.Assert.fail(Assert.java:89) > > > >> at org.junit.Assert.failNotEquals(Assert.java:835) > > > >> at org.junit.Assert.assertEquals(Assert.java:647) > > > >> at org.junit.Assert.assertEquals(Assert.java:633) > > > >> at > > > >> > > > > org.apache.phoenix.end2end.IndexToolIT.runIndexTool(IndexToolIT.java:806) > > > >> at > > > >> > > > > org.apache.phoenix.end2end.IndexToolIT.runIndexTool(IndexToolIT.java:785) > > > >> at > > > >> > > > > org.apache.phoenix.end2end.IndexToolIT.runIndexTool(IndexToolIT.java:776) > > > >> at > > > >> > > > > org.apache.phoenix.end2end.IndexToolIT.runIndexTool(IndexToolIT.java:770) > > > >> at > > > >> > > > > org.apache.phoenix.end2end.IndexToolIT.runIndexTool(IndexToolIT.java:744) > > > >> at > > > >> > > > > > > org.apache.phoenix.end2end.IndexExtendedIT.testMutableIndexWithUpdates(IndexExtendedIT.java:166) > > > >> > > > >> > > > >> and the similar stack is on master， I suggest we should rollback or > > stop > > > >> commit to the repo until the problem is fixed. > > > > > >
Re: IndexExtendedIT always failed on 4.x and master
I already reverted the patch from both branches earlier this afternoon. Sorry for the noise. Geoffrey On Thu, Dec 10, 2020 at 2:44 PM Ankit Singhal wrote: > Please free to revert from 4.x (and master) and re-open the corresponding > JIRA. > > On Thu, Dec 10, 2020 at 5:50 AM 程磊 wrote: > > > > > > > > > Yes， when I revert the 4.x before PHOENIX-5140, the IndexExtendedIT and > > IndexScrutinyToolIT are sucess. > > but after applying PHOENIX-5140,both IndexExtendedIT and > > IndexScrutinyToolIT are always failed. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > At 2020-12-10 16:51:27, "Ankit Singhal" > wrote: > > >Thanks Chenglei for bringing the failures to the notice. Have you > > confirmed > > >that reverting PHOENIX-5140 fixes the problem? if yes then I would > suggest > > >reverting the fix and re-open the JIRA to be worked upon separately for > > the > > >new fix. > > > > > >On Wed, Dec 9, 2020 at 7:14 PM cheng...@apache.org > > > >wrote: > > > > > >> I noticed IndexExtendedIT always failed on 4.x and master now, It may > be > > >> caused by PHOENIX-5140 , for 4.x , the stack is : > > >> java.lang.AssertionError: expected:<0> but was:<-1> > > >> at org.junit.Assert.fail(Assert.java:89) > > >> at org.junit.Assert.failNotEquals(Assert.java:835) > > >> at org.junit.Assert.assertEquals(Assert.java:647) > > >> at org.junit.Assert.assertEquals(Assert.java:633) > > >> at > > >> > > org.apache.phoenix.end2end.IndexToolIT.runIndexTool(IndexToolIT.java:806) > > >> at > > >> > > org.apache.phoenix.end2end.IndexToolIT.runIndexTool(IndexToolIT.java:785) > > >> at > > >> > > org.apache.phoenix.end2end.IndexToolIT.runIndexTool(IndexToolIT.java:776) > > >> at > > >> > > org.apache.phoenix.end2end.IndexToolIT.runIndexTool(IndexToolIT.java:770) > > >> at > > >> > > org.apache.phoenix.end2end.IndexToolIT.runIndexTool(IndexToolIT.java:744) > > >> at > > >> > > > org.apache.phoenix.end2end.IndexExtendedIT.testMutableIndexWithUpdates(IndexExtendedIT.java:166) > > >> > > >> > > >> and the similar stack is on master， I suggest we should rollback or > stop > > >> commit to the repo until the problem is fixed. > > >
Re: IndexExtendedIT always failed on 4.x and master
Please free to revert from 4.x (and master) and re-open the corresponding JIRA. On Thu, Dec 10, 2020 at 5:50 AM 程磊 wrote: > > > > Yes， when I revert the 4.x before PHOENIX-5140, the IndexExtendedIT and > IndexScrutinyToolIT are sucess. > but after applying PHOENIX-5140,both IndexExtendedIT and > IndexScrutinyToolIT are always failed. > > > > > > > > > > > > > > > At 2020-12-10 16:51:27, "Ankit Singhal" wrote: > >Thanks Chenglei for bringing the failures to the notice. Have you > confirmed > >that reverting PHOENIX-5140 fixes the problem? if yes then I would suggest > >reverting the fix and re-open the JIRA to be worked upon separately for > the > >new fix. > > > >On Wed, Dec 9, 2020 at 7:14 PM cheng...@apache.org > >wrote: > > > >> I noticed IndexExtendedIT always failed on 4.x and master now, It may be > >> caused by PHOENIX-5140 , for 4.x , the stack is : > >> java.lang.AssertionError: expected:<0> but was:<-1> > >> at org.junit.Assert.fail(Assert.java:89) > >> at org.junit.Assert.failNotEquals(Assert.java:835) > >> at org.junit.Assert.assertEquals(Assert.java:647) > >> at org.junit.Assert.assertEquals(Assert.java:633) > >> at > >> > org.apache.phoenix.end2end.IndexToolIT.runIndexTool(IndexToolIT.java:806) > >> at > >> > org.apache.phoenix.end2end.IndexToolIT.runIndexTool(IndexToolIT.java:785) > >> at > >> > org.apache.phoenix.end2end.IndexToolIT.runIndexTool(IndexToolIT.java:776) > >> at > >> > org.apache.phoenix.end2end.IndexToolIT.runIndexTool(IndexToolIT.java:770) > >> at > >> > org.apache.phoenix.end2end.IndexToolIT.runIndexTool(IndexToolIT.java:744) > >> at > >> > org.apache.phoenix.end2end.IndexExtendedIT.testMutableIndexWithUpdates(IndexExtendedIT.java:166) > >> > >> > >> and the similar stack is on master， I suggest we should rollback or stop > >> commit to the repo until the problem is fixed. >
[jira] [Updated] (PHOENIX-6250) Fix ViewMetadataIT test flapper
[
https://issues.apache.org/jira/browse/PHOENIX-6250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xinyi Yan updated PHOENIX-6250:
---
Attachment: (was: PHOENIX-6250.4.x.v1.patch)
> Fix ViewMetadataIT test flapper
> ---
>
> Key: PHOENIX-6250
> URL: https://issues.apache.org/jira/browse/PHOENIX-6250
> Project: Phoenix
> Issue Type: Improvement
>Reporter: Xinyi Yan
>Priority: Major
> Fix For: 4.16.0
>
> Attachments: PHOENIX-6250.4.x.v2.patch
>
>
> ViewMetadataIT failed multi-times at 4.x branch.
> Here is the logging:
> {code:java}
> 17:32:58 [ERROR] Tests run: 25, Failures: 1, Errors: 0, Skipped: 0, Time
> elapsed: 353.71 s <<< FAILURE! - in org.apache.phoenix.end2end.ViewMetadataIT
> 17:32:58 [ERROR]
> testRepeatedCreateAndDropCascadeTableWorks(org.apache.phoenix.end2end.ViewMetadataIT)
> Time elapsed: 11.52 s <<< FAILURE!
> 17:32:58 java.lang.AssertionError: View SCHEMA2.N74 should have been
> deleted when parent was dropped
> 17:32:58 at org.junit.Assert.fail(Assert.java:89)
> 17:32:58 at
> org.apache.phoenix.end2end.ViewMetadataIT.validateViewDoesNotExist(ViewMetadataIT.java:1373)
> 17:32:58 at
> org.apache.phoenix.end2end.ViewMetadataIT.testRepeatedCreateAndDropCascadeTableWorks(ViewMetadataIT.java:818)
> 17:32:58 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 17:32:58 at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 17:32:58 at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 17:32:58 at java.lang.reflect.Method.invoke(Method.java:498)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (PHOENIX-6250) Fix ViewMetadataIT test flapper
[
https://issues.apache.org/jira/browse/PHOENIX-6250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xinyi Yan updated PHOENIX-6250:
---
Attachment: PHOENIX-6250.4.x.v2.patch
> Fix ViewMetadataIT test flapper
> ---
>
> Key: PHOENIX-6250
> URL: https://issues.apache.org/jira/browse/PHOENIX-6250
> Project: Phoenix
> Issue Type: Improvement
>Reporter: Xinyi Yan
>Priority: Major
> Fix For: 4.16.0
>
> Attachments: PHOENIX-6250.4.x.v1.patch, PHOENIX-6250.4.x.v2.patch
>
>
> ViewMetadataIT failed multi-times at 4.x branch.
> Here is the logging:
> {code:java}
> 17:32:58 [ERROR] Tests run: 25, Failures: 1, Errors: 0, Skipped: 0, Time
> elapsed: 353.71 s <<< FAILURE! - in org.apache.phoenix.end2end.ViewMetadataIT
> 17:32:58 [ERROR]
> testRepeatedCreateAndDropCascadeTableWorks(org.apache.phoenix.end2end.ViewMetadataIT)
> Time elapsed: 11.52 s <<< FAILURE!
> 17:32:58 java.lang.AssertionError: View SCHEMA2.N74 should have been
> deleted when parent was dropped
> 17:32:58 at org.junit.Assert.fail(Assert.java:89)
> 17:32:58 at
> org.apache.phoenix.end2end.ViewMetadataIT.validateViewDoesNotExist(ViewMetadataIT.java:1373)
> 17:32:58 at
> org.apache.phoenix.end2end.ViewMetadataIT.testRepeatedCreateAndDropCascadeTableWorks(ViewMetadataIT.java:818)
> 17:32:58 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 17:32:58 at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 17:32:58 at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 17:32:58 at java.lang.reflect.Method.invoke(Method.java:498)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Reopened] (PHOENIX-5140) TableNotFoundException occurs when we create local asynchronous index
[
https://issues.apache.org/jira/browse/PHOENIX-5140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Geoffrey Jacoby reopened PHOENIX-5140:
--
Reopening because of reports that this patch broke IndexExtendedIT. Reverted
the patch for now from 4.x and master. Sorry for the noise.
[~clevertension] [~comnetwork] [~yanxinyi], fyi.
> TableNotFoundException occurs when we create local asynchronous index
> -
>
> Key: PHOENIX-5140
> URL: https://issues.apache.org/jira/browse/PHOENIX-5140
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 5.0.0
> Environment: > HDP : 3.0.0.0， HBase : 2.0.0，phoenix : 5.0.0 and
> hadoop : 3.1.0
>Reporter: MariaCarrie
>Assignee: dan zheng
>Priority: Major
> Labels: IndexTool, localIndex, tableUndefined
> Fix For: 5.1.0, 4.16.0
>
> Attachments: PHOENIX-5140-master-v1.patch,
> PHOENIX-5140-master-v2.patch
>
> Original Estimate: 48h
> Time Spent: 20m
> Remaining Estimate: 47h 40m
>
> First I create the table and insert the data:
> ^create table DMP.DMP_INDEX_TEST2 (id varchar not null primary key,name
> varchar,age varchar);^
> ^upsert into DMP.DMP_INDEX_TEST2 values('id01','name01','age01');^
> The asynchronous index is then created:
> ^create local index if not exists TMP_INDEX_DMP_TEST2 on DMP.DMP_INDEX_TEST2
> (name) ASYNC;^
> Because kerberos is enabled,So I need kinit HBase principal first,Then
> execute the following command:
> ^HADOOP_CLASSPATH="/etc/hbase/conf" hadoop jar
> /usr/hdp/3.0.0.0-1634/phoenix/phoenix-client.jar
> org.apache.phoenix.mapreduce.index.IndexTool --schema DMP --data-table
> DMP_INDEX_TEST2 --index-table TMP_INDEX_DMP_TEST2 --output-path
> /hbase-backup2^
> But I got the following error:
> ^Error: java.lang.RuntimeException:
> org.apache.phoenix.schema.TableNotFoundException: ERROR 1012 (42M03): Table
> undefined. tableName=DMP.DMP_INDEX_TEST2^
> ^at
> org.apache.phoenix.mapreduce.index.PhoenixIndexImportMapper.map(PhoenixIndexImportMapper.java:124)^
> ^at
> org.apache.phoenix.mapreduce.index.PhoenixIndexImportMapper.map(PhoenixIndexImportMapper.java:50)^
> ^at org.apache.hadoop.mapreduce.Mapper.run(Mapper.java:146)^
> ^at org.apache.hadoop.mapred.MapTask.runNewMapper(MapTask.java:799)^
> ^at org.apache.hadoop.mapred.MapTask.run(MapTask.java:347)^
> ^at org.apache.hadoop.mapred.YarnChild$2.run(YarnChild.java:174)^
> ^at java.security.AccessController.doPrivileged(Native Method)^
> ^at javax.security.auth.Subject.doAs(Subject.java:422)^
> ^at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1688)^
> ^at org.apache.hadoop.mapred.YarnChild.main(YarnChild.java:168)^
> ^Caused by: org.apache.phoenix.schema.TableNotFoundException: ERROR 1012
> (42M03): Table undefined. tableName=DMP.DMP_INDEX_TEST2^
> ^at
> org.apache.phoenix.query.ConnectionQueryServicesImpl.getTableRegionLocation(ConnectionQueryServicesImpl.java:4544)^
> ^at
> org.apache.phoenix.query.DelegateConnectionQueryServices.getTableRegionLocation(DelegateConnectionQueryServices.java:312)^
> ^at
> org.apache.phoenix.compile.UpsertCompiler.setValues(UpsertCompiler.java:163)^
> ^at
> org.apache.phoenix.compile.UpsertCompiler.access$500(UpsertCompiler.java:118)^
> ^at
> org.apache.phoenix.compile.UpsertCompiler$UpsertValuesMutationPlan.execute(UpsertCompiler.java:1202)^
> ^at
> org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:408)^
> ^at
> org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:391)^
> ^at org.apache.phoenix.call.CallRunner.run(CallRunner.java:53)^
> ^at
> org.apache.phoenix.jdbc.PhoenixStatement.executeMutation(PhoenixStatement.java:390)^
> ^at
> org.apache.phoenix.jdbc.PhoenixStatement.executeMutation(PhoenixStatement.java:378)^
> ^at
> org.apache.phoenix.jdbc.PhoenixPreparedStatement.execute(PhoenixPreparedStatement.java:173)^
> ^at
> org.apache.phoenix.jdbc.PhoenixPreparedStatement.execute(PhoenixPreparedStatement.java:183)^
> ^at
> org.apache.phoenix.mapreduce.index.PhoenixIndexImportMapper.map(PhoenixIndexImportMapper.java:103)^
> ^... 9 more^
> I can query this table and have access to it,It works well:
> ^select * from DMP.DMP_INDEX_TEST2;^
> ^select * from DMP.TMP_INDEX_DMP_TEST2;^
> ^drop table DMP.DMP_INDEX_TEST2;^
> But why did my MR task make this mistake? Any Suggestions from anyone?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (PHOENIX-6252) Fix BackwardCompatibilityIT test flapper
[ https://issues.apache.org/jira/browse/PHOENIX-6252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan updated PHOENIX-6252: --- Attachment: PHOENIX-6252.4.x.v1.patch > Fix BackwardCompatibilityIT test flapper > > > Key: PHOENIX-6252 > URL: https://issues.apache.org/jira/browse/PHOENIX-6252 > Project: Phoenix > Issue Type: Improvement >Reporter: Xinyi Yan >Assignee: Xinyi Yan >Priority: Major > Fix For: 4.16.0 > > Attachments: PHOENIX-6252.4.x.v1.patch, PHOENIX-6252.master.v2.patch > > > BackwardCompatibilityIT failed 4 out of the last 10 runs. > > [https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-mulitbranch/job/4.x/135/testReport/org.apache.phoenix.end2end/BackwardCompatibilityIT/MatrixBuild___Matrix___HBASE_PROFILE1_4BuildAndTest___testSystemTaskCreationWithIndexAsyncRebuild_BackwardCompatibilityIT_compatibleClientVersion_4_15_0_HBase_1_4_/] > https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-mulitbranch/job/4.x/128/testReport/org.apache.phoenix.end2end/BackwardCompatibilityIT/MatrixBuild___Matrix___HBASE_PROFILE1_4BuildAndTest___testSystemTaskCreationWithIndexAsyncRebuild_BackwardCompatibilityIT_compatibleClientVersion_4_15_0_HBase_1_4_/ > > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6252) Fix BackwardCompatibilityIT test flapper
[ https://issues.apache.org/jira/browse/PHOENIX-6252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan updated PHOENIX-6252: --- Attachment: (was: PHOENIX-6252.4.x.v1.patch) > Fix BackwardCompatibilityIT test flapper > > > Key: PHOENIX-6252 > URL: https://issues.apache.org/jira/browse/PHOENIX-6252 > Project: Phoenix > Issue Type: Improvement >Reporter: Xinyi Yan >Assignee: Xinyi Yan >Priority: Major > Fix For: 4.16.0 > > Attachments: PHOENIX-6252.4.x.v1.patch, PHOENIX-6252.master.v2.patch > > > BackwardCompatibilityIT failed 4 out of the last 10 runs. > > [https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-mulitbranch/job/4.x/135/testReport/org.apache.phoenix.end2end/BackwardCompatibilityIT/MatrixBuild___Matrix___HBASE_PROFILE1_4BuildAndTest___testSystemTaskCreationWithIndexAsyncRebuild_BackwardCompatibilityIT_compatibleClientVersion_4_15_0_HBase_1_4_/] > https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-mulitbranch/job/4.x/128/testReport/org.apache.phoenix.end2end/BackwardCompatibilityIT/MatrixBuild___Matrix___HBASE_PROFILE1_4BuildAndTest___testSystemTaskCreationWithIndexAsyncRebuild_BackwardCompatibilityIT_compatibleClientVersion_4_15_0_HBase_1_4_/ > > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (PHOENIX-6256) Fix MaxConcurrentConnectionsIT test flapper
[ https://issues.apache.org/jira/browse/PHOENIX-6256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni reassigned PHOENIX-6256: - Assignee: Chinmay Kulkarni > Fix MaxConcurrentConnectionsIT test flapper > --- > > Key: PHOENIX-6256 > URL: https://issues.apache.org/jira/browse/PHOENIX-6256 > Project: Phoenix > Issue Type: Improvement >Reporter: Xinyi Yan >Assignee: Chinmay Kulkarni >Priority: Major > Fix For: 4.16.0 > > > MaxConcurrentConnectionsIT failed 3 out of last 10 runs. > > h3. Error Message > Found 1 connections still open. expected:<0> but was:<1> > h3. Stacktrace > java.lang.AssertionError: Found 1 connections still open. expected:<0> but > was:<1> at org.junit.Assert.fail(Assert.java:89) at > org.junit.Assert.failNotEquals(Assert.java:835) at > org.junit.Assert.assertEquals(Assert.java:647) at > org.apache.phoenix.query.MaxConcurrentConnectionsIT.testDeleteRuntimeFailureClosesConnections(MaxConcurrentConnectionsIT.java:122) > 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:59) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56) > at > org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306) at > org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366) at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63) > at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331) at > org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79) at > org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329) at > org.junit.runners.ParentRunner.access$100(ParentRunner.java:66) at > org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293) at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at > org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:54) at > org.junit.rules.RunRules.evaluate(RunRules.java:20) at > org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306) at > org.junit.runners.ParentRunner.run(ParentRunner.java:413) at > org.junit.runners.Suite.runChild(Suite.java:128) at > org.junit.runners.Suite.runChild(Suite.java:27) at > org.junit.runners.ParentRunner$4.run(ParentRunner.java:331) at > org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79) at > org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329) at > org.junit.runners.ParentRunner.access$100(ParentRunner.java:66) at > org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293) at > org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306) at > org.junit.runners.ParentRunner.run(ParentRunner.java:413) at > org.apache.maven.surefire.junitcore.JUnitCore.run(JUnitCore.java:55) at > org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:137) > at > org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107) > at > org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:83) > at > org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75) > at > org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:158) > at > org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:383) > at > org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:344) > at > org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:125) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:417) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6251) Fix ConcurrentMutationsExtendedIT.testConcurrentUpsertsWithNoIndexedColumns timout issue
[ https://issues.apache.org/jira/browse/PHOENIX-6251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viraj Jasani updated PHOENIX-6251: -- Affects Version/s: 4.15.0 > Fix ConcurrentMutationsExtendedIT.testConcurrentUpsertsWithNoIndexedColumns > timout issue > > > Key: PHOENIX-6251 > URL: https://issues.apache.org/jira/browse/PHOENIX-6251 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 4.15.0 >Reporter: Xinyi Yan >Assignee: Viraj Jasani >Priority: Major > Fix For: 5.1.0, 4.16.0 > > > ConcurrentMutationsExtendedIT.testConcurrentUpsertsWithNoIndexedColumns > failed 3 out last 10 runs. > > [https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-mulitbranch/job/4.x/134/testReport/org.apache.phoenix.end2end/ConcurrentMutationsExtendedIT/MatrixBuild___Matrix___HBASE_PROFILE1_6BuildAndTest___testConcurrentUpsertsWithNoIndexedColumns/] > > https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-mulitbranch/job/4.x/137/testReport/org.apache.phoenix.end2end/ConcurrentMutationsExtendedIT/MatrixBuild___Matrix___HBASE_PROFILE1_3BuildAndTest___testConcurrentUpsertsWithNoIndexedColumns/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6251) Fix ConcurrentMutationsExtendedIT.testConcurrentUpsertsWithNoIndexedColumns timout issue
[ https://issues.apache.org/jira/browse/PHOENIX-6251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viraj Jasani updated PHOENIX-6251: -- Fix Version/s: 5.1.0 > Fix ConcurrentMutationsExtendedIT.testConcurrentUpsertsWithNoIndexedColumns > timout issue > > > Key: PHOENIX-6251 > URL: https://issues.apache.org/jira/browse/PHOENIX-6251 > Project: Phoenix > Issue Type: Improvement >Reporter: Xinyi Yan >Assignee: Viraj Jasani >Priority: Major > Fix For: 5.1.0, 4.16.0 > > > ConcurrentMutationsExtendedIT.testConcurrentUpsertsWithNoIndexedColumns > failed 3 out last 10 runs. > > [https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-mulitbranch/job/4.x/134/testReport/org.apache.phoenix.end2end/ConcurrentMutationsExtendedIT/MatrixBuild___Matrix___HBASE_PROFILE1_6BuildAndTest___testConcurrentUpsertsWithNoIndexedColumns/] > > https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-mulitbranch/job/4.x/137/testReport/org.apache.phoenix.end2end/ConcurrentMutationsExtendedIT/MatrixBuild___Matrix___HBASE_PROFILE1_3BuildAndTest___testConcurrentUpsertsWithNoIndexedColumns/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (PHOENIX-6251) Fix ConcurrentMutationsExtendedIT.testConcurrentUpsertsWithNoIndexedColumns timout issue
[ https://issues.apache.org/jira/browse/PHOENIX-6251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viraj Jasani reassigned PHOENIX-6251: - Assignee: Viraj Jasani > Fix ConcurrentMutationsExtendedIT.testConcurrentUpsertsWithNoIndexedColumns > timout issue > > > Key: PHOENIX-6251 > URL: https://issues.apache.org/jira/browse/PHOENIX-6251 > Project: Phoenix > Issue Type: Improvement >Reporter: Xinyi Yan >Assignee: Viraj Jasani >Priority: Major > Fix For: 4.16.0 > > > ConcurrentMutationsExtendedIT.testConcurrentUpsertsWithNoIndexedColumns > failed 3 out last 10 runs. > > [https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-mulitbranch/job/4.x/134/testReport/org.apache.phoenix.end2end/ConcurrentMutationsExtendedIT/MatrixBuild___Matrix___HBASE_PROFILE1_6BuildAndTest___testConcurrentUpsertsWithNoIndexedColumns/] > > https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-mulitbranch/job/4.x/137/testReport/org.apache.phoenix.end2end/ConcurrentMutationsExtendedIT/MatrixBuild___Matrix___HBASE_PROFILE1_3BuildAndTest___testConcurrentUpsertsWithNoIndexedColumns/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (PHOENIX-6260) Omid exclusions are incomplete
[ https://issues.apache.org/jira/browse/PHOENIX-6260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth resolved PHOENIX-6260. -- Fix Version/s: 5.1.0 Resolution: Fixed Committed to master. Does not apply to 4.x. Thanks for the review [~vjasani] > Omid exclusions are incomplete > -- > > Key: PHOENIX-6260 > URL: https://issues.apache.org/jira/browse/PHOENIX-6260 > Project: Phoenix > Issue Type: Bug > Components: core >Affects Versions: 5.1.0 >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > Fix For: 5.1.0 > > > Phoenix 5 pulls org.apache.omid:omid-hbase-common-hbase1.x > This seems to be caused by the incomplete Omid exclusion definitions. > This really should be fixed in Omid in the long term, so that the exclusions > are not needed, but short term we need to amend the exclusion list. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (PHOENIX-6249) Create shaded phoenix-spark connector jar
[ https://issues.apache.org/jira/browse/PHOENIX-6249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth resolved PHOENIX-6249. -- Fix Version/s: connectors-6.0.0 Resolution: Fixed Committed to master. Thanks for the review [~rajeshbabu] > Create shaded phoenix-spark connector jar > - > > Key: PHOENIX-6249 > URL: https://issues.apache.org/jira/browse/PHOENIX-6249 > Project: Phoenix > Issue Type: Task > Components: connectors, spark-connector >Affects Versions: connectors-6.0.0 >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > Fix For: connectors-6.0.0 > > > Since connectors have been split, we do not have the spark connector shaded > into phoenix-client. > Create shaded connector for spark that takes Hadoop from the spark classpath > (thus minimizing the chances of classpath conflicts) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[DISCUSS] Fixing non-standard maven module structure in core and connectors
Hi! When we added the compatibility modules to phoenix we broke that standard maven structure, as the compatibility modules are NOT the children of the main module, but standalone modules. Maven expects the whole project to be a single tree, not a forest. This results in maven throwing warnings at startup, and some maven functions, like version:set not working. (Which I had to hack around in the release scripts) Richard Antal has found a way to fix the maven structure, basically by adding another common ancestor module to the old main module, and the compatibility modules. The change itself is low risk, and no java code is touched, but as this would move around most files in the repo, I'd like to ask for more reviewers, especially from the SFDC side. The ticket is https://issues.apache.org/jira/browse/PHOENIX-6261 and the PR for is https://github.com/apache/phoenix-connectors/pull/44 The PR is for the phoenix-connectors repo, but the problem is the same in core, and the fix would directly apply there. regards Istvan
Re: IndexExtendedIT always failed on 4.x and master
Yes， when I revert the 4.x before PHOENIX-5140, the IndexExtendedIT and IndexScrutinyToolIT are sucess. but after applying PHOENIX-5140,both IndexExtendedIT and IndexScrutinyToolIT are always failed. At 2020-12-10 16:51:27, "Ankit Singhal" wrote: >Thanks Chenglei for bringing the failures to the notice. Have you confirmed >that reverting PHOENIX-5140 fixes the problem? if yes then I would suggest >reverting the fix and re-open the JIRA to be worked upon separately for the >new fix. > >On Wed, Dec 9, 2020 at 7:14 PM cheng...@apache.org >wrote: > >> I noticed IndexExtendedIT always failed on 4.x and master now, It may be >> caused by PHOENIX-5140 , for 4.x , the stack is : >> java.lang.AssertionError: expected:<0> but was:<-1> >> at org.junit.Assert.fail(Assert.java:89) >> at org.junit.Assert.failNotEquals(Assert.java:835) >> at org.junit.Assert.assertEquals(Assert.java:647) >> at org.junit.Assert.assertEquals(Assert.java:633) >> at >> org.apache.phoenix.end2end.IndexToolIT.runIndexTool(IndexToolIT.java:806) >> at >> org.apache.phoenix.end2end.IndexToolIT.runIndexTool(IndexToolIT.java:785) >> at >> org.apache.phoenix.end2end.IndexToolIT.runIndexTool(IndexToolIT.java:776) >> at >> org.apache.phoenix.end2end.IndexToolIT.runIndexTool(IndexToolIT.java:770) >> at >> org.apache.phoenix.end2end.IndexToolIT.runIndexTool(IndexToolIT.java:744) >> at >> org.apache.phoenix.end2end.IndexExtendedIT.testMutableIndexWithUpdates(IndexExtendedIT.java:166) >> >> >> and the similar stack is on master， I suggest we should rollback or stop >> commit to the repo until the problem is fixed.
Re: IndexExtendedIT always failed on 4.x and master
Yes， when I revert the 4.x before PHOENIX-5140, the IndexExtendedIT and IndexScrutinyToolIT are sucess. but after applying PHOENIX-5140,both IndexExtendedIT and IndexScrutinyToolIT are always failed. At 2020-12-10 16:51:27, "Ankit Singhal" wrote: >Thanks Chenglei for bringing the failures to the notice. Have you confirmed >that reverting PHOENIX-5140 fixes the problem? if yes then I would suggest >reverting the fix and re-open the JIRA to be worked upon separately for the >new fix. > >On Wed, Dec 9, 2020 at 7:14 PM cheng...@apache.org >wrote: > >> I noticed IndexExtendedIT always failed on 4.x and master now, It may be >> caused by PHOENIX-5140 , for 4.x , the stack is : >> java.lang.AssertionError: expected:<0> but was:<-1> >> at org.junit.Assert.fail(Assert.java:89) >> at org.junit.Assert.failNotEquals(Assert.java:835) >> at org.junit.Assert.assertEquals(Assert.java:647) >> at org.junit.Assert.assertEquals(Assert.java:633) >> at >> org.apache.phoenix.end2end.IndexToolIT.runIndexTool(IndexToolIT.java:806) >> at >> org.apache.phoenix.end2end.IndexToolIT.runIndexTool(IndexToolIT.java:785) >> at >> org.apache.phoenix.end2end.IndexToolIT.runIndexTool(IndexToolIT.java:776) >> at >> org.apache.phoenix.end2end.IndexToolIT.runIndexTool(IndexToolIT.java:770) >> at >> org.apache.phoenix.end2end.IndexToolIT.runIndexTool(IndexToolIT.java:744) >> at >> org.apache.phoenix.end2end.IndexExtendedIT.testMutableIndexWithUpdates(IndexExtendedIT.java:166) >> >> >> and the similar stack is on master， I suggest we should rollback or stop >> commit to the repo until the problem is fixed.
[jira] [Assigned] (PHOENIX-6261) Reorganise project structure to make mvn versions:set work
[ https://issues.apache.org/jira/browse/PHOENIX-6261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal reassigned PHOENIX-6261: -- Assignee: Richard Antal > Reorganise project structure to make mvn versions:set work > -- > > Key: PHOENIX-6261 > URL: https://issues.apache.org/jira/browse/PHOENIX-6261 > Project: Phoenix > Issue Type: Task > Components: connectors, core >Reporter: Richard Antal >Assignee: Richard Antal >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-6261) Reorganise project structure to make mvn versions:set work
Richard Antal created PHOENIX-6261: -- Summary: Reorganise project structure to make mvn versions:set work Key: PHOENIX-6261 URL: https://issues.apache.org/jira/browse/PHOENIX-6261 Project: Phoenix Issue Type: Task Components: connectors, core Reporter: Richard Antal -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: IndexExtendedIT always failed on 4.x and master
Thanks Chenglei for bringing the failures to the notice. Have you confirmed that reverting PHOENIX-5140 fixes the problem? if yes then I would suggest reverting the fix and re-open the JIRA to be worked upon separately for the new fix. On Wed, Dec 9, 2020 at 7:14 PM cheng...@apache.org wrote: > I noticed IndexExtendedIT always failed on 4.x and master now, It may be > caused by PHOENIX-5140 , for 4.x , the stack is : > java.lang.AssertionError: expected:<0> but was:<-1> > at org.junit.Assert.fail(Assert.java:89) > at org.junit.Assert.failNotEquals(Assert.java:835) > at org.junit.Assert.assertEquals(Assert.java:647) > at org.junit.Assert.assertEquals(Assert.java:633) > at > org.apache.phoenix.end2end.IndexToolIT.runIndexTool(IndexToolIT.java:806) > at > org.apache.phoenix.end2end.IndexToolIT.runIndexTool(IndexToolIT.java:785) > at > org.apache.phoenix.end2end.IndexToolIT.runIndexTool(IndexToolIT.java:776) > at > org.apache.phoenix.end2end.IndexToolIT.runIndexTool(IndexToolIT.java:770) > at > org.apache.phoenix.end2end.IndexToolIT.runIndexTool(IndexToolIT.java:744) > at > org.apache.phoenix.end2end.IndexExtendedIT.testMutableIndexWithUpdates(IndexExtendedIT.java:166) > > > and the similar stack is on master， I suggest we should rollback or stop > commit to the repo until the problem is fixed.
IndexExtendedIT and IndexScrutinyToolIT are always failed on 4.x and master
Beside IndexExtendedIT, IndexScrutinyToolIT also always failed on 4.x and master, both failed tests may be caused by PHOENIX-5140 在 2020-12-10 11:14:25，"cheng...@apache.org" 写道： I noticed IndexExtendedIT always failed on 4.x and master now, It may be caused by PHOENIX-5140 , for 4.x , the stack is : java.lang.AssertionError: expected:<0> but was:<-1> at org.junit.Assert.fail(Assert.java:89) at org.junit.Assert.failNotEquals(Assert.java:835) at org.junit.Assert.assertEquals(Assert.java:647) at org.junit.Assert.assertEquals(Assert.java:633) at org.apache.phoenix.end2end.IndexToolIT.runIndexTool(IndexToolIT.java:806) at org.apache.phoenix.end2end.IndexToolIT.runIndexTool(IndexToolIT.java:785) at org.apache.phoenix.end2end.IndexToolIT.runIndexTool(IndexToolIT.java:776) at org.apache.phoenix.end2end.IndexToolIT.runIndexTool(IndexToolIT.java:770) at org.apache.phoenix.end2end.IndexToolIT.runIndexTool(IndexToolIT.java:744) at org.apache.phoenix.end2end.IndexExtendedIT.testMutableIndexWithUpdates(IndexExtendedIT.java:166) and the similar stack is on master， I suggest we should rollback or stop commit to the repo until the problem is fixed.
[jira] [Created] (PHOENIX-6260) Omid exclusions are incomplete
Istvan Toth created PHOENIX-6260: Summary: Omid exclusions are incomplete Key: PHOENIX-6260 URL: https://issues.apache.org/jira/browse/PHOENIX-6260 Project: Phoenix Issue Type: Bug Components: core Affects Versions: 5.1.0 Reporter: Istvan Toth Assignee: Istvan Toth Phoenix 5 pulls org.apache.omid:omid-hbase-common-hbase1.x This seems to be caused by the incomplete Omid exclusion definitions. This really should be fixed in Omid in the long term, so that the exclusions are not needed, but short term we need to amend the exclusion list. -- This message was sent by Atlassian Jira (v8.3.4#803005)
