[jira] [Commented] (GEODE-8554) CI Failure: JMXMBeanReconnectDUnitTest.locatorMXBeansOnOtherLocatorAreRestoredAfterCrashedLocatorReturns
[
https://issues.apache.org/jira/browse/GEODE-8554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17512647#comment-17512647
]
Geode Integration commented on GEODE-8554:
--
Seen in [distributed-test-openjdk8
#245|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/distributed-test-openjdk8/builds/245]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1033/test-results/distributedTest/1648253717/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1033/test-artifacts/1648253717/distributedtestfiles-openjdk8-1.15.0-build.1033.tgz].
> CI Failure:
> JMXMBeanReconnectDUnitTest.locatorMXBeansOnOtherLocatorAreRestoredAfterCrashedLocatorReturns
>
>
> Key: GEODE-8554
> URL: https://issues.apache.org/jira/browse/GEODE-8554
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Jianxia Chen
>Assignee: Kirk Lund
>Priority: Major
>
> {noformat}
> org.apache.geode.management.JMXMBeanReconnectDUnitTest >
> locatorMXBeansOnOtherLocatorAreRestoredAfterCrashedLocatorReturns FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.management.JMXMBeanReconnectDUnitTest$$Lambda$355/858468979.call
> in VM -1 running on Host 7a5c340f5c23 with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:620)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:472)
> at
> org.apache.geode.management.JMXMBeanReconnectDUnitTest.setUp(JMXMBeanReconnectDUnitTest.java:191)
> Caused by:
> org.awaitility.core.ConditionTimeoutException: Assertion condition
> defined as a lambda expression in
> org.apache.geode.management.JMXMBeanReconnectDUnitTest [GemFire mbeans on
> locator2]
> Expecting HashSet:
> <[GemFire:type=Member,member=locator1,
>
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator2,
> GemFire:type=Member,member=server1,
> GemFire:service=Manager,type=Member,member=locator1,
> GemFire:service=Locator,type=Member,member=locator2,
> GemFire:type=Member,member=locator2,
> GemFire:service=Region,name=/region1,type=Member,member=server1,
> GemFire:service=FileUploader,type=Distributed,
>
> GemFire:service=DiskStore,name=cluster_config,type=Member,member=locator2,
> GemFire:service=Manager,type=Member,member=locator2,
> GemFire:service=Locator,type=Member,member=locator1,
> GemFire:service=System,type=Distributed,
> GemFire:service=AccessControl,type=Distributed,
>
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Distributed,
> GemFire:service=Region,name=/region1,type=Distributed]>
> to contain:
> <[GemFire:type=Member,member=locator1,
> GemFire:service=Locator,type=Member,member=locator1,
> GemFire:service=Manager,type=Member,member=locator1,
>
> GemFire:service=DiskStore,name=cluster_config,type=Member,member=locator1,
>
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator1]>
> but could not find the following element(s):
>
> <[GemFire:service=DiskStore,name=cluster_config,type=Member,member=locator1,
>
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator1]>
> within 5 minutes.
> at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
> at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:895)
> at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:679)
> at
> org.apache.geode.management.JMXMBeanReconnectDUnitTest.lambda$setUp$515fd116$3(JMXMBeanReconnectDUnitTest.java:192)
> 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.apache.geode.test.dunit.internal.MethodInvoker.executeObject(MethodInvoker.java:123)
> at
> org.apache.geode.test.dunit.internal.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:78)
>
[jira] [Commented] (GEODE-8554) CI Failure: JMXMBeanReconnectDUnitTest.locatorMXBeansOnOtherLocatorAreRestoredAfterCrashedLocatorReturns
[
https://issues.apache.org/jira/browse/GEODE-8554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17512646#comment-17512646
]
Jianxia Chen commented on GEODE-8554:
-
Failed again:
[https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/distributed-test-openjdk8/builds/245]
=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1033/test-results/distributedTest/1648253717/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Test report artifacts from this job are available at:
http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1033/test-artifacts/1648253717/distributedtestfiles-openjdk8-1.15.0-build.1033.tgz
> CI Failure:
> JMXMBeanReconnectDUnitTest.locatorMXBeansOnOtherLocatorAreRestoredAfterCrashedLocatorReturns
>
>
> Key: GEODE-8554
> URL: https://issues.apache.org/jira/browse/GEODE-8554
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Jianxia Chen
>Assignee: Kirk Lund
>Priority: Major
>
> {noformat}
> org.apache.geode.management.JMXMBeanReconnectDUnitTest >
> locatorMXBeansOnOtherLocatorAreRestoredAfterCrashedLocatorReturns FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.management.JMXMBeanReconnectDUnitTest$$Lambda$355/858468979.call
> in VM -1 running on Host 7a5c340f5c23 with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:620)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:472)
> at
> org.apache.geode.management.JMXMBeanReconnectDUnitTest.setUp(JMXMBeanReconnectDUnitTest.java:191)
> Caused by:
> org.awaitility.core.ConditionTimeoutException: Assertion condition
> defined as a lambda expression in
> org.apache.geode.management.JMXMBeanReconnectDUnitTest [GemFire mbeans on
> locator2]
> Expecting HashSet:
> <[GemFire:type=Member,member=locator1,
>
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator2,
> GemFire:type=Member,member=server1,
> GemFire:service=Manager,type=Member,member=locator1,
> GemFire:service=Locator,type=Member,member=locator2,
> GemFire:type=Member,member=locator2,
> GemFire:service=Region,name=/region1,type=Member,member=server1,
> GemFire:service=FileUploader,type=Distributed,
>
> GemFire:service=DiskStore,name=cluster_config,type=Member,member=locator2,
> GemFire:service=Manager,type=Member,member=locator2,
> GemFire:service=Locator,type=Member,member=locator1,
> GemFire:service=System,type=Distributed,
> GemFire:service=AccessControl,type=Distributed,
>
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Distributed,
> GemFire:service=Region,name=/region1,type=Distributed]>
> to contain:
> <[GemFire:type=Member,member=locator1,
> GemFire:service=Locator,type=Member,member=locator1,
> GemFire:service=Manager,type=Member,member=locator1,
>
> GemFire:service=DiskStore,name=cluster_config,type=Member,member=locator1,
>
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator1]>
> but could not find the following element(s):
>
> <[GemFire:service=DiskStore,name=cluster_config,type=Member,member=locator1,
>
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator1]>
> within 5 minutes.
> at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
> at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:895)
> at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:679)
> at
> org.apache.geode.management.JMXMBeanReconnectDUnitTest.lambda$setUp$515fd116$3(JMXMBeanReconnectDUnitTest.java:192)
> 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.apache.geode.test.dunit.internal.MethodInvoker.executeObject(MethodIn
[jira] [Commented] (GEODE-10178) CI Failure: PartitionedGetLongBenchmark > run()
[
https://issues.apache.org/jira/browse/GEODE-10178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17512638#comment-17512638
]
Jianxia Chen commented on GEODE-10178:
--
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/benchmark-base/builds/232
> CI Failure: PartitionedGetLongBenchmark > run()
> ---
>
> Key: GEODE-10178
> URL: https://issues.apache.org/jira/browse/GEODE-10178
> Project: Geode
> Issue Type: Bug
>Reporter: Jianxia Chen
>Priority: Major
> Labels: needsTriage
>
> {code:java}
> PartitionedGetLongBenchmark > run() FAILED
> 01:08:25net.schmizz.sshj.transport.TransportException: Connection reset
> 01:08:25at
> net.schmizz.sshj.transport.TransportImpl.init(TransportImpl.java:194)
> 01:08:25at net.schmizz.sshj.SSHClient.onConnect(SSHClient.java:793)
> 01:08:25at
> net.schmizz.sshj.SocketClient.connect(SocketClient.java:178)
> 01:08:25at
> org.apache.geode.perftest.infrastructure.ssh.SshInfrastructure.getSSHClient(SshInfrastructure.java:74)
> 01:08:25at
> org.apache.geode.perftest.infrastructure.ssh.SshInfrastructure.copyFromNode(SshInfrastructure.java:185)
> 01:08:25at
> org.apache.geode.perftest.jvms.RemoteJVMs.copyResults(RemoteJVMs.java:87)
> 01:08:25at
> org.apache.geode.perftest.runner.DefaultTestRunner.runTest(DefaultTestRunner.java:112)
> 01:08:25at
> org.apache.geode.perftest.runner.DefaultTestRunner.runTest(DefaultTestRunner.java:65)
> 01:08:25at
> org.apache.geode.benchmark.tests.PartitionedGetLongBenchmark.run(PartitionedGetLongBenchmark.java:45)
> 01:08:25
> 01:08:25Caused by:
> 01:08:25java.net.SocketException: Connection reset
> 01:08:25at
> java.net.SocketInputStream.read(SocketInputStream.java:210)
> 01:08:25at
> java.net.SocketInputStream.read(SocketInputStream.java:141)
> 01:08:25at
> java.net.SocketInputStream.read(SocketInputStream.java:224)
> 01:08:25at
> net.schmizz.sshj.transport.TransportImpl.receiveServerIdent(TransportImpl.java:211)
> 01:08:25at
> net.schmizz.sshj.transport.TransportImpl.init(TransportImpl.java:187)
> 01:08:25... 8 more {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-10178) CI Failure: PartitionedGetLongBenchmark > run()
[
https://issues.apache.org/jira/browse/GEODE-10178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17512639#comment-17512639
]
Geode Integration commented on GEODE-10178:
---
Seen in [benchmark-base
#232|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/benchmark-base/builds/232].
> CI Failure: PartitionedGetLongBenchmark > run()
> ---
>
> Key: GEODE-10178
> URL: https://issues.apache.org/jira/browse/GEODE-10178
> Project: Geode
> Issue Type: Bug
>Reporter: Jianxia Chen
>Priority: Major
> Labels: needsTriage
>
> {code:java}
> PartitionedGetLongBenchmark > run() FAILED
> 01:08:25net.schmizz.sshj.transport.TransportException: Connection reset
> 01:08:25at
> net.schmizz.sshj.transport.TransportImpl.init(TransportImpl.java:194)
> 01:08:25at net.schmizz.sshj.SSHClient.onConnect(SSHClient.java:793)
> 01:08:25at
> net.schmizz.sshj.SocketClient.connect(SocketClient.java:178)
> 01:08:25at
> org.apache.geode.perftest.infrastructure.ssh.SshInfrastructure.getSSHClient(SshInfrastructure.java:74)
> 01:08:25at
> org.apache.geode.perftest.infrastructure.ssh.SshInfrastructure.copyFromNode(SshInfrastructure.java:185)
> 01:08:25at
> org.apache.geode.perftest.jvms.RemoteJVMs.copyResults(RemoteJVMs.java:87)
> 01:08:25at
> org.apache.geode.perftest.runner.DefaultTestRunner.runTest(DefaultTestRunner.java:112)
> 01:08:25at
> org.apache.geode.perftest.runner.DefaultTestRunner.runTest(DefaultTestRunner.java:65)
> 01:08:25at
> org.apache.geode.benchmark.tests.PartitionedGetLongBenchmark.run(PartitionedGetLongBenchmark.java:45)
> 01:08:25
> 01:08:25Caused by:
> 01:08:25java.net.SocketException: Connection reset
> 01:08:25at
> java.net.SocketInputStream.read(SocketInputStream.java:210)
> 01:08:25at
> java.net.SocketInputStream.read(SocketInputStream.java:141)
> 01:08:25at
> java.net.SocketInputStream.read(SocketInputStream.java:224)
> 01:08:25at
> net.schmizz.sshj.transport.TransportImpl.receiveServerIdent(TransportImpl.java:211)
> 01:08:25at
> net.schmizz.sshj.transport.TransportImpl.init(TransportImpl.java:187)
> 01:08:25... 8 more {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-10178) CI Failure: PartitionedGetLongBenchmark > run()
[
https://issues.apache.org/jira/browse/GEODE-10178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Murmann updated GEODE-10178:
--
Labels: needsTriage (was: )
> CI Failure: PartitionedGetLongBenchmark > run()
> ---
>
> Key: GEODE-10178
> URL: https://issues.apache.org/jira/browse/GEODE-10178
> Project: Geode
> Issue Type: Bug
>Reporter: Jianxia Chen
>Priority: Major
> Labels: needsTriage
>
> {code:java}
> PartitionedGetLongBenchmark > run() FAILED
> 01:08:25net.schmizz.sshj.transport.TransportException: Connection reset
> 01:08:25at
> net.schmizz.sshj.transport.TransportImpl.init(TransportImpl.java:194)
> 01:08:25at net.schmizz.sshj.SSHClient.onConnect(SSHClient.java:793)
> 01:08:25at
> net.schmizz.sshj.SocketClient.connect(SocketClient.java:178)
> 01:08:25at
> org.apache.geode.perftest.infrastructure.ssh.SshInfrastructure.getSSHClient(SshInfrastructure.java:74)
> 01:08:25at
> org.apache.geode.perftest.infrastructure.ssh.SshInfrastructure.copyFromNode(SshInfrastructure.java:185)
> 01:08:25at
> org.apache.geode.perftest.jvms.RemoteJVMs.copyResults(RemoteJVMs.java:87)
> 01:08:25at
> org.apache.geode.perftest.runner.DefaultTestRunner.runTest(DefaultTestRunner.java:112)
> 01:08:25at
> org.apache.geode.perftest.runner.DefaultTestRunner.runTest(DefaultTestRunner.java:65)
> 01:08:25at
> org.apache.geode.benchmark.tests.PartitionedGetLongBenchmark.run(PartitionedGetLongBenchmark.java:45)
> 01:08:25
> 01:08:25Caused by:
> 01:08:25java.net.SocketException: Connection reset
> 01:08:25at
> java.net.SocketInputStream.read(SocketInputStream.java:210)
> 01:08:25at
> java.net.SocketInputStream.read(SocketInputStream.java:141)
> 01:08:25at
> java.net.SocketInputStream.read(SocketInputStream.java:224)
> 01:08:25at
> net.schmizz.sshj.transport.TransportImpl.receiveServerIdent(TransportImpl.java:211)
> 01:08:25at
> net.schmizz.sshj.transport.TransportImpl.init(TransportImpl.java:187)
> 01:08:25... 8 more {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (GEODE-10178) CI Failure: PartitionedGetLongBenchmark > run()
Jianxia Chen created GEODE-10178:
Summary: CI Failure: PartitionedGetLongBenchmark > run()
Key: GEODE-10178
URL: https://issues.apache.org/jira/browse/GEODE-10178
Project: Geode
Issue Type: Bug
Reporter: Jianxia Chen
{code:java}
PartitionedGetLongBenchmark > run() FAILED
01:08:25net.schmizz.sshj.transport.TransportException: Connection reset
01:08:25at
net.schmizz.sshj.transport.TransportImpl.init(TransportImpl.java:194)
01:08:25at net.schmizz.sshj.SSHClient.onConnect(SSHClient.java:793)
01:08:25at net.schmizz.sshj.SocketClient.connect(SocketClient.java:178)
01:08:25at
org.apache.geode.perftest.infrastructure.ssh.SshInfrastructure.getSSHClient(SshInfrastructure.java:74)
01:08:25at
org.apache.geode.perftest.infrastructure.ssh.SshInfrastructure.copyFromNode(SshInfrastructure.java:185)
01:08:25at
org.apache.geode.perftest.jvms.RemoteJVMs.copyResults(RemoteJVMs.java:87)
01:08:25at
org.apache.geode.perftest.runner.DefaultTestRunner.runTest(DefaultTestRunner.java:112)
01:08:25at
org.apache.geode.perftest.runner.DefaultTestRunner.runTest(DefaultTestRunner.java:65)
01:08:25at
org.apache.geode.benchmark.tests.PartitionedGetLongBenchmark.run(PartitionedGetLongBenchmark.java:45)
01:08:25
01:08:25Caused by:
01:08:25java.net.SocketException: Connection reset
01:08:25at
java.net.SocketInputStream.read(SocketInputStream.java:210)
01:08:25at
java.net.SocketInputStream.read(SocketInputStream.java:141)
01:08:25at
java.net.SocketInputStream.read(SocketInputStream.java:224)
01:08:25at
net.schmizz.sshj.transport.TransportImpl.receiveServerIdent(TransportImpl.java:211)
01:08:25at
net.schmizz.sshj.transport.TransportImpl.init(TransportImpl.java:187)
01:08:25... 8 more {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-10177) CI Failure: PubSubDUnitTest > shouldContinueToFunction_whenOneServerShutsDownGracefully_givenTwoSubscribersTwoPublishers
[
https://issues.apache.org/jira/browse/GEODE-10177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17512634#comment-17512634
]
Jianxia Chen commented on GEODE-10177:
--
Might be due to GEODE-10174. Maybe one test failed and the subsequent tests in
the same file failed as well.
> CI Failure: PubSubDUnitTest >
> shouldContinueToFunction_whenOneServerShutsDownGracefully_givenTwoSubscribersTwoPublishers
>
>
> Key: GEODE-10177
> URL: https://issues.apache.org/jira/browse/GEODE-10177
> Project: Geode
> Issue Type: Bug
>Reporter: Jianxia Chen
>Priority: Major
> Labels: needsTriage
>
>
> {code:java}
> org.apache.geode.redis.internal.executor.pubsub.PubSubDUnitTest >
> shouldContinueToFunction_whenOneServerShutsDownGracefully_givenTwoSubscribersTwoPublishers
> FAILED
> 15:35:00org.awaitility.core.ConditionTimeoutException: Assertion
> condition defined as a lambda expression in
> org.apache.geode.redis.internal.executor.pubsub.PubSubDUnitTest that uses
> java.util.concurrent.Future null within 5 minutes.
> 15:35:00at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165)
> 15:35:00at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
> 15:35:00at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
> 15:35:00at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:895)
> 15:35:00at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:679)
> 15:35:00at
> org.apache.geode.redis.internal.executor.pubsub.PubSubDUnitTest.shouldContinueToFunction_whenOneServerShutsDownGracefully_givenTwoSubscribersTwoPublishers(PubSubDUnitTest.java:319)
> 15:35:00
> 15:35:00Caused by:
> 15:35:00java.util.concurrent.TimeoutException
> 15:35:00at
> java.util.concurrent.FutureTask.get(FutureTask.java:205)
> 15:35:00at
> org.awaitility.core.Uninterruptibles.getUninterruptibly(Uninterruptibles.java:101)
> 15:35:00at
> org.awaitility.core.Uninterruptibles.getUninterruptibly(Uninterruptibles.java:81)
> 15:35:00at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:101)
> 15:35:00... 5 more {code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-10177) CI Failure: PubSubDUnitTest > shouldContinueToFunction_whenOneServerShutsDownGracefully_givenTwoSubscribersTwoPublishers
[
https://issues.apache.org/jira/browse/GEODE-10177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17512632#comment-17512632
]
Jianxia Chen commented on GEODE-10177:
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.5-build.0938/test-results/distributedTest/1648080229/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Test report artifacts from this job are available at:
http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.5-build.0938/test-artifacts/1648080229/distributedtestfiles-openjdk8-1.14.5-build.0938.tgz
> CI Failure: PubSubDUnitTest >
> shouldContinueToFunction_whenOneServerShutsDownGracefully_givenTwoSubscribersTwoPublishers
>
>
> Key: GEODE-10177
> URL: https://issues.apache.org/jira/browse/GEODE-10177
> Project: Geode
> Issue Type: Bug
>Reporter: Jianxia Chen
>Priority: Major
> Labels: needsTriage
>
>
> {code:java}
> org.apache.geode.redis.internal.executor.pubsub.PubSubDUnitTest >
> shouldContinueToFunction_whenOneServerShutsDownGracefully_givenTwoSubscribersTwoPublishers
> FAILED
> 15:35:00org.awaitility.core.ConditionTimeoutException: Assertion
> condition defined as a lambda expression in
> org.apache.geode.redis.internal.executor.pubsub.PubSubDUnitTest that uses
> java.util.concurrent.Future null within 5 minutes.
> 15:35:00at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165)
> 15:35:00at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
> 15:35:00at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
> 15:35:00at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:895)
> 15:35:00at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:679)
> 15:35:00at
> org.apache.geode.redis.internal.executor.pubsub.PubSubDUnitTest.shouldContinueToFunction_whenOneServerShutsDownGracefully_givenTwoSubscribersTwoPublishers(PubSubDUnitTest.java:319)
> 15:35:00
> 15:35:00Caused by:
> 15:35:00java.util.concurrent.TimeoutException
> 15:35:00at
> java.util.concurrent.FutureTask.get(FutureTask.java:205)
> 15:35:00at
> org.awaitility.core.Uninterruptibles.getUninterruptibly(Uninterruptibles.java:101)
> 15:35:00at
> org.awaitility.core.Uninterruptibles.getUninterruptibly(Uninterruptibles.java:81)
> 15:35:00at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:101)
> 15:35:00... 5 more {code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (GEODE-10177) CI Failure: PubSubDUnitTest > shouldContinueToFunction_whenOneServerShutsDownGracefully_givenTwoSubscribersTwoPublishers
Jianxia Chen created GEODE-10177:
Summary: CI Failure: PubSubDUnitTest >
shouldContinueToFunction_whenOneServerShutsDownGracefully_givenTwoSubscribersTwoPublishers
Key: GEODE-10177
URL: https://issues.apache.org/jira/browse/GEODE-10177
Project: Geode
Issue Type: Bug
Reporter: Jianxia Chen
{code:java}
org.apache.geode.redis.internal.executor.pubsub.PubSubDUnitTest >
shouldContinueToFunction_whenOneServerShutsDownGracefully_givenTwoSubscribersTwoPublishers
FAILED
15:35:00org.awaitility.core.ConditionTimeoutException: Assertion condition
defined as a lambda expression in
org.apache.geode.redis.internal.executor.pubsub.PubSubDUnitTest that uses
java.util.concurrent.Future null within 5 minutes.
15:35:00at
org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165)
15:35:00at
org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
15:35:00at
org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
15:35:00at
org.awaitility.core.ConditionFactory.until(ConditionFactory.java:895)
15:35:00at
org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:679)
15:35:00at
org.apache.geode.redis.internal.executor.pubsub.PubSubDUnitTest.shouldContinueToFunction_whenOneServerShutsDownGracefully_givenTwoSubscribersTwoPublishers(PubSubDUnitTest.java:319)
15:35:00
15:35:00Caused by:
15:35:00java.util.concurrent.TimeoutException
15:35:00at java.util.concurrent.FutureTask.get(FutureTask.java:205)
15:35:00at
org.awaitility.core.Uninterruptibles.getUninterruptibly(Uninterruptibles.java:101)
15:35:00at
org.awaitility.core.Uninterruptibles.getUninterruptibly(Uninterruptibles.java:81)
15:35:00at
org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:101)
15:35:00... 5 more {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-10177) CI Failure: PubSubDUnitTest > shouldContinueToFunction_whenOneServerShutsDownGracefully_givenTwoSubscribersTwoPublishers
[
https://issues.apache.org/jira/browse/GEODE-10177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Murmann updated GEODE-10177:
--
Labels: needsTriage (was: )
> CI Failure: PubSubDUnitTest >
> shouldContinueToFunction_whenOneServerShutsDownGracefully_givenTwoSubscribersTwoPublishers
>
>
> Key: GEODE-10177
> URL: https://issues.apache.org/jira/browse/GEODE-10177
> Project: Geode
> Issue Type: Bug
>Reporter: Jianxia Chen
>Priority: Major
> Labels: needsTriage
>
>
> {code:java}
> org.apache.geode.redis.internal.executor.pubsub.PubSubDUnitTest >
> shouldContinueToFunction_whenOneServerShutsDownGracefully_givenTwoSubscribersTwoPublishers
> FAILED
> 15:35:00org.awaitility.core.ConditionTimeoutException: Assertion
> condition defined as a lambda expression in
> org.apache.geode.redis.internal.executor.pubsub.PubSubDUnitTest that uses
> java.util.concurrent.Future null within 5 minutes.
> 15:35:00at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165)
> 15:35:00at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
> 15:35:00at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
> 15:35:00at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:895)
> 15:35:00at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:679)
> 15:35:00at
> org.apache.geode.redis.internal.executor.pubsub.PubSubDUnitTest.shouldContinueToFunction_whenOneServerShutsDownGracefully_givenTwoSubscribersTwoPublishers(PubSubDUnitTest.java:319)
> 15:35:00
> 15:35:00Caused by:
> 15:35:00java.util.concurrent.TimeoutException
> 15:35:00at
> java.util.concurrent.FutureTask.get(FutureTask.java:205)
> 15:35:00at
> org.awaitility.core.Uninterruptibles.getUninterruptibly(Uninterruptibles.java:101)
> 15:35:00at
> org.awaitility.core.Uninterruptibles.getUninterruptibly(Uninterruptibles.java:81)
> 15:35:00at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:101)
> 15:35:00... 5 more {code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-10175) CI Failure: PubSubDUnitTest > shouldContinueToFunction_whenOneServerShutsDownAbruptly_givenTwoSubscribersOnePublisher
[
https://issues.apache.org/jira/browse/GEODE-10175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jianxia Chen updated GEODE-10175:
-
Description:
{code:java}
org.apache.geode.redis.internal.executor.pubsub.PubSubDUnitTest >
shouldContinueToFunction_whenOneServerShutsDownAbruptly_givenTwoSubscribersOnePublisher
FAILED
15:29:24org.junit.ComparisonFailure: [channel subscription was not
received]
15:29:24Expecting value to be true but was false expected:<[tru]e> but
was:<[fals]e>
15:29:24at
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
15:29:24at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
15:29:24at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
15:29:24at
org.apache.geode.redis.internal.executor.pubsub.PubSubDUnitTest.shouldContinueToFunction_whenOneServerShutsDownAbruptly_givenTwoSubscribersOnePublisher(PubSubDUnitTest.java:255)
{code}
=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.5-build.0938/test-results/distributedTest/1648080229/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Test report artifacts from this job are available at:
http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.5-build.0938/test-artifacts/1648080229/distributedtestfiles-openjdk8-1.14.5-build.0938.tgz
was:
{code:java}
org.apache.geode.redis.internal.executor.pubsub.PubSubDUnitTest >
shouldContinueToFunction_whenOneServerShutsDownAbruptly_givenTwoSubscribersOnePublisher
FAILED
15:29:24org.junit.ComparisonFailure: [channel subscription was not
received]
15:29:24Expecting value to be true but was false expected:<[tru]e> but
was:<[fals]e>
15:29:24at
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
15:29:24at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
15:29:24at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
15:29:24at
org.apache.geode.redis.internal.executor.pubsub.PubSubDUnitTest.shouldContinueToFunction_whenOneServerShutsDownAbruptly_givenTwoSubscribersOnePublisher(PubSubDUnitTest.java:255)
{code}
=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.5-build.0938/test-results/distributedTest/1648080229/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=Test
report artifacts from this job are available
at:http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.5-build.0938/test-artifacts/1648080229/distributedtestfiles-openjdk8-1.14.5-build.0938.tgz
> CI Failure: PubSubDUnitTest >
> shouldContinueToFunction_whenOneServerShutsDownAbruptly_givenTwoSubscribersOnePublisher
> -
>
> Key: GEODE-10175
> URL: https://issues.apache.org/jira/browse/GEODE-10175
> Project: Geode
> Issue Type: Bug
>Reporter: Jianxia Chen
>Priority: Major
> Labels: needsTriage
>
> {code:java}
> org.apache.geode.redis.internal.executor.pubsub.PubSubDUnitTest >
> shouldContinueToFunction_whenOneServerShutsDownAbruptly_givenTwoSubscribersOnePublisher
> FAILED
> 15:29:24org.junit.ComparisonFailure: [channel subscription was not
> received]
> 15:29:24Expecting value to be true but was false expected:<[tru]e> but
> was:<[fals]e>
> 15:29:24at
> sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> 15:29:24at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> 15:29:24at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> 15:29:24at
> org.apache.geode.redis.internal.executor.pubsub.PubSubDUnitTest.shouldContinueToFunction_whenOneServerShutsDownAbruptly_givenTwoSubscribersOnePublisher(PubSubDUnitTest.java:255)
> {code}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.5-build.0938/test-results/distributedTest/1648080229/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.5-build.0938/test-artifacts/1648080229/distributedtestfiles-openjdk8-1.14.5-build.0938.tgz
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-10176) CI Failure: PubSubDUnitTest > shouldContinueToFunction_whenOneServerShutsDownGracefully_givenTwoSubscribersOnePublisher
[
https://issues.apache.org/jira/browse/GEODE-10176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jianxia Chen updated GEODE-10176:
-
Description:
{code:java}
org.apache.geode.redis.internal.executor.pubsub.PubSubDUnitTest >
shouldContinueToFunction_whenOneServerShutsDownGracefully_givenTwoSubscribersOnePublisher
FAILED
15:29:54org.junit.ComparisonFailure: [channel subscription was not
received]
15:29:54Expecting value to be true but was false expected:<[tru]e> but
was:<[fals]e>
15:29:54at
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
15:29:54at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
15:29:54at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
15:29:54at
org.apache.geode.redis.internal.executor.pubsub.PubSubDUnitTest.shouldContinueToFunction_whenOneServerShutsDownGracefully_givenTwoSubscribersOnePublisher(PubSubDUnitTest.java:225)
{code}
=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.5-build.0938/test-results/distributedTest/1648080229/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Test report artifacts from this job are available at:
http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.5-build.0938/test-artifacts/1648080229/distributedtestfiles-openjdk8-1.14.5-build.0938.tgz
was:
{code:java}
org.apache.geode.redis.internal.executor.pubsub.PubSubDUnitTest >
shouldContinueToFunction_whenOneServerShutsDownGracefully_givenTwoSubscribersOnePublisher
FAILED
15:29:54org.junit.ComparisonFailure: [channel subscription was not
received]
15:29:54Expecting value to be true but was false expected:<[tru]e> but
was:<[fals]e>
15:29:54at
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
15:29:54at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
15:29:54at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
15:29:54at
org.apache.geode.redis.internal.executor.pubsub.PubSubDUnitTest.shouldContinueToFunction_whenOneServerShutsDownGracefully_givenTwoSubscribersOnePublisher(PubSubDUnitTest.java:225)
{code}
=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.5-build.0938/test-results/distributedTest/1648080229/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=Test
report artifacts from this job are available
at:http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.5-build.0938/test-artifacts/1648080229/distributedtestfiles-openjdk8-1.14.5-build.0938.tgz
> CI Failure: PubSubDUnitTest >
> shouldContinueToFunction_whenOneServerShutsDownGracefully_givenTwoSubscribersOnePublisher
> ---
>
> Key: GEODE-10176
> URL: https://issues.apache.org/jira/browse/GEODE-10176
> Project: Geode
> Issue Type: Bug
>Reporter: Jianxia Chen
>Priority: Major
> Labels: needsTriage
>
> {code:java}
> org.apache.geode.redis.internal.executor.pubsub.PubSubDUnitTest >
> shouldContinueToFunction_whenOneServerShutsDownGracefully_givenTwoSubscribersOnePublisher
> FAILED
> 15:29:54org.junit.ComparisonFailure: [channel subscription was not
> received]
> 15:29:54Expecting value to be true but was false expected:<[tru]e> but
> was:<[fals]e>
> 15:29:54at
> sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> 15:29:54at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> 15:29:54at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> 15:29:54at
> org.apache.geode.redis.internal.executor.pubsub.PubSubDUnitTest.shouldContinueToFunction_whenOneServerShutsDownGracefully_givenTwoSubscribersOnePublisher(PubSubDUnitTest.java:225)
> {code}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.5-build.0938/test-results/distributedTest/1648080229/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.5-build.0938/test-artifacts/1648080229/distributedtestfiles-openjdk8-1.14.5-build.0938.tgz
--
This message was sent by Atlassian Jira
(v8
[jira] [Commented] (GEODE-10176) CI Failure: PubSubDUnitTest > shouldContinueToFunction_whenOneServerShutsDownGracefully_givenTwoSubscribersOnePublisher
[
https://issues.apache.org/jira/browse/GEODE-10176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17512630#comment-17512630
]
Jianxia Chen commented on GEODE-10176:
--
Might be due to GEODE-10174. Maybe one test failed and the subsequent tests in
the same file failed as well.
> CI Failure: PubSubDUnitTest >
> shouldContinueToFunction_whenOneServerShutsDownGracefully_givenTwoSubscribersOnePublisher
> ---
>
> Key: GEODE-10176
> URL: https://issues.apache.org/jira/browse/GEODE-10176
> Project: Geode
> Issue Type: Bug
>Reporter: Jianxia Chen
>Priority: Major
> Labels: needsTriage
>
> {code:java}
> org.apache.geode.redis.internal.executor.pubsub.PubSubDUnitTest >
> shouldContinueToFunction_whenOneServerShutsDownGracefully_givenTwoSubscribersOnePublisher
> FAILED
> 15:29:54org.junit.ComparisonFailure: [channel subscription was not
> received]
> 15:29:54Expecting value to be true but was false expected:<[tru]e> but
> was:<[fals]e>
> 15:29:54at
> sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> 15:29:54at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> 15:29:54at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> 15:29:54at
> org.apache.geode.redis.internal.executor.pubsub.PubSubDUnitTest.shouldContinueToFunction_whenOneServerShutsDownGracefully_givenTwoSubscribersOnePublisher(PubSubDUnitTest.java:225)
> {code}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.5-build.0938/test-results/distributedTest/1648080229/
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=Test
> report artifacts from this job are available
> at:http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.5-build.0938/test-artifacts/1648080229/distributedtestfiles-openjdk8-1.14.5-build.0938.tgz
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-10176) CI Failure: PubSubDUnitTest > shouldContinueToFunction_whenOneServerShutsDownGracefully_givenTwoSubscribersOnePublisher
[
https://issues.apache.org/jira/browse/GEODE-10176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Murmann updated GEODE-10176:
--
Labels: needsTriage (was: )
> CI Failure: PubSubDUnitTest >
> shouldContinueToFunction_whenOneServerShutsDownGracefully_givenTwoSubscribersOnePublisher
> ---
>
> Key: GEODE-10176
> URL: https://issues.apache.org/jira/browse/GEODE-10176
> Project: Geode
> Issue Type: Bug
>Reporter: Jianxia Chen
>Priority: Major
> Labels: needsTriage
>
> {code:java}
> org.apache.geode.redis.internal.executor.pubsub.PubSubDUnitTest >
> shouldContinueToFunction_whenOneServerShutsDownGracefully_givenTwoSubscribersOnePublisher
> FAILED
> 15:29:54org.junit.ComparisonFailure: [channel subscription was not
> received]
> 15:29:54Expecting value to be true but was false expected:<[tru]e> but
> was:<[fals]e>
> 15:29:54at
> sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> 15:29:54at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> 15:29:54at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> 15:29:54at
> org.apache.geode.redis.internal.executor.pubsub.PubSubDUnitTest.shouldContinueToFunction_whenOneServerShutsDownGracefully_givenTwoSubscribersOnePublisher(PubSubDUnitTest.java:225)
> {code}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.5-build.0938/test-results/distributedTest/1648080229/
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=Test
> report artifacts from this job are available
> at:http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.5-build.0938/test-artifacts/1648080229/distributedtestfiles-openjdk8-1.14.5-build.0938.tgz
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (GEODE-10176) CI Failure: PubSubDUnitTest > shouldContinueToFunction_whenOneServerShutsDownGracefully_givenTwoSubscribersOnePublisher
Jianxia Chen created GEODE-10176:
Summary: CI Failure: PubSubDUnitTest >
shouldContinueToFunction_whenOneServerShutsDownGracefully_givenTwoSubscribersOnePublisher
Key: GEODE-10176
URL: https://issues.apache.org/jira/browse/GEODE-10176
Project: Geode
Issue Type: Bug
Reporter: Jianxia Chen
{code:java}
org.apache.geode.redis.internal.executor.pubsub.PubSubDUnitTest >
shouldContinueToFunction_whenOneServerShutsDownGracefully_givenTwoSubscribersOnePublisher
FAILED
15:29:54org.junit.ComparisonFailure: [channel subscription was not
received]
15:29:54Expecting value to be true but was false expected:<[tru]e> but
was:<[fals]e>
15:29:54at
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
15:29:54at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
15:29:54at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
15:29:54at
org.apache.geode.redis.internal.executor.pubsub.PubSubDUnitTest.shouldContinueToFunction_whenOneServerShutsDownGracefully_givenTwoSubscribersOnePublisher(PubSubDUnitTest.java:225)
{code}
=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.5-build.0938/test-results/distributedTest/1648080229/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=Test
report artifacts from this job are available
at:http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.5-build.0938/test-artifacts/1648080229/distributedtestfiles-openjdk8-1.14.5-build.0938.tgz
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-10175) CI Failure: PubSubDUnitTest > shouldContinueToFunction_whenOneServerShutsDownAbruptly_givenTwoSubscribersOnePublisher
[
https://issues.apache.org/jira/browse/GEODE-10175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17512629#comment-17512629
]
Jianxia Chen commented on GEODE-10175:
--
Might be due to GEODE-10174. Maybe one test failed and the subsequent tests in
the same file failed as well.
> CI Failure: PubSubDUnitTest >
> shouldContinueToFunction_whenOneServerShutsDownAbruptly_givenTwoSubscribersOnePublisher
> -
>
> Key: GEODE-10175
> URL: https://issues.apache.org/jira/browse/GEODE-10175
> Project: Geode
> Issue Type: Bug
>Reporter: Jianxia Chen
>Priority: Major
> Labels: needsTriage
>
> {code:java}
> org.apache.geode.redis.internal.executor.pubsub.PubSubDUnitTest >
> shouldContinueToFunction_whenOneServerShutsDownAbruptly_givenTwoSubscribersOnePublisher
> FAILED
> 15:29:24org.junit.ComparisonFailure: [channel subscription was not
> received]
> 15:29:24Expecting value to be true but was false expected:<[tru]e> but
> was:<[fals]e>
> 15:29:24at
> sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> 15:29:24at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> 15:29:24at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> 15:29:24at
> org.apache.geode.redis.internal.executor.pubsub.PubSubDUnitTest.shouldContinueToFunction_whenOneServerShutsDownAbruptly_givenTwoSubscribersOnePublisher(PubSubDUnitTest.java:255)
> {code}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.5-build.0938/test-results/distributedTest/1648080229/
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=Test
> report artifacts from this job are available
> at:http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.5-build.0938/test-artifacts/1648080229/distributedtestfiles-openjdk8-1.14.5-build.0938.tgz
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-10175) CI Failure: PubSubDUnitTest > shouldContinueToFunction_whenOneServerShutsDownAbruptly_givenTwoSubscribersOnePublisher
[
https://issues.apache.org/jira/browse/GEODE-10175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Murmann updated GEODE-10175:
--
Labels: needsTriage (was: )
> CI Failure: PubSubDUnitTest >
> shouldContinueToFunction_whenOneServerShutsDownAbruptly_givenTwoSubscribersOnePublisher
> -
>
> Key: GEODE-10175
> URL: https://issues.apache.org/jira/browse/GEODE-10175
> Project: Geode
> Issue Type: Bug
>Reporter: Jianxia Chen
>Priority: Major
> Labels: needsTriage
>
> {code:java}
> org.apache.geode.redis.internal.executor.pubsub.PubSubDUnitTest >
> shouldContinueToFunction_whenOneServerShutsDownAbruptly_givenTwoSubscribersOnePublisher
> FAILED
> 15:29:24org.junit.ComparisonFailure: [channel subscription was not
> received]
> 15:29:24Expecting value to be true but was false expected:<[tru]e> but
> was:<[fals]e>
> 15:29:24at
> sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> 15:29:24at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> 15:29:24at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> 15:29:24at
> org.apache.geode.redis.internal.executor.pubsub.PubSubDUnitTest.shouldContinueToFunction_whenOneServerShutsDownAbruptly_givenTwoSubscribersOnePublisher(PubSubDUnitTest.java:255)
> {code}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.5-build.0938/test-results/distributedTest/1648080229/
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=Test
> report artifacts from this job are available
> at:http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.5-build.0938/test-artifacts/1648080229/distributedtestfiles-openjdk8-1.14.5-build.0938.tgz
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (GEODE-10175) CI Failure: PubSubDUnitTest > shouldContinueToFunction_whenOneServerShutsDownAbruptly_givenTwoSubscribersOnePublisher
Jianxia Chen created GEODE-10175:
Summary: CI Failure: PubSubDUnitTest >
shouldContinueToFunction_whenOneServerShutsDownAbruptly_givenTwoSubscribersOnePublisher
Key: GEODE-10175
URL: https://issues.apache.org/jira/browse/GEODE-10175
Project: Geode
Issue Type: Bug
Reporter: Jianxia Chen
{code:java}
org.apache.geode.redis.internal.executor.pubsub.PubSubDUnitTest >
shouldContinueToFunction_whenOneServerShutsDownAbruptly_givenTwoSubscribersOnePublisher
FAILED
15:29:24org.junit.ComparisonFailure: [channel subscription was not
received]
15:29:24Expecting value to be true but was false expected:<[tru]e> but
was:<[fals]e>
15:29:24at
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
15:29:24at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
15:29:24at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
15:29:24at
org.apache.geode.redis.internal.executor.pubsub.PubSubDUnitTest.shouldContinueToFunction_whenOneServerShutsDownAbruptly_givenTwoSubscribersOnePublisher(PubSubDUnitTest.java:255)
{code}
=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.5-build.0938/test-results/distributedTest/1648080229/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=Test
report artifacts from this job are available
at:http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.5-build.0938/test-artifacts/1648080229/distributedtestfiles-openjdk8-1.14.5-build.0938.tgz
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-9704) When durable clients recovers, it sends "ready for event" signal before register for interest, this might cause problem for caching_proxy regions
[ https://issues.apache.org/jira/browse/GEODE-9704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17512627#comment-17512627 ] Mark Hanson commented on GEODE-9704: PR 7442 is available. I have made changes to fix the behavior that was causing the problems. The core of the problem was that registerinterst should be called before readyforevents. It was reversed effectively, so that has been corrected. LocalRegionUpdateTest.java was created to house two unit tests for the new code. AuthExpirationDUnitTest has a test by Jinmei that has been uncommented that would typically be flaky, but with this fix, no longer fails. I believe this bug is done with the exception of the review phase of the PR and associated changes. > When durable clients recovers, it sends "ready for event" signal before > register for interest, this might cause problem for caching_proxy regions > - > > Key: GEODE-9704 > URL: https://issues.apache.org/jira/browse/GEODE-9704 > Project: Geode > Issue Type: Bug > Components: regions >Affects Versions: 1.15.0 >Reporter: Jinmei Liao >Assignee: Mark Hanson >Priority: Major > Labels: GeodeOperationAPI, blocks-1.15.1, pull-request-available > > This is the old Geode behavior, but may or may not be the correct behavior. > When durable clients recovers, there is a queueTimer thread that runs > `QueueManagerImp.recoverPrimary` method, it > * makes new connection to server > - sends readyForEvents (which will cause the server to start sending the > queued events) > - recovers interest > - clears the region of keys of interest > - re-registers interest > It sends readyForEvents before it clears region of keys of interest, if > server sends some events of those keys in between, it will clear them, thus > it seems to the user that the client region doesn't have those keys. > > Run geode-core distributedTest > AuthExpirationDUnitTest.registeredInterest_slowReAuth_policyKeys_durableClient(), > change the InterestResultPolicy to NONE, you would see the test would fail > occasionally, Adding sleep code in QueueManagerImp.recoverPrimary between > `createNewPrimary` and `recoverInterest` would make the test fail more > consistently. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10174) CI Failure: PubSubDUnitTest > testConcurrentPubSub
[
https://issues.apache.org/jira/browse/GEODE-10174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17512626#comment-17512626
]
Geode Integration commented on GEODE-10174:
---
Seen on support/1.14 in [distributed-test-openjdk8
#38|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-14-main/jobs/distributed-test-openjdk8/builds/38]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.5-build.0938/test-results/distributedTest/1648080229/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.5-build.0938/test-artifacts/1648080229/distributedtestfiles-openjdk8-1.14.5-build.0938.tgz].
> CI Failure: PubSubDUnitTest > testConcurrentPubSub
> --
>
> Key: GEODE-10174
> URL: https://issues.apache.org/jira/browse/GEODE-10174
> Project: Geode
> Issue Type: Bug
>Reporter: Jianxia Chen
>Priority: Major
> Labels: needsTriage
>
> {code:java}
> org.apache.geode.redis.internal.executor.pubsub.PubSubDUnitTest >
> testConcurrentPubSub FAILED
> 15:28:39java.util.concurrent.ExecutionException:
> redis.clients.jedis.exceptions.JedisConnectionException:
> java.net.SocketTimeoutException: Read timed out
> 15:28:39
> 15:28:39Caused by:
> 15:28:39redis.clients.jedis.exceptions.JedisConnectionException:
> java.net.SocketTimeoutException: Read timed out
> 15:28:39at
> redis.clients.jedis.util.RedisInputStream.ensureFill(RedisInputStream.java:205)
> 15:28:39at
> redis.clients.jedis.util.RedisInputStream.readByte(RedisInputStream.java:43)
> 15:28:39at redis.clients.jedis.Protocol.process(Protocol.java:155)
> 15:28:39at redis.clients.jedis.Protocol.read(Protocol.java:220)
> 15:28:39at
> redis.clients.jedis.Connection.readProtocolWithCheckingBroken(Connection.java:283)
> 15:28:39at
> redis.clients.jedis.Connection.getIntegerReply(Connection.java:225)
> 15:28:39at redis.clients.jedis.Jedis.publish(Jedis.java:2908)
> 15:28:39at
> org.apache.geode.redis.internal.executor.pubsub.PubSubDUnitTest.lambda$testConcurrentPubSub$16(PubSubDUnitTest.java:373)
> 15:28:39
> 15:28:39Caused by:
> 15:28:39java.net.SocketTimeoutException: Read timed out
> 15:28:39at java.net.SocketInputStream.socketRead0(Native
> Method)
> 15:28:39at
> java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
> 15:28:39at
> java.net.SocketInputStream.read(SocketInputStream.java:171)
> 15:28:39at
> java.net.SocketInputStream.read(SocketInputStream.java:141)
> 15:28:39at
> java.net.SocketInputStream.read(SocketInputStream.java:127)
> 15:28:39at
> redis.clients.jedis.util.RedisInputStream.ensureFill(RedisInputStream.java:199)
> 15:28:39... 7 more
> 15:29:24 {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-10174) CI Failure: PubSubDUnitTest > testConcurrentPubSub
[
https://issues.apache.org/jira/browse/GEODE-10174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17512625#comment-17512625
]
Jianxia Chen commented on GEODE-10174:
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.5-build.0938/test-results/distributedTest/1648080229/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Test report artifacts from this job are available at:
http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.5-build.0938/test-artifacts/1648080229/distributedtestfiles-openjdk8-1.14.5-build.0938.tgz
> CI Failure: PubSubDUnitTest > testConcurrentPubSub
> --
>
> Key: GEODE-10174
> URL: https://issues.apache.org/jira/browse/GEODE-10174
> Project: Geode
> Issue Type: Bug
>Reporter: Jianxia Chen
>Priority: Major
> Labels: needsTriage
>
> {code:java}
> org.apache.geode.redis.internal.executor.pubsub.PubSubDUnitTest >
> testConcurrentPubSub FAILED
> 15:28:39java.util.concurrent.ExecutionException:
> redis.clients.jedis.exceptions.JedisConnectionException:
> java.net.SocketTimeoutException: Read timed out
> 15:28:39
> 15:28:39Caused by:
> 15:28:39redis.clients.jedis.exceptions.JedisConnectionException:
> java.net.SocketTimeoutException: Read timed out
> 15:28:39at
> redis.clients.jedis.util.RedisInputStream.ensureFill(RedisInputStream.java:205)
> 15:28:39at
> redis.clients.jedis.util.RedisInputStream.readByte(RedisInputStream.java:43)
> 15:28:39at redis.clients.jedis.Protocol.process(Protocol.java:155)
> 15:28:39at redis.clients.jedis.Protocol.read(Protocol.java:220)
> 15:28:39at
> redis.clients.jedis.Connection.readProtocolWithCheckingBroken(Connection.java:283)
> 15:28:39at
> redis.clients.jedis.Connection.getIntegerReply(Connection.java:225)
> 15:28:39at redis.clients.jedis.Jedis.publish(Jedis.java:2908)
> 15:28:39at
> org.apache.geode.redis.internal.executor.pubsub.PubSubDUnitTest.lambda$testConcurrentPubSub$16(PubSubDUnitTest.java:373)
> 15:28:39
> 15:28:39Caused by:
> 15:28:39java.net.SocketTimeoutException: Read timed out
> 15:28:39at java.net.SocketInputStream.socketRead0(Native
> Method)
> 15:28:39at
> java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
> 15:28:39at
> java.net.SocketInputStream.read(SocketInputStream.java:171)
> 15:28:39at
> java.net.SocketInputStream.read(SocketInputStream.java:141)
> 15:28:39at
> java.net.SocketInputStream.read(SocketInputStream.java:127)
> 15:28:39at
> redis.clients.jedis.util.RedisInputStream.ensureFill(RedisInputStream.java:199)
> 15:28:39... 7 more
> 15:29:24 {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (GEODE-10174) CI Failure: PubSubDUnitTest > testConcurrentPubSub
Jianxia Chen created GEODE-10174:
Summary: CI Failure: PubSubDUnitTest > testConcurrentPubSub
Key: GEODE-10174
URL: https://issues.apache.org/jira/browse/GEODE-10174
Project: Geode
Issue Type: Bug
Reporter: Jianxia Chen
{code:java}
org.apache.geode.redis.internal.executor.pubsub.PubSubDUnitTest >
testConcurrentPubSub FAILED
15:28:39java.util.concurrent.ExecutionException:
redis.clients.jedis.exceptions.JedisConnectionException:
java.net.SocketTimeoutException: Read timed out
15:28:39
15:28:39Caused by:
15:28:39redis.clients.jedis.exceptions.JedisConnectionException:
java.net.SocketTimeoutException: Read timed out
15:28:39at
redis.clients.jedis.util.RedisInputStream.ensureFill(RedisInputStream.java:205)
15:28:39at
redis.clients.jedis.util.RedisInputStream.readByte(RedisInputStream.java:43)
15:28:39at redis.clients.jedis.Protocol.process(Protocol.java:155)
15:28:39at redis.clients.jedis.Protocol.read(Protocol.java:220)
15:28:39at
redis.clients.jedis.Connection.readProtocolWithCheckingBroken(Connection.java:283)
15:28:39at
redis.clients.jedis.Connection.getIntegerReply(Connection.java:225)
15:28:39at redis.clients.jedis.Jedis.publish(Jedis.java:2908)
15:28:39at
org.apache.geode.redis.internal.executor.pubsub.PubSubDUnitTest.lambda$testConcurrentPubSub$16(PubSubDUnitTest.java:373)
15:28:39
15:28:39Caused by:
15:28:39java.net.SocketTimeoutException: Read timed out
15:28:39at java.net.SocketInputStream.socketRead0(Native Method)
15:28:39at
java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
15:28:39at
java.net.SocketInputStream.read(SocketInputStream.java:171)
15:28:39at
java.net.SocketInputStream.read(SocketInputStream.java:141)
15:28:39at
java.net.SocketInputStream.read(SocketInputStream.java:127)
15:28:39at
redis.clients.jedis.util.RedisInputStream.ensureFill(RedisInputStream.java:199)
15:28:39... 7 more
15:29:24 {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-10174) CI Failure: PubSubDUnitTest > testConcurrentPubSub
[
https://issues.apache.org/jira/browse/GEODE-10174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Murmann updated GEODE-10174:
--
Labels: needsTriage (was: )
> CI Failure: PubSubDUnitTest > testConcurrentPubSub
> --
>
> Key: GEODE-10174
> URL: https://issues.apache.org/jira/browse/GEODE-10174
> Project: Geode
> Issue Type: Bug
>Reporter: Jianxia Chen
>Priority: Major
> Labels: needsTriage
>
> {code:java}
> org.apache.geode.redis.internal.executor.pubsub.PubSubDUnitTest >
> testConcurrentPubSub FAILED
> 15:28:39java.util.concurrent.ExecutionException:
> redis.clients.jedis.exceptions.JedisConnectionException:
> java.net.SocketTimeoutException: Read timed out
> 15:28:39
> 15:28:39Caused by:
> 15:28:39redis.clients.jedis.exceptions.JedisConnectionException:
> java.net.SocketTimeoutException: Read timed out
> 15:28:39at
> redis.clients.jedis.util.RedisInputStream.ensureFill(RedisInputStream.java:205)
> 15:28:39at
> redis.clients.jedis.util.RedisInputStream.readByte(RedisInputStream.java:43)
> 15:28:39at redis.clients.jedis.Protocol.process(Protocol.java:155)
> 15:28:39at redis.clients.jedis.Protocol.read(Protocol.java:220)
> 15:28:39at
> redis.clients.jedis.Connection.readProtocolWithCheckingBroken(Connection.java:283)
> 15:28:39at
> redis.clients.jedis.Connection.getIntegerReply(Connection.java:225)
> 15:28:39at redis.clients.jedis.Jedis.publish(Jedis.java:2908)
> 15:28:39at
> org.apache.geode.redis.internal.executor.pubsub.PubSubDUnitTest.lambda$testConcurrentPubSub$16(PubSubDUnitTest.java:373)
> 15:28:39
> 15:28:39Caused by:
> 15:28:39java.net.SocketTimeoutException: Read timed out
> 15:28:39at java.net.SocketInputStream.socketRead0(Native
> Method)
> 15:28:39at
> java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
> 15:28:39at
> java.net.SocketInputStream.read(SocketInputStream.java:171)
> 15:28:39at
> java.net.SocketInputStream.read(SocketInputStream.java:141)
> 15:28:39at
> java.net.SocketInputStream.read(SocketInputStream.java:127)
> 15:28:39at
> redis.clients.jedis.util.RedisInputStream.ensureFill(RedisInputStream.java:199)
> 15:28:39... 7 more
> 15:29:24 {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-10164) Revert wording change in rebalance result
[
https://issues.apache.org/jira/browse/GEODE-10164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barrett Oglesby updated GEODE-10164:
Affects Version/s: 1.15.0
> Revert wording change in rebalance result
> -
>
> Key: GEODE-10164
> URL: https://issues.apache.org/jira/browse/GEODE-10164
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Affects Versions: 1.15.0
>Reporter: Barrett Oglesby
>Assignee: Barrett Oglesby
>Priority: Major
> Labels: blocks-1.15.0, needsTriage, pull-request-available
> Fix For: 1.12.10, 1.13.9, 1.14.5, 1.15.0
>
>
> I made a change to the wording of the rebalance command result
> from:
> {noformat}
> Rebalanced partition regions {noformat}
> to:
> {noformat}
> Rebalanced partitioned region {noformat}
> This change caused hydra and other tests to fail, so I'm reverting it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-10164) Revert wording change in rebalance result
[
https://issues.apache.org/jira/browse/GEODE-10164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barrett Oglesby updated GEODE-10164:
Labels: blocks-1.15.0 needsTriage pull-request-available (was: needsTriage
pull-request-available)
> Revert wording change in rebalance result
> -
>
> Key: GEODE-10164
> URL: https://issues.apache.org/jira/browse/GEODE-10164
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Barrett Oglesby
>Assignee: Barrett Oglesby
>Priority: Major
> Labels: blocks-1.15.0, needsTriage, pull-request-available
> Fix For: 1.12.10, 1.13.9, 1.14.5, 1.15.0
>
>
> I made a change to the wording of the rebalance command result
> from:
> {noformat}
> Rebalanced partition regions {noformat}
> to:
> {noformat}
> Rebalanced partitioned region {noformat}
> This change caused hydra and other tests to fail, so I'm reverting it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-7960) CI: SingleThreadColocationLoggerTest.logsMissingChildRegionUntilCompletion FAILED on Windows
[
https://issues.apache.org/jira/browse/GEODE-7960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17512620#comment-17512620
]
Geode Integration commented on GEODE-7960:
--
Seen on support/1.14 in [windows-unit-test-openjdk8
#37|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-14-main/jobs/windows-unit-test-openjdk8/builds/37]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.5-build.0938/test-results/test/1648075272/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.5-build.0938/test-artifacts/1648075272/windows-unittestfiles-openjdk8-1.14.5-build.0938.tgz].
> CI: SingleThreadColocationLoggerTest.logsMissingChildRegionUntilCompletion
> FAILED on Windows
>
>
> Key: GEODE-7960
> URL: https://issues.apache.org/jira/browse/GEODE-7960
> Project: Geode
> Issue Type: Bug
> Components: logging
>Reporter: Jinmei Liao
>Assignee: Kirk Lund
>Priority: Major
>
> Looks like a flaky test on windows:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/WindowsUnitTestOpenJDK11/builds/21
> {noformat}
> org.apache.geode.internal.cache.partitioned.colocation.SingleThreadColocationLoggerTest
> > logsMissingChildRegionUntilCompletion FAILED
> org.mockito.exceptions.verification.NoInteractionsWanted:
> No interactions wanted here:
> -> at
> org.apache.geode.internal.cache.partitioned.colocation.SingleThreadColocationLoggerTest.logsMissingChildRegionUntilCompletion(SingleThreadColocationLoggerTest.java:180)
> But found this interaction on mock 'consumer':
> -> at
> org.apache.geode.internal.cache.partitioned.colocation.SingleThreadColocationLogger.logMissingRegions(SingleThreadColocationLogger.java:229)
> ***
> For your reference, here is the list of all invocations ([?] - means
> unverified).
> 1. -> at
> org.apache.geode.internal.cache.partitioned.colocation.SingleThreadColocationLogger.logMissingRegions(SingleThreadColocationLogger.java:229)
> 2. [?]-> at
> org.apache.geode.internal.cache.partitioned.colocation.SingleThreadColocationLogger.logMissingRegions(SingleThreadColocationLogger.java:229)
> at
> org.apache.geode.internal.cache.partitioned.colocation.SingleThreadColocationLoggerTest.logsMissingChildRegionUntilCompletion(SingleThreadColocationLoggerTest.java:180)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-7960) CI: SingleThreadColocationLoggerTest.logsMissingChildRegionUntilCompletion FAILED on Windows
[
https://issues.apache.org/jira/browse/GEODE-7960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17512621#comment-17512621
]
Jianxia Chen commented on GEODE-7960:
-
Failed again:
[https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-14-main/jobs/windows-unit-test-openjdk8/builds/37]
> CI: SingleThreadColocationLoggerTest.logsMissingChildRegionUntilCompletion
> FAILED on Windows
>
>
> Key: GEODE-7960
> URL: https://issues.apache.org/jira/browse/GEODE-7960
> Project: Geode
> Issue Type: Bug
> Components: logging
>Reporter: Jinmei Liao
>Assignee: Kirk Lund
>Priority: Major
>
> Looks like a flaky test on windows:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/WindowsUnitTestOpenJDK11/builds/21
> {noformat}
> org.apache.geode.internal.cache.partitioned.colocation.SingleThreadColocationLoggerTest
> > logsMissingChildRegionUntilCompletion FAILED
> org.mockito.exceptions.verification.NoInteractionsWanted:
> No interactions wanted here:
> -> at
> org.apache.geode.internal.cache.partitioned.colocation.SingleThreadColocationLoggerTest.logsMissingChildRegionUntilCompletion(SingleThreadColocationLoggerTest.java:180)
> But found this interaction on mock 'consumer':
> -> at
> org.apache.geode.internal.cache.partitioned.colocation.SingleThreadColocationLogger.logMissingRegions(SingleThreadColocationLogger.java:229)
> ***
> For your reference, here is the list of all invocations ([?] - means
> unverified).
> 1. -> at
> org.apache.geode.internal.cache.partitioned.colocation.SingleThreadColocationLogger.logMissingRegions(SingleThreadColocationLogger.java:229)
> 2. [?]-> at
> org.apache.geode.internal.cache.partitioned.colocation.SingleThreadColocationLogger.logMissingRegions(SingleThreadColocationLogger.java:229)
> at
> org.apache.geode.internal.cache.partitioned.colocation.SingleThreadColocationLoggerTest.logsMissingChildRegionUntilCompletion(SingleThreadColocationLoggerTest.java:180)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-10091) Benchmark instability in RedisZaddAndZremBenchmark
[
https://issues.apache.org/jira/browse/GEODE-10091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17512616#comment-17512616
]
Geode Integration commented on GEODE-10091:
---
Seen in [benchmark-radish
#241|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/benchmark-radish/builds/241].
> Benchmark instability in RedisZaddAndZremBenchmark
> --
>
> Key: GEODE-10091
> URL: https://issues.apache.org/jira/browse/GEODE-10091
> Project: Geode
> Issue Type: Bug
> Components: benchmarks, redis
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Assignee: Eric Zoerner
>Priority: Major
> Labels: needsTriage
>
> {noformat}
> This is ITERATION 1 of benchmarking against baseline.
> RedisGetBenchmark avg ops/sec
> Baseline:428358.55 Test:446241.49 Difference: +4.2%
> avg latency
> Baseline: 1678809.55 Test: 1611045.34 Difference: -4.0%
> RedisHgetBenchmark avg ops/sec
> Baseline:438535.25 Test:441078.97 Difference: +0.6%
> avg latency
> Baseline: 1638968.92 Test: 1630999.16 Difference: -0.5%
> RedisHsetAndHgetBenchmark avg ops/sec
> Baseline:191331.54 Test:186806.37 Difference: -2.4%
> avg latency
> Baseline: 3759694.09 Test: 3850396.04 Difference: +2.4%
> RedisHsetBenchmark avg ops/sec
> Baseline:308079.41 Test:303715.78 Difference: -1.4%
> avg latency
> Baseline: 2332102.91 Test: 2367639.93 Difference: +1.5%
> RedisSetBenchmark avg ops/sec
> Baseline:318147.74 Test:326996.22 Difference: +2.8%
> avg latency
> Baseline: 2263687.57 Test: 2198181.68 Difference: -2.9%
> RedisWeightedHsetAndHgetBenchmark avg ops/sec
> Baseline:390383.79 Test:385565.48 Difference: -1.2%
> avg latency
> Baseline: 1842561.96 Test: 1864716.09 Difference: +1.2%
> RedisWeightedZaddAndZrangeBenchmark avg ops/sec
> Baseline:375078.82 Test:350886.03 Difference: -6.5%
> avg latency
> Baseline: 1917476.15 Test: 2049452.87 Difference: +6.9%
> RedisZaddAndZremBenchmark avg ops/sec
> Baseline:124763.60 Test:118600.72 Difference: -4.9%
> avg latency
> Baseline: 5766048.34 Test: 6065491.13 Difference: +5.2%
> RedisZaddBenchmark avg ops/sec
> Baseline:432494.29 Test:438594.53 Difference: +1.4%
> avg latency
> Baseline: 1662639.09 Test: 1639906.18 Difference: -1.4%
> RedisZrangeBenchmark avg ops/sec
> Baseline:295523.77 Test:340381.87 Difference: +15.2%
> avg latency
> Baseline: 2433250.54 Test: 2112961.66 Difference: -13.2%
> RedisZrangeByScoreBenchmark avg ops/sec
> Baseline:285836.33 Test:356142.91 Difference: +24.6%
> avg latency
> Baseline: 2515708.23 Test: 2019249.68 Difference: -19.7%
> This is ITERATION 2 of benchmarking against baseline.
> RedisWeightedZaddAndZrangeBenchmark avg ops/sec
> Baseline:358570.33 Test:348012.02 Difference: -2.9%
> avg latency
> Baseline: 2005804.05 Test: 2066535.24 Difference: +3.0%
> RedisZaddAndZremBenchmark avg ops/sec
> Baseline:122900.38 Test:115226.22 Difference: -6.2%
> avg latency
> Baseline: 5858357.13 Test: 6243018.38 Difference: +6.6%
> This is ITERATION 3 of benchmarking against baseline.
> RedisZaddAndZremBenchmark avg ops/sec
> Baseline:125677.36 Test:118359.94 Difference: -5.8%
> a
[jira] [Commented] (GEODE-8494) CI Failure: Tomcat7SessionsTest.setupClass fails due to java.net.BindException: Address already in use
[
https://issues.apache.org/jira/browse/GEODE-8494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17512612#comment-17512612
]
Jianxia Chen commented on GEODE-8494:
-
Failed again:
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/integration-test-openjdk11/builds/239
> CI Failure: Tomcat7SessionsTest.setupClass fails due to
> java.net.BindException: Address already in use
> --
>
> Key: GEODE-8494
> URL: https://issues.apache.org/jira/browse/GEODE-8494
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.12.3, 1.13.3, 1.14.0
>Reporter: Donal Evans
>Priority: Major
>
> This is possibly just an unlucky port collision due to multiple tests being
> run at the same time.
> {noformat}
> org.apache.geode.modules.session.Tomcat7SessionsTest > classMethod FAILED
> org.apache.catalina.LifecycleException: service.getName(): "null";
> Protocol handler start failed
> at
> org.apache.catalina.connector.Connector.startInternal(Connector.java:986)
> at
> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
> at
> org.apache.catalina.startup.Embedded.startInternal(Embedded.java:781)
> at
> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
> at
> org.apache.geode.modules.session.EmbeddedTomcat.startContainer(EmbeddedTomcat.java:98)
> at
> org.apache.geode.modules.session.AbstractSessionsTest.setupServer(AbstractSessionsTest.java:71)
> at
> org.apache.geode.modules.session.Tomcat7SessionsTest.setupClass(Tomcat7SessionsTest.java:36)
> Caused by:
> java.net.BindException: Address already in use: NET_Bind :49811
> at
> org.apache.tomcat.util.net.JIoEndpoint.bind(JIoEndpoint.java:414)
> at
> org.apache.tomcat.util.net.AbstractEndpoint.start(AbstractEndpoint.java:767)
> at
> org.apache.coyote.AbstractProtocol.start(AbstractProtocol.java:482)
> at
> org.apache.catalina.connector.Connector.startInternal(Connector.java:979)
> ... 6 more
> Caused by:
> java.net.BindException: Address already in use: NET_Bind
> at java.net.PlainSocketImpl.bind0(Native Method)
> at
> java.net.PlainSocketImpl.socketBind(PlainSocketImpl.java:132)
> at
> java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:436)
> at java.net.ServerSocket.bind(ServerSocket.java:395)
> at java.net.ServerSocket.(ServerSocket.java:257)
> at java.net.ServerSocket.(ServerSocket.java:201)
> at
> org.apache.tomcat.util.net.DefaultServerSocketFactory.createSocket(DefaultServerSocketFactory.java:49)
> at
> org.apache.tomcat.util.net.JIoEndpoint.bind(JIoEndpoint.java:401)
> ... 9 more
> {noformat}
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>
> [http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0330/test-results/integrationTest/1600111592/]
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> [http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0330/test-artifacts/1600111592/windows-integrationtestfiles-OpenJDK11-1.14.0-build.0330.tgz]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-8494) CI Failure: Tomcat7SessionsTest.setupClass fails due to java.net.BindException: Address already in use
[
https://issues.apache.org/jira/browse/GEODE-8494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17512611#comment-17512611
]
Geode Integration commented on GEODE-8494:
--
Seen in [integration-test-openjdk11
#239|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/integration-test-openjdk11/builds/239]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1032/test-results/integrationTest/1648244778/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1032/test-artifacts/1648244778/integrationtestfiles-openjdk11-1.15.0-build.1032.tgz].
> CI Failure: Tomcat7SessionsTest.setupClass fails due to
> java.net.BindException: Address already in use
> --
>
> Key: GEODE-8494
> URL: https://issues.apache.org/jira/browse/GEODE-8494
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.12.3, 1.13.3, 1.14.0
>Reporter: Donal Evans
>Priority: Major
>
> This is possibly just an unlucky port collision due to multiple tests being
> run at the same time.
> {noformat}
> org.apache.geode.modules.session.Tomcat7SessionsTest > classMethod FAILED
> org.apache.catalina.LifecycleException: service.getName(): "null";
> Protocol handler start failed
> at
> org.apache.catalina.connector.Connector.startInternal(Connector.java:986)
> at
> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
> at
> org.apache.catalina.startup.Embedded.startInternal(Embedded.java:781)
> at
> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
> at
> org.apache.geode.modules.session.EmbeddedTomcat.startContainer(EmbeddedTomcat.java:98)
> at
> org.apache.geode.modules.session.AbstractSessionsTest.setupServer(AbstractSessionsTest.java:71)
> at
> org.apache.geode.modules.session.Tomcat7SessionsTest.setupClass(Tomcat7SessionsTest.java:36)
> Caused by:
> java.net.BindException: Address already in use: NET_Bind :49811
> at
> org.apache.tomcat.util.net.JIoEndpoint.bind(JIoEndpoint.java:414)
> at
> org.apache.tomcat.util.net.AbstractEndpoint.start(AbstractEndpoint.java:767)
> at
> org.apache.coyote.AbstractProtocol.start(AbstractProtocol.java:482)
> at
> org.apache.catalina.connector.Connector.startInternal(Connector.java:979)
> ... 6 more
> Caused by:
> java.net.BindException: Address already in use: NET_Bind
> at java.net.PlainSocketImpl.bind0(Native Method)
> at
> java.net.PlainSocketImpl.socketBind(PlainSocketImpl.java:132)
> at
> java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:436)
> at java.net.ServerSocket.bind(ServerSocket.java:395)
> at java.net.ServerSocket.(ServerSocket.java:257)
> at java.net.ServerSocket.(ServerSocket.java:201)
> at
> org.apache.tomcat.util.net.DefaultServerSocketFactory.createSocket(DefaultServerSocketFactory.java:49)
> at
> org.apache.tomcat.util.net.JIoEndpoint.bind(JIoEndpoint.java:401)
> ... 9 more
> {noformat}
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>
> [http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0330/test-results/integrationTest/1600111592/]
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> [http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0330/test-artifacts/1600111592/windows-integrationtestfiles-OpenJDK11-1.14.0-build.0330.tgz]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-10173) CI failure: P2pPartitionedGetBenchmark > run()
[
https://issues.apache.org/jira/browse/GEODE-10173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17512608#comment-17512608
]
Geode Integration commented on GEODE-10173:
---
Seen on support/1.14 in [benchmark-base
#36|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-14-main/jobs/benchmark-base/builds/36].
> CI failure: P2pPartitionedGetBenchmark > run()
> --
>
> Key: GEODE-10173
> URL: https://issues.apache.org/jira/browse/GEODE-10173
> Project: Geode
> Issue Type: Bug
>Reporter: Jianxia Chen
>Priority: Major
> Labels: needsTriage
>
> {code:java}
> org.apache.geode.benchmark.tests.P2pPartitionedGetBenchmark > run() FAILED
> 15:49:10net.schmizz.sshj.transport.TransportException: Connection reset
> 15:49:10at
> net.schmizz.sshj.transport.TransportImpl.init(TransportImpl.java:181)
> 15:49:10at net.schmizz.sshj.SSHClient.onConnect(SSHClient.java:771)
> 15:49:10at
> net.schmizz.sshj.SocketClient.connect(SocketClient.java:150)
> 15:49:10at
> org.apache.geode.perftest.infrastructure.ssh.SshInfrastructure.getSSHClient(SshInfrastructure.java:75)
> 15:49:10at
> org.apache.geode.perftest.infrastructure.ssh.SshInfrastructure.copyFromNode(SshInfrastructure.java:186)
> 15:49:10at
> org.apache.geode.perftest.jvms.RemoteJVMs.copyResults(RemoteJVMs.java:87)
> 15:49:10at
> org.apache.geode.perftest.runner.DefaultTestRunner.runTest(DefaultTestRunner.java:136)
> 15:49:10at
> org.apache.geode.perftest.runner.DefaultTestRunner.runTest(DefaultTestRunner.java:68)
> 15:49:10at
> org.apache.geode.benchmark.tests.P2pPartitionedGetBenchmark.run(P2pPartitionedGetBenchmark.java:44)
> 15:49:10
> 15:49:10Caused by:
> 15:49:10java.net.SocketException: Connection reset
> 15:49:10at
> java.net.SocketInputStream.read(SocketInputStream.java:210)
> 15:49:10at
> java.net.SocketInputStream.read(SocketInputStream.java:141)
> 15:49:10at
> java.net.SocketInputStream.read(SocketInputStream.java:224)
> 15:49:10at
> net.schmizz.sshj.transport.TransportImpl.receiveServerIdent(TransportImpl.java:198)
> 15:49:10at
> net.schmizz.sshj.transport.TransportImpl.init(TransportImpl.java:174)
> 15:49:10... 8 more {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (GEODE-10173) CI failure: P2pPartitionedGetBenchmark > run()
Jianxia Chen created GEODE-10173:
Summary: CI failure: P2pPartitionedGetBenchmark > run()
Key: GEODE-10173
URL: https://issues.apache.org/jira/browse/GEODE-10173
Project: Geode
Issue Type: Bug
Reporter: Jianxia Chen
{code:java}
org.apache.geode.benchmark.tests.P2pPartitionedGetBenchmark > run() FAILED
15:49:10net.schmizz.sshj.transport.TransportException: Connection reset
15:49:10at
net.schmizz.sshj.transport.TransportImpl.init(TransportImpl.java:181)
15:49:10at net.schmizz.sshj.SSHClient.onConnect(SSHClient.java:771)
15:49:10at net.schmizz.sshj.SocketClient.connect(SocketClient.java:150)
15:49:10at
org.apache.geode.perftest.infrastructure.ssh.SshInfrastructure.getSSHClient(SshInfrastructure.java:75)
15:49:10at
org.apache.geode.perftest.infrastructure.ssh.SshInfrastructure.copyFromNode(SshInfrastructure.java:186)
15:49:10at
org.apache.geode.perftest.jvms.RemoteJVMs.copyResults(RemoteJVMs.java:87)
15:49:10at
org.apache.geode.perftest.runner.DefaultTestRunner.runTest(DefaultTestRunner.java:136)
15:49:10at
org.apache.geode.perftest.runner.DefaultTestRunner.runTest(DefaultTestRunner.java:68)
15:49:10at
org.apache.geode.benchmark.tests.P2pPartitionedGetBenchmark.run(P2pPartitionedGetBenchmark.java:44)
15:49:10
15:49:10Caused by:
15:49:10java.net.SocketException: Connection reset
15:49:10at
java.net.SocketInputStream.read(SocketInputStream.java:210)
15:49:10at
java.net.SocketInputStream.read(SocketInputStream.java:141)
15:49:10at
java.net.SocketInputStream.read(SocketInputStream.java:224)
15:49:10at
net.schmizz.sshj.transport.TransportImpl.receiveServerIdent(TransportImpl.java:198)
15:49:10at
net.schmizz.sshj.transport.TransportImpl.init(TransportImpl.java:174)
15:49:10... 8 more {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-10173) CI failure: P2pPartitionedGetBenchmark > run()
[
https://issues.apache.org/jira/browse/GEODE-10173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Murmann updated GEODE-10173:
--
Labels: needsTriage (was: )
> CI failure: P2pPartitionedGetBenchmark > run()
> --
>
> Key: GEODE-10173
> URL: https://issues.apache.org/jira/browse/GEODE-10173
> Project: Geode
> Issue Type: Bug
>Reporter: Jianxia Chen
>Priority: Major
> Labels: needsTriage
>
> {code:java}
> org.apache.geode.benchmark.tests.P2pPartitionedGetBenchmark > run() FAILED
> 15:49:10net.schmizz.sshj.transport.TransportException: Connection reset
> 15:49:10at
> net.schmizz.sshj.transport.TransportImpl.init(TransportImpl.java:181)
> 15:49:10at net.schmizz.sshj.SSHClient.onConnect(SSHClient.java:771)
> 15:49:10at
> net.schmizz.sshj.SocketClient.connect(SocketClient.java:150)
> 15:49:10at
> org.apache.geode.perftest.infrastructure.ssh.SshInfrastructure.getSSHClient(SshInfrastructure.java:75)
> 15:49:10at
> org.apache.geode.perftest.infrastructure.ssh.SshInfrastructure.copyFromNode(SshInfrastructure.java:186)
> 15:49:10at
> org.apache.geode.perftest.jvms.RemoteJVMs.copyResults(RemoteJVMs.java:87)
> 15:49:10at
> org.apache.geode.perftest.runner.DefaultTestRunner.runTest(DefaultTestRunner.java:136)
> 15:49:10at
> org.apache.geode.perftest.runner.DefaultTestRunner.runTest(DefaultTestRunner.java:68)
> 15:49:10at
> org.apache.geode.benchmark.tests.P2pPartitionedGetBenchmark.run(P2pPartitionedGetBenchmark.java:44)
> 15:49:10
> 15:49:10Caused by:
> 15:49:10java.net.SocketException: Connection reset
> 15:49:10at
> java.net.SocketInputStream.read(SocketInputStream.java:210)
> 15:49:10at
> java.net.SocketInputStream.read(SocketInputStream.java:141)
> 15:49:10at
> java.net.SocketInputStream.read(SocketInputStream.java:224)
> 15:49:10at
> net.schmizz.sshj.transport.TransportImpl.receiveServerIdent(TransportImpl.java:198)
> 15:49:10at
> net.schmizz.sshj.transport.TransportImpl.init(TransportImpl.java:174)
> 15:49:10... 8 more {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Comment Edited] (GEODE-9476) VMStats processCpuTime, fdLimit, and fdsOpen will always be zero on java 16 and later
[
https://issues.apache.org/jira/browse/GEODE-9476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17512603#comment-17512603
]
Darrel Schneider edited comment on GEODE-9476 at 3/25/22, 10:08 PM:
I think the issue with having com.sun.management.OperatingSystemMXBean in our
code is that it does not exist on Windows. I think we support building on
Windows not just running on it. Code with a reference to this class will fail
to compile on Windows. If it was just a Windows runtime issue we catch
ClassNotFoundException and be okay.
But I might be wrong about this. It just be an issue with the fd limits. It is
worth doing some builds on windows to see what will work.
was (Author: dschneider):
I think the issue with having com.sun.management.OperatingSystemMXBean in our
code is that it does not exist on Windows. I think we support building on
Windows not just running on it. Code with a reference to this class will fail
to compile on Windows. If it was just a Windows runtime issue we catch
ClassNotFoundException and be okay.
> VMStats processCpuTime, fdLimit, and fdsOpen will always be zero on java 16
> and later
> -
>
> Key: GEODE-9476
> URL: https://issues.apache.org/jira/browse/GEODE-9476
> Project: Geode
> Issue Type: Bug
> Components: statistics
>Reporter: Darrel Schneider
>Priority: Major
> Labels: Java16
>
> VMStats processCpuTime, fdLimit, and fdsOpen will always be zero on java 16
> and later.
> This is because it calls Method.setAccessible which is not allowed under
> normal conditions starting with java 16 (see:
> https://softwaregarden.dev/en/posts/new-java/illegal-access-in-java-16).
> A workaround for this bug is to start the jvm with --illegal-access=permit
> The setAccessible call is in the static initializer for:
> org.apache.geode.internal.stats50.VMStats50
> It turns out the following works for calling processCpuTime:
> {code:java}
> OperatingSystemMXBean osBean =
> ManagementFactory.getOperatingSystemMXBean();
> com.sun.management.OperatingSystemMXBean sunBean =
> (com.sun.management.OperatingSystemMXBean) osBean;
> System.out.println("getProcessCpuTime=" +
> sunBean.getProcessCpuTime());
> {code}
> so we can get rid of the setAccessible call
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-9476) VMStats processCpuTime, fdLimit, and fdsOpen will always be zero on java 16 and later
[
https://issues.apache.org/jira/browse/GEODE-9476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17512603#comment-17512603
]
Darrel Schneider commented on GEODE-9476:
-
I think the issue with having com.sun.management.OperatingSystemMXBean in our
code is that it does not exist on Windows. I think we support building on
Windows not just running on it. Code with a reference to this class will fail
to compile on Windows. If it was just a Windows runtime issue we catch
ClassNotFoundException and be okay.
> VMStats processCpuTime, fdLimit, and fdsOpen will always be zero on java 16
> and later
> -
>
> Key: GEODE-9476
> URL: https://issues.apache.org/jira/browse/GEODE-9476
> Project: Geode
> Issue Type: Bug
> Components: statistics
>Reporter: Darrel Schneider
>Priority: Major
> Labels: Java16
>
> VMStats processCpuTime, fdLimit, and fdsOpen will always be zero on java 16
> and later.
> This is because it calls Method.setAccessible which is not allowed under
> normal conditions starting with java 16 (see:
> https://softwaregarden.dev/en/posts/new-java/illegal-access-in-java-16).
> A workaround for this bug is to start the jvm with --illegal-access=permit
> The setAccessible call is in the static initializer for:
> org.apache.geode.internal.stats50.VMStats50
> It turns out the following works for calling processCpuTime:
> {code:java}
> OperatingSystemMXBean osBean =
> ManagementFactory.getOperatingSystemMXBean();
> com.sun.management.OperatingSystemMXBean sunBean =
> (com.sun.management.OperatingSystemMXBean) osBean;
> System.out.println("getProcessCpuTime=" +
> sunBean.getProcessCpuTime());
> {code}
> so we can get rid of the setAccessible call
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-10133) ReflectionSingleObjectSizer throws when sizing hidden classes
[
https://issues.apache.org/jira/browse/GEODE-10133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17512599#comment-17512599
]
ASF subversion and git services commented on GEODE-10133:
-
Commit feb2f8755a8bf93ddc0970f0e190b5c3fe2645e4 in geode's branch
refs/heads/develop from Darrel Schneider
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=feb2f87 ]
GEODE-10133: change sizeof to handle UnsupportedOperationException (#7484)
* the sizeof method now handles UnsupportedOperationException
* added unit test coverage for ReflectionSingleObjectSizer sizeof
> ReflectionSingleObjectSizer throws when sizing hidden classes
> -
>
> Key: GEODE-10133
> URL: https://issues.apache.org/jira/browse/GEODE-10133
> Project: Geode
> Issue Type: Improvement
> Components: core
>Reporter: Dale Emery
>Assignee: Darrel Schneider
>Priority: Major
> Labels: Java17, pull-request-available
> Fix For: 1.15.0
>
>
> On JDK 17, the class of a lambda is a "hidden" class. When
> {{ReflectionSingleObjectSizer}} tries to find the offset of the fields of a
> hidden class, the JDK throws {{UnsupportedOperationException}}.
> Tests that fail due to this exception:
> - {{MemoryOverheadIntegrationTest}}
> - {{OutOfMemoryDUnitTest}}
> - {{SessionReplicationLocalCacheJUnitTest}}
> Example exception from {{MemoryOverheadIntegrationTest}}:
> {noformat}
> ava.lang.UnsupportedOperationException: can't get field offset on a hidden
> class: private final org.apache.geode.internal.cache.InternalCache
> org.apache.geode.redis.internal.GeodeRedisServer$$Lambda$607/0x0008011434d8.arg$1
> at sun.misc.Unsafe.objectFieldOffset(Unsafe.java:645)
> at
> org.apache.geode.unsafe.internal.sun.misc.Unsafe.fieldOffset(Unsafe.java:187)
> at
> org.apache.geode.internal.size.ReflectionSingleObjectSizer.sizeof(ReflectionSingleObjectSizer.java:106)
> at
> org.apache.geode.internal.size.ReflectionSingleObjectSizer.sizeof(ReflectionSingleObjectSizer.java:84)
> at
> org.apache.geode.internal.size.ReflectionSingleObjectSizer.sizeof(ReflectionSingleObjectSizer.java:52)
> at
> org.apache.geode.internal.size.CachingSingleObjectSizer.sizeof(CachingSingleObjectSizer.java:39)
> at
> org.apache.geode.internal.size.ObjectGraphSizer$SizeVisitor.visit(ObjectGraphSizer.java:223)
> at
> org.apache.geode.internal.size.ObjectTraverser$VisitStack.add(ObjectTraverser.java:163)
> at
> org.apache.geode.internal.size.ObjectTraverser.doSearch(ObjectTraverser.java:87)
> at
> org.apache.geode.internal.size.ObjectTraverser.breadthFirstSearch(ObjectTraverser.java:54)
> at
> org.apache.geode.internal.size.ObjectGraphSizer.size(ObjectGraphSizer.java:96)
> at
> org.apache.geode.redis.internal.data.MemoryOverheadIntegrationTest.getUsedMemory(MemoryOverheadIntegrationTest.java:95)
> at
> org.apache.geode.redis.internal.data.AbstractMemoryOverheadIntegrationTest.measureAndCheckPerEntryOverhead(AbstractMemoryOverheadIntegrationTest.java:284)
> at
> org.apache.geode.redis.internal.data.AbstractMemoryOverheadIntegrationTest.measureOverheadPerHash(AbstractMemoryOverheadIntegrationTest.java:127)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
> at
> jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:568)
> 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.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at
> org.apache.geode.test.junit.rules.serializable.SerializableExternalResource$1.evaluate(SerializableExternalResource.java:38)
> 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.ParentRun
[jira] [Resolved] (GEODE-10133) ReflectionSingleObjectSizer throws when sizing hidden classes
[
https://issues.apache.org/jira/browse/GEODE-10133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darrel Schneider resolved GEODE-10133.
--
Fix Version/s: 1.15.0
Resolution: Fixed
> ReflectionSingleObjectSizer throws when sizing hidden classes
> -
>
> Key: GEODE-10133
> URL: https://issues.apache.org/jira/browse/GEODE-10133
> Project: Geode
> Issue Type: Improvement
> Components: core
>Reporter: Dale Emery
>Assignee: Darrel Schneider
>Priority: Major
> Labels: Java17, pull-request-available
> Fix For: 1.15.0
>
>
> On JDK 17, the class of a lambda is a "hidden" class. When
> {{ReflectionSingleObjectSizer}} tries to find the offset of the fields of a
> hidden class, the JDK throws {{UnsupportedOperationException}}.
> Tests that fail due to this exception:
> - {{MemoryOverheadIntegrationTest}}
> - {{OutOfMemoryDUnitTest}}
> - {{SessionReplicationLocalCacheJUnitTest}}
> Example exception from {{MemoryOverheadIntegrationTest}}:
> {noformat}
> ava.lang.UnsupportedOperationException: can't get field offset on a hidden
> class: private final org.apache.geode.internal.cache.InternalCache
> org.apache.geode.redis.internal.GeodeRedisServer$$Lambda$607/0x0008011434d8.arg$1
> at sun.misc.Unsafe.objectFieldOffset(Unsafe.java:645)
> at
> org.apache.geode.unsafe.internal.sun.misc.Unsafe.fieldOffset(Unsafe.java:187)
> at
> org.apache.geode.internal.size.ReflectionSingleObjectSizer.sizeof(ReflectionSingleObjectSizer.java:106)
> at
> org.apache.geode.internal.size.ReflectionSingleObjectSizer.sizeof(ReflectionSingleObjectSizer.java:84)
> at
> org.apache.geode.internal.size.ReflectionSingleObjectSizer.sizeof(ReflectionSingleObjectSizer.java:52)
> at
> org.apache.geode.internal.size.CachingSingleObjectSizer.sizeof(CachingSingleObjectSizer.java:39)
> at
> org.apache.geode.internal.size.ObjectGraphSizer$SizeVisitor.visit(ObjectGraphSizer.java:223)
> at
> org.apache.geode.internal.size.ObjectTraverser$VisitStack.add(ObjectTraverser.java:163)
> at
> org.apache.geode.internal.size.ObjectTraverser.doSearch(ObjectTraverser.java:87)
> at
> org.apache.geode.internal.size.ObjectTraverser.breadthFirstSearch(ObjectTraverser.java:54)
> at
> org.apache.geode.internal.size.ObjectGraphSizer.size(ObjectGraphSizer.java:96)
> at
> org.apache.geode.redis.internal.data.MemoryOverheadIntegrationTest.getUsedMemory(MemoryOverheadIntegrationTest.java:95)
> at
> org.apache.geode.redis.internal.data.AbstractMemoryOverheadIntegrationTest.measureAndCheckPerEntryOverhead(AbstractMemoryOverheadIntegrationTest.java:284)
> at
> org.apache.geode.redis.internal.data.AbstractMemoryOverheadIntegrationTest.measureOverheadPerHash(AbstractMemoryOverheadIntegrationTest.java:127)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
> at
> jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:568)
> 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.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at
> org.apache.geode.test.junit.rules.serializable.SerializableExternalResource$1.evaluate(SerializableExternalResource.java:38)
> 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.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:115)
> at
> org.junit.vintage.engine.execution.RunnerExecutor.
[jira] [Updated] (GEODE-10171) AbstractRedisData version being incremented for no-op operations can lead to delta not being applied on secondary
[
https://issues.apache.org/jira/browse/GEODE-10171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-10171:
---
Labels: blocks-1.15.0 pull-request-available (was: blocks-1.15.0)
> AbstractRedisData version being incremented for no-op operations can lead to
> delta not being applied on secondary
> -
>
> Key: GEODE-10171
> URL: https://issues.apache.org/jira/browse/GEODE-10171
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Priority: Major
> Labels: blocks-1.15.0, pull-request-available
>
> For SADD, which may or may not modify the data in the region depending on
> whether the member being added is already present in the set, the version in
> AbstractRedisData is updated regardless of whether a Delta is sent to the
> secondary. This can lead to the version on the primary wrapping around to be
> equal to the version on the secondary, which means that if a delta is sent,
> it will not be applied on the secondary, leading to potential data loss.
> Below is a test to show this behaviour:
> {code:java}
> @Test
> public void deltaVersionOnPrimary_shouldNotUpdate_ifNoDeltaSent() {
> String originalMember = "fixedMemberName";
> String key = clusterStartUp.getKeyOnServer("tag", 1);
>
> // Version of primary = 0
> // Version of secondary = 0
> jedis.sadd(key, originalMember);
> // No changes are made to the set, since adding an already existing member
> doesn't modify it
> // Version of primary wraps around back to -1
> // Version of secondary doesn't change because we don't send a delta
> for (int i = 0; i < 255; ++i) {
> jedis.sadd(key, originalMember);
> }
> String newMember = "aNewMemberName";
> // Version of primary = 0
> // Version of secondary = 0, delta is not applied
> jedis.sadd(key, newMember);
> assertThat(jedis.smembers(key)).containsExactlyInAnyOrder(originalMember,
> newMember);
> clusterStartUp.crashVM(1); // kill primary server
> assertThat(jedis.smembers(key)).containsExactlyInAnyOrder(originalMember,
> newMember);
> } {code}
> The example here uses SADD, but potentially, any command that can be a no-op
> and uses a versioned Delta is at risk of hitting this. All commands should be
> checked to ensure they're not vulnerable to this bug.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-10172) User Guide: Escape braces and angle brackets for format consistency
[
https://issues.apache.org/jira/browse/GEODE-10172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17512585#comment-17512585
]
ASF subversion and git services commented on GEODE-10172:
-
Commit 09ea8560b88770018f9bbee3a9403ac880bf8439 in geode's branch
refs/heads/develop from Dave Barnes
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=09ea856 ]
GEODE-10172: User Guide: Escape braces and angle brackets for format
consistency (#7495)
> User Guide: Escape braces and angle brackets for format consistency
> ---
>
> Key: GEODE-10172
> URL: https://issues.apache.org/jira/browse/GEODE-10172
> Project: Geode
> Issue Type: Improvement
> Components: docs
>Affects Versions: 1.14.4
>Reporter: Dave Barnes
>Assignee: Dave Barnes
>Priority: Major
> Labels: pull-request-available
>
> The REST Apps section contains expressions that make heavy use of braces {}
> and angle-brackets <>. Escape these chars for more consistent rendering by
> various formatting tools.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Resolved] (GEODE-10172) User Guide: Escape braces and angle brackets for format consistency
[
https://issues.apache.org/jira/browse/GEODE-10172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Barnes resolved GEODE-10172.
-
Fix Version/s: 1.15.0
Resolution: Fixed
> User Guide: Escape braces and angle brackets for format consistency
> ---
>
> Key: GEODE-10172
> URL: https://issues.apache.org/jira/browse/GEODE-10172
> Project: Geode
> Issue Type: Improvement
> Components: docs
>Affects Versions: 1.14.4
>Reporter: Dave Barnes
>Assignee: Dave Barnes
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> The REST Apps section contains expressions that make heavy use of braces {}
> and angle-brackets <>. Escape these chars for more consistent rendering by
> various formatting tools.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-10172) User Guide: Escape braces and angle brackets for format consistency
[
https://issues.apache.org/jira/browse/GEODE-10172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-10172:
---
Labels: pull-request-available (was: )
> User Guide: Escape braces and angle brackets for format consistency
> ---
>
> Key: GEODE-10172
> URL: https://issues.apache.org/jira/browse/GEODE-10172
> Project: Geode
> Issue Type: Improvement
> Components: docs
>Affects Versions: 1.14.4
>Reporter: Dave Barnes
>Assignee: Dave Barnes
>Priority: Major
> Labels: pull-request-available
>
> The REST Apps section contains expressions that make heavy use of braces {}
> and angle-brackets <>. Escape these chars for more consistent rendering by
> various formatting tools.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (GEODE-10172) User Guide: Escape braces and angle brackets for format consistency
[
https://issues.apache.org/jira/browse/GEODE-10172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Barnes reassigned GEODE-10172:
---
Assignee: Dave Barnes
> User Guide: Escape braces and angle brackets for format consistency
> ---
>
> Key: GEODE-10172
> URL: https://issues.apache.org/jira/browse/GEODE-10172
> Project: Geode
> Issue Type: Improvement
> Components: docs
>Affects Versions: 1.14.4
>Reporter: Dave Barnes
>Assignee: Dave Barnes
>Priority: Major
>
> The REST Apps section contains expressions that make heavy use of braces {}
> and angle-brackets <>. Escape these chars for more consistent rendering by
> various formatting tools.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (GEODE-10172) User Guide: Escape braces and angle brackets for format consistency
Dave Barnes created GEODE-10172:
---
Summary: User Guide: Escape braces and angle brackets for format
consistency
Key: GEODE-10172
URL: https://issues.apache.org/jira/browse/GEODE-10172
Project: Geode
Issue Type: Improvement
Reporter: Dave Barnes
The REST Apps section contains expressions that make heavy use of braces {} and
angle-brackets <>. Escape these chars for more consistent rendering by various
formatting tools.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-10172) User Guide: Escape braces and angle brackets for format consistency
[
https://issues.apache.org/jira/browse/GEODE-10172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Barnes updated GEODE-10172:
Affects Version/s: 1.14.4
> User Guide: Escape braces and angle brackets for format consistency
> ---
>
> Key: GEODE-10172
> URL: https://issues.apache.org/jira/browse/GEODE-10172
> Project: Geode
> Issue Type: Improvement
>Affects Versions: 1.14.4
>Reporter: Dave Barnes
>Priority: Major
>
> The REST Apps section contains expressions that make heavy use of braces {}
> and angle-brackets <>. Escape these chars for more consistent rendering by
> various formatting tools.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-10172) User Guide: Escape braces and angle brackets for format consistency
[
https://issues.apache.org/jira/browse/GEODE-10172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Barnes updated GEODE-10172:
Component/s: docs
> User Guide: Escape braces and angle brackets for format consistency
> ---
>
> Key: GEODE-10172
> URL: https://issues.apache.org/jira/browse/GEODE-10172
> Project: Geode
> Issue Type: Improvement
> Components: docs
>Affects Versions: 1.14.4
>Reporter: Dave Barnes
>Priority: Major
>
> The REST Apps section contains expressions that make heavy use of braces {}
> and angle-brackets <>. Escape these chars for more consistent rendering by
> various formatting tools.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-10151) Make geode-for-redis an optional dependency of a geode server
[ https://issues.apache.org/jira/browse/GEODE-10151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-10151: --- Labels: pull-request-available (was: ) > Make geode-for-redis an optional dependency of a geode server > - > > Key: GEODE-10151 > URL: https://issues.apache.org/jira/browse/GEODE-10151 > Project: Geode > Issue Type: Improvement > Components: redis >Reporter: Dan Smith >Assignee: Dan Smith >Priority: Major > Labels: pull-request-available > > The geode-for-redis module and its related dependencies are on the classpath > of the server by default when starting a server with gfsh start server or > using the geode dependencies jar. > We should make the module an optional dependencies, like some of our other > extensions (for example, the tomcat http session modules). This would allow a > user to choose if they want redis on the classpath or not. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-10151) Make geode-for-redis an optional dependency of a geode server
[ https://issues.apache.org/jira/browse/GEODE-10151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith reassigned GEODE-10151: - Assignee: Dan Smith > Make geode-for-redis an optional dependency of a geode server > - > > Key: GEODE-10151 > URL: https://issues.apache.org/jira/browse/GEODE-10151 > Project: Geode > Issue Type: Improvement > Components: redis >Reporter: Dan Smith >Assignee: Dan Smith >Priority: Major > > The geode-for-redis module and its related dependencies are on the classpath > of the server by default when starting a server with gfsh start server or > using the geode dependencies jar. > We should make the module an optional dependencies, like some of our other > extensions (for example, the tomcat http session modules). This would allow a > user to choose if they want redis on the classpath or not. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10155) ServerConnection thread hangs when client function execution times-out
[ https://issues.apache.org/jira/browse/GEODE-10155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-10155: --- Labels: needsTriage pull-request-available (was: needsTriage) > ServerConnection thread hangs when client function execution times-out > -- > > Key: GEODE-10155 > URL: https://issues.apache.org/jira/browse/GEODE-10155 > Project: Geode > Issue Type: Bug > Components: core, functions >Reporter: Alberto Gomez >Assignee: Alberto Gomez >Priority: Major > Labels: needsTriage, pull-request-available > > If a Geode client executes a server function with a timeout > and > the function is handled in the Geode server by a "Function Execution > Processor" thread (for example by calling the function with onRegion() on a > partitioned region without a filter) > and > the function times-out before the server has answered back with all the > results > then > the ServerConnection thread that originally started to handle the function > execution will be stuck forever. > > If this happens several times and the max-threads parameters is set to a > value greater than 0, the server will eventually run out of ServerConnection > threads and will not be able to process more client requests. > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10135) Redis Benchmarks
[ https://issues.apache.org/jira/browse/GEODE-10135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-10135: --- Labels: pull-request-available (was: ) > Redis Benchmarks > > > Key: GEODE-10135 > URL: https://issues.apache.org/jira/browse/GEODE-10135 > Project: Geode > Issue Type: Improvement > Components: redis >Reporter: Wayne >Priority: Major > Labels: pull-request-available > > Remove Redis benchmarks from the Geode benchmark job. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-8641) CI Failure: PartitionedIndexedQueryBenchmark.run
[
https://issues.apache.org/jira/browse/GEODE-8641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17512536#comment-17512536
]
Geode Integration commented on GEODE-8641:
--
Seen on support/1.14 in [benchmark-with-security-manager
#37|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-14-main/jobs/benchmark-with-security-manager/builds/37].
> CI Failure: PartitionedIndexedQueryBenchmark.run
>
>
> Key: GEODE-8641
> URL: https://issues.apache.org/jira/browse/GEODE-8641
> Project: Geode
> Issue Type: Test
> Components: benchmarks, tests
>Reporter: Jens Deppe
>Priority: Major
>
> Benchmarking looks like some internal error:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/Benchmark_base/builds/406
> {noformat}
> org.apache.geode.benchmark.tests.PartitionedIndexedQueryBenchmark > run()
> FAILED
> java.util.concurrent.CompletionException: java.lang.RuntimeException:
> java.rmi.UnmarshalException: Error unmarshaling return header; nested
> exception is:
> java.io.EOFException
> Caused by:
> java.lang.RuntimeException: java.rmi.UnmarshalException: Error
> unmarshaling return header; nested exception is:
> java.io.EOFException
> Caused by:
> java.rmi.UnmarshalException: Error unmarshaling return header;
> nested exception is:
> java.io.EOFException
> Caused by:
> java.io.EOFException
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Reopened] (GEODE-8641) CI Failure: PartitionedIndexedQueryBenchmark.run
[
https://issues.apache.org/jira/browse/GEODE-8641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jianxia Chen reopened GEODE-8641:
-
> CI Failure: PartitionedIndexedQueryBenchmark.run
>
>
> Key: GEODE-8641
> URL: https://issues.apache.org/jira/browse/GEODE-8641
> Project: Geode
> Issue Type: Test
> Components: benchmarks, tests
>Reporter: Jens Deppe
>Priority: Major
>
> Benchmarking looks like some internal error:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/Benchmark_base/builds/406
> {noformat}
> org.apache.geode.benchmark.tests.PartitionedIndexedQueryBenchmark > run()
> FAILED
> java.util.concurrent.CompletionException: java.lang.RuntimeException:
> java.rmi.UnmarshalException: Error unmarshaling return header; nested
> exception is:
> java.io.EOFException
> Caused by:
> java.lang.RuntimeException: java.rmi.UnmarshalException: Error
> unmarshaling return header; nested exception is:
> java.io.EOFException
> Caused by:
> java.rmi.UnmarshalException: Error unmarshaling return header;
> nested exception is:
> java.io.EOFException
> Caused by:
> java.io.EOFException
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-8641) CI Failure: PartitionedIndexedQueryBenchmark.run
[
https://issues.apache.org/jira/browse/GEODE-8641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17512535#comment-17512535
]
Jianxia Chen commented on GEODE-8641:
-
Failed again:
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-14-main/jobs/benchmark-with-security-manager/builds/37
> CI Failure: PartitionedIndexedQueryBenchmark.run
>
>
> Key: GEODE-8641
> URL: https://issues.apache.org/jira/browse/GEODE-8641
> Project: Geode
> Issue Type: Test
> Components: benchmarks, tests
>Reporter: Jens Deppe
>Priority: Major
>
> Benchmarking looks like some internal error:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/Benchmark_base/builds/406
> {noformat}
> org.apache.geode.benchmark.tests.PartitionedIndexedQueryBenchmark > run()
> FAILED
> java.util.concurrent.CompletionException: java.lang.RuntimeException:
> java.rmi.UnmarshalException: Error unmarshaling return header; nested
> exception is:
> java.io.EOFException
> Caused by:
> java.lang.RuntimeException: java.rmi.UnmarshalException: Error
> unmarshaling return header; nested exception is:
> java.io.EOFException
> Caused by:
> java.rmi.UnmarshalException: Error unmarshaling return header;
> nested exception is:
> java.io.EOFException
> Caused by:
> java.io.EOFException
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-10171) AbstractRedisData version being incremented for no-op operations can lead to delta not being applied on secondary
[
https://issues.apache.org/jira/browse/GEODE-10171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donal Evans updated GEODE-10171:
Description:
For SADD, which may or may not modify the data in the region depending on
whether the member being added is already present in the set, the version in
AbstractRedisData is updated regardless of whether a Delta is sent to the
secondary. This can lead to the version on the primary wrapping around to be
equal to the version on the secondary, which means that if a delta is sent, it
will not be applied on the secondary, leading to potential data loss.
Below is a test to show this behaviour:
{code:java}
@Test
public void deltaVersionOnPrimary_shouldNotUpdate_ifNoDeltaSent() {
String originalMember = "fixedMemberName";
String key = clusterStartUp.getKeyOnServer("tag", 1);
// Version of primary = 0
// Version of secondary = 0
jedis.sadd(key, originalMember);
// No changes are made to the set, since adding an already existing member
doesn't modify it
// Version of primary wraps around back to -1
// Version of secondary doesn't change because we don't send a delta
for (int i = 0; i < 255; ++i) {
jedis.sadd(key, originalMember);
}
String newMember = "aNewMemberName";
// Version of primary = 0
// Version of secondary = 0, delta is not applied
jedis.sadd(key, newMember);
assertThat(jedis.smembers(key)).containsExactlyInAnyOrder(originalMember,
newMember);
clusterStartUp.crashVM(1); // kill primary server
assertThat(jedis.smembers(key)).containsExactlyInAnyOrder(originalMember,
newMember);
} {code}
The example here uses SADD, but potentially, any command that can be a no-op
and uses a versioned Delta is at risk of hitting this. All commands should be
checked to ensure they're not vulnerable to this bug.
was:
For SADD, which may or may not modify the data in the region depending on
whether the member being added is already present in the set, the version in
AbstractRedisData is updated regardless of whether a Delta is sent to the
secondary. This can lead to the version on the primary wrapping around to be
equal to the version on the secondary, which means that if a delta is sent, it
will not be applied on the secondary, leading to potential data loss.
Below is a test to show this behaviour:
{code:java}
@Test
public void deltaVersionOnPrimary_shouldNotUpdate_ifNoDeltaSent() {
String originalMember = "fixedMemberName";
String key = clusterStartUp.getKeyOnServer("lrem", 1);
// Version of primary = 0
// Version of secondary = 0
jedis.sadd(key, originalMember);
// No changes are made to the set, since adding an already existing member
doesn't modify it
// Version of primary wraps around back to -1
// Version of secondary doesn't change because we don't send a delta
for (int i = 0; i < 255; ++i) {
jedis.sadd(key, originalMember);
}
String newMember = "aNewMemberName";
// Version of primary = 0
// Version of secondary = 0, delta is not applied
jedis.sadd(key, newMember);
assertThat(jedis.smembers(key)).containsExactlyInAnyOrder(originalMember,
newMember);
clusterStartUp.crashVM(1); // kill primary server
assertThat(jedis.smembers(key)).containsExactlyInAnyOrder(originalMember,
newMember);
} {code}
> AbstractRedisData version being incremented for no-op operations can lead to
> delta not being applied on secondary
> -
>
> Key: GEODE-10171
> URL: https://issues.apache.org/jira/browse/GEODE-10171
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Priority: Major
> Labels: blocks-1.15.0
>
> For SADD, which may or may not modify the data in the region depending on
> whether the member being added is already present in the set, the version in
> AbstractRedisData is updated regardless of whether a Delta is sent to the
> secondary. This can lead to the version on the primary wrapping around to be
> equal to the version on the secondary, which means that if a delta is sent,
> it will not be applied on the secondary, leading to potential data loss.
> Below is a test to show this behaviour:
> {code:java}
> @Test
> public void deltaVersionOnPrimary_shouldNotUpdate_ifNoDeltaSent() {
> String originalMember = "fixedMemberName";
> String key = clusterStartUp.getKeyOnServer("tag", 1);
>
> // Version of primary = 0
> // Version of secondary = 0
> jedis.sadd(key, originalMember);
> // No changes are made to the set, since adding an already existing member
> doesn't modify it
> // Version of primary wraps around back to -1
> // Version of secondary doesn't change because we don't send a delta
> for (int i = 0; i < 255; ++i) {
>
[jira] [Commented] (GEODE-9889) LettucePubSubIntegrationTest > subscribePsubscribeSameClient FAILED
[
https://issues.apache.org/jira/browse/GEODE-9889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17512528#comment-17512528
]
Geode Integration commented on GEODE-9889:
--
Seen on support/1.14 in [integration-test-openjdk11
#38|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-14-main/jobs/integration-test-openjdk11/builds/38]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.5-build.0941/test-results/integrationTest/1648228259/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.5-build.0941/test-artifacts/1648228259/integrationtestfiles-openjdk11-1.14.5-build.0941.tgz].
> LettucePubSubIntegrationTest > subscribePsubscribeSameClient FAILED
> ---
>
> Key: GEODE-9889
> URL: https://issues.apache.org/jira/browse/GEODE-9889
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.14.0
>Reporter: Ray Ingles
>Assignee: Hale Bales
>Priority: Major
>
> Seen in a CI build:
>
> {{> Task :geode-apis-compatible-with-redis:integrationTest}}
> {{org.apache.geode.redis.internal.executor.pubsub.LettucePubSubIntegrationTest
> > subscribePsubscribeSameClient FAILED}}
> {{org.junit.ComparisonFailure: expected:<[2]L> but was:<[0]L>}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Reopened] (GEODE-9889) LettucePubSubIntegrationTest > subscribePsubscribeSameClient FAILED
[
https://issues.apache.org/jira/browse/GEODE-9889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jianxia Chen reopened GEODE-9889:
-
Failed again
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-14-main/jobs/integration-test-openjdk11/builds/38
> LettucePubSubIntegrationTest > subscribePsubscribeSameClient FAILED
> ---
>
> Key: GEODE-9889
> URL: https://issues.apache.org/jira/browse/GEODE-9889
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.14.0
>Reporter: Ray Ingles
>Assignee: Hale Bales
>Priority: Major
>
> Seen in a CI build:
>
> {{> Task :geode-apis-compatible-with-redis:integrationTest}}
> {{org.apache.geode.redis.internal.executor.pubsub.LettucePubSubIntegrationTest
> > subscribePsubscribeSameClient FAILED}}
> {{org.junit.ComparisonFailure: expected:<[2]L> but was:<[0]L>}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-9889) LettucePubSubIntegrationTest > subscribePsubscribeSameClient FAILED
[
https://issues.apache.org/jira/browse/GEODE-9889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17512526#comment-17512526
]
Jianxia Chen commented on GEODE-9889:
-
Failed again at
[https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-14-main/jobs/integration-test-openjdk11/builds/38]
=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.5-build.0941/test-results/integrationTest/1648228259/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Test report artifacts from this job are available at:
http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.5-build.0941/test-artifacts/1648228259/integrationtestfiles-openjdk11-1.14.5-build.0941.tgz
> LettucePubSubIntegrationTest > subscribePsubscribeSameClient FAILED
> ---
>
> Key: GEODE-9889
> URL: https://issues.apache.org/jira/browse/GEODE-9889
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.14.0
>Reporter: Ray Ingles
>Assignee: Hale Bales
>Priority: Major
>
> Seen in a CI build:
>
> {{> Task :geode-apis-compatible-with-redis:integrationTest}}
> {{org.apache.geode.redis.internal.executor.pubsub.LettucePubSubIntegrationTest
> > subscribePsubscribeSameClient FAILED}}
> {{org.junit.ComparisonFailure: expected:<[2]L> but was:<[0]L>}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-10171) AbstractRedisData version being incremented for no-op operations can lead to delta not being applied on secondary
[
https://issues.apache.org/jira/browse/GEODE-10171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donal Evans updated GEODE-10171:
Labels: blocks-1.15.0 (was: needsTriage)
> AbstractRedisData version being incremented for no-op operations can lead to
> delta not being applied on secondary
> -
>
> Key: GEODE-10171
> URL: https://issues.apache.org/jira/browse/GEODE-10171
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Priority: Major
> Labels: blocks-1.15.0
>
> For SADD, which may or may not modify the data in the region depending on
> whether the member being added is already present in the set, the version in
> AbstractRedisData is updated regardless of whether a Delta is sent to the
> secondary. This can lead to the version on the primary wrapping around to be
> equal to the version on the secondary, which means that if a delta is sent,
> it will not be applied on the secondary, leading to potential data loss.
> Below is a test to show this behaviour:
> {code:java}
> @Test
> public void deltaVersionOnPrimary_shouldNotUpdate_ifNoDeltaSent() {
> String originalMember = "fixedMemberName";
> String key = clusterStartUp.getKeyOnServer("lrem", 1);
>
> // Version of primary = 0
> // Version of secondary = 0
> jedis.sadd(key, originalMember);
> // No changes are made to the set, since adding an already existing member
> doesn't modify it
> // Version of primary wraps around back to -1
> // Version of secondary doesn't change because we don't send a delta
> for (int i = 0; i < 255; ++i) {
> jedis.sadd(key, originalMember);
> }
> String newMember = "aNewMemberName";
> // Version of primary = 0
> // Version of secondary = 0, delta is not applied
> jedis.sadd(key, newMember);
> assertThat(jedis.smembers(key)).containsExactlyInAnyOrder(originalMember,
> newMember);
> clusterStartUp.crashVM(1); // kill primary server
> assertThat(jedis.smembers(key)).containsExactlyInAnyOrder(originalMember,
> newMember);
> } {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-10171) AbstractRedisData version being incremented for no-op operations can lead to delta not being applied on secondary
[
https://issues.apache.org/jira/browse/GEODE-10171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Murmann updated GEODE-10171:
--
Labels: needsTriage (was: )
> AbstractRedisData version being incremented for no-op operations can lead to
> delta not being applied on secondary
> -
>
> Key: GEODE-10171
> URL: https://issues.apache.org/jira/browse/GEODE-10171
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Priority: Major
> Labels: needsTriage
>
> For SADD, which may or may not modify the data in the region depending on
> whether the member being added is already present in the set, the version in
> AbstractRedisData is updated regardless of whether a Delta is sent to the
> secondary. This can lead to the version on the primary wrapping around to be
> equal to the version on the secondary, which means that if a delta is sent,
> it will not be applied on the secondary, leading to potential data loss.
> Below is a test to show this behaviour:
> {code:java}
> @Test
> public void deltaVersionOnPrimary_shouldNotUpdate_ifNoDeltaSent() {
> String originalMember = "fixedMemberName";
> String key = clusterStartUp.getKeyOnServer("lrem", 1);
>
> // Version of primary = 0
> // Version of secondary = 0
> jedis.sadd(key, originalMember);
> // No changes are made to the set, since adding an already existing member
> doesn't modify it
> // Version of primary wraps around back to -1
> // Version of secondary doesn't change because we don't send a delta
> for (int i = 0; i < 255; ++i) {
> jedis.sadd(key, originalMember);
> }
> String newMember = "aNewMemberName";
> // Version of primary = 0
> // Version of secondary = 0, delta is not applied
> jedis.sadd(key, newMember);
> assertThat(jedis.smembers(key)).containsExactlyInAnyOrder(originalMember,
> newMember);
> clusterStartUp.crashVM(1); // kill primary server
> assertThat(jedis.smembers(key)).containsExactlyInAnyOrder(originalMember,
> newMember);
> } {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (GEODE-10171) AbstractRedisData version being incremented for no-op operations can lead to delta not being applied on secondary
Donal Evans created GEODE-10171:
---
Summary: AbstractRedisData version being incremented for no-op
operations can lead to delta not being applied on secondary
Key: GEODE-10171
URL: https://issues.apache.org/jira/browse/GEODE-10171
Project: Geode
Issue Type: Bug
Components: redis
Affects Versions: 1.15.0
Reporter: Donal Evans
For SADD, which may or may not modify the data in the region depending on
whether the member being added is already present in the set, the version in
AbstractRedisData is updated regardless of whether a Delta is sent to the
secondary. This can lead to the version on the primary wrapping around to be
equal to the version on the secondary, which means that if a delta is sent, it
will not be applied on the secondary, leading to potential data loss.
Below is a test to show this behaviour:
{code:java}
@Test
public void deltaVersionOnPrimary_shouldNotUpdate_ifNoDeltaSent() {
String originalMember = "fixedMemberName";
String key = clusterStartUp.getKeyOnServer("lrem", 1);
// Version of primary = 0
// Version of secondary = 0
jedis.sadd(key, originalMember);
// No changes are made to the set, since adding an already existing member
doesn't modify it
// Version of primary wraps around back to -1
// Version of secondary doesn't change because we don't send a delta
for (int i = 0; i < 255; ++i) {
jedis.sadd(key, originalMember);
}
String newMember = "aNewMemberName";
// Version of primary = 0
// Version of secondary = 0, delta is not applied
jedis.sadd(key, newMember);
assertThat(jedis.smembers(key)).containsExactlyInAnyOrder(originalMember,
newMember);
clusterStartUp.crashVM(1); // kill primary server
assertThat(jedis.smembers(key)).containsExactlyInAnyOrder(originalMember,
newMember);
} {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Resolved] (GEODE-10164) Revert wording change in rebalance result
[
https://issues.apache.org/jira/browse/GEODE-10164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barrett Oglesby resolved GEODE-10164.
-
Fix Version/s: 1.12.10
1.13.9
1.14.5
1.15.0
Resolution: Fixed
> Revert wording change in rebalance result
> -
>
> Key: GEODE-10164
> URL: https://issues.apache.org/jira/browse/GEODE-10164
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Barrett Oglesby
>Assignee: Barrett Oglesby
>Priority: Major
> Labels: needsTriage, pull-request-available
> Fix For: 1.12.10, 1.13.9, 1.14.5, 1.15.0
>
>
> I made a change to the wording of the rebalance command result
> from:
> {noformat}
> Rebalanced partition regions {noformat}
> to:
> {noformat}
> Rebalanced partitioned region {noformat}
> This change caused hydra and other tests to fail, so I'm reverting it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-10170) CI failure: DistributedSystemBridgeIntegrationTest > testPrepareErrorAbortsBackup
[
https://issues.apache.org/jira/browse/GEODE-10170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17512520#comment-17512520
]
Jianxia Chen commented on GEODE-10170:
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1025/test-results/integrationTest/1648083972/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Test report artifacts from this job are available at:
http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1025/test-artifacts/1648083972/integrationtestfiles-openjdk8-1.15.0-build.1025.tgz
> CI failure: DistributedSystemBridgeIntegrationTest >
> testPrepareErrorAbortsBackup
> -
>
> Key: GEODE-10170
> URL: https://issues.apache.org/jira/browse/GEODE-10170
> Project: Geode
> Issue Type: Bug
>Reporter: Jianxia Chen
>Priority: Major
> Labels: needsTriage
>
> {code:java}
> DistributedSystemBridgeIntegrationTest > testPrepareErrorAbortsBackup FAILED
> java.lang.AssertionError:
> Expecting actual throwable to be an instance of:
> java.lang.RuntimeException
> but was:
> java.lang.NoClassDefFoundError: Could not initialize class
> org.apache.geode.internal.util.concurrent.StoppableCountDownLatch
> at
> org.apache.geode.distributed.internal.ReplyProcessor21.(ReplyProcessor21.java:333)
> at
> org.apache.geode.distributed.internal.ReplyProcessor21.(ReplyProcessor21.java:307)
> at
> org.apache.geode.distributed.internal.ReplyProcessor21.(ReplyProcessor21.java:264)
> ...(83 remaining lines not displayed - this can be changed with
> Assertions.setMaxStackTraceElementsDisplayed)
> at
> org.apache.geode.management.internal.beans.DistributedSystemBridgeIntegrationTest.testPrepareErrorAbortsBackup(DistributedSystemBridgeIntegrationTest.java:134)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (GEODE-10170) CI failure: DistributedSystemBridgeIntegrationTest > testPrepareErrorAbortsBackup
Jianxia Chen created GEODE-10170:
Summary: CI failure: DistributedSystemBridgeIntegrationTest >
testPrepareErrorAbortsBackup
Key: GEODE-10170
URL: https://issues.apache.org/jira/browse/GEODE-10170
Project: Geode
Issue Type: Bug
Reporter: Jianxia Chen
{code:java}
DistributedSystemBridgeIntegrationTest > testPrepareErrorAbortsBackup FAILED
java.lang.AssertionError:
Expecting actual throwable to be an instance of:
java.lang.RuntimeException
but was:
java.lang.NoClassDefFoundError: Could not initialize class
org.apache.geode.internal.util.concurrent.StoppableCountDownLatch
at
org.apache.geode.distributed.internal.ReplyProcessor21.(ReplyProcessor21.java:333)
at
org.apache.geode.distributed.internal.ReplyProcessor21.(ReplyProcessor21.java:307)
at
org.apache.geode.distributed.internal.ReplyProcessor21.(ReplyProcessor21.java:264)
...(83 remaining lines not displayed - this can be changed with
Assertions.setMaxStackTraceElementsDisplayed)
at
org.apache.geode.management.internal.beans.DistributedSystemBridgeIntegrationTest.testPrepareErrorAbortsBackup(DistributedSystemBridgeIntegrationTest.java:134)
{code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-10170) CI failure: DistributedSystemBridgeIntegrationTest > testPrepareErrorAbortsBackup
[
https://issues.apache.org/jira/browse/GEODE-10170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Murmann updated GEODE-10170:
--
Labels: needsTriage (was: )
> CI failure: DistributedSystemBridgeIntegrationTest >
> testPrepareErrorAbortsBackup
> -
>
> Key: GEODE-10170
> URL: https://issues.apache.org/jira/browse/GEODE-10170
> Project: Geode
> Issue Type: Bug
>Reporter: Jianxia Chen
>Priority: Major
> Labels: needsTriage
>
> {code:java}
> DistributedSystemBridgeIntegrationTest > testPrepareErrorAbortsBackup FAILED
> java.lang.AssertionError:
> Expecting actual throwable to be an instance of:
> java.lang.RuntimeException
> but was:
> java.lang.NoClassDefFoundError: Could not initialize class
> org.apache.geode.internal.util.concurrent.StoppableCountDownLatch
> at
> org.apache.geode.distributed.internal.ReplyProcessor21.(ReplyProcessor21.java:333)
> at
> org.apache.geode.distributed.internal.ReplyProcessor21.(ReplyProcessor21.java:307)
> at
> org.apache.geode.distributed.internal.ReplyProcessor21.(ReplyProcessor21.java:264)
> ...(83 remaining lines not displayed - this can be changed with
> Assertions.setMaxStackTraceElementsDisplayed)
> at
> org.apache.geode.management.internal.beans.DistributedSystemBridgeIntegrationTest.testPrepareErrorAbortsBackup(DistributedSystemBridgeIntegrationTest.java:134)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-10169) CI failure: DistributedSystemBridgeIntegrationTest > testSuccessfulBackup
[
https://issues.apache.org/jira/browse/GEODE-10169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17512521#comment-17512521
]
Geode Integration commented on GEODE-10169:
---
Seen in [integration-test-openjdk8
#236|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/integration-test-openjdk8/builds/236]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1025/test-results/integrationTest/1648083972/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1025/test-artifacts/1648083972/integrationtestfiles-openjdk8-1.15.0-build.1025.tgz].
> CI failure: DistributedSystemBridgeIntegrationTest > testSuccessfulBackup
> -
>
> Key: GEODE-10169
> URL: https://issues.apache.org/jira/browse/GEODE-10169
> Project: Geode
> Issue Type: Bug
>Reporter: Jianxia Chen
>Priority: Major
> Labels: needsTriage
>
> {code:java}
> DistributedSystemBridgeIntegrationTest > testSuccessfulBackup FAILED
> 17:57:56java.lang.ExceptionInInitializerError
> 17:57:56at
> java.util.concurrent.ConcurrentHashMap.fullAddCount(ConcurrentHashMap.java:2526)
> 17:57:56at
> java.util.concurrent.ConcurrentHashMap.addCount(ConcurrentHashMap.java:2266)
> 17:57:56at
> java.util.concurrent.ConcurrentHashMap.replaceNode(ConcurrentHashMap.java:1166)
> 17:57:56at
> java.util.concurrent.ConcurrentHashMap.remove(ConcurrentHashMap.java:1097)
> 17:57:56at
> org.mockito.internal.util.concurrent.WeakConcurrentMap.expungeStaleEntries(WeakConcurrentMap.java:139)
> 17:57:56at
> org.mockito.internal.util.concurrent.WeakConcurrentMap$WithInlinedExpunction.containsKey(WeakConcurrentMap.java:272)
> 17:57:56at
> org.mockito.internal.creation.bytebuddy.MockMethodAdvice.isMock(MockMethodAdvice.java:169)
> 17:57:56at
> org.mockito.internal.creation.bytebuddy.MockMethodAdvice.isMocked(MockMethodAdvice.java:174)
> 17:57:56at java.util.Properties.getProperty(Properties.java:969)
> 17:57:56at java.lang.System.getProperty(System.java:722)
> 17:57:56at java.lang.Long.getLong(Long.java:1208)
> 17:57:56at java.lang.Long.getLong(Long.java:1157)
> 17:57:56at
> org.apache.geode.internal.util.concurrent.StoppableCountDownLatch.(StoppableCountDownLatch.java:36)
> 17:57:56at
> org.apache.geode.distributed.internal.ReplyProcessor21.(ReplyProcessor21.java:333)
> 17:57:56at
> org.apache.geode.distributed.internal.ReplyProcessor21.(ReplyProcessor21.java:307)
> 17:57:56at
> org.apache.geode.distributed.internal.ReplyProcessor21.(ReplyProcessor21.java:264)
> 17:57:56at
> org.apache.geode.distributed.internal.ReplyProcessor21.(ReplyProcessor21.java:249)
> 17:57:56at
> org.apache.geode.internal.admin.remote.AdminMultipleReplyProcessor.(AdminMultipleReplyProcessor.java:32)
> 17:57:56at
> org.apache.geode.internal.admin.remote.MissingPersistentIDsRequest$MissingPersistentIDProcessor.(MissingPersistentIDsRequest.java:115)
> 17:57:56at
> org.apache.geode.internal.admin.remote.MissingPersistentIDsRequest$MissingPersistentIDProcessor.(MissingPersistentIDsRequest.java:108)
> 17:57:56at
> org.apache.geode.internal.admin.remote.MissingPersistentIDsRequest.send(MissingPersistentIDsRequest.java:55)
> 17:57:56at
> org.apache.geode.admin.internal.AdminDistributedSystemImpl.getMissingPersistentMembers(AdminDistributedSystemImpl.java:2226)
> 17:57:56at
> org.apache.geode.internal.cache.backup.BackupOperation$DefaultMissingPersistentMembersProvider.getMissingPersistentMembers(BackupOperation.java:147)
> 17:57:56at
> org.apache.geode.internal.cache.backup.BackupOperation.performBackupUnderLock(BackupOperation.java:89)
> 17:57:56at
> org.apache.geode.internal.cache.backup.BackupOperation.performBackup(BackupOperation.java:77)
> 17:57:56at
> org.apache.geode.internal.cache.backup.BackupOperation.backupAllMembers(BackupOperation.java:71)
> 17:57:56at
> org.apache.geode.management.internal.beans.DistributedSystemBridge.backupAllMembers(DistributedSystemBridge.java:489)
> 17:57:56at
> org.apache.geode.management.internal.beans.DistributedSystemBridgeIntegrationTest.testSuccessfulBackup(DistributedSystemBridgeIntegrationTest.java:113)
> 17:57:56
> 17:57:56Caused by:
> 17:57:56java.lang.NullPointerException
> 17:57:56at
> java.util.concurrent.ThreadLocalRandom.getProbe(ThreadLocalRandom.java:980)
> 17:57:56at
> java.util.concurrent.ConcurrentHashMap.fullAddCount(ConcurrentHashMap.java:2526)
> 17:57:56at
> java.util.concurrent.ConcurrentHashMap.addCoun
[jira] [Created] (GEODE-10169) CI failure: DistributedSystemBridgeIntegrationTest > testSuccessfulBackup
Jianxia Chen created GEODE-10169:
Summary: CI failure: DistributedSystemBridgeIntegrationTest >
testSuccessfulBackup
Key: GEODE-10169
URL: https://issues.apache.org/jira/browse/GEODE-10169
Project: Geode
Issue Type: Bug
Reporter: Jianxia Chen
{code:java}
DistributedSystemBridgeIntegrationTest > testSuccessfulBackup FAILED
17:57:56java.lang.ExceptionInInitializerError
17:57:56at
java.util.concurrent.ConcurrentHashMap.fullAddCount(ConcurrentHashMap.java:2526)
17:57:56at
java.util.concurrent.ConcurrentHashMap.addCount(ConcurrentHashMap.java:2266)
17:57:56at
java.util.concurrent.ConcurrentHashMap.replaceNode(ConcurrentHashMap.java:1166)
17:57:56at
java.util.concurrent.ConcurrentHashMap.remove(ConcurrentHashMap.java:1097)
17:57:56at
org.mockito.internal.util.concurrent.WeakConcurrentMap.expungeStaleEntries(WeakConcurrentMap.java:139)
17:57:56at
org.mockito.internal.util.concurrent.WeakConcurrentMap$WithInlinedExpunction.containsKey(WeakConcurrentMap.java:272)
17:57:56at
org.mockito.internal.creation.bytebuddy.MockMethodAdvice.isMock(MockMethodAdvice.java:169)
17:57:56at
org.mockito.internal.creation.bytebuddy.MockMethodAdvice.isMocked(MockMethodAdvice.java:174)
17:57:56at java.util.Properties.getProperty(Properties.java:969)
17:57:56at java.lang.System.getProperty(System.java:722)
17:57:56at java.lang.Long.getLong(Long.java:1208)
17:57:56at java.lang.Long.getLong(Long.java:1157)
17:57:56at
org.apache.geode.internal.util.concurrent.StoppableCountDownLatch.(StoppableCountDownLatch.java:36)
17:57:56at
org.apache.geode.distributed.internal.ReplyProcessor21.(ReplyProcessor21.java:333)
17:57:56at
org.apache.geode.distributed.internal.ReplyProcessor21.(ReplyProcessor21.java:307)
17:57:56at
org.apache.geode.distributed.internal.ReplyProcessor21.(ReplyProcessor21.java:264)
17:57:56at
org.apache.geode.distributed.internal.ReplyProcessor21.(ReplyProcessor21.java:249)
17:57:56at
org.apache.geode.internal.admin.remote.AdminMultipleReplyProcessor.(AdminMultipleReplyProcessor.java:32)
17:57:56at
org.apache.geode.internal.admin.remote.MissingPersistentIDsRequest$MissingPersistentIDProcessor.(MissingPersistentIDsRequest.java:115)
17:57:56at
org.apache.geode.internal.admin.remote.MissingPersistentIDsRequest$MissingPersistentIDProcessor.(MissingPersistentIDsRequest.java:108)
17:57:56at
org.apache.geode.internal.admin.remote.MissingPersistentIDsRequest.send(MissingPersistentIDsRequest.java:55)
17:57:56at
org.apache.geode.admin.internal.AdminDistributedSystemImpl.getMissingPersistentMembers(AdminDistributedSystemImpl.java:2226)
17:57:56at
org.apache.geode.internal.cache.backup.BackupOperation$DefaultMissingPersistentMembersProvider.getMissingPersistentMembers(BackupOperation.java:147)
17:57:56at
org.apache.geode.internal.cache.backup.BackupOperation.performBackupUnderLock(BackupOperation.java:89)
17:57:56at
org.apache.geode.internal.cache.backup.BackupOperation.performBackup(BackupOperation.java:77)
17:57:56at
org.apache.geode.internal.cache.backup.BackupOperation.backupAllMembers(BackupOperation.java:71)
17:57:56at
org.apache.geode.management.internal.beans.DistributedSystemBridge.backupAllMembers(DistributedSystemBridge.java:489)
17:57:56at
org.apache.geode.management.internal.beans.DistributedSystemBridgeIntegrationTest.testSuccessfulBackup(DistributedSystemBridgeIntegrationTest.java:113)
17:57:56
17:57:56Caused by:
17:57:56java.lang.NullPointerException
17:57:56at
java.util.concurrent.ThreadLocalRandom.getProbe(ThreadLocalRandom.java:980)
17:57:56at
java.util.concurrent.ConcurrentHashMap.fullAddCount(ConcurrentHashMap.java:2526)
17:57:56at
java.util.concurrent.ConcurrentHashMap.addCount(ConcurrentHashMap.java:2266)
17:57:56at
java.util.concurrent.ConcurrentHashMap.replaceNode(ConcurrentHashMap.java:1166)
17:57:56at
java.util.concurrent.ConcurrentHashMap.remove(ConcurrentHashMap.java:1097)
17:57:56at
org.mockito.internal.util.concurrent.WeakConcurrentMap.expungeStaleEntries(WeakConcurrentMap.java:139)
17:57:56at
org.mockito.internal.util.concurrent.WeakConcurrentMap$WithInlinedExpunction.containsKey(WeakConcurrentMap.java:272)
17:57:56at
org.mockito.internal.creation.bytebuddy.MockMethodAdvice.isMock(MockMethodAdvice.java:169)
17:57:56at
org.mockito.internal.creation.bytebuddy.MockMethodAdvice.isMocked(MockMethodAdvice.java:174)
17:57:56at java.util.Hashtable.isEmpty(Hashtable.java:245)
17:57:56at sun.misc.VM.getSavedProperty(VM.java:258)
17:57:56at
java.util.concurrent.ThreadLocalRandom.initia
[jira] [Commented] (GEODE-10169) CI failure: DistributedSystemBridgeIntegrationTest > testSuccessfulBackup
[
https://issues.apache.org/jira/browse/GEODE-10169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17512519#comment-17512519
]
Jianxia Chen commented on GEODE-10169:
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1025/test-results/integrationTest/1648083972/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Test report artifacts from this job are available at:
http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1025/test-artifacts/1648083972/integrationtestfiles-openjdk8-1.15.0-build.1025.tgz
> CI failure: DistributedSystemBridgeIntegrationTest > testSuccessfulBackup
> -
>
> Key: GEODE-10169
> URL: https://issues.apache.org/jira/browse/GEODE-10169
> Project: Geode
> Issue Type: Bug
>Reporter: Jianxia Chen
>Priority: Major
> Labels: needsTriage
>
> {code:java}
> DistributedSystemBridgeIntegrationTest > testSuccessfulBackup FAILED
> 17:57:56java.lang.ExceptionInInitializerError
> 17:57:56at
> java.util.concurrent.ConcurrentHashMap.fullAddCount(ConcurrentHashMap.java:2526)
> 17:57:56at
> java.util.concurrent.ConcurrentHashMap.addCount(ConcurrentHashMap.java:2266)
> 17:57:56at
> java.util.concurrent.ConcurrentHashMap.replaceNode(ConcurrentHashMap.java:1166)
> 17:57:56at
> java.util.concurrent.ConcurrentHashMap.remove(ConcurrentHashMap.java:1097)
> 17:57:56at
> org.mockito.internal.util.concurrent.WeakConcurrentMap.expungeStaleEntries(WeakConcurrentMap.java:139)
> 17:57:56at
> org.mockito.internal.util.concurrent.WeakConcurrentMap$WithInlinedExpunction.containsKey(WeakConcurrentMap.java:272)
> 17:57:56at
> org.mockito.internal.creation.bytebuddy.MockMethodAdvice.isMock(MockMethodAdvice.java:169)
> 17:57:56at
> org.mockito.internal.creation.bytebuddy.MockMethodAdvice.isMocked(MockMethodAdvice.java:174)
> 17:57:56at java.util.Properties.getProperty(Properties.java:969)
> 17:57:56at java.lang.System.getProperty(System.java:722)
> 17:57:56at java.lang.Long.getLong(Long.java:1208)
> 17:57:56at java.lang.Long.getLong(Long.java:1157)
> 17:57:56at
> org.apache.geode.internal.util.concurrent.StoppableCountDownLatch.(StoppableCountDownLatch.java:36)
> 17:57:56at
> org.apache.geode.distributed.internal.ReplyProcessor21.(ReplyProcessor21.java:333)
> 17:57:56at
> org.apache.geode.distributed.internal.ReplyProcessor21.(ReplyProcessor21.java:307)
> 17:57:56at
> org.apache.geode.distributed.internal.ReplyProcessor21.(ReplyProcessor21.java:264)
> 17:57:56at
> org.apache.geode.distributed.internal.ReplyProcessor21.(ReplyProcessor21.java:249)
> 17:57:56at
> org.apache.geode.internal.admin.remote.AdminMultipleReplyProcessor.(AdminMultipleReplyProcessor.java:32)
> 17:57:56at
> org.apache.geode.internal.admin.remote.MissingPersistentIDsRequest$MissingPersistentIDProcessor.(MissingPersistentIDsRequest.java:115)
> 17:57:56at
> org.apache.geode.internal.admin.remote.MissingPersistentIDsRequest$MissingPersistentIDProcessor.(MissingPersistentIDsRequest.java:108)
> 17:57:56at
> org.apache.geode.internal.admin.remote.MissingPersistentIDsRequest.send(MissingPersistentIDsRequest.java:55)
> 17:57:56at
> org.apache.geode.admin.internal.AdminDistributedSystemImpl.getMissingPersistentMembers(AdminDistributedSystemImpl.java:2226)
> 17:57:56at
> org.apache.geode.internal.cache.backup.BackupOperation$DefaultMissingPersistentMembersProvider.getMissingPersistentMembers(BackupOperation.java:147)
> 17:57:56at
> org.apache.geode.internal.cache.backup.BackupOperation.performBackupUnderLock(BackupOperation.java:89)
> 17:57:56at
> org.apache.geode.internal.cache.backup.BackupOperation.performBackup(BackupOperation.java:77)
> 17:57:56at
> org.apache.geode.internal.cache.backup.BackupOperation.backupAllMembers(BackupOperation.java:71)
> 17:57:56at
> org.apache.geode.management.internal.beans.DistributedSystemBridge.backupAllMembers(DistributedSystemBridge.java:489)
> 17:57:56at
> org.apache.geode.management.internal.beans.DistributedSystemBridgeIntegrationTest.testSuccessfulBackup(DistributedSystemBridgeIntegrationTest.java:113)
> 17:57:56
> 17:57:56Caused by:
> 17:57:56java.lang.NullPointerException
> 17:57:56at
> java.util.concurrent.ThreadLocalRandom.getProbe(ThreadLocalRandom.java:980)
> 17:57:56at
> java.util.concurrent.ConcurrentHashMap.fullAddCount(ConcurrentHashMap.java:2526)
> 17:57:56at
> java.util.concurrent.ConcurrentHashMap.addCount(Co
[jira] [Updated] (GEODE-10169) CI failure: DistributedSystemBridgeIntegrationTest > testSuccessfulBackup
[
https://issues.apache.org/jira/browse/GEODE-10169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Murmann updated GEODE-10169:
--
Labels: needsTriage (was: )
> CI failure: DistributedSystemBridgeIntegrationTest > testSuccessfulBackup
> -
>
> Key: GEODE-10169
> URL: https://issues.apache.org/jira/browse/GEODE-10169
> Project: Geode
> Issue Type: Bug
>Reporter: Jianxia Chen
>Priority: Major
> Labels: needsTriage
>
> {code:java}
> DistributedSystemBridgeIntegrationTest > testSuccessfulBackup FAILED
> 17:57:56java.lang.ExceptionInInitializerError
> 17:57:56at
> java.util.concurrent.ConcurrentHashMap.fullAddCount(ConcurrentHashMap.java:2526)
> 17:57:56at
> java.util.concurrent.ConcurrentHashMap.addCount(ConcurrentHashMap.java:2266)
> 17:57:56at
> java.util.concurrent.ConcurrentHashMap.replaceNode(ConcurrentHashMap.java:1166)
> 17:57:56at
> java.util.concurrent.ConcurrentHashMap.remove(ConcurrentHashMap.java:1097)
> 17:57:56at
> org.mockito.internal.util.concurrent.WeakConcurrentMap.expungeStaleEntries(WeakConcurrentMap.java:139)
> 17:57:56at
> org.mockito.internal.util.concurrent.WeakConcurrentMap$WithInlinedExpunction.containsKey(WeakConcurrentMap.java:272)
> 17:57:56at
> org.mockito.internal.creation.bytebuddy.MockMethodAdvice.isMock(MockMethodAdvice.java:169)
> 17:57:56at
> org.mockito.internal.creation.bytebuddy.MockMethodAdvice.isMocked(MockMethodAdvice.java:174)
> 17:57:56at java.util.Properties.getProperty(Properties.java:969)
> 17:57:56at java.lang.System.getProperty(System.java:722)
> 17:57:56at java.lang.Long.getLong(Long.java:1208)
> 17:57:56at java.lang.Long.getLong(Long.java:1157)
> 17:57:56at
> org.apache.geode.internal.util.concurrent.StoppableCountDownLatch.(StoppableCountDownLatch.java:36)
> 17:57:56at
> org.apache.geode.distributed.internal.ReplyProcessor21.(ReplyProcessor21.java:333)
> 17:57:56at
> org.apache.geode.distributed.internal.ReplyProcessor21.(ReplyProcessor21.java:307)
> 17:57:56at
> org.apache.geode.distributed.internal.ReplyProcessor21.(ReplyProcessor21.java:264)
> 17:57:56at
> org.apache.geode.distributed.internal.ReplyProcessor21.(ReplyProcessor21.java:249)
> 17:57:56at
> org.apache.geode.internal.admin.remote.AdminMultipleReplyProcessor.(AdminMultipleReplyProcessor.java:32)
> 17:57:56at
> org.apache.geode.internal.admin.remote.MissingPersistentIDsRequest$MissingPersistentIDProcessor.(MissingPersistentIDsRequest.java:115)
> 17:57:56at
> org.apache.geode.internal.admin.remote.MissingPersistentIDsRequest$MissingPersistentIDProcessor.(MissingPersistentIDsRequest.java:108)
> 17:57:56at
> org.apache.geode.internal.admin.remote.MissingPersistentIDsRequest.send(MissingPersistentIDsRequest.java:55)
> 17:57:56at
> org.apache.geode.admin.internal.AdminDistributedSystemImpl.getMissingPersistentMembers(AdminDistributedSystemImpl.java:2226)
> 17:57:56at
> org.apache.geode.internal.cache.backup.BackupOperation$DefaultMissingPersistentMembersProvider.getMissingPersistentMembers(BackupOperation.java:147)
> 17:57:56at
> org.apache.geode.internal.cache.backup.BackupOperation.performBackupUnderLock(BackupOperation.java:89)
> 17:57:56at
> org.apache.geode.internal.cache.backup.BackupOperation.performBackup(BackupOperation.java:77)
> 17:57:56at
> org.apache.geode.internal.cache.backup.BackupOperation.backupAllMembers(BackupOperation.java:71)
> 17:57:56at
> org.apache.geode.management.internal.beans.DistributedSystemBridge.backupAllMembers(DistributedSystemBridge.java:489)
> 17:57:56at
> org.apache.geode.management.internal.beans.DistributedSystemBridgeIntegrationTest.testSuccessfulBackup(DistributedSystemBridgeIntegrationTest.java:113)
> 17:57:56
> 17:57:56Caused by:
> 17:57:56java.lang.NullPointerException
> 17:57:56at
> java.util.concurrent.ThreadLocalRandom.getProbe(ThreadLocalRandom.java:980)
> 17:57:56at
> java.util.concurrent.ConcurrentHashMap.fullAddCount(ConcurrentHashMap.java:2526)
> 17:57:56at
> java.util.concurrent.ConcurrentHashMap.addCount(ConcurrentHashMap.java:2266)
> 17:57:56at
> java.util.concurrent.ConcurrentHashMap.replaceNode(ConcurrentHashMap.java:1166)
> 17:57:56at
> java.util.concurrent.ConcurrentHashMap.remove(ConcurrentHashMap.java:1097)
> 17:57:56at
> org.mockito.internal.util.concurrent.WeakConcurrentMap.expungeStaleEntries(WeakConcurrentMap.java:139)
> 17:57:56at
> org.mockito.internal.util.concurrent.WeakConcurrentMap$WithInlinedExpunction.containsKey(WeakConcurrentMap.java:27
[jira] [Commented] (GEODE-10168) CI failure: RestAPICompatibilityTest > restCommandExecutedOnLatestLocatorShouldBeBackwardsCompatible
[
https://issues.apache.org/jira/browse/GEODE-10168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17512515#comment-17512515
]
Geode Integration commented on GEODE-10168:
---
Seen in [upgrade-test-openjdk11
#229|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/upgrade-test-openjdk11/builds/229]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1027/test-results/upgradeTest/1648161810/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1027/test-artifacts/1648161810/upgradetestfiles-openjdk11-1.15.0-build.1027.tgz].
> CI failure: RestAPICompatibilityTest >
> restCommandExecutedOnLatestLocatorShouldBeBackwardsCompatible
>
>
> Key: GEODE-10168
> URL: https://issues.apache.org/jira/browse/GEODE-10168
> Project: Geode
> Issue Type: Bug
>Reporter: Jianxia Chen
>Priority: Major
> Labels: needsTriage
>
> {code:java}
> RestAPICompatibilityTest >
> restCommandExecutedOnLatestLocatorShouldBeBackwardsCompatible[1.13.0] FAILED
> 13:12:20java.lang.AssertionError: Suspicious strings were written to the
> log during this run.
> 13:12:20Fix the strings or use IgnoredException.addIgnoredException to
> ignore.
> 13:12:20
> ---
> 13:12:20Found suspect string in 'dunit_suspect-vm1.log' at line 511
> 13:12:20
> 13:12:20[fatal 2022/03/24 20:11:53.071 UTC receiver,heavy-lifter-8ca77d83-23cd-5773-ab23-a0729142416f-17781> tid=55]
> Membership service failure: Member isn't responding to heartbeat requests
> 13:12:20
> org.apache.geode.distributed.internal.membership.api.MemberDisconnectedException:
> Member isn't responding to heartbeat requests
> 13:12:20 at
> org.apache.geode.distributed.internal.membership.gms.GMSMembership$ManagerImpl.forceDisconnect(GMSMembership.java:2012)
> 13:12:20 at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.forceDisconnect(GMSJoinLeave.java:1085)
> 13:12:20 at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.processMessage(GMSJoinLeave.java:688)
> 13:12:20 at
> org.apache.geode.distributed.internal.membership.gms.messenger.JGroupsMessenger$JGroupsReceiver.receive(JGroupsMessenger.java:1331)
> 13:12:20 at
> org.apache.geode.distributed.internal.membership.gms.messenger.JGroupsMessenger$JGroupsReceiver.receive(JGroupsMessenger.java:1267)
> 13:12:20 at org.jgroups.JChannel.invokeCallback(JChannel.java:816)
> 13:12:20 at org.jgroups.JChannel.up(JChannel.java:741)
> 13:12:20 at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:1030)
> 13:12:20 at org.jgroups.protocols.FRAG2.up(FRAG2.java:165)
> 13:12:20 at org.jgroups.protocols.FlowControl.up(FlowControl.java:390)
> 13:12:20 at
> org.jgroups.protocols.UNICAST3.deliverMessage(UNICAST3.java:1077)
> 13:12:20 at
> org.jgroups.protocols.UNICAST3.handleDataReceived(UNICAST3.java:792)
> 13:12:20 at org.jgroups.protocols.UNICAST3.up(UNICAST3.java:433)
> 13:12:20 at
> org.apache.geode.distributed.internal.membership.gms.messenger.StatRecorder.up(StatRecorder.java:72)
> 13:12:20 at
> org.apache.geode.distributed.internal.membership.gms.messenger.AddressManager.up(AddressManager.java:70)
> 13:12:20 at org.jgroups.protocols.TP.passMessageUp(TP.java:1658)
> 13:12:20 at
> org.jgroups.protocols.TP$SingleMessageHandler.run(TP.java:1876)
> 13:12:20 at
> org.jgroups.util.DirectExecutor.execute(DirectExecutor.java:10)
> 13:12:20 at org.jgroups.protocols.TP.handleSingleMessage(TP.java:1789)
> 13:12:20 at org.jgroups.protocols.TP.receive(TP.java:1714)
> 13:12:20 at
> org.apache.geode.distributed.internal.membership.gms.messenger.Transport.receive(Transport.java:159)
> 13:12:20 at org.jgroups.protocols.UDP$PacketReceiver.run(UDP.java:701)
> 13:12:20 at java.base/java.lang.Thread.run(Thread.java:829)
> 13:12:20at org.junit.Assert.fail(Assert.java:89)
> 13:12:20at
> org.apache.geode.test.dunit.internal.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:422)
> 13:12:20at
> org.apache.geode.test.dunit.internal.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:438)
> 13:12:20at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.after(ClusterStartupRule.java:183)
> 13:12:20at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.access$100(ClusterStartupRule.java:70)
> 13:12:20at
> org.apache.geode.test.dunit.rules.ClusterStartupRule$1.evaluate(ClusterStartupRule.java:141)
> 13:12:20at
> org.apache.geode.test.j
[jira] [Commented] (GEODE-10168) CI failure: RestAPICompatibilityTest > restCommandExecutedOnLatestLocatorShouldBeBackwardsCompatible
[
https://issues.apache.org/jira/browse/GEODE-10168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17512514#comment-17512514
]
Jianxia Chen commented on GEODE-10168:
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1027/test-results/upgradeTest/1648161810/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Test report artifacts from this job are available at:
http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1027/test-artifacts/1648161810/upgradetestfiles-openjdk11-1.15.0-build.1027.tgz
> CI failure: RestAPICompatibilityTest >
> restCommandExecutedOnLatestLocatorShouldBeBackwardsCompatible
>
>
> Key: GEODE-10168
> URL: https://issues.apache.org/jira/browse/GEODE-10168
> Project: Geode
> Issue Type: Bug
>Reporter: Jianxia Chen
>Priority: Major
> Labels: needsTriage
>
> {code:java}
> RestAPICompatibilityTest >
> restCommandExecutedOnLatestLocatorShouldBeBackwardsCompatible[1.13.0] FAILED
> 13:12:20java.lang.AssertionError: Suspicious strings were written to the
> log during this run.
> 13:12:20Fix the strings or use IgnoredException.addIgnoredException to
> ignore.
> 13:12:20
> ---
> 13:12:20Found suspect string in 'dunit_suspect-vm1.log' at line 511
> 13:12:20
> 13:12:20[fatal 2022/03/24 20:11:53.071 UTC receiver,heavy-lifter-8ca77d83-23cd-5773-ab23-a0729142416f-17781> tid=55]
> Membership service failure: Member isn't responding to heartbeat requests
> 13:12:20
> org.apache.geode.distributed.internal.membership.api.MemberDisconnectedException:
> Member isn't responding to heartbeat requests
> 13:12:20 at
> org.apache.geode.distributed.internal.membership.gms.GMSMembership$ManagerImpl.forceDisconnect(GMSMembership.java:2012)
> 13:12:20 at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.forceDisconnect(GMSJoinLeave.java:1085)
> 13:12:20 at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.processMessage(GMSJoinLeave.java:688)
> 13:12:20 at
> org.apache.geode.distributed.internal.membership.gms.messenger.JGroupsMessenger$JGroupsReceiver.receive(JGroupsMessenger.java:1331)
> 13:12:20 at
> org.apache.geode.distributed.internal.membership.gms.messenger.JGroupsMessenger$JGroupsReceiver.receive(JGroupsMessenger.java:1267)
> 13:12:20 at org.jgroups.JChannel.invokeCallback(JChannel.java:816)
> 13:12:20 at org.jgroups.JChannel.up(JChannel.java:741)
> 13:12:20 at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:1030)
> 13:12:20 at org.jgroups.protocols.FRAG2.up(FRAG2.java:165)
> 13:12:20 at org.jgroups.protocols.FlowControl.up(FlowControl.java:390)
> 13:12:20 at
> org.jgroups.protocols.UNICAST3.deliverMessage(UNICAST3.java:1077)
> 13:12:20 at
> org.jgroups.protocols.UNICAST3.handleDataReceived(UNICAST3.java:792)
> 13:12:20 at org.jgroups.protocols.UNICAST3.up(UNICAST3.java:433)
> 13:12:20 at
> org.apache.geode.distributed.internal.membership.gms.messenger.StatRecorder.up(StatRecorder.java:72)
> 13:12:20 at
> org.apache.geode.distributed.internal.membership.gms.messenger.AddressManager.up(AddressManager.java:70)
> 13:12:20 at org.jgroups.protocols.TP.passMessageUp(TP.java:1658)
> 13:12:20 at
> org.jgroups.protocols.TP$SingleMessageHandler.run(TP.java:1876)
> 13:12:20 at
> org.jgroups.util.DirectExecutor.execute(DirectExecutor.java:10)
> 13:12:20 at org.jgroups.protocols.TP.handleSingleMessage(TP.java:1789)
> 13:12:20 at org.jgroups.protocols.TP.receive(TP.java:1714)
> 13:12:20 at
> org.apache.geode.distributed.internal.membership.gms.messenger.Transport.receive(Transport.java:159)
> 13:12:20 at org.jgroups.protocols.UDP$PacketReceiver.run(UDP.java:701)
> 13:12:20 at java.base/java.lang.Thread.run(Thread.java:829)
> 13:12:20at org.junit.Assert.fail(Assert.java:89)
> 13:12:20at
> org.apache.geode.test.dunit.internal.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:422)
> 13:12:20at
> org.apache.geode.test.dunit.internal.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:438)
> 13:12:20at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.after(ClusterStartupRule.java:183)
> 13:12:20at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.access$100(ClusterStartupRule.java:70)
> 13:12:20at
> org.apache.geode.test.dunit.rules.ClusterStartupRule$1.evaluate(ClusterStartupRule.java:141)
> 13:12:20at
> org.apache.geode.test
[jira] [Updated] (GEODE-10168) CI failure: RestAPICompatibilityTest > restCommandExecutedOnLatestLocatorShouldBeBackwardsCompatible
[
https://issues.apache.org/jira/browse/GEODE-10168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Murmann updated GEODE-10168:
--
Labels: needsTriage (was: )
> CI failure: RestAPICompatibilityTest >
> restCommandExecutedOnLatestLocatorShouldBeBackwardsCompatible
>
>
> Key: GEODE-10168
> URL: https://issues.apache.org/jira/browse/GEODE-10168
> Project: Geode
> Issue Type: Bug
>Reporter: Jianxia Chen
>Priority: Major
> Labels: needsTriage
>
> {code:java}
> RestAPICompatibilityTest >
> restCommandExecutedOnLatestLocatorShouldBeBackwardsCompatible[1.13.0] FAILED
> 13:12:20java.lang.AssertionError: Suspicious strings were written to the
> log during this run.
> 13:12:20Fix the strings or use IgnoredException.addIgnoredException to
> ignore.
> 13:12:20
> ---
> 13:12:20Found suspect string in 'dunit_suspect-vm1.log' at line 511
> 13:12:20
> 13:12:20[fatal 2022/03/24 20:11:53.071 UTC receiver,heavy-lifter-8ca77d83-23cd-5773-ab23-a0729142416f-17781> tid=55]
> Membership service failure: Member isn't responding to heartbeat requests
> 13:12:20
> org.apache.geode.distributed.internal.membership.api.MemberDisconnectedException:
> Member isn't responding to heartbeat requests
> 13:12:20 at
> org.apache.geode.distributed.internal.membership.gms.GMSMembership$ManagerImpl.forceDisconnect(GMSMembership.java:2012)
> 13:12:20 at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.forceDisconnect(GMSJoinLeave.java:1085)
> 13:12:20 at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.processMessage(GMSJoinLeave.java:688)
> 13:12:20 at
> org.apache.geode.distributed.internal.membership.gms.messenger.JGroupsMessenger$JGroupsReceiver.receive(JGroupsMessenger.java:1331)
> 13:12:20 at
> org.apache.geode.distributed.internal.membership.gms.messenger.JGroupsMessenger$JGroupsReceiver.receive(JGroupsMessenger.java:1267)
> 13:12:20 at org.jgroups.JChannel.invokeCallback(JChannel.java:816)
> 13:12:20 at org.jgroups.JChannel.up(JChannel.java:741)
> 13:12:20 at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:1030)
> 13:12:20 at org.jgroups.protocols.FRAG2.up(FRAG2.java:165)
> 13:12:20 at org.jgroups.protocols.FlowControl.up(FlowControl.java:390)
> 13:12:20 at
> org.jgroups.protocols.UNICAST3.deliverMessage(UNICAST3.java:1077)
> 13:12:20 at
> org.jgroups.protocols.UNICAST3.handleDataReceived(UNICAST3.java:792)
> 13:12:20 at org.jgroups.protocols.UNICAST3.up(UNICAST3.java:433)
> 13:12:20 at
> org.apache.geode.distributed.internal.membership.gms.messenger.StatRecorder.up(StatRecorder.java:72)
> 13:12:20 at
> org.apache.geode.distributed.internal.membership.gms.messenger.AddressManager.up(AddressManager.java:70)
> 13:12:20 at org.jgroups.protocols.TP.passMessageUp(TP.java:1658)
> 13:12:20 at
> org.jgroups.protocols.TP$SingleMessageHandler.run(TP.java:1876)
> 13:12:20 at
> org.jgroups.util.DirectExecutor.execute(DirectExecutor.java:10)
> 13:12:20 at org.jgroups.protocols.TP.handleSingleMessage(TP.java:1789)
> 13:12:20 at org.jgroups.protocols.TP.receive(TP.java:1714)
> 13:12:20 at
> org.apache.geode.distributed.internal.membership.gms.messenger.Transport.receive(Transport.java:159)
> 13:12:20 at org.jgroups.protocols.UDP$PacketReceiver.run(UDP.java:701)
> 13:12:20 at java.base/java.lang.Thread.run(Thread.java:829)
> 13:12:20at org.junit.Assert.fail(Assert.java:89)
> 13:12:20at
> org.apache.geode.test.dunit.internal.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:422)
> 13:12:20at
> org.apache.geode.test.dunit.internal.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:438)
> 13:12:20at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.after(ClusterStartupRule.java:183)
> 13:12:20at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.access$100(ClusterStartupRule.java:70)
> 13:12:20at
> org.apache.geode.test.dunit.rules.ClusterStartupRule$1.evaluate(ClusterStartupRule.java:141)
> 13:12:20at
> org.apache.geode.test.junit.rules.DescribedExternalResource$1.evaluate(DescribedExternalResource.java:40)
> 13:12:20at
> org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> 13:12:20at
> org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
> 13:12:20at
> org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
> 13:12:20at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
> 13:12:20at
> org.
[jira] [Created] (GEODE-10168) CI failure: RestAPICompatibilityTest > restCommandExecutedOnLatestLocatorShouldBeBackwardsCompatible
Jianxia Chen created GEODE-10168:
Summary: CI failure: RestAPICompatibilityTest >
restCommandExecutedOnLatestLocatorShouldBeBackwardsCompatible
Key: GEODE-10168
URL: https://issues.apache.org/jira/browse/GEODE-10168
Project: Geode
Issue Type: Bug
Reporter: Jianxia Chen
{code:java}
RestAPICompatibilityTest >
restCommandExecutedOnLatestLocatorShouldBeBackwardsCompatible[1.13.0] FAILED
13:12:20java.lang.AssertionError: Suspicious strings were written to the
log during this run.
13:12:20Fix the strings or use IgnoredException.addIgnoredException to
ignore.
13:12:20
---
13:12:20Found suspect string in 'dunit_suspect-vm1.log' at line 511
13:12:20
13:12:20[fatal 2022/03/24 20:11:53.071 UTC tid=55]
Membership service failure: Member isn't responding to heartbeat requests
13:12:20
org.apache.geode.distributed.internal.membership.api.MemberDisconnectedException:
Member isn't responding to heartbeat requests
13:12:20at
org.apache.geode.distributed.internal.membership.gms.GMSMembership$ManagerImpl.forceDisconnect(GMSMembership.java:2012)
13:12:20at
org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.forceDisconnect(GMSJoinLeave.java:1085)
13:12:20at
org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.processMessage(GMSJoinLeave.java:688)
13:12:20at
org.apache.geode.distributed.internal.membership.gms.messenger.JGroupsMessenger$JGroupsReceiver.receive(JGroupsMessenger.java:1331)
13:12:20at
org.apache.geode.distributed.internal.membership.gms.messenger.JGroupsMessenger$JGroupsReceiver.receive(JGroupsMessenger.java:1267)
13:12:20at org.jgroups.JChannel.invokeCallback(JChannel.java:816)
13:12:20at org.jgroups.JChannel.up(JChannel.java:741)
13:12:20at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:1030)
13:12:20at org.jgroups.protocols.FRAG2.up(FRAG2.java:165)
13:12:20at org.jgroups.protocols.FlowControl.up(FlowControl.java:390)
13:12:20at
org.jgroups.protocols.UNICAST3.deliverMessage(UNICAST3.java:1077)
13:12:20at
org.jgroups.protocols.UNICAST3.handleDataReceived(UNICAST3.java:792)
13:12:20at org.jgroups.protocols.UNICAST3.up(UNICAST3.java:433)
13:12:20at
org.apache.geode.distributed.internal.membership.gms.messenger.StatRecorder.up(StatRecorder.java:72)
13:12:20at
org.apache.geode.distributed.internal.membership.gms.messenger.AddressManager.up(AddressManager.java:70)
13:12:20at org.jgroups.protocols.TP.passMessageUp(TP.java:1658)
13:12:20at
org.jgroups.protocols.TP$SingleMessageHandler.run(TP.java:1876)
13:12:20at
org.jgroups.util.DirectExecutor.execute(DirectExecutor.java:10)
13:12:20at org.jgroups.protocols.TP.handleSingleMessage(TP.java:1789)
13:12:20at org.jgroups.protocols.TP.receive(TP.java:1714)
13:12:20at
org.apache.geode.distributed.internal.membership.gms.messenger.Transport.receive(Transport.java:159)
13:12:20at org.jgroups.protocols.UDP$PacketReceiver.run(UDP.java:701)
13:12:20at java.base/java.lang.Thread.run(Thread.java:829)
13:12:20at org.junit.Assert.fail(Assert.java:89)
13:12:20at
org.apache.geode.test.dunit.internal.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:422)
13:12:20at
org.apache.geode.test.dunit.internal.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:438)
13:12:20at
org.apache.geode.test.dunit.rules.ClusterStartupRule.after(ClusterStartupRule.java:183)
13:12:20at
org.apache.geode.test.dunit.rules.ClusterStartupRule.access$100(ClusterStartupRule.java:70)
13:12:20at
org.apache.geode.test.dunit.rules.ClusterStartupRule$1.evaluate(ClusterStartupRule.java:141)
13:12:20at
org.apache.geode.test.junit.rules.DescribedExternalResource$1.evaluate(DescribedExternalResource.java:40)
13:12:20at
org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
13:12:20at
org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
13:12:20at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
13:12:20at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
13:12:20at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
13:12:20at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
13:12:20at
org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
13:12:20at
org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
13:12:20at
org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
13:12:20at
org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
[jira] [Commented] (GEODE-10164) Revert wording change in rebalance result
[
https://issues.apache.org/jira/browse/GEODE-10164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17512509#comment-17512509
]
ASF subversion and git services commented on GEODE-10164:
-
Commit fdd5c2cc3df85911dc84ffe889369adb18eee1f5 in geode's branch
refs/heads/support/1.12 from Barry Oglesby
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=fdd5c2c ]
GEODE-10164: Revert wording change in rebalance result (#7490)
I changed the wording on the rebalance command results with the fix to
support rebalancing subregions. This change caused downstream tests to
fail that were expecting the original wording. This change reverts the
change to the wording back to the original.
(cherry picked from commit 9b2351029a6d24f63cc2b1a20af9112e9ed09997)
(cherry picked from commit 6bf622d597e4763e4430ad3f6f1f6e099e220b29)
(cherry picked from commit 26f52542ae23e9c0353e1182ad5d3dd8b4bf5d79)
> Revert wording change in rebalance result
> -
>
> Key: GEODE-10164
> URL: https://issues.apache.org/jira/browse/GEODE-10164
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Barrett Oglesby
>Assignee: Barrett Oglesby
>Priority: Major
> Labels: needsTriage, pull-request-available
>
> I made a change to the wording of the rebalance command result
> from:
> {noformat}
> Rebalanced partition regions {noformat}
> to:
> {noformat}
> Rebalanced partitioned region {noformat}
> This change caused hydra and other tests to fail, so I'm reverting it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-10167) CI failure: RollingUpgradeQueryReturnsCorrectResultAfterTwoLocatorsWithTwoServersAreRolled > luceneQueryReturnsCorrectResultAfterTwoLocatorsWithTwoServersAreRolled
[
https://issues.apache.org/jira/browse/GEODE-10167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17512508#comment-17512508
]
Geode Integration commented on GEODE-10167:
---
Seen in [upgrade-test-openjdk11
#232|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/upgrade-test-openjdk11/builds/232]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1030/test-results/upgradeTest/1648201193/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1030/test-artifacts/1648201193/upgradetestfiles-openjdk11-1.15.0-build.1030.tgz].
> CI failure:
> RollingUpgradeQueryReturnsCorrectResultAfterTwoLocatorsWithTwoServersAreRolled
> > luceneQueryReturnsCorrectResultAfterTwoLocatorsWithTwoServersAreRolled
> ---
>
> Key: GEODE-10167
> URL: https://issues.apache.org/jira/browse/GEODE-10167
> Project: Geode
> Issue Type: Bug
>Reporter: Jianxia Chen
>Priority: Major
> Labels: needsTriage
>
> {code:java}
> RollingUpgradeQueryReturnsCorrectResultAfterTwoLocatorsWithTwoServersAreRolled
> >
> luceneQueryReturnsCorrectResultAfterTwoLocatorsWithTwoServersAreRolled[from_v1.8.0,
> with reindex=false, singleHopEnabled=true] FAILED
> 00:24:01org.gradle.internal.exceptions.DefaultMultiCauseException:
> Multiple Failures (2 failures)
> 00:24:01 org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache.lucene.LuceneSearchWithRollingUpgradeTestBase$$Lambda$422/0x000100379c40.run
> in VM 2 running on Host
> heavy-lifter-138290eb-3fbe-5801-8565-60d3c24284e9.c.apachegeode-ci.internal
> with 4 VMs
> 00:24:01 java.lang.AssertionError: Suspicious strings were written to
> the log during this run.
> 00:24:01Fix the strings or use IgnoredException.addIgnoredException to
> ignore.
> 00:24:01
> ---
> 00:24:01Found suspect string in 'dunit_suspect-vm2.log' at line 3243
> 00:24:01
> 00:24:01[fatal 2022/03/25 07:23:55.137 UTC receiver,heavy-lifter-138290eb-3fbe-5801-8565-60d3c24284e9-23002> tid=49]
> Membership service failure: Member isn't responding to heartbeat requests
> 00:24:01
> org.apache.geode.distributed.internal.membership.api.MemberDisconnectedException:
> Member isn't responding to heartbeat requests
> 00:24:01 at
> org.apache.geode.distributed.internal.membership.gms.GMSMembership$ManagerImpl.forceDisconnect(GMSMembership.java:1806)
> 00:24:01 at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.forceDisconnect(GMSJoinLeave.java:1120)
> 00:24:01 at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.processRemoveMemberMessage(GMSJoinLeave.java:723)
> 00:24:01 at
> org.apache.geode.distributed.internal.membership.gms.messenger.JGroupsMessenger$JGroupsReceiver.receive(JGroupsMessenger.java:1367)
> 00:24:01 at
> org.apache.geode.distributed.internal.membership.gms.messenger.JGroupsMessenger$JGroupsReceiver.receive(JGroupsMessenger.java:1303)
> 00:24:01 at org.jgroups.JChannel.invokeCallback(JChannel.java:816)
> 00:24:01 at org.jgroups.JChannel.up(JChannel.java:741)
> 00:24:01 at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:1030)
> 00:24:01 at org.jgroups.protocols.FRAG2.up(FRAG2.java:165)
> 00:24:01 at org.jgroups.protocols.FlowControl.up(FlowControl.java:390)
> 00:24:01 at
> org.jgroups.protocols.UNICAST3.deliverMessage(UNICAST3.java:1077)
> 00:24:01 at
> org.jgroups.protocols.UNICAST3.handleDataReceived(UNICAST3.java:792)
> 00:24:01 at org.jgroups.protocols.UNICAST3.up(UNICAST3.java:433)
> 00:24:01 at
> org.apache.geode.distributed.internal.membership.gms.messenger.StatRecorder.up(StatRecorder.java:72)
> 00:24:01 at
> org.apache.geode.distributed.internal.membership.gms.messenger.AddressManager.up(AddressManager.java:70)
> 00:24:01 at org.jgroups.protocols.TP.passMessageUp(TP.java:1658)
> 00:24:01 at
> org.jgroups.protocols.TP$SingleMessageHandler.run(TP.java:1876)
> 00:24:01 at
> org.jgroups.util.DirectExecutor.execute(DirectExecutor.java:10)
> 00:24:01 at org.jgroups.protocols.TP.handleSingleMessage(TP.java:1789)
> 00:24:01 at org.jgroups.protocols.TP.receive(TP.java:1714)
> 00:24:01 at
> org.apache.geode.distributed.internal.membership.gms.messenger.Transport.receive(Transport.java:160)
> 00:24:01 at org.jgroups.protocols.UDP$PacketReceiver.run(UDP.java:701)
> 00:24:01 at java.base/java.lang.Thread.run(Thread.java:829)
> 00:24:01at
> org.jun
[jira] [Commented] (GEODE-10091) Benchmark instability in RedisZaddAndZremBenchmark
[
https://issues.apache.org/jira/browse/GEODE-10091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17512507#comment-17512507
]
Geode Integration commented on GEODE-10091:
---
Seen in [benchmark-radish
#240|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/benchmark-radish/builds/240].
> Benchmark instability in RedisZaddAndZremBenchmark
> --
>
> Key: GEODE-10091
> URL: https://issues.apache.org/jira/browse/GEODE-10091
> Project: Geode
> Issue Type: Bug
> Components: benchmarks, redis
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Assignee: Eric Zoerner
>Priority: Major
> Labels: needsTriage
>
> {noformat}
> This is ITERATION 1 of benchmarking against baseline.
> RedisGetBenchmark avg ops/sec
> Baseline:428358.55 Test:446241.49 Difference: +4.2%
> avg latency
> Baseline: 1678809.55 Test: 1611045.34 Difference: -4.0%
> RedisHgetBenchmark avg ops/sec
> Baseline:438535.25 Test:441078.97 Difference: +0.6%
> avg latency
> Baseline: 1638968.92 Test: 1630999.16 Difference: -0.5%
> RedisHsetAndHgetBenchmark avg ops/sec
> Baseline:191331.54 Test:186806.37 Difference: -2.4%
> avg latency
> Baseline: 3759694.09 Test: 3850396.04 Difference: +2.4%
> RedisHsetBenchmark avg ops/sec
> Baseline:308079.41 Test:303715.78 Difference: -1.4%
> avg latency
> Baseline: 2332102.91 Test: 2367639.93 Difference: +1.5%
> RedisSetBenchmark avg ops/sec
> Baseline:318147.74 Test:326996.22 Difference: +2.8%
> avg latency
> Baseline: 2263687.57 Test: 2198181.68 Difference: -2.9%
> RedisWeightedHsetAndHgetBenchmark avg ops/sec
> Baseline:390383.79 Test:385565.48 Difference: -1.2%
> avg latency
> Baseline: 1842561.96 Test: 1864716.09 Difference: +1.2%
> RedisWeightedZaddAndZrangeBenchmark avg ops/sec
> Baseline:375078.82 Test:350886.03 Difference: -6.5%
> avg latency
> Baseline: 1917476.15 Test: 2049452.87 Difference: +6.9%
> RedisZaddAndZremBenchmark avg ops/sec
> Baseline:124763.60 Test:118600.72 Difference: -4.9%
> avg latency
> Baseline: 5766048.34 Test: 6065491.13 Difference: +5.2%
> RedisZaddBenchmark avg ops/sec
> Baseline:432494.29 Test:438594.53 Difference: +1.4%
> avg latency
> Baseline: 1662639.09 Test: 1639906.18 Difference: -1.4%
> RedisZrangeBenchmark avg ops/sec
> Baseline:295523.77 Test:340381.87 Difference: +15.2%
> avg latency
> Baseline: 2433250.54 Test: 2112961.66 Difference: -13.2%
> RedisZrangeByScoreBenchmark avg ops/sec
> Baseline:285836.33 Test:356142.91 Difference: +24.6%
> avg latency
> Baseline: 2515708.23 Test: 2019249.68 Difference: -19.7%
> This is ITERATION 2 of benchmarking against baseline.
> RedisWeightedZaddAndZrangeBenchmark avg ops/sec
> Baseline:358570.33 Test:348012.02 Difference: -2.9%
> avg latency
> Baseline: 2005804.05 Test: 2066535.24 Difference: +3.0%
> RedisZaddAndZremBenchmark avg ops/sec
> Baseline:122900.38 Test:115226.22 Difference: -6.2%
> avg latency
> Baseline: 5858357.13 Test: 6243018.38 Difference: +6.6%
> This is ITERATION 3 of benchmarking against baseline.
> RedisZaddAndZremBenchmark avg ops/sec
> Baseline:125677.36 Test:118359.94 Difference: -5.8%
> a
[jira] [Commented] (GEODE-10167) CI failure: RollingUpgradeQueryReturnsCorrectResultAfterTwoLocatorsWithTwoServersAreRolled > luceneQueryReturnsCorrectResultAfterTwoLocatorsWithTwoServersAreRolled
[
https://issues.apache.org/jira/browse/GEODE-10167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17512504#comment-17512504
]
Jianxia Chen commented on GEODE-10167:
--
[https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/upgrade-test-openjdk11/builds/232]
=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1030/test-results/upgradeTest/1648201193/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Test report artifacts from this job are available at:
http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1030/test-artifacts/1648201193/upgradetestfiles-openjdk11-1.15.0-build.1030.tgz
> CI failure:
> RollingUpgradeQueryReturnsCorrectResultAfterTwoLocatorsWithTwoServersAreRolled
> > luceneQueryReturnsCorrectResultAfterTwoLocatorsWithTwoServersAreRolled
> ---
>
> Key: GEODE-10167
> URL: https://issues.apache.org/jira/browse/GEODE-10167
> Project: Geode
> Issue Type: Bug
>Reporter: Jianxia Chen
>Priority: Major
> Labels: needsTriage
>
> {code:java}
> RollingUpgradeQueryReturnsCorrectResultAfterTwoLocatorsWithTwoServersAreRolled
> >
> luceneQueryReturnsCorrectResultAfterTwoLocatorsWithTwoServersAreRolled[from_v1.8.0,
> with reindex=false, singleHopEnabled=true] FAILED
> 00:24:01org.gradle.internal.exceptions.DefaultMultiCauseException:
> Multiple Failures (2 failures)
> 00:24:01 org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache.lucene.LuceneSearchWithRollingUpgradeTestBase$$Lambda$422/0x000100379c40.run
> in VM 2 running on Host
> heavy-lifter-138290eb-3fbe-5801-8565-60d3c24284e9.c.apachegeode-ci.internal
> with 4 VMs
> 00:24:01 java.lang.AssertionError: Suspicious strings were written to
> the log during this run.
> 00:24:01Fix the strings or use IgnoredException.addIgnoredException to
> ignore.
> 00:24:01
> ---
> 00:24:01Found suspect string in 'dunit_suspect-vm2.log' at line 3243
> 00:24:01
> 00:24:01[fatal 2022/03/25 07:23:55.137 UTC receiver,heavy-lifter-138290eb-3fbe-5801-8565-60d3c24284e9-23002> tid=49]
> Membership service failure: Member isn't responding to heartbeat requests
> 00:24:01
> org.apache.geode.distributed.internal.membership.api.MemberDisconnectedException:
> Member isn't responding to heartbeat requests
> 00:24:01 at
> org.apache.geode.distributed.internal.membership.gms.GMSMembership$ManagerImpl.forceDisconnect(GMSMembership.java:1806)
> 00:24:01 at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.forceDisconnect(GMSJoinLeave.java:1120)
> 00:24:01 at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.processRemoveMemberMessage(GMSJoinLeave.java:723)
> 00:24:01 at
> org.apache.geode.distributed.internal.membership.gms.messenger.JGroupsMessenger$JGroupsReceiver.receive(JGroupsMessenger.java:1367)
> 00:24:01 at
> org.apache.geode.distributed.internal.membership.gms.messenger.JGroupsMessenger$JGroupsReceiver.receive(JGroupsMessenger.java:1303)
> 00:24:01 at org.jgroups.JChannel.invokeCallback(JChannel.java:816)
> 00:24:01 at org.jgroups.JChannel.up(JChannel.java:741)
> 00:24:01 at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:1030)
> 00:24:01 at org.jgroups.protocols.FRAG2.up(FRAG2.java:165)
> 00:24:01 at org.jgroups.protocols.FlowControl.up(FlowControl.java:390)
> 00:24:01 at
> org.jgroups.protocols.UNICAST3.deliverMessage(UNICAST3.java:1077)
> 00:24:01 at
> org.jgroups.protocols.UNICAST3.handleDataReceived(UNICAST3.java:792)
> 00:24:01 at org.jgroups.protocols.UNICAST3.up(UNICAST3.java:433)
> 00:24:01 at
> org.apache.geode.distributed.internal.membership.gms.messenger.StatRecorder.up(StatRecorder.java:72)
> 00:24:01 at
> org.apache.geode.distributed.internal.membership.gms.messenger.AddressManager.up(AddressManager.java:70)
> 00:24:01 at org.jgroups.protocols.TP.passMessageUp(TP.java:1658)
> 00:24:01 at
> org.jgroups.protocols.TP$SingleMessageHandler.run(TP.java:1876)
> 00:24:01 at
> org.jgroups.util.DirectExecutor.execute(DirectExecutor.java:10)
> 00:24:01 at org.jgroups.protocols.TP.handleSingleMessage(TP.java:1789)
> 00:24:01 at org.jgroups.protocols.TP.receive(TP.java:1714)
> 00:24:01 at
> org.apache.geode.distributed.internal.membership.gms.messenger.Transport.receive(Transport.java:160)
> 00:24:01 at org.jgroups.protocols.UDP$Packe
[jira] [Created] (GEODE-10167) CI failure: RollingUpgradeQueryReturnsCorrectResultAfterTwoLocatorsWithTwoServersAreRolled > luceneQueryReturnsCorrectResultAfterTwoLocatorsWithTwoServersAreRolled
Jianxia Chen created GEODE-10167:
Summary: CI failure:
RollingUpgradeQueryReturnsCorrectResultAfterTwoLocatorsWithTwoServersAreRolled
> luceneQueryReturnsCorrectResultAfterTwoLocatorsWithTwoServersAreRolled
Key: GEODE-10167
URL: https://issues.apache.org/jira/browse/GEODE-10167
Project: Geode
Issue Type: Bug
Reporter: Jianxia Chen
{code:java}
RollingUpgradeQueryReturnsCorrectResultAfterTwoLocatorsWithTwoServersAreRolled
>
luceneQueryReturnsCorrectResultAfterTwoLocatorsWithTwoServersAreRolled[from_v1.8.0,
with reindex=false, singleHopEnabled=true] FAILED
00:24:01org.gradle.internal.exceptions.DefaultMultiCauseException: Multiple
Failures (2 failures)
00:24:01org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.cache.lucene.LuceneSearchWithRollingUpgradeTestBase$$Lambda$422/0x000100379c40.run
in VM 2 running on Host
heavy-lifter-138290eb-3fbe-5801-8565-60d3c24284e9.c.apachegeode-ci.internal
with 4 VMs
00:24:01java.lang.AssertionError: Suspicious strings were written to
the log during this run.
00:24:01Fix the strings or use IgnoredException.addIgnoredException to
ignore.
00:24:01
---
00:24:01Found suspect string in 'dunit_suspect-vm2.log' at line 3243
00:24:01
00:24:01[fatal 2022/03/25 07:23:55.137 UTC tid=49]
Membership service failure: Member isn't responding to heartbeat requests
00:24:01
org.apache.geode.distributed.internal.membership.api.MemberDisconnectedException:
Member isn't responding to heartbeat requests
00:24:01at
org.apache.geode.distributed.internal.membership.gms.GMSMembership$ManagerImpl.forceDisconnect(GMSMembership.java:1806)
00:24:01at
org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.forceDisconnect(GMSJoinLeave.java:1120)
00:24:01at
org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.processRemoveMemberMessage(GMSJoinLeave.java:723)
00:24:01at
org.apache.geode.distributed.internal.membership.gms.messenger.JGroupsMessenger$JGroupsReceiver.receive(JGroupsMessenger.java:1367)
00:24:01at
org.apache.geode.distributed.internal.membership.gms.messenger.JGroupsMessenger$JGroupsReceiver.receive(JGroupsMessenger.java:1303)
00:24:01at org.jgroups.JChannel.invokeCallback(JChannel.java:816)
00:24:01at org.jgroups.JChannel.up(JChannel.java:741)
00:24:01at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:1030)
00:24:01at org.jgroups.protocols.FRAG2.up(FRAG2.java:165)
00:24:01at org.jgroups.protocols.FlowControl.up(FlowControl.java:390)
00:24:01at
org.jgroups.protocols.UNICAST3.deliverMessage(UNICAST3.java:1077)
00:24:01at
org.jgroups.protocols.UNICAST3.handleDataReceived(UNICAST3.java:792)
00:24:01at org.jgroups.protocols.UNICAST3.up(UNICAST3.java:433)
00:24:01at
org.apache.geode.distributed.internal.membership.gms.messenger.StatRecorder.up(StatRecorder.java:72)
00:24:01at
org.apache.geode.distributed.internal.membership.gms.messenger.AddressManager.up(AddressManager.java:70)
00:24:01at org.jgroups.protocols.TP.passMessageUp(TP.java:1658)
00:24:01at
org.jgroups.protocols.TP$SingleMessageHandler.run(TP.java:1876)
00:24:01at
org.jgroups.util.DirectExecutor.execute(DirectExecutor.java:10)
00:24:01at org.jgroups.protocols.TP.handleSingleMessage(TP.java:1789)
00:24:01at org.jgroups.protocols.TP.receive(TP.java:1714)
00:24:01at
org.apache.geode.distributed.internal.membership.gms.messenger.Transport.receive(Transport.java:160)
00:24:01at org.jgroups.protocols.UDP$PacketReceiver.run(UDP.java:701)
00:24:01at java.base/java.lang.Thread.run(Thread.java:829)
00:24:01at
org.junit.vintage.engine.execution.TestRun.getStoredResultOrSuccessful(TestRun.java:196)
00:24:01at
org.junit.vintage.engine.execution.RunListenerAdapter.fireExecutionFinished(RunListenerAdapter.java:226)
00:24:01at
org.junit.vintage.engine.execution.RunListenerAdapter.testFinished(RunListenerAdapter.java:192)
00:24:01at
org.junit.vintage.engine.execution.RunListenerAdapter.testFinished(RunListenerAdapter.java:79)
00:24:01at
org.junit.runner.notification.SynchronizedRunListener.testFinished(SynchronizedRunListener.java:87)
00:24:01at
org.junit.runner.notification.RunNotifier$9.notifyListener(RunNotifier.java:225)
00:24:01at
org.junit.runner.notification.RunNotifier$SafeNotifier.run(RunNotifier.java:72)
00:24:01at
org.junit.runner.notification.RunNotifier.fireTestFinished(RunNotifier.java:222)
00:24:01at
org.junit.internal.runners.model.EachTestNotifier.fireTestFinished(EachTestNotifier.java:38)
00:24:01at org.junit.runners.ParentRunner.runLeaf(Pa
[jira] [Updated] (GEODE-10167) CI failure: RollingUpgradeQueryReturnsCorrectResultAfterTwoLocatorsWithTwoServersAreRolled > luceneQueryReturnsCorrectResultAfterTwoLocatorsWithTwoServersAreRolled
[
https://issues.apache.org/jira/browse/GEODE-10167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Murmann updated GEODE-10167:
--
Labels: needsTriage (was: )
> CI failure:
> RollingUpgradeQueryReturnsCorrectResultAfterTwoLocatorsWithTwoServersAreRolled
> > luceneQueryReturnsCorrectResultAfterTwoLocatorsWithTwoServersAreRolled
> ---
>
> Key: GEODE-10167
> URL: https://issues.apache.org/jira/browse/GEODE-10167
> Project: Geode
> Issue Type: Bug
>Reporter: Jianxia Chen
>Priority: Major
> Labels: needsTriage
>
> {code:java}
> RollingUpgradeQueryReturnsCorrectResultAfterTwoLocatorsWithTwoServersAreRolled
> >
> luceneQueryReturnsCorrectResultAfterTwoLocatorsWithTwoServersAreRolled[from_v1.8.0,
> with reindex=false, singleHopEnabled=true] FAILED
> 00:24:01org.gradle.internal.exceptions.DefaultMultiCauseException:
> Multiple Failures (2 failures)
> 00:24:01 org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache.lucene.LuceneSearchWithRollingUpgradeTestBase$$Lambda$422/0x000100379c40.run
> in VM 2 running on Host
> heavy-lifter-138290eb-3fbe-5801-8565-60d3c24284e9.c.apachegeode-ci.internal
> with 4 VMs
> 00:24:01 java.lang.AssertionError: Suspicious strings were written to
> the log during this run.
> 00:24:01Fix the strings or use IgnoredException.addIgnoredException to
> ignore.
> 00:24:01
> ---
> 00:24:01Found suspect string in 'dunit_suspect-vm2.log' at line 3243
> 00:24:01
> 00:24:01[fatal 2022/03/25 07:23:55.137 UTC receiver,heavy-lifter-138290eb-3fbe-5801-8565-60d3c24284e9-23002> tid=49]
> Membership service failure: Member isn't responding to heartbeat requests
> 00:24:01
> org.apache.geode.distributed.internal.membership.api.MemberDisconnectedException:
> Member isn't responding to heartbeat requests
> 00:24:01 at
> org.apache.geode.distributed.internal.membership.gms.GMSMembership$ManagerImpl.forceDisconnect(GMSMembership.java:1806)
> 00:24:01 at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.forceDisconnect(GMSJoinLeave.java:1120)
> 00:24:01 at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.processRemoveMemberMessage(GMSJoinLeave.java:723)
> 00:24:01 at
> org.apache.geode.distributed.internal.membership.gms.messenger.JGroupsMessenger$JGroupsReceiver.receive(JGroupsMessenger.java:1367)
> 00:24:01 at
> org.apache.geode.distributed.internal.membership.gms.messenger.JGroupsMessenger$JGroupsReceiver.receive(JGroupsMessenger.java:1303)
> 00:24:01 at org.jgroups.JChannel.invokeCallback(JChannel.java:816)
> 00:24:01 at org.jgroups.JChannel.up(JChannel.java:741)
> 00:24:01 at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:1030)
> 00:24:01 at org.jgroups.protocols.FRAG2.up(FRAG2.java:165)
> 00:24:01 at org.jgroups.protocols.FlowControl.up(FlowControl.java:390)
> 00:24:01 at
> org.jgroups.protocols.UNICAST3.deliverMessage(UNICAST3.java:1077)
> 00:24:01 at
> org.jgroups.protocols.UNICAST3.handleDataReceived(UNICAST3.java:792)
> 00:24:01 at org.jgroups.protocols.UNICAST3.up(UNICAST3.java:433)
> 00:24:01 at
> org.apache.geode.distributed.internal.membership.gms.messenger.StatRecorder.up(StatRecorder.java:72)
> 00:24:01 at
> org.apache.geode.distributed.internal.membership.gms.messenger.AddressManager.up(AddressManager.java:70)
> 00:24:01 at org.jgroups.protocols.TP.passMessageUp(TP.java:1658)
> 00:24:01 at
> org.jgroups.protocols.TP$SingleMessageHandler.run(TP.java:1876)
> 00:24:01 at
> org.jgroups.util.DirectExecutor.execute(DirectExecutor.java:10)
> 00:24:01 at org.jgroups.protocols.TP.handleSingleMessage(TP.java:1789)
> 00:24:01 at org.jgroups.protocols.TP.receive(TP.java:1714)
> 00:24:01 at
> org.apache.geode.distributed.internal.membership.gms.messenger.Transport.receive(Transport.java:160)
> 00:24:01 at org.jgroups.protocols.UDP$PacketReceiver.run(UDP.java:701)
> 00:24:01 at java.base/java.lang.Thread.run(Thread.java:829)
> 00:24:01at
> org.junit.vintage.engine.execution.TestRun.getStoredResultOrSuccessful(TestRun.java:196)
> 00:24:01at
> org.junit.vintage.engine.execution.RunListenerAdapter.fireExecutionFinished(RunListenerAdapter.java:226)
> 00:24:01at
> org.junit.vintage.engine.execution.RunListenerAdapter.testFinished(RunListenerAdapter.java:192)
> 00:24:01at
> org.junit.vintage.engine.execution.RunListenerAdapter.testFinished(RunListenerAdapter.java:79)
> 00:24:01at
> org.junit.runner.notificatio
[jira] [Commented] (GEODE-10164) Revert wording change in rebalance result
[
https://issues.apache.org/jira/browse/GEODE-10164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17512495#comment-17512495
]
ASF subversion and git services commented on GEODE-10164:
-
Commit 26f52542ae23e9c0353e1182ad5d3dd8b4bf5d79 in geode's branch
refs/heads/support/1.13 from Barry Oglesby
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=26f5254 ]
GEODE-10164: Revert wording change in rebalance result (#7490)
I changed the wording on the rebalance command results with the fix to
support rebalancing subregions. This change caused downstream tests to
fail that were expecting the original wording. This change reverts the
change to the wording back to the original.
(cherry picked from commit 9b2351029a6d24f63cc2b1a20af9112e9ed09997)
(cherry picked from commit 6bf622d597e4763e4430ad3f6f1f6e099e220b29)
> Revert wording change in rebalance result
> -
>
> Key: GEODE-10164
> URL: https://issues.apache.org/jira/browse/GEODE-10164
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Barrett Oglesby
>Assignee: Barrett Oglesby
>Priority: Major
> Labels: needsTriage, pull-request-available
>
> I made a change to the wording of the rebalance command result
> from:
> {noformat}
> Rebalanced partition regions {noformat}
> to:
> {noformat}
> Rebalanced partitioned region {noformat}
> This change caused hydra and other tests to fail, so I'm reverting it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-10164) Revert wording change in rebalance result
[
https://issues.apache.org/jira/browse/GEODE-10164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17512486#comment-17512486
]
ASF subversion and git services commented on GEODE-10164:
-
Commit 6bf622d597e4763e4430ad3f6f1f6e099e220b29 in geode's branch
refs/heads/support/1.14 from Barry Oglesby
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=6bf622d ]
GEODE-10164: Revert wording change in rebalance result (#7490)
I changed the wording on the rebalance command results with the fix to
support rebalancing subregions. This change caused downstream tests to
fail that were expecting the original wording. This change reverts the
change to the wording back to the original.
(cherry picked from commit 9b2351029a6d24f63cc2b1a20af9112e9ed09997)
> Revert wording change in rebalance result
> -
>
> Key: GEODE-10164
> URL: https://issues.apache.org/jira/browse/GEODE-10164
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Barrett Oglesby
>Assignee: Barrett Oglesby
>Priority: Major
> Labels: needsTriage, pull-request-available
>
> I made a change to the wording of the rebalance command result
> from:
> {noformat}
> Rebalanced partition regions {noformat}
> to:
> {noformat}
> Rebalanced partitioned region {noformat}
> This change caused hydra and other tests to fail, so I'm reverting it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-10091) Benchmark instability in RedisZaddAndZremBenchmark
[
https://issues.apache.org/jira/browse/GEODE-10091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17512483#comment-17512483
]
Jianxia Chen commented on GEODE-10091:
--
Failed again in
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/benchmark-radish/builds/240
> Benchmark instability in RedisZaddAndZremBenchmark
> --
>
> Key: GEODE-10091
> URL: https://issues.apache.org/jira/browse/GEODE-10091
> Project: Geode
> Issue Type: Bug
> Components: benchmarks, redis
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Assignee: Eric Zoerner
>Priority: Major
> Labels: needsTriage
>
> {noformat}
> This is ITERATION 1 of benchmarking against baseline.
> RedisGetBenchmark avg ops/sec
> Baseline:428358.55 Test:446241.49 Difference: +4.2%
> avg latency
> Baseline: 1678809.55 Test: 1611045.34 Difference: -4.0%
> RedisHgetBenchmark avg ops/sec
> Baseline:438535.25 Test:441078.97 Difference: +0.6%
> avg latency
> Baseline: 1638968.92 Test: 1630999.16 Difference: -0.5%
> RedisHsetAndHgetBenchmark avg ops/sec
> Baseline:191331.54 Test:186806.37 Difference: -2.4%
> avg latency
> Baseline: 3759694.09 Test: 3850396.04 Difference: +2.4%
> RedisHsetBenchmark avg ops/sec
> Baseline:308079.41 Test:303715.78 Difference: -1.4%
> avg latency
> Baseline: 2332102.91 Test: 2367639.93 Difference: +1.5%
> RedisSetBenchmark avg ops/sec
> Baseline:318147.74 Test:326996.22 Difference: +2.8%
> avg latency
> Baseline: 2263687.57 Test: 2198181.68 Difference: -2.9%
> RedisWeightedHsetAndHgetBenchmark avg ops/sec
> Baseline:390383.79 Test:385565.48 Difference: -1.2%
> avg latency
> Baseline: 1842561.96 Test: 1864716.09 Difference: +1.2%
> RedisWeightedZaddAndZrangeBenchmark avg ops/sec
> Baseline:375078.82 Test:350886.03 Difference: -6.5%
> avg latency
> Baseline: 1917476.15 Test: 2049452.87 Difference: +6.9%
> RedisZaddAndZremBenchmark avg ops/sec
> Baseline:124763.60 Test:118600.72 Difference: -4.9%
> avg latency
> Baseline: 5766048.34 Test: 6065491.13 Difference: +5.2%
> RedisZaddBenchmark avg ops/sec
> Baseline:432494.29 Test:438594.53 Difference: +1.4%
> avg latency
> Baseline: 1662639.09 Test: 1639906.18 Difference: -1.4%
> RedisZrangeBenchmark avg ops/sec
> Baseline:295523.77 Test:340381.87 Difference: +15.2%
> avg latency
> Baseline: 2433250.54 Test: 2112961.66 Difference: -13.2%
> RedisZrangeByScoreBenchmark avg ops/sec
> Baseline:285836.33 Test:356142.91 Difference: +24.6%
> avg latency
> Baseline: 2515708.23 Test: 2019249.68 Difference: -19.7%
> This is ITERATION 2 of benchmarking against baseline.
> RedisWeightedZaddAndZrangeBenchmark avg ops/sec
> Baseline:358570.33 Test:348012.02 Difference: -2.9%
> avg latency
> Baseline: 2005804.05 Test: 2066535.24 Difference: +3.0%
> RedisZaddAndZremBenchmark avg ops/sec
> Baseline:122900.38 Test:115226.22 Difference: -6.2%
> avg latency
> Baseline: 5858357.13 Test: 6243018.38 Difference: +6.6%
> This is ITERATION 3 of benchmarking against baseline.
> RedisZaddAndZremBenchmark avg ops/sec
> Baseline:125677.36 Test:118359.94 Difference: -5.8%
> avg latency
> Baseline:
[jira] [Commented] (GEODE-10101) release 1.14.4
[ https://issues.apache.org/jira/browse/GEODE-10101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17512480#comment-17512480 ] ASF GitHub Bot commented on GEODE-10101: moleske commented on pull request #948: URL: https://github.com/apache/geode-native/pull/948#issuecomment-1079216806 @dickcav can you push an empty commit to retrigger the checks? This pr is needed to unblock other prs -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@geode.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org > release 1.14.4 > -- > > Key: GEODE-10101 > URL: https://issues.apache.org/jira/browse/GEODE-10101 > Project: Geode > Issue Type: Task > Components: release >Reporter: Dick Cavender >Priority: Major > Labels: pull-request-available > Fix For: 1.14.5, 1.15.0 > > > Release to incorporate GEODE-10093 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9758) Provide an easy to configure a process-wide serialization filter for use on Java 8
[ https://issues.apache.org/jira/browse/GEODE-9758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17512471#comment-17512471 ] ASF subversion and git services commented on GEODE-9758: Commit e6a1a403bfa20d054c1a8b4242ed2c632de0198f in geode's branch refs/heads/support/1.14 from Kirk Lund [ https://gitbox.apache.org/repos/asf?p=geode.git;h=e6a1a40 ] Revert "GEODE-9980: Improve error handling of serial filters (#7355)" (#7489) This reverts commit 5d9e4b5b54b84c2de28b670fe6feb0b0c3f7. Revert "GEODE-9758: Add internal serial filter API (#7217)" This reverts commit f0809e411d561226f736adca9d40cbbe27033e53. Revert "GEODE-9879: Extract SystemProperty to geode-common (#7177)" This reverts commit 2652bd65cd4192068de6c601f7ba92d120816593. Revert "GEODE-9758: Move ClassUtils to geode-common (#7166)" This reverts commit e821d6eff4541ae478a0eb67217bcb456abae97a. Revert "GEODE-9758: Move SanctionedSerializables to filter package (#7165)" This reverts commit 3f66ab05e5683edb4bcb43e52304d8e5f58ac707. Revert "GEODE-9817: Enable customized source set paths for ClassAnalysisRule (#7367)" This reverts commit 8f3186cb74ccd2eb1ec8ba648c7a11b08d575962. > Provide an easy to configure a process-wide serialization filter for use on > Java 8 > -- > > Key: GEODE-9758 > URL: https://issues.apache.org/jira/browse/GEODE-9758 > Project: Geode > Issue Type: Improvement > Components: configuration, serialization >Affects Versions: 1.12.7, 1.13.0, 1.14.0 >Reporter: Jianxia Chen >Assignee: Kirk Lund >Priority: Major > Labels: GeodeOperationAPI, docs, pull-request-available > > Provide an easy way to configure a process-wide serialization filter for use > on Java 8. When enabled, validate-serializable-objects should be enabled and > the process-wide serialization filter should be configured to accept only JDK > classes and Geode classes in addition to anything the user might specify with > serializable-object-filter. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9879) Extract part of SystemPropertyHelper to geode-common for wider use
[ https://issues.apache.org/jira/browse/GEODE-9879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17512472#comment-17512472 ] ASF subversion and git services commented on GEODE-9879: Commit e6a1a403bfa20d054c1a8b4242ed2c632de0198f in geode's branch refs/heads/support/1.14 from Kirk Lund [ https://gitbox.apache.org/repos/asf?p=geode.git;h=e6a1a40 ] Revert "GEODE-9980: Improve error handling of serial filters (#7355)" (#7489) This reverts commit 5d9e4b5b54b84c2de28b670fe6feb0b0c3f7. Revert "GEODE-9758: Add internal serial filter API (#7217)" This reverts commit f0809e411d561226f736adca9d40cbbe27033e53. Revert "GEODE-9879: Extract SystemProperty to geode-common (#7177)" This reverts commit 2652bd65cd4192068de6c601f7ba92d120816593. Revert "GEODE-9758: Move ClassUtils to geode-common (#7166)" This reverts commit e821d6eff4541ae478a0eb67217bcb456abae97a. Revert "GEODE-9758: Move SanctionedSerializables to filter package (#7165)" This reverts commit 3f66ab05e5683edb4bcb43e52304d8e5f58ac707. Revert "GEODE-9817: Enable customized source set paths for ClassAnalysisRule (#7367)" This reverts commit 8f3186cb74ccd2eb1ec8ba648c7a11b08d575962. > Extract part of SystemPropertyHelper to geode-common for wider use > -- > > Key: GEODE-9879 > URL: https://issues.apache.org/jira/browse/GEODE-9879 > Project: Geode > Issue Type: Wish > Components: core >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > I need to use the dual property prefix part of SystemPropertyHelper to > geode-common so that it can be used from non-core geode modules such as > geode-serialization. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9980) Startup of Locator or Server should fail fast if geode.enableGlobalSerialFilter is enabled but fails configuration
[
https://issues.apache.org/jira/browse/GEODE-9980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17512470#comment-17512470
]
ASF subversion and git services commented on GEODE-9980:
Commit e6a1a403bfa20d054c1a8b4242ed2c632de0198f in geode's branch
refs/heads/support/1.14 from Kirk Lund
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=e6a1a40 ]
Revert "GEODE-9980: Improve error handling of serial filters (#7355)" (#7489)
This reverts commit 5d9e4b5b54b84c2de28b670fe6feb0b0c3f7.
Revert "GEODE-9758: Add internal serial filter API (#7217)"
This reverts commit f0809e411d561226f736adca9d40cbbe27033e53.
Revert "GEODE-9879: Extract SystemProperty to geode-common (#7177)"
This reverts commit 2652bd65cd4192068de6c601f7ba92d120816593.
Revert "GEODE-9758: Move ClassUtils to geode-common (#7166)"
This reverts commit e821d6eff4541ae478a0eb67217bcb456abae97a.
Revert "GEODE-9758: Move SanctionedSerializables to filter package (#7165)"
This reverts commit 3f66ab05e5683edb4bcb43e52304d8e5f58ac707.
Revert "GEODE-9817: Enable customized source set paths for ClassAnalysisRule
(#7367)"
This reverts commit 8f3186cb74ccd2eb1ec8ba648c7a11b08d575962.
> Startup of Locator or Server should fail fast if
> geode.enableGlobalSerialFilter is enabled but fails configuration
> --
>
> Key: GEODE-9980
> URL: https://issues.apache.org/jira/browse/GEODE-9980
> Project: Geode
> Issue Type: Bug
> Components: serialization
>Affects Versions: 1.15.0
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
> Labels: GeodeOperationAPI, blocks-1.15.0, pull-request-available
>
> The following error conditions need better handling which includes handling
> of all errors consistently and cause the startup of a Locator or Server to
> fail if it's unable to honor the setting of
> {{-Dgeode.enableGlobalSerialFilter=true}} for any reason. Currently, if
> {{-Dgeode.enableGlobalSerialFilter=true}} is specified but Geode is unable to
> create a global serial filter, then it will will log a warning and continue
> running. A user may easily miss that log statement and believe that the JVM
> is running with a properly configured serialization filter.
> 1) The user is trying to secure the JVM very thoroughly and accidentally
> specifies both {{-Djdk.serialFilter}} and
> {{-Dgeode.enableGlobalSerialFilter}}.
> 2) The user runs some non-Geode code in the same JVM that invokes
> {{ObjectInputFilter.Config.setFilter(...)}} directly.
> 3) The user is using a version of Java 8 prior to 8u121 (the release that
> first added {{sun.misc.ObjectInputFilter}}) and specifies
> {{-Dgeode.enableGlobalSerialFilter=true}}. Also, the same behavior occurs if
> they do NOT specify enabling that property.
> 4) {{LocatorLauncher}} or {{ServerLauncher}} is started in a JVM that has
> already created at least one {{ObjectInputStream}} which will cause
> {{ObjectInputFilter.Config.setFilter(...)}} to fail.
> 5) {{LocatorLauncher}} or {{ServerLauncher}} is started in a Java 8 JVM that
> is not based on OpenJDK (ie {{sun.misc.ObjectInputFilter}} does not exist).
> 6) {{LocatorLauncher}} or {{ServerLauncher}} is started in an unforeseen
> environment that causes invocation of
> {{ObjectInputFilter.Config.setFilter(...)}} via Java Reflection to throw
> {{IllegalAccessException}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-9817) Allow analyze serializables tests to provide custom source set paths to ClassAnalysisRule
[ https://issues.apache.org/jira/browse/GEODE-9817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17512473#comment-17512473 ] ASF subversion and git services commented on GEODE-9817: Commit e6a1a403bfa20d054c1a8b4242ed2c632de0198f in geode's branch refs/heads/support/1.14 from Kirk Lund [ https://gitbox.apache.org/repos/asf?p=geode.git;h=e6a1a40 ] Revert "GEODE-9980: Improve error handling of serial filters (#7355)" (#7489) This reverts commit 5d9e4b5b54b84c2de28b670fe6feb0b0c3f7. Revert "GEODE-9758: Add internal serial filter API (#7217)" This reverts commit f0809e411d561226f736adca9d40cbbe27033e53. Revert "GEODE-9879: Extract SystemProperty to geode-common (#7177)" This reverts commit 2652bd65cd4192068de6c601f7ba92d120816593. Revert "GEODE-9758: Move ClassUtils to geode-common (#7166)" This reverts commit e821d6eff4541ae478a0eb67217bcb456abae97a. Revert "GEODE-9758: Move SanctionedSerializables to filter package (#7165)" This reverts commit 3f66ab05e5683edb4bcb43e52304d8e5f58ac707. Revert "GEODE-9817: Enable customized source set paths for ClassAnalysisRule (#7367)" This reverts commit 8f3186cb74ccd2eb1ec8ba648c7a11b08d575962. > Allow analyze serializables tests to provide custom source set paths to > ClassAnalysisRule > - > > Key: GEODE-9817 > URL: https://issues.apache.org/jira/browse/GEODE-9817 > Project: Geode > Issue Type: Wish > Components: tests >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Labels: pull-request-available > Fix For: 1.14.4, 1.15.0 > > > In order to make SanctionedSerializablesService and the related tests to be > more pluggable by external modules, I need to make changes to allow analyze > serializables tests to provide custom source set paths to ClassAnalysisRule. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10166) Several tests in geode-dunit are in the "main" source set instead of "distributedTest"
[ https://issues.apache.org/jira/browse/GEODE-10166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-10166: --- Labels: pull-request-available (was: ) > Several tests in geode-dunit are in the "main" source set instead of > "distributedTest" > -- > > Key: GEODE-10166 > URL: https://issues.apache.org/jira/browse/GEODE-10166 > Project: Geode > Issue Type: Bug > Components: tests >Affects Versions: 1.15.0 >Reporter: Donal Evans >Assignee: Donal Evans >Priority: Major > Labels: pull-request-available > > The below tests in the geode-dunit module have been incorrectly placed in the > "main" directory rather than the "distributedTest" directory, meaning that > they are not run as part of pre-checkin or in the pipeline: > InternalCacheForClientAccessDUnitTest > NestedQueryClassCastExceptionFailureDUnitTest > RebalanceCommandDistributedTest > They should be moved to the appropriate directory -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-10136) FunctionServiceBase tests fail because lambda classes have no canonical name on JDK 17
[
https://issues.apache.org/jira/browse/GEODE-10136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dale Emery reassigned GEODE-10136:
--
Assignee: Dale Emery
> FunctionServiceBase tests fail because lambda classes have no canonical name
> on JDK 17
> --
>
> Key: GEODE-10136
> URL: https://issues.apache.org/jira/browse/GEODE-10136
> Project: Geode
> Issue Type: Improvement
> Components: functions, tests
>Affects Versions: 1.15.0
>Reporter: Dale Emery
>Assignee: Dale Emery
>Priority: Major
> Labels: Java17
>
> {{FunctionServiceBase}} tests fail on JDK 17.
> Here are the relevant factors:
> - {{FunctionServiceBase}} uses lambda expressions to create the function
> objects used to test the function service.
> - The objects that represent these lambda expressions use the default
> implementation of all {{Function}} methods other than
> {{execute(FunctionContext)}}.
> - The default implementation of {{getId()}} returns the canonical name of the
> function object's class.
> - In JDK 17, the class of a lambda expression has no canonical name.
> - The product classes {{AbstractExecution}} and
> {{DistributedRegionFunctionExecutor}} both throw exceptions if the given
> function reports its ID as {{null}}.
> The tests can be fixed by replacing the lambda expressions with uses of a
> class that returns a non-{{null}} ID.
> This may be a product issue. Given that {{Function}} is explicitly annotated
> as a {{@FunctionalInterface}}:
> - It is clearly intended to be used with lambda expressions, yet on JDK 17 it
> cannot be used with lamda expressions.
> - It would be reasonable to expect that an anonymous class that extends
> `Function` could safely use the default implementation of {{getId()}}, yet
> anonymous classes have no canonical names on any JDK.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-10166) Several tests in geode-dunit are in the "main" source set instead of "distributedTest"
[ https://issues.apache.org/jira/browse/GEODE-10166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donal Evans updated GEODE-10166: Affects Version/s: 1.15.0 > Several tests in geode-dunit are in the "main" source set instead of > "distributedTest" > -- > > Key: GEODE-10166 > URL: https://issues.apache.org/jira/browse/GEODE-10166 > Project: Geode > Issue Type: Bug > Components: tests >Affects Versions: 1.15.0 >Reporter: Donal Evans >Assignee: Donal Evans >Priority: Major > > The below tests in the geode-dunit module have been incorrectly placed in the > "main" directory rather than the "distributedTest" directory, meaning that > they are not run as part of pre-checkin or in the pipeline: > InternalCacheForClientAccessDUnitTest > NestedQueryClassCastExceptionFailureDUnitTest > RebalanceCommandDistributedTest > They should be moved to the appropriate directory -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10166) Several tests in geode-dunit are in the "main" source set instead of "distributedTest"
[ https://issues.apache.org/jira/browse/GEODE-10166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-10166: -- Labels: needsTriage (was: ) > Several tests in geode-dunit are in the "main" source set instead of > "distributedTest" > -- > > Key: GEODE-10166 > URL: https://issues.apache.org/jira/browse/GEODE-10166 > Project: Geode > Issue Type: Bug > Components: tests >Reporter: Donal Evans >Priority: Major > Labels: needsTriage > > The below tests in the geode-dunit module have been incorrectly placed in the > "main" directory rather than the "distributedTest" directory, meaning that > they are not run as part of pre-checkin or in the pipeline: > InternalCacheForClientAccessDUnitTest > NestedQueryClassCastExceptionFailureDUnitTest > RebalanceCommandDistributedTest > They should be moved to the appropriate directory -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-10166) Several tests in geode-dunit are in the "main" source set instead of "distributedTest"
Donal Evans created GEODE-10166: --- Summary: Several tests in geode-dunit are in the "main" source set instead of "distributedTest" Key: GEODE-10166 URL: https://issues.apache.org/jira/browse/GEODE-10166 Project: Geode Issue Type: Bug Components: tests Reporter: Donal Evans The below tests in the geode-dunit module have been incorrectly placed in the "main" directory rather than the "distributedTest" directory, meaning that they are not run as part of pre-checkin or in the pipeline: InternalCacheForClientAccessDUnitTest NestedQueryClassCastExceptionFailureDUnitTest RebalanceCommandDistributedTest They should be moved to the appropriate directory -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10166) Several tests in geode-dunit are in the "main" source set instead of "distributedTest"
[ https://issues.apache.org/jira/browse/GEODE-10166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donal Evans updated GEODE-10166: Labels: (was: needsTriage) > Several tests in geode-dunit are in the "main" source set instead of > "distributedTest" > -- > > Key: GEODE-10166 > URL: https://issues.apache.org/jira/browse/GEODE-10166 > Project: Geode > Issue Type: Bug > Components: tests >Reporter: Donal Evans >Assignee: Donal Evans >Priority: Major > > The below tests in the geode-dunit module have been incorrectly placed in the > "main" directory rather than the "distributedTest" directory, meaning that > they are not run as part of pre-checkin or in the pipeline: > InternalCacheForClientAccessDUnitTest > NestedQueryClassCastExceptionFailureDUnitTest > RebalanceCommandDistributedTest > They should be moved to the appropriate directory -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-10166) Several tests in geode-dunit are in the "main" source set instead of "distributedTest"
[ https://issues.apache.org/jira/browse/GEODE-10166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donal Evans reassigned GEODE-10166: --- Assignee: Donal Evans > Several tests in geode-dunit are in the "main" source set instead of > "distributedTest" > -- > > Key: GEODE-10166 > URL: https://issues.apache.org/jira/browse/GEODE-10166 > Project: Geode > Issue Type: Bug > Components: tests >Reporter: Donal Evans >Assignee: Donal Evans >Priority: Major > Labels: needsTriage > > The below tests in the geode-dunit module have been incorrectly placed in the > "main" directory rather than the "distributedTest" directory, meaning that > they are not run as part of pre-checkin or in the pipeline: > InternalCacheForClientAccessDUnitTest > NestedQueryClassCastExceptionFailureDUnitTest > RebalanceCommandDistributedTest > They should be moved to the appropriate directory -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10164) Revert wording change in rebalance result
[
https://issues.apache.org/jira/browse/GEODE-10164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17512459#comment-17512459
]
ASF subversion and git services commented on GEODE-10164:
-
Commit 9b2351029a6d24f63cc2b1a20af9112e9ed09997 in geode's branch
refs/heads/develop from Barry Oglesby
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=9b23510 ]
GEODE-10164: Revert wording change in rebalance result (#7490)
I changed the wording on the rebalance command results with the fix to
support rebalancing subregions. This change caused downstream tests to
fail that were expecting the original wording. This change reverts the
change to the wording back to the original.
> Revert wording change in rebalance result
> -
>
> Key: GEODE-10164
> URL: https://issues.apache.org/jira/browse/GEODE-10164
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Barrett Oglesby
>Assignee: Barrett Oglesby
>Priority: Major
> Labels: needsTriage, pull-request-available
>
> I made a change to the wording of the rebalance command result
> from:
> {noformat}
> Rebalanced partition regions {noformat}
> to:
> {noformat}
> Rebalanced partitioned region {noformat}
> This change caused hydra and other tests to fail, so I'm reverting it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
