[jira] [Commented] (GEODE-8996) Rebalance GFSH commands and restore redundancy commands were not backward compatible
[ https://issues.apache.org/jira/browse/GEODE-8996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17319788#comment-17319788 ] ASF subversion and git services commented on GEODE-8996: Commit 0fbb98837afe30a375064c0d8814c9c8ef598e83 in geode's branch refs/heads/develop from Nabarun Nag [ https://gitbox.apache.org/repos/asf?p=geode.git;h=0fbb988 ] GEODE-8996: Separated the gfsh rebalance test from other tests. * Support for gfsh rebalance compatibilty is from 1.11.0 * Remaining connectivity tests should be run with all other versions. * In the previous commit for GEODE-8996, the existing tests missed certain versions. > Rebalance GFSH commands and restore redundancy commands were not backward > compatible > > > Key: GEODE-8996 > URL: https://issues.apache.org/jira/browse/GEODE-8996 > Project: Geode > Issue Type: Bug > Components: gfsh, rest (admin) >Reporter: Nabarun Nag >Assignee: Nabarun Nag >Priority: Major > Labels: blocks-1.14.0, pull-request-available > Fix For: 1.12.2, 1.13.2, 1.14.0, 1.15.0 > > > Issue: > * Rebalance command when executed with 1.12.0+ locator and older servers, > the command failed > * This was because the Rebalance function moved to a new package > * Similar problem with REST calls because of moving CacheRealizationFunction > to a new package > * There was another problem where Serializable classes with UIDs were > changed in couple of releases > * The variation of the UIDs caused deserialization issues when REST commands > were executed from new locators and old servers. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8996) Rebalance GFSH commands and restore redundancy commands were not backward compatible
[ https://issues.apache.org/jira/browse/GEODE-8996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17319787#comment-17319787 ] ASF subversion and git services commented on GEODE-8996: Commit 0fbb98837afe30a375064c0d8814c9c8ef598e83 in geode's branch refs/heads/develop from Nabarun Nag [ https://gitbox.apache.org/repos/asf?p=geode.git;h=0fbb988 ] GEODE-8996: Separated the gfsh rebalance test from other tests. * Support for gfsh rebalance compatibilty is from 1.11.0 * Remaining connectivity tests should be run with all other versions. * In the previous commit for GEODE-8996, the existing tests missed certain versions. > Rebalance GFSH commands and restore redundancy commands were not backward > compatible > > > Key: GEODE-8996 > URL: https://issues.apache.org/jira/browse/GEODE-8996 > Project: Geode > Issue Type: Bug > Components: gfsh, rest (admin) >Reporter: Nabarun Nag >Assignee: Nabarun Nag >Priority: Major > Labels: blocks-1.14.0, pull-request-available > Fix For: 1.12.2, 1.13.2, 1.14.0, 1.15.0 > > > Issue: > * Rebalance command when executed with 1.12.0+ locator and older servers, > the command failed > * This was because the Rebalance function moved to a new package > * Similar problem with REST calls because of moving CacheRealizationFunction > to a new package > * There was another problem where Serializable classes with UIDs were > changed in couple of releases > * The variation of the UIDs caused deserialization issues when REST commands > were executed from new locators and old servers. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8741) Filter out CQ Create/Update/Destroy notifications
[ https://issues.apache.org/jira/browse/GEODE-8741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17319780#comment-17319780 ] Anilkumar Gingade commented on GEODE-8741: -- [~mivanac] I have to look into the PR to see what your are really are trying to achieve in this ticket. It will be helpful if you can add more information with the example (depending on the issue). E.g. Avoid sending CQ events for specific CQ query-operations (E.g. destroy Query operation) to client. For a region.put() which results in CQ event with its query operation as destroy; avoid sending this event to client. I am not seeing any value/scenario that needs this kind of behavior. Do you have any example can you please explain here. The core CQ design aspect was to establish a data view representing a query result that can be expressed in the form of query. And support event mechanism that will enable to manage/maintain that view as the change happens on the source data. The changes requested in this ticket, breaks the core design and can allow one to represent/establish a different data view that is not in-line with the source data (a query result view). I don't see need for supporting that kind of behavior in the server side. If Client is not interested to see specific event/operation it should be filtering this out on the client side. Why the need for this behavior? Looking the Pull Request opened; its not like its avoiding processing of CQs, which is generally more expensive part of having CQ; only thing its avoiding sending the CQ event to client. If this is the behavior client/application is looking for; probably CQ is not the functionality to use. Also, it will be nice to use Request For Change (RFC) process for any issues that has behavior/functional or new API requirements. It will help to get feedback during design phase itself. > Filter out CQ Create/Update/Destroy notifications > - > > Key: GEODE-8741 > URL: https://issues.apache.org/jira/browse/GEODE-8741 > Project: Geode > Issue Type: Wish > Components: cq >Reporter: Mario Ivanac >Assignee: Mario Ivanac >Priority: Minor > Labels: pull-request-available > > Clients subscribe to server-side events by using SQL-type query filtering. > The server sends all events that modify the query results. CQ event delivery > uses the client/server subscription framework. > We want possibility for each client to block/suppress CQ > Create/Update/Destroy event (notification). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9140) CI Failure: DeploymentManagementUpgradeTest > newLocatorCanReadOldConfigurationData fails with ComparisonFailure
[
https://issues.apache.org/jira/browse/GEODE-9140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17319777#comment-17319777
]
Geode Integration commented on GEODE-9140:
--
Seen in [UpgradeTestOpenJDK8
#137|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/UpgradeTestOpenJDK8/builds/137]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0131/test-results/upgradeTest/1618007435/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0131/test-artifacts/1618007435/upgradetestfiles-OpenJDK8-1.15.0-build.0131.tgz].
> CI Failure: DeploymentManagementUpgradeTest >
> newLocatorCanReadOldConfigurationData fails with ComparisonFailure
>
>
> Key: GEODE-9140
> URL: https://issues.apache.org/jira/browse/GEODE-9140
> Project: Geode
> Issue Type: Wish
> Components: gfsh, management
>Reporter: Kirk Lund
>Priority: Major
>
> {noformat}
> org.apache.geode.management.DeploymentManagementUpgradeTest >
> newLocatorCanReadOldConfigurationData[1.13.2] FAILED
> org.junit.ComparisonFailure: [Exit value from process started by
> [c0f4fa64150ca1ed: gfsh -e start locator --name=test --port=28819
> --http-service-port=28818 --J=-Dgemfire.jmx-manager-port=28820]]
> expected:<[0]> but was:<[1]>
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshExecution.awaitTermination(GfshExecution.java:103)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:143)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshScript.execute(GfshScript.java:160)
> at
> org.apache.geode.management.DeploymentManagementUpgradeTest.newLocatorCanReadOldConfigurationData(DeploymentManagementUpgradeTest.java:99)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-9142) Make disk size for heavy lifters parameterized
[ https://issues.apache.org/jira/browse/GEODE-9142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-9142: -- Labels: pull-request-available (was: ) > Make disk size for heavy lifters parameterized > -- > > Key: GEODE-9142 > URL: https://issues.apache.org/jira/browse/GEODE-9142 > Project: Geode > Issue Type: Improvement > Components: ci >Reporter: Sean Goller >Priority: Major > Labels: pull-request-available > > We're running out of disk space on certain jobs. Make it so we can choose how > much disk to allocate on a per job basis. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8886) When performing a rolling upgrade to 1.14 from an older version some messages are not delivered
[ https://issues.apache.org/jira/browse/GEODE-8886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17319755#comment-17319755 ] ASF subversion and git services commented on GEODE-8886: Commit a309bb6c8a58bdb7f9d2b6c0380a9156cfdda869 in geode's branch refs/heads/develop from mhansonp [ https://gitbox.apache.org/repos/asf?p=geode.git;h=a309bb6 ] Geode 8886 new test (#6128) GEODE-8886: New test with documentation corrections. > When performing a rolling upgrade to 1.14 from an older version some messages > are not delivered > --- > > Key: GEODE-8886 > URL: https://issues.apache.org/jira/browse/GEODE-8886 > Project: Geode > Issue Type: Bug > Components: core >Affects Versions: 1.14.0 >Reporter: Mark Hanson >Assignee: Mark Hanson >Priority: Major > Labels: blocks-1.14.0, pull-request-available > Fix For: 1.14.0, 1.15.0 > > > We are running a test where we are performing a rolling upgrade from an older > version to 1.14.0 and we are finding that for whatever reason in this test > that not all "updates" are being passed to all servers and clients while > using gateway senders. It is not clear that gateway senders are the cause, > but at this point, it is just an interesting point. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-6070) CI Failure: ShutdownCommandOverHttpDUnitTest > testShutdownAll
[
https://issues.apache.org/jira/browse/GEODE-6070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17319751#comment-17319751
]
Geode Integration commented on GEODE-6070:
--
Seen on support/1.12 in [WindowsGfshDistributedTestOpenJDK11
#19|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/WindowsGfshDistributedTestOpenJDK11/builds/19]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.2-build.0196/test-results/distributedTest/1615034385/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.2-build.0196/test-artifacts/1615034385/windows-gfshdistributedtest-OpenJDK11-1.12.2-build.0196.tgz].
> CI Failure: ShutdownCommandOverHttpDUnitTest > testShutdownAll
> --
>
> Key: GEODE-6070
> URL: https://issues.apache.org/jira/browse/GEODE-6070
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.12.0
>Reporter: Hale Bales
>Priority: Major
> Labels: GeodeOperationAPI, flaky
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Failed with stacktrace:
> {noformat}
> org.apache.geode.management.internal.cli.commands.ShutdownCommandOverHttpDUnitTest
> > testShutdownAll FAILED
> java.lang.AssertionError: Suspicious strings were written to the log
> during this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in log4j at line 302
> org.apache.geode.distributed.DistributedSystemDisconnectedException:
> Distribution manager on 172.17.0.3(server-1:496):41002 started at Thu Nov
> 15 19:47:58 UTC 2018: Message distribution has terminated
> {noformat}
> Test results can be found here:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.9.0-build.158/test-results/distributedTest/1542315851/classes/org.apache.geode.management.internal.cli.commands.ShutdownCommandOverHttpDUnitTest.html#testShutdownAll
>
> Test Artifacts can be found here:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.9.0-build.158/test-artifacts/1542315851/distributedtestfiles-OpenJDK8-1.9.0-build.158.tgz
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-5782) LauncherMemberMXBeanIntegrationTest can fail intermittently
[
https://issues.apache.org/jira/browse/GEODE-5782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17319750#comment-17319750
]
Geode Integration commented on GEODE-5782:
--
Seen on support/1.12 in [WindowsCoreIntegrationTestOpenJDK8
#18|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/WindowsCoreIntegrationTestOpenJDK8/builds/18]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.2-build.0191/test-results/integrationTest/1614665626/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.2-build.0191/test-artifacts/1614665626/windows-coreintegrationtestfiles-OpenJDK8-1.12.2-build.0191.tgz].
> LauncherMemberMXBeanIntegrationTest can fail intermittently
> ---
>
> Key: GEODE-5782
> URL: https://issues.apache.org/jira/browse/GEODE-5782
> Project: Geode
> Issue Type: Bug
> Components: jmx
>Affects Versions: 1.9.0
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
> Fix For: 1.14.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Noticed this failure:
> {noformat}
> org.apache.geode.distributed.LauncherMemberMXBeanIntegrationTest >
> showOSMetrics_reconstructsOSMetricsFromCompositeDataType FAILED
> org.junit.ComparisonFailure: expected:<204.[68]> but was:<204.[55]>
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.distributed.LauncherMemberMXBeanIntegrationTest.showOSMetrics_reconstructsOSMetricsFromCompositeDataType(LauncherMemberMXBeanIntegrationTest.java:143)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-8634) CI failure: AsyncInvocationTimeoutDistributedTest. get_callable_timeout_includesStackTraceAsCause
[
https://issues.apache.org/jira/browse/GEODE-8634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17319749#comment-17319749
]
Geode Integration commented on GEODE-8634:
--
Seen on support/1.12 in [DistributedTestOpenJDK8
#25|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/DistributedTestOpenJDK8/builds/25]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.2-build.0198/test-results/distributedTest/1615509559/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.2-build.0198/test-artifacts/1615509559/distributedtestfiles-OpenJDK8-1.12.2-build.0198.tgz].
> CI failure: AsyncInvocationTimeoutDistributedTest.
> get_callable_timeout_includesStackTraceAsCause
> -
>
> Key: GEODE-8634
> URL: https://issues.apache.org/jira/browse/GEODE-8634
> Project: Geode
> Issue Type: Test
> Components: tests
>Affects Versions: 1.13.0, 1.14.0
>Reporter: Jens Deppe
>Assignee: Kirk Lund
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.14.0
>
>
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-13-main/jobs/DistributedTestOpenJDK8/builds/24
> {noformat}
> org.apache.geode.test.dunit.tests.AsyncInvocationTimeoutDistributedTest >
> get_callable_timeout_includesStackTraceAsCause FAILED
> java.lang.AssertionError:
> Expecting message to be:
> <"Stack trace for vm-0 thread-32">
> but was:
> <"Stack trace for vm-0 thread-33">
> Throwable that failed the check:
> org.apache.geode.test.dunit.internal.StackTrace: Stack trace for vm-0
> thread-33
> at sun.misc.Unsafe.park(Native Method)
> at
> java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos(AbstractQueuedSynchronizer.java:1037)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1328)
> at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:277)
> at
> org.apache.geode.test.dunit.tests.AsyncInvocationTimeoutDistributedTest.lambda$get_callable_timeout_includesStackTraceAsCause$c2252e51$1(AsyncInvocationTimeoutDistributedTest.java:109)
> at
> org.apache.geode.test.dunit.tests.AsyncInvocationTimeoutDistributedTest$$Lambda$36/681142003.call(Unknown
> Source)
> at
> org.apache.geode.test.dunit.internal.IdentifiableCallable.call(IdentifiableCallable.java:41)
> 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)
> 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 sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:357)
> at sun.rmi.transport.Transport$1.run(Transport.java:200)
> at sun.rmi.transport.Transport$1.run(Transport.java:197)
> at java.security.AccessController.doPrivileged(Native Method)
> at sun.rmi.transport.Transport.serviceCall(Transport.java:196)
> at
> sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:573)
> at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:834)
> at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:688)
> at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler$$Lambda$15/1238667039.run(Unknown
> Source)
> at java.security.AccessController.doPrivileged(Native Method)
> at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:687)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> at
>
[jira] [Commented] (GEODE-8634) CI failure: AsyncInvocationTimeoutDistributedTest. get_callable_timeout_includesStackTraceAsCause
[
https://issues.apache.org/jira/browse/GEODE-8634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17319748#comment-17319748
]
Geode Integration commented on GEODE-8634:
--
Seen on support/1.12 in [DistributedTestOpenJDK8
#26|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/DistributedTestOpenJDK8/builds/26]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.2-build.0198/test-results/distributedTest/1615532907/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.2-build.0198/test-artifacts/1615532907/distributedtestfiles-OpenJDK8-1.12.2-build.0198.tgz].
> CI failure: AsyncInvocationTimeoutDistributedTest.
> get_callable_timeout_includesStackTraceAsCause
> -
>
> Key: GEODE-8634
> URL: https://issues.apache.org/jira/browse/GEODE-8634
> Project: Geode
> Issue Type: Test
> Components: tests
>Affects Versions: 1.13.0, 1.14.0
>Reporter: Jens Deppe
>Assignee: Kirk Lund
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.14.0
>
>
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-13-main/jobs/DistributedTestOpenJDK8/builds/24
> {noformat}
> org.apache.geode.test.dunit.tests.AsyncInvocationTimeoutDistributedTest >
> get_callable_timeout_includesStackTraceAsCause FAILED
> java.lang.AssertionError:
> Expecting message to be:
> <"Stack trace for vm-0 thread-32">
> but was:
> <"Stack trace for vm-0 thread-33">
> Throwable that failed the check:
> org.apache.geode.test.dunit.internal.StackTrace: Stack trace for vm-0
> thread-33
> at sun.misc.Unsafe.park(Native Method)
> at
> java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos(AbstractQueuedSynchronizer.java:1037)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1328)
> at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:277)
> at
> org.apache.geode.test.dunit.tests.AsyncInvocationTimeoutDistributedTest.lambda$get_callable_timeout_includesStackTraceAsCause$c2252e51$1(AsyncInvocationTimeoutDistributedTest.java:109)
> at
> org.apache.geode.test.dunit.tests.AsyncInvocationTimeoutDistributedTest$$Lambda$36/681142003.call(Unknown
> Source)
> at
> org.apache.geode.test.dunit.internal.IdentifiableCallable.call(IdentifiableCallable.java:41)
> 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)
> 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 sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:357)
> at sun.rmi.transport.Transport$1.run(Transport.java:200)
> at sun.rmi.transport.Transport$1.run(Transport.java:197)
> at java.security.AccessController.doPrivileged(Native Method)
> at sun.rmi.transport.Transport.serviceCall(Transport.java:196)
> at
> sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:573)
> at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:834)
> at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:688)
> at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler$$Lambda$15/1238667039.run(Unknown
> Source)
> at java.security.AccessController.doPrivileged(Native Method)
> at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:687)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> at
>
[jira] [Commented] (GEODE-7460) CI failure: DistributedMemberDUnitTest.testGroupsInAllVMs ForcedDisconnectException Failure
[ https://issues.apache.org/jira/browse/GEODE-7460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17319747#comment-17319747 ] Geode Integration commented on GEODE-7460: -- Seen on support/1.12 in [DistributedTestOpenJDK8 #28|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/DistributedTestOpenJDK8/builds/28] ... see [test results|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.2-build.0199/test-results/distributedTest/1615547954/] or download [artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.2-build.0199/test-artifacts/1615547954/distributedtestfiles-OpenJDK8-1.12.2-build.0199.tgz]. > CI failure: DistributedMemberDUnitTest.testGroupsInAllVMs > ForcedDisconnectException Failure > --- > > Key: GEODE-7460 > URL: https://issues.apache.org/jira/browse/GEODE-7460 > Project: Geode > Issue Type: Bug > Components: membership >Affects Versions: 1.13.0, 1.14.0 >Reporter: Robert Houghton >Assignee: Bill Burcham >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > From the failing job: > =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > http://files.apachegeode-ci.info/builds/apache-develop-main/1.12.0-SNAPSHOT.0016/test-results/distributedTest/1573784422/ > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Test report artifacts from this job are available at: > http://files.apachegeode-ci.info/builds/apache-develop-main/1.12.0-SNAPSHOT.0016/test-artifacts/1573784422/distributedtestfiles-OpenJDK8-1.12.0-SNAPSHOT.0016.tgz > DistributedTest failure due to exception: > org.apache.geode.distributed.DistributedMemberDUnitTest > testGroupsInAllVMs > FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.distributed.DistributedMemberDUnitTest$6.run in VM 0 running > on Host 3e09f1029b44 with 4 VMs > at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579) > at org.apache.geode.test.dunit.VM.invoke(VM.java:406) > at > org.apache.geode.distributed.DistributedMemberDUnitTest.testGroupsInAllVMs(DistributedMemberDUnitTest.java:333) > Caused by: > org.apache.geode.SystemConnectException: One or more peers generated > exceptions during connection attempt > at > org.apache.geode.distributed.internal.ClusterDistributionManager.sendStartupMessage(ClusterDistributionManager.java:1625) > at > org.apache.geode.distributed.internal.ClusterDistributionManager.create(ClusterDistributionManager.java:354) > at > org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:759) > at > org.apache.geode.distributed.internal.InternalDistributedSystem.access$200(InternalDistributedSystem.java:136) > at > org.apache.geode.distributed.internal.InternalDistributedSystem$Builder.build(InternalDistributedSystem.java:3009) > at > org.apache.geode.distributed.internal.InternalDistributedSystem.connectInternal(InternalDistributedSystem.java:269) > at > org.apache.geode.distributed.DistributedSystem.connect(DistributedSystem.java:159) > at > org.apache.geode.test.dunit.internal.JUnit4DistributedTestCase.getSystem(JUnit4DistributedTestCase.java:181) > at > org.apache.geode.distributed.DistributedMemberDUnitTest$6.run(DistributedMemberDUnitTest.java:339) > Caused by: > > org.apache.geode.distributed.DistributedSystemDisconnectedException: > DistributedSystem is shutting down, caused by > org.apache.geode.ForcedDisconnectException: Exiting due to possible network > partition event due to loss of 1 cache processes: > [172.17.0.14(myName:1):41001] > at > org.apache.geode.distributed.internal.membership.adapter.GMSMembershipManager.directChannelSend(GMSMembershipManager.java:1591) > at > org.apache.geode.distributed.internal.membership.adapter.GMSMembershipManager.send(GMSMembershipManager.java:1751) > at > org.apache.geode.distributed.internal.ClusterDistributionManager.sendViaMembershipManager(ClusterDistributionManager.java:2058) > at > org.apache.geode.distributed.internal.ClusterDistributionManager.sendOutgoing(ClusterDistributionManager.java:1985) > at > org.apache.geode.distributed.internal.StartupOperation.sendStartupMessage(StartupOperation.java:74) > at > org.apache.geode.distributed.internal.ClusterDistributionManager.sendStartupMessage(ClusterDistributionManager.java:1622) > ... 8 more > Caused
[jira] [Commented] (GEODE-7460) CI failure: DistributedMemberDUnitTest.testGroupsInAllVMs ForcedDisconnectException Failure
[ https://issues.apache.org/jira/browse/GEODE-7460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17319745#comment-17319745 ] Geode Integration commented on GEODE-7460: -- Seen on support/1.12 in [DistributedTestOpenJDK8 #34.1|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/DistributedTestOpenJDK8/builds/34.1] ... see [test results|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.2-build.0204/test-results/distributedTest/1616824052/] or download [artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.2-build.0204/test-artifacts/1616824052/distributedtestfiles-OpenJDK8-1.12.2-build.0204.tgz]. > CI failure: DistributedMemberDUnitTest.testGroupsInAllVMs > ForcedDisconnectException Failure > --- > > Key: GEODE-7460 > URL: https://issues.apache.org/jira/browse/GEODE-7460 > Project: Geode > Issue Type: Bug > Components: membership >Affects Versions: 1.13.0, 1.14.0 >Reporter: Robert Houghton >Assignee: Bill Burcham >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > From the failing job: > =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > http://files.apachegeode-ci.info/builds/apache-develop-main/1.12.0-SNAPSHOT.0016/test-results/distributedTest/1573784422/ > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Test report artifacts from this job are available at: > http://files.apachegeode-ci.info/builds/apache-develop-main/1.12.0-SNAPSHOT.0016/test-artifacts/1573784422/distributedtestfiles-OpenJDK8-1.12.0-SNAPSHOT.0016.tgz > DistributedTest failure due to exception: > org.apache.geode.distributed.DistributedMemberDUnitTest > testGroupsInAllVMs > FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.distributed.DistributedMemberDUnitTest$6.run in VM 0 running > on Host 3e09f1029b44 with 4 VMs > at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579) > at org.apache.geode.test.dunit.VM.invoke(VM.java:406) > at > org.apache.geode.distributed.DistributedMemberDUnitTest.testGroupsInAllVMs(DistributedMemberDUnitTest.java:333) > Caused by: > org.apache.geode.SystemConnectException: One or more peers generated > exceptions during connection attempt > at > org.apache.geode.distributed.internal.ClusterDistributionManager.sendStartupMessage(ClusterDistributionManager.java:1625) > at > org.apache.geode.distributed.internal.ClusterDistributionManager.create(ClusterDistributionManager.java:354) > at > org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:759) > at > org.apache.geode.distributed.internal.InternalDistributedSystem.access$200(InternalDistributedSystem.java:136) > at > org.apache.geode.distributed.internal.InternalDistributedSystem$Builder.build(InternalDistributedSystem.java:3009) > at > org.apache.geode.distributed.internal.InternalDistributedSystem.connectInternal(InternalDistributedSystem.java:269) > at > org.apache.geode.distributed.DistributedSystem.connect(DistributedSystem.java:159) > at > org.apache.geode.test.dunit.internal.JUnit4DistributedTestCase.getSystem(JUnit4DistributedTestCase.java:181) > at > org.apache.geode.distributed.DistributedMemberDUnitTest$6.run(DistributedMemberDUnitTest.java:339) > Caused by: > > org.apache.geode.distributed.DistributedSystemDisconnectedException: > DistributedSystem is shutting down, caused by > org.apache.geode.ForcedDisconnectException: Exiting due to possible network > partition event due to loss of 1 cache processes: > [172.17.0.14(myName:1):41001] > at > org.apache.geode.distributed.internal.membership.adapter.GMSMembershipManager.directChannelSend(GMSMembershipManager.java:1591) > at > org.apache.geode.distributed.internal.membership.adapter.GMSMembershipManager.send(GMSMembershipManager.java:1751) > at > org.apache.geode.distributed.internal.ClusterDistributionManager.sendViaMembershipManager(ClusterDistributionManager.java:2058) > at > org.apache.geode.distributed.internal.ClusterDistributionManager.sendOutgoing(ClusterDistributionManager.java:1985) > at > org.apache.geode.distributed.internal.StartupOperation.sendStartupMessage(StartupOperation.java:74) > at > org.apache.geode.distributed.internal.ClusterDistributionManager.sendStartupMessage(ClusterDistributionManager.java:1622) > ... 8 more >
[jira] [Commented] (GEODE-7604) QueryConfigurationServiceConstraintsDistributedTest
[
https://issues.apache.org/jira/browse/GEODE-7604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17319746#comment-17319746
]
Geode Integration commented on GEODE-7604:
--
Seen on support/1.12 in [DistributedTestOpenJDK8
#32|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/DistributedTestOpenJDK8/builds/32]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.2-build.0202/test-results/distributedTest/1616791383/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.2-build.0202/test-artifacts/1616791383/distributedtestfiles-OpenJDK8-1.12.2-build.0202.tgz].
> QueryConfigurationServiceConstraintsDistributedTest
> ---
>
> Key: GEODE-7604
> URL: https://issues.apache.org/jira/browse/GEODE-7604
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Mark Hanson
>Assignee: Juan Ramos
>Priority: Major
> Labels: GeodeCommons
> Fix For: 1.13.0
>
> Time Spent: 3h
> Remaining Estimate: 0h
>
> QueryConfigurationServiceConstraintsDistributedTest had two failures in the
> mass test run...
> [2]
> https://concourse.apachegeode-ci.info/teams/main/pipelines/mhansonp-mhanson-mass-test-ru-main/jobs/DistributedTestOpenJDK8/builds/2252
> [6]
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/mhansonp-mhanson-mass-test-ru-main/jobs/DistributedTestOpenJDK8/builds/2211]
>
> {noformat}
> 01:28:56org.apache.geode.cache.query.internal.QueryConfigurationServiceConstraintsDistributedTest
> > [2]
> cqsShouldSucceedDuringEventProcessingAfterRegionOperationWhenMethodAuthorizerIsChangedAndQueryContainsMethodsAllowedByTheNewAuthorizer(RegionType:REPLICATE;Operation:CREATE,ExecuteWithInitialResults:true)
> FAILED
> 01:28:56org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache.query.internal.QueryConfigurationServiceConstraintsDistributedTest$$Lambda$57/2082907347.run
> in VM 2 running on Host 8cbcba2ac2b2 with 4 VMs
> 01:28:56at
> org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:610)
> 01:28:56at org.apache.geode.test.dunit.VM.invoke(VM.java:437)
> 01:28:56at
> org.apache.geode.test.junit.rules.VMProvider.invoke(VMProvider.java:94)
> 01:28:56at
> org.apache.geode.cache.query.internal.QueryConfigurationServiceConstraintsDistributedTest.cqsShouldSucceedDuringEventProcessingAfterRegionOperationWhenMethodAuthorizerIsChangedAndQueryContainsMethodsAllowedByTheNewAuthorizer(QueryConfigurationServiceConstraintsDistributedTest.java:260)
> 01:28:56
> 01:28:56Caused by:
> 01:28:56org.awaitility.core.ConditionTimeoutException: Assertion
> condition defined as a
> org.apache.geode.cache.query.internal.QueryConfigurationServiceConstraintsDistributedTest
> expected:<[7]> but was:<[4]> within 300 seconds.
> 01:28:56at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:145)
> 01:28:56at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:122)
> 01:28:56at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:32)
> 01:28:56at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:902)
> 01:28:56at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:723)
> 01:28:56at
> org.apache.geode.cache.query.internal.QueryConfigurationServiceConstraintsDistributedTest.lambda$cqsShouldSucceedDuringEventProcessingAfterRegionOperationWhenMethodAuthorizerIsChangedAndQueryContainsMethodsAllowedByTheNewAuthorizer$868d1d80$1(QueryConfigurationServiceConstraintsDistributedTest.java:264)
> 01:28:56
> 01:28:56Caused by:
> 01:28:56org.junit.ComparisonFailure: expected:<[7]> but was:<[4]>
> 01:28:56at
> sun.reflect.GeneratedConstructorAccessor207.newInstance(Unknown Source)
> 01:28:56at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> 01:28:56at
> org.apache.geode.cache.query.internal.QueryConfigurationServiceConstraintsDistributedTest.lambda$null$13(QueryConfigurationServiceConstraintsDistributedTest.java:266)
> 02:03:51
> 02:03:51679 tests completed, 1 failed, 39 skipped {noformat}
>
>
> {noformat}
> 07:59:46org.apache.geode.cache.query.internal.QueryConfigurationServiceConstraintsDistributedTest
> > [6]
> cqsShouldFailDuringEventProcessingAfterRegionOperationWhenMethodAuthorizerIsChangedAndQueryContainsMethodsNotAllowedByTheNewAuthorizer(RegionType:REPLICATE;Operation:DESTROY,ExecuteWithInitialResults:true)
> FAILED
> 07:59:46org.apache.geode.test.dunit.RMIException: While
[jira] [Commented] (GEODE-7702) DistributedAckRegionCCEDUnitTest > testClearOnNonReplicateWithConcurrentEvents is showing a product bug
[
https://issues.apache.org/jira/browse/GEODE-7702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17319744#comment-17319744
]
Geode Integration commented on GEODE-7702:
--
Seen on support/1.12 in [DistributedTestOpenJDK11
#12|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/DistributedTestOpenJDK11/builds/12]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.2-build.0187/test-results/distributedTest/1614317568/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.2-build.0187/test-artifacts/1614317568/distributedtestfiles-OpenJDK11-1.12.2-build.0187.tgz].
> DistributedAckRegionCCEDUnitTest >
> testClearOnNonReplicateWithConcurrentEvents is showing a product bug
> ---
>
> Key: GEODE-7702
> URL: https://issues.apache.org/jira/browse/GEODE-7702
> Project: Geode
> Issue Type: Bug
> Components: client/server
>Reporter: Mark Hanson
>Assignee: Xiaojian Zhou
>Priority: Major
> Labels: GeodeCommons
> Fix For: 1.14.0
>
>
> testClearOnNonReplicateWithConcurrentEvents in
> DistributedAckRegionCCEDUnitTest.java
> versionTestClearOnNonReplicateWithConcurrentEvents in
> MultiVMRegionTestCase.java
> doOpsLoop
> doOpsLoopNoFlush
> {noformat}
> case 5:
> if (includeClear) {
> CCRegion.clear();
> break;
> } else {
> if (CCRegion.getAttributes().getDataPolicy().withReplication()) {
> if (oldkey != null) {
> CCRegion.putIfAbsent(oldkey, value);
> }
> break;
> } // else fall through to invalidate
> } {noformat}
> the addition of this chunk of code causes this test to fail.
> The core of the problem is that a putall and a clear are happening
> concurrently and the "system" does not respond by either clearing all entries
> or letting all entries persist.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-7702) DistributedAckRegionCCEDUnitTest > testClearOnNonReplicateWithConcurrentEvents is showing a product bug
[
https://issues.apache.org/jira/browse/GEODE-7702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17319743#comment-17319743
]
Geode Integration commented on GEODE-7702:
--
Seen on support/1.12 in [DistributedTestOpenJDK8
#18|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/DistributedTestOpenJDK8/builds/18]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.2-build.0191/test-results/distributedTest/1614656769/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.2-build.0191/test-artifacts/1614656769/distributedtestfiles-OpenJDK8-1.12.2-build.0191.tgz].
> DistributedAckRegionCCEDUnitTest >
> testClearOnNonReplicateWithConcurrentEvents is showing a product bug
> ---
>
> Key: GEODE-7702
> URL: https://issues.apache.org/jira/browse/GEODE-7702
> Project: Geode
> Issue Type: Bug
> Components: client/server
>Reporter: Mark Hanson
>Assignee: Xiaojian Zhou
>Priority: Major
> Labels: GeodeCommons
> Fix For: 1.14.0
>
>
> testClearOnNonReplicateWithConcurrentEvents in
> DistributedAckRegionCCEDUnitTest.java
> versionTestClearOnNonReplicateWithConcurrentEvents in
> MultiVMRegionTestCase.java
> doOpsLoop
> doOpsLoopNoFlush
> {noformat}
> case 5:
> if (includeClear) {
> CCRegion.clear();
> break;
> } else {
> if (CCRegion.getAttributes().getDataPolicy().withReplication()) {
> if (oldkey != null) {
> CCRegion.putIfAbsent(oldkey, value);
> }
> break;
> } // else fall through to invalidate
> } {noformat}
> the addition of this chunk of code causes this test to fail.
> The core of the problem is that a putall and a clear are happening
> concurrently and the "system" does not respond by either clearing all entries
> or letting all entries persist.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-7702) DistributedAckRegionCCEDUnitTest > testClearOnNonReplicateWithConcurrentEvents is showing a product bug
[
https://issues.apache.org/jira/browse/GEODE-7702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17319741#comment-17319741
]
Geode Integration commented on GEODE-7702:
--
Seen on support/1.12 in [DistributedTestOpenJDK8
#36|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/DistributedTestOpenJDK8/builds/36]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.2-build.0209/test-results/distributedTest/1617670290/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.2-build.0209/test-artifacts/1617670290/distributedtestfiles-OpenJDK8-1.12.2-build.0209.tgz].
> DistributedAckRegionCCEDUnitTest >
> testClearOnNonReplicateWithConcurrentEvents is showing a product bug
> ---
>
> Key: GEODE-7702
> URL: https://issues.apache.org/jira/browse/GEODE-7702
> Project: Geode
> Issue Type: Bug
> Components: client/server
>Reporter: Mark Hanson
>Assignee: Xiaojian Zhou
>Priority: Major
> Labels: GeodeCommons
> Fix For: 1.14.0
>
>
> testClearOnNonReplicateWithConcurrentEvents in
> DistributedAckRegionCCEDUnitTest.java
> versionTestClearOnNonReplicateWithConcurrentEvents in
> MultiVMRegionTestCase.java
> doOpsLoop
> doOpsLoopNoFlush
> {noformat}
> case 5:
> if (includeClear) {
> CCRegion.clear();
> break;
> } else {
> if (CCRegion.getAttributes().getDataPolicy().withReplication()) {
> if (oldkey != null) {
> CCRegion.putIfAbsent(oldkey, value);
> }
> break;
> } // else fall through to invalidate
> } {noformat}
> the addition of this chunk of code causes this test to fail.
> The core of the problem is that a putall and a clear are happening
> concurrently and the "system" does not respond by either clearing all entries
> or letting all entries persist.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-7702) DistributedAckRegionCCEDUnitTest > testClearOnNonReplicateWithConcurrentEvents is showing a product bug
[
https://issues.apache.org/jira/browse/GEODE-7702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17319742#comment-17319742
]
Geode Integration commented on GEODE-7702:
--
Seen on support/1.12 in [DistributedTestOpenJDK8
#25.1|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/DistributedTestOpenJDK8/builds/25.1]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.2-build.0198/test-results/distributedTest/1615519982/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.2-build.0198/test-artifacts/1615519982/distributedtestfiles-OpenJDK8-1.12.2-build.0198.tgz].
> DistributedAckRegionCCEDUnitTest >
> testClearOnNonReplicateWithConcurrentEvents is showing a product bug
> ---
>
> Key: GEODE-7702
> URL: https://issues.apache.org/jira/browse/GEODE-7702
> Project: Geode
> Issue Type: Bug
> Components: client/server
>Reporter: Mark Hanson
>Assignee: Xiaojian Zhou
>Priority: Major
> Labels: GeodeCommons
> Fix For: 1.14.0
>
>
> testClearOnNonReplicateWithConcurrentEvents in
> DistributedAckRegionCCEDUnitTest.java
> versionTestClearOnNonReplicateWithConcurrentEvents in
> MultiVMRegionTestCase.java
> doOpsLoop
> doOpsLoopNoFlush
> {noformat}
> case 5:
> if (includeClear) {
> CCRegion.clear();
> break;
> } else {
> if (CCRegion.getAttributes().getDataPolicy().withReplication()) {
> if (oldkey != null) {
> CCRegion.putIfAbsent(oldkey, value);
> }
> break;
> } // else fall through to invalidate
> } {noformat}
> the addition of this chunk of code causes this test to fail.
> The core of the problem is that a putall and a clear are happening
> concurrently and the "system" does not respond by either clearing all entries
> or letting all entries persist.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-7600) DistributedAckRegionCCEDUnitTest and DistributedAckPersistentRegionCCEOffHeapDUnitTest fail in testConcurrentEventsOnEmptyRegion
[ https://issues.apache.org/jira/browse/GEODE-7600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17319740#comment-17319740 ] Geode Integration commented on GEODE-7600: -- Seen on support/1.12 in [DistributedTestOpenJDK11 #15|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/DistributedTestOpenJDK11/builds/15] ... see [test results|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.2-build.0190/test-results/distributedTest/1614630780/] or download [artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.2-build.0190/test-artifacts/1614630780/distributedtestfiles-OpenJDK11-1.12.2-build.0190.tgz]. > DistributedAckRegionCCEDUnitTest and > DistributedAckPersistentRegionCCEOffHeapDUnitTest fail in > testConcurrentEventsOnEmptyRegion > > > Key: GEODE-7600 > URL: https://issues.apache.org/jira/browse/GEODE-7600 > Project: Geode > Issue Type: Bug > Components: tests >Reporter: Mark Hanson >Assignee: Ernest Burghardt >Priority: Major > Labels: GeodeCommons > Fix For: 1.13.0 > > Time Spent: 5h 40m > Remaining Estimate: 0h > > DistributedAckRegionCCEDUnitTest > https://concourse.apachegeode-ci.info/teams/main/pipelines/mhansonp-mhanson-mass-test-ru-main/jobs/DistributedTestOpenJDK8/builds/2176 > DistributedAckPersistentRegionCCEOffHeapDUnitTest > https://concourse.apachegeode-ci.info/teams/main/pipelines/mhansonp-mhanson-mass-test-ru-main/jobs/DistributedTestOpenJDK8/builds/2143 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7600) DistributedAckRegionCCEDUnitTest and DistributedAckPersistentRegionCCEOffHeapDUnitTest fail in testConcurrentEventsOnEmptyRegion
[ https://issues.apache.org/jira/browse/GEODE-7600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17319739#comment-17319739 ] Geode Integration commented on GEODE-7600: -- Seen on support/1.12 in [DistributedTestOpenJDK8 #34|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/DistributedTestOpenJDK8/builds/34] ... see [test results|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.2-build.0204/test-results/distributedTest/1616810414/] or download [artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.2-build.0204/test-artifacts/1616810414/distributedtestfiles-OpenJDK8-1.12.2-build.0204.tgz]. > DistributedAckRegionCCEDUnitTest and > DistributedAckPersistentRegionCCEOffHeapDUnitTest fail in > testConcurrentEventsOnEmptyRegion > > > Key: GEODE-7600 > URL: https://issues.apache.org/jira/browse/GEODE-7600 > Project: Geode > Issue Type: Bug > Components: tests >Reporter: Mark Hanson >Assignee: Ernest Burghardt >Priority: Major > Labels: GeodeCommons > Fix For: 1.13.0 > > Time Spent: 5h 40m > Remaining Estimate: 0h > > DistributedAckRegionCCEDUnitTest > https://concourse.apachegeode-ci.info/teams/main/pipelines/mhansonp-mhanson-mass-test-ru-main/jobs/DistributedTestOpenJDK8/builds/2176 > DistributedAckPersistentRegionCCEOffHeapDUnitTest > https://concourse.apachegeode-ci.info/teams/main/pipelines/mhansonp-mhanson-mass-test-ru-main/jobs/DistributedTestOpenJDK8/builds/2143 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7702) DistributedAckRegionCCEDUnitTest > testClearOnNonReplicateWithConcurrentEvents is showing a product bug
[
https://issues.apache.org/jira/browse/GEODE-7702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17319737#comment-17319737
]
Geode Integration commented on GEODE-7702:
--
Seen on support/1.12 in [DistributedTestOpenJDK8
#44|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/DistributedTestOpenJDK8/builds/44]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.2-build.0217/test-results/distributedTest/1617984582/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.2-build.0217/test-artifacts/1617984582/distributedtestfiles-OpenJDK8-1.12.2-build.0217.tgz].
> DistributedAckRegionCCEDUnitTest >
> testClearOnNonReplicateWithConcurrentEvents is showing a product bug
> ---
>
> Key: GEODE-7702
> URL: https://issues.apache.org/jira/browse/GEODE-7702
> Project: Geode
> Issue Type: Bug
> Components: client/server
>Reporter: Mark Hanson
>Assignee: Xiaojian Zhou
>Priority: Major
> Labels: GeodeCommons
> Fix For: 1.14.0
>
>
> testClearOnNonReplicateWithConcurrentEvents in
> DistributedAckRegionCCEDUnitTest.java
> versionTestClearOnNonReplicateWithConcurrentEvents in
> MultiVMRegionTestCase.java
> doOpsLoop
> doOpsLoopNoFlush
> {noformat}
> case 5:
> if (includeClear) {
> CCRegion.clear();
> break;
> } else {
> if (CCRegion.getAttributes().getDataPolicy().withReplication()) {
> if (oldkey != null) {
> CCRegion.putIfAbsent(oldkey, value);
> }
> break;
> } // else fall through to invalidate
> } {noformat}
> the addition of this chunk of code causes this test to fail.
> The core of the problem is that a putall and a clear are happening
> concurrently and the "system" does not respond by either clearing all entries
> or letting all entries persist.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-7761) DistributedAckRegionCCEOffHeapDUnitTest > testClearOnNonReplicateWithConcurrentEvents
[
https://issues.apache.org/jira/browse/GEODE-7761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17319738#comment-17319738
]
Geode Integration commented on GEODE-7761:
--
Seen on support/1.12 in [DistributedTestOpenJDK8
#33|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/DistributedTestOpenJDK8/builds/33]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.2-build.0203/test-results/distributedTest/1616800327/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.2-build.0203/test-artifacts/1616800327/distributedtestfiles-OpenJDK8-1.12.2-build.0203.tgz].
> DistributedAckRegionCCEOffHeapDUnitTest >
> testClearOnNonReplicateWithConcurrentEvents
> -
>
> Key: GEODE-7761
> URL: https://issues.apache.org/jira/browse/GEODE-7761
> Project: Geode
> Issue Type: Bug
> Components: offheap, regions
>Reporter: Robert Houghton
>Priority: Major
> Fix For: 1.13.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> CI Failure in DistributedTestOpenJDK11
> {noformat}
> org.apache.geode.cache30.DistributedAckRegionCCEOffHeapDUnitTest >
> testClearOnNonReplicateWithConcurrentEvents FAILED
> org.awaitility.core.ConditionTimeoutException: Assertion condition
> defined as a lambda expression in
> org.apache.geode.cache30.MultiVMRegionTestCase expected:<[3]> but was:<[0]>
> within 300 seconds.
> Caused by:
> org.junit.ComparisonFailure: expected:<[3]> but was:<[0]>
> {noformat}
> Logs:
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.12.0-SNAPSHOT.0237/test-results/distributedTest/1580506766/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.12.0-SNAPSHOT.0237/test-artifacts/1580506766/distributedtestfiles-OpenJDK11-1.12.0-SNAPSHOT.0237.tgz
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-9142) Make disk size for heavy lifters parameterized
Sean Goller created GEODE-9142: -- Summary: Make disk size for heavy lifters parameterized Key: GEODE-9142 URL: https://issues.apache.org/jira/browse/GEODE-9142 Project: Geode Issue Type: Improvement Components: ci Reporter: Sean Goller We're running out of disk space on certain jobs. Make it so we can choose how much disk to allocate on a per job basis. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-9141) Hang while shutting down a cache server due to corrupted message
[
https://issues.apache.org/jira/browse/GEODE-9141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce J Schuchardt reassigned GEODE-9141:
-
Assignee: Bruce J Schuchardt
> Hang while shutting down a cache server due to corrupted message
>
>
> Key: GEODE-9141
> URL: https://issues.apache.org/jira/browse/GEODE-9141
> Project: Geode
> Issue Type: Test
> Components: membership, messaging
>Reporter: Bruce J Schuchardt
>Assignee: Bruce J Schuchardt
>Priority: Major
>
> We have a test that fails once in 5000 runs with a corrupted
> DestroyRegionMessage. It is always during CacheServer teardown when
> destroying a HARegionQueue Region.
> {noformat}
> "vm_0_thr_0_bridge_1_1_host1_6920" #144 daemon prio=5 os_prio=0
> tid=0x7fec70058800 nid=0x1d28 waiting on condition [0x7fec62063000]
>java.lang.Thread.State: TIMED_WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for <0xf4f654f8> (a
> java.util.concurrent.CountDownLatch$Sync)
> at
> java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos(AbstractQueuedSynchronizer.java:1037)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1328)
> at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:277)
> at
> org.apache.geode.internal.util.concurrent.StoppableCountDownLatch.await(StoppableCountDownLatch.java:72)
> at
> org.apache.geode.distributed.internal.ReplyProcessor21.basicWait(ReplyProcessor21.java:723)
> at
> org.apache.geode.distributed.internal.ReplyProcessor21.waitForRepliesUninterruptibly(ReplyProcessor21.java:794)
> at
> org.apache.geode.distributed.internal.ReplyProcessor21.waitForRepliesUninterruptibly(ReplyProcessor21.java:771)
> at
> org.apache.geode.distributed.internal.ReplyProcessor21.waitForRepliesUninterruptibly(ReplyProcessor21.java:857)
> at
> org.apache.geode.internal.cache.DistributedCacheOperation.waitForAckIfNeeded(DistributedCacheOperation.java:779)
> at
> org.apache.geode.internal.cache.DistributedCacheOperation._distribute(DistributedCacheOperation.java:676)
> at
> org.apache.geode.internal.cache.DistributedCacheOperation.startOperation(DistributedCacheOperation.java:277)
> at
> org.apache.geode.internal.cache.DistributedCacheOperation.distribute(DistributedCacheOperation.java:318)
> at
> org.apache.geode.internal.cache.DistributedRegion.distributeDestroyRegion(DistributedRegion.java:1865)
> at
> org.apache.geode.internal.cache.DistributedRegion.basicDestroyRegion(DistributedRegion.java:1844)
> at
> org.apache.geode.internal.cache.LocalRegion.basicDestroyRegion(LocalRegion.java:6180)
> at
> org.apache.geode.internal.cache.HARegion.destroyRegion(HARegion.java:331)
> at
> org.apache.geode.internal.cache.AbstractRegion.destroyRegion(AbstractRegion.java:476)
> at
> org.apache.geode.internal.cache.ha.HARegionQueue.destroy(HARegionQueue.java:3438)
> at
> org.apache.geode.internal.cache.ha.HARegionQueue$BlockingHARegionQueue.destroy(HARegionQueue.java:2272)
> at
> org.apache.geode.internal.cache.tier.sockets.CacheClientProxy.destroyRQ(CacheClientProxy.java:1031)
> at
> org.apache.geode.internal.cache.tier.sockets.CacheClientProxy.terminateDispatching(CacheClientProxy.java:939)
> at
> org.apache.geode.internal.cache.tier.sockets.CacheClientNotifier.shutdown(CacheClientNotifier.java:1306)
> - locked <0xf8022800> (a
> org.apache.geode.internal.cache.tier.sockets.CacheClientNotifier)
> at
> org.apache.geode.internal.cache.tier.sockets.AcceptorImpl.close(AcceptorImpl.java:1630)
> - locked <0xf5f7b888> (a java.lang.Object)
> at
> org.apache.geode.internal.cache.CacheServerImpl.stop(CacheServerImpl.java:491)
> - locked <0xf7ef2980> (a
> org.apache.geode.internal.cache.CacheServerImpl)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.stopServers(GemFireCacheImpl.java:2672)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.doClose(GemFireCacheImpl.java:2263)
> - locked <0xf5a21a08> (a java.lang.Class for
> org.apache.geode.internal.cache.GemFireCacheImpl)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.close(GemFireCacheImpl.java:2151)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.disconnect(InternalDistributedSystem.java:1559)
> - locked <0xf5a21a08> (a java.lang.Class for
> org.apache.geode.internal.cache.GemFireCacheImpl)
> at
>
[jira] [Created] (GEODE-9141) Hang while shutting down a cache server due to corrupted message
Bruce J Schuchardt created GEODE-9141:
-
Summary: Hang while shutting down a cache server due to corrupted
message
Key: GEODE-9141
URL: https://issues.apache.org/jira/browse/GEODE-9141
Project: Geode
Issue Type: Test
Components: membership, messaging
Reporter: Bruce J Schuchardt
We have a test that fails once in 5000 runs with a corrupted
DestroyRegionMessage. It is always during CacheServer teardown when destroying
a HARegionQueue Region.
{noformat}
"vm_0_thr_0_bridge_1_1_host1_6920" #144 daemon prio=5 os_prio=0
tid=0x7fec70058800 nid=0x1d28 waiting on condition [0x7fec62063000]
java.lang.Thread.State: TIMED_WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <0xf4f654f8> (a
java.util.concurrent.CountDownLatch$Sync)
at
java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos(AbstractQueuedSynchronizer.java:1037)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1328)
at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:277)
at
org.apache.geode.internal.util.concurrent.StoppableCountDownLatch.await(StoppableCountDownLatch.java:72)
at
org.apache.geode.distributed.internal.ReplyProcessor21.basicWait(ReplyProcessor21.java:723)
at
org.apache.geode.distributed.internal.ReplyProcessor21.waitForRepliesUninterruptibly(ReplyProcessor21.java:794)
at
org.apache.geode.distributed.internal.ReplyProcessor21.waitForRepliesUninterruptibly(ReplyProcessor21.java:771)
at
org.apache.geode.distributed.internal.ReplyProcessor21.waitForRepliesUninterruptibly(ReplyProcessor21.java:857)
at
org.apache.geode.internal.cache.DistributedCacheOperation.waitForAckIfNeeded(DistributedCacheOperation.java:779)
at
org.apache.geode.internal.cache.DistributedCacheOperation._distribute(DistributedCacheOperation.java:676)
at
org.apache.geode.internal.cache.DistributedCacheOperation.startOperation(DistributedCacheOperation.java:277)
at
org.apache.geode.internal.cache.DistributedCacheOperation.distribute(DistributedCacheOperation.java:318)
at
org.apache.geode.internal.cache.DistributedRegion.distributeDestroyRegion(DistributedRegion.java:1865)
at
org.apache.geode.internal.cache.DistributedRegion.basicDestroyRegion(DistributedRegion.java:1844)
at
org.apache.geode.internal.cache.LocalRegion.basicDestroyRegion(LocalRegion.java:6180)
at
org.apache.geode.internal.cache.HARegion.destroyRegion(HARegion.java:331)
at
org.apache.geode.internal.cache.AbstractRegion.destroyRegion(AbstractRegion.java:476)
at
org.apache.geode.internal.cache.ha.HARegionQueue.destroy(HARegionQueue.java:3438)
at
org.apache.geode.internal.cache.ha.HARegionQueue$BlockingHARegionQueue.destroy(HARegionQueue.java:2272)
at
org.apache.geode.internal.cache.tier.sockets.CacheClientProxy.destroyRQ(CacheClientProxy.java:1031)
at
org.apache.geode.internal.cache.tier.sockets.CacheClientProxy.terminateDispatching(CacheClientProxy.java:939)
at
org.apache.geode.internal.cache.tier.sockets.CacheClientNotifier.shutdown(CacheClientNotifier.java:1306)
- locked <0xf8022800> (a
org.apache.geode.internal.cache.tier.sockets.CacheClientNotifier)
at
org.apache.geode.internal.cache.tier.sockets.AcceptorImpl.close(AcceptorImpl.java:1630)
- locked <0xf5f7b888> (a java.lang.Object)
at
org.apache.geode.internal.cache.CacheServerImpl.stop(CacheServerImpl.java:491)
- locked <0xf7ef2980> (a
org.apache.geode.internal.cache.CacheServerImpl)
at
org.apache.geode.internal.cache.GemFireCacheImpl.stopServers(GemFireCacheImpl.java:2672)
at
org.apache.geode.internal.cache.GemFireCacheImpl.doClose(GemFireCacheImpl.java:2263)
- locked <0xf5a21a08> (a java.lang.Class for
org.apache.geode.internal.cache.GemFireCacheImpl)
at
org.apache.geode.internal.cache.GemFireCacheImpl.close(GemFireCacheImpl.java:2151)
at
org.apache.geode.distributed.internal.InternalDistributedSystem.disconnect(InternalDistributedSystem.java:1559)
- locked <0xf5a21a08> (a java.lang.Class for
org.apache.geode.internal.cache.GemFireCacheImpl)
at
org.apache.geode.distributed.internal.InternalDistributedSystem.disconnect(InternalDistributedSystem.java:1257)
at hydra.RemoteTestModule$2.run(RemoteTestModule.java:388)
{noformat}
Another server logs this corrupted message. It is almost always the same
corruption. When it's not we see the message header messed up, not a bad DSFID.
{noformat}
[fatal 2021/03/06 09:45:02.796 PST
[jira] [Updated] (GEODE-9139) SSLException in starting up a Locator
[
https://issues.apache.org/jira/browse/GEODE-9139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-9139:
--
Labels: pull-request-available (was: )
> SSLException in starting up a Locator
> -
>
> Key: GEODE-9139
> URL: https://issues.apache.org/jira/browse/GEODE-9139
> Project: Geode
> Issue Type: Bug
> Components: membership, messaging
>Reporter: Bruce J Schuchardt
>Assignee: Bruce J Schuchardt
>Priority: Major
> Labels: pull-request-available
>
> If you start up a locator using its host name, without a domain name, as a
> bind address you may get an SSLException in the form
> {noformat}
> javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException:
> No subject alternative DNS name matching hostname.domainname found
> {noformat}
> The LocatorLauncher and InternalLocator throw away the bind address string
> and later do a reverse lookup to find the fully qualified hostname to use in
> endpoint identification matching.If the locator's own TLS certificate
> doesn't have the fully qualified name in it as a Subject Alternate Name the
> connection that the Locator makes to its own location service will fail.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-7674) Partitioned region clear should handle/update lucene index
[ https://issues.apache.org/jira/browse/GEODE-7674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17319665#comment-17319665 ] ASF subversion and git services commented on GEODE-7674: Commit bab989942200490e5fe31942f1493305bbdb226f in geode's branch refs/heads/feature/GEODE-7674 from zhouxh [ https://gitbox.apache.org/repos/asf?p=geode.git;h=bab9899 ] feature/GEODE-7674: Clear on PR with lucene index should throw exception > Partitioned region clear should handle/update lucene index > -- > > Key: GEODE-7674 > URL: https://issues.apache.org/jira/browse/GEODE-7674 > Project: Geode > Issue Type: Sub-task > Components: lucene, regions >Reporter: Nabarun Nag >Priority: Major > Labels: GeodeCommons, pull-request-available > > Clear operation on partitioned region should appropriately handle lucene > indexes defined on that partitioned region. > Existing behavior (complexities in updating lucene indexes): > The lucene indexes are managed through AsyncEventQueue (AEQ); the region > operations on the clear (both for replicated and partitioned region) > generated RegionEvents, currently the AEQ does not support handling > RegionEvent. Supporting RegionEvent with AEQ is separate task which needs to > be considered outside of the clear implementation. > Till the RegionEvents are supported on AEQs, the PR clear will not be > supported on regions with Lucene indexes. > Expectation: > Throw exception for PR clear operation when there is lucene index on the > region. > Acceptance : > - Add test to verify exception is thrown when PR clear is performed on the > region with local clear. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9132) PR clear to take locks on all buckets unconditionally.
[
https://issues.apache.org/jira/browse/GEODE-9132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17319654#comment-17319654
]
ASF subversion and git services commented on GEODE-9132:
Commit a43d103b8a9973cdf03166a2fdbc16de29a120fd in geode's branch
refs/heads/feature/GEODE-7674 from Kirk Lund
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=a43d103 ]
GEODE-9132: Minor cleanup of PartitionedRegionClearTest
> PR clear to take locks on all buckets unconditionally.
> --
>
> Key: GEODE-9132
> URL: https://issues.apache.org/jira/browse/GEODE-9132
> Project: Geode
> Issue Type: Sub-task
> Components: regions
>Reporter: Anilkumar Gingade
>Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
>
> Existing behavior:
> PR clear employs two different locking behavior based on the presence of
> client subscription and cache-listeners. If there is no subscription or
> cache-listener it takes the bucket locks on local nodes else it will send a
> message to take locks on all buckets before doing the clear.
> Expected behavior:
> To keep the code/behavior simple PR clear to employ single locking behavior.
> It will take the lock on all buckets before doing clear irrespective of
> subscription or cache-listener presence.
> Solution:
> Remove the following check that drives taking lock on local nodes:
> {code}
> boolean acquireClearLockForNotification =
> (partitionedRegion.hasAnyClientsInterested() ||
> partitionedRegion.hasListener());
> {code}
> And it will call:
> {code}
> obtainLockForClear(regionEvent);
> {code}
> Also remove the logic taking lock in individual nodes in:
> DistributedRegion.obtainWriteLocksForClear()
> Remove:
> if (!localLockedAlready) {
> lockLocallyForClear(getDistributionManager(), getMyId(), regionEvent);
> }
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-7674) Partitioned region clear should handle/update lucene index
[ https://issues.apache.org/jira/browse/GEODE-7674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17319656#comment-17319656 ] ASF subversion and git services commented on GEODE-7674: Commit e093cec9906ab563534730873be0f3b9d5e6e030 in geode's branch refs/heads/feature/GEODE-7674 from Xiaojian Zhou [ https://gitbox.apache.org/repos/asf?p=geode.git;h=e093cec ] Merge branch 'feature/GEODE-7665' into feature/GEODE-7674 > Partitioned region clear should handle/update lucene index > -- > > Key: GEODE-7674 > URL: https://issues.apache.org/jira/browse/GEODE-7674 > Project: Geode > Issue Type: Sub-task > Components: lucene, regions >Reporter: Nabarun Nag >Priority: Major > Labels: GeodeCommons, pull-request-available > > Clear operation on partitioned region should appropriately handle lucene > indexes defined on that partitioned region. > Existing behavior (complexities in updating lucene indexes): > The lucene indexes are managed through AsyncEventQueue (AEQ); the region > operations on the clear (both for replicated and partitioned region) > generated RegionEvents, currently the AEQ does not support handling > RegionEvent. Supporting RegionEvent with AEQ is separate task which needs to > be considered outside of the clear implementation. > Till the RegionEvents are supported on AEQs, the PR clear will not be > supported on regions with Lucene indexes. > Expectation: > Throw exception for PR clear operation when there is lucene index on the > region. > Acceptance : > - Add test to verify exception is thrown when PR clear is performed on the > region with local clear. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7665) Ability to clear a Partitioned Region
[ https://issues.apache.org/jira/browse/GEODE-7665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17319655#comment-17319655 ] ASF subversion and git services commented on GEODE-7665: Commit e093cec9906ab563534730873be0f3b9d5e6e030 in geode's branch refs/heads/feature/GEODE-7674 from Xiaojian Zhou [ https://gitbox.apache.org/repos/asf?p=geode.git;h=e093cec ] Merge branch 'feature/GEODE-7665' into feature/GEODE-7674 > Ability to clear a Partitioned Region > - > > Key: GEODE-7665 > URL: https://issues.apache.org/jira/browse/GEODE-7665 > Project: Geode > Issue Type: New Feature > Components: regions >Reporter: Nabarun Nag >Priority: Major > Labels: GeodeCommons > > With the successful voting of the RFC for implementing clear operation on > Partitioned Region > [[https://cwiki.apache.org/confluence/display/GEODE/Support+for+clear+operation+on+partitioned+region]] > we are starting the code implementation. > > Details of the implementation and design are maintained in the RFC document > mentioned above. This ticket will act as a parent Jira under which all the > subsequent sub-JIRAs will be created. This ticket will be closed once all the > sub jiras are implemented. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9138) Add warning in server logs when data event is ignored as a duplicate
[ https://issues.apache.org/jira/browse/GEODE-9138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-9138: - Component/s: logging > Add warning in server logs when data event is ignored as a duplicate > > > Key: GEODE-9138 > URL: https://issues.apache.org/jira/browse/GEODE-9138 > Project: Geode > Issue Type: Bug > Components: client/server, logging >Reporter: Diane Hardman >Priority: Major > > Under certain rare conditions, a client may send or resend a data event with > an eventId that causes the server to interpret it as a duplicate event and > discard it. > It is currently impossible to trace when this happens without extra logging > added. > From Barry: > No, if the server thinks it has seen the event, it silently eats it. See > DistributedEventTracker.hasSeenEvent. It has a trace log message but thats it. > The log message that tracks this behavior in the server needs to be added > permanently. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9140) CI Failure: DeploymentManagementUpgradeTest > newLocatorCanReadOldConfigurationData fails with ComparisonFailure
[
https://issues.apache.org/jira/browse/GEODE-9140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-9140:
-
Description:
{noformat}
org.apache.geode.management.DeploymentManagementUpgradeTest >
newLocatorCanReadOldConfigurationData[1.13.2] FAILED
org.junit.ComparisonFailure: [Exit value from process started by
[c0f4fa64150ca1ed: gfsh -e start locator --name=test --port=28819
--http-service-port=28818 --J=-Dgemfire.jmx-manager-port=28820]] expected:<[0]>
but was:<[1]>
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at
org.apache.geode.test.junit.rules.gfsh.GfshExecution.awaitTermination(GfshExecution.java:103)
at
org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:143)
at
org.apache.geode.test.junit.rules.gfsh.GfshScript.execute(GfshScript.java:160)
at
org.apache.geode.management.DeploymentManagementUpgradeTest.newLocatorCanReadOldConfigurationData(DeploymentManagementUpgradeTest.java:99)
{noformat}
was:
org.apache.geode.management.DeploymentManagementUpgradeTest >
newLocatorCanReadOldConfigurationData[1.13.2] FAILED
org.junit.ComparisonFailure: [Exit value from process started by
[c0f4fa64150ca1ed: gfsh -e start locator --name=test --port=28819
--http-service-port=28818 --J=-Dgemfire.jmx-manager-port=28820]] expected:<[0]>
but was:<[1]>
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at
org.apache.geode.test.junit.rules.gfsh.GfshExecution.awaitTermination(GfshExecution.java:103)
at
org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:143)
at
org.apache.geode.test.junit.rules.gfsh.GfshScript.execute(GfshScript.java:160)
at
org.apache.geode.management.DeploymentManagementUpgradeTest.newLocatorCanReadOldConfigurationData(DeploymentManagementUpgradeTest.java:99)
> CI Failure: DeploymentManagementUpgradeTest >
> newLocatorCanReadOldConfigurationData fails with ComparisonFailure
>
>
> Key: GEODE-9140
> URL: https://issues.apache.org/jira/browse/GEODE-9140
> Project: Geode
> Issue Type: Wish
> Components: gfsh, management
>Reporter: Kirk Lund
>Priority: Major
>
> {noformat}
> org.apache.geode.management.DeploymentManagementUpgradeTest >
> newLocatorCanReadOldConfigurationData[1.13.2] FAILED
> org.junit.ComparisonFailure: [Exit value from process started by
> [c0f4fa64150ca1ed: gfsh -e start locator --name=test --port=28819
> --http-service-port=28818 --J=-Dgemfire.jmx-manager-port=28820]]
> expected:<[0]> but was:<[1]>
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshExecution.awaitTermination(GfshExecution.java:103)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:143)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshScript.execute(GfshScript.java:160)
> at
> org.apache.geode.management.DeploymentManagementUpgradeTest.newLocatorCanReadOldConfigurationData(DeploymentManagementUpgradeTest.java:99)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-9140) CI Failure: DeploymentManagementUpgradeTest > newLocatorCanReadOldConfigurationData fails with ComparisonFailure
Kirk Lund created GEODE-9140: Summary: CI Failure: DeploymentManagementUpgradeTest > newLocatorCanReadOldConfigurationData fails with ComparisonFailure Key: GEODE-9140 URL: https://issues.apache.org/jira/browse/GEODE-9140 Project: Geode Issue Type: Wish Components: gfsh, management Reporter: Kirk Lund org.apache.geode.management.DeploymentManagementUpgradeTest > newLocatorCanReadOldConfigurationData[1.13.2] FAILED org.junit.ComparisonFailure: [Exit value from process started by [c0f4fa64150ca1ed: gfsh -e start locator --name=test --port=28819 --http-service-port=28818 --J=-Dgemfire.jmx-manager-port=28820]] expected:<[0]> but was:<[1]> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at org.apache.geode.test.junit.rules.gfsh.GfshExecution.awaitTermination(GfshExecution.java:103) at org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:143) at org.apache.geode.test.junit.rules.gfsh.GfshScript.execute(GfshScript.java:160) at org.apache.geode.management.DeploymentManagementUpgradeTest.newLocatorCanReadOldConfigurationData(DeploymentManagementUpgradeTest.java:99) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9139) SSLException in starting up a Locator
[
https://issues.apache.org/jira/browse/GEODE-9139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce J Schuchardt updated GEODE-9139:
--
Issue Type: Bug (was: Test)
> SSLException in starting up a Locator
> -
>
> Key: GEODE-9139
> URL: https://issues.apache.org/jira/browse/GEODE-9139
> Project: Geode
> Issue Type: Bug
> Components: membership, messaging
>Reporter: Bruce J Schuchardt
>Assignee: Bruce J Schuchardt
>Priority: Major
>
> If you start up a locator using its host name, without a domain name, as a
> bind address you may get an SSLException in the form
> {noformat}
> javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException:
> No subject alternative DNS name matching hostname.domainname found
> {noformat}
> The LocatorLauncher and InternalLocator throw away the bind address string
> and later do a reverse lookup to find the fully qualified hostname to use in
> endpoint identification matching.If the locator's own TLS certificate
> doesn't have the fully qualified name in it as a Subject Alternate Name the
> connection that the Locator makes to its own location service will fail.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (GEODE-9139) SSLException in starting up a Locator
[
https://issues.apache.org/jira/browse/GEODE-9139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce J Schuchardt reassigned GEODE-9139:
-
Assignee: Bruce J Schuchardt
> SSLException in starting up a Locator
> -
>
> Key: GEODE-9139
> URL: https://issues.apache.org/jira/browse/GEODE-9139
> Project: Geode
> Issue Type: Test
> Components: membership, messaging
>Reporter: Bruce J Schuchardt
>Assignee: Bruce J Schuchardt
>Priority: Major
>
> If you start up a locator using its host name, without a domain name, as a
> bind address you may get an SSLException in the form
> {noformat}
> javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException:
> No subject alternative DNS name matching hostname.domainname found
> {noformat}
> The LocatorLauncher and InternalLocator throw away the bind address string
> and later do a reverse lookup to find the fully qualified hostname to use in
> endpoint identification matching.If the locator's own TLS certificate
> doesn't have the fully qualified name in it as a Subject Alternate Name the
> connection that the Locator makes to its own location service will fail.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-9139) SSLException in starting up a Locator
Bruce J Schuchardt created GEODE-9139:
-
Summary: SSLException in starting up a Locator
Key: GEODE-9139
URL: https://issues.apache.org/jira/browse/GEODE-9139
Project: Geode
Issue Type: Test
Components: membership, messaging
Reporter: Bruce J Schuchardt
If you start up a locator using its host name, without a domain name, as a bind
address you may get an SSLException in the form
{noformat}
javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException:
No subject alternative DNS name matching hostname.domainname found
{noformat}
The LocatorLauncher and InternalLocator throw away the bind address string and
later do a reverse lookup to find the fully qualified hostname to use in
endpoint identification matching.If the locator's own TLS certificate
doesn't have the fully qualified name in it as a Subject Alternate Name the
connection that the Locator makes to its own location service will fail.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-9120) CI: ClientServerCacheOperationDUnitTest > largeObjectPutWithReadTimeoutThrowsException FAILED due with NoAvailableLocatorsException: Unable to connect to any locators in
[
https://issues.apache.org/jira/browse/GEODE-9120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-9120:
-
Labels: GeodeOperationAPI (was: )
> CI: ClientServerCacheOperationDUnitTest >
> largeObjectPutWithReadTimeoutThrowsException FAILED due with
> NoAvailableLocatorsException: Unable to connect to any locators in the list
> --
>
> Key: GEODE-9120
> URL: https://issues.apache.org/jira/browse/GEODE-9120
> Project: Geode
> Issue Type: Bug
> Components: membership
>Reporter: Nabarun Nag
>Priority: Major
> Labels: GeodeOperationAPI
>
>
> {noformat}
> org.apache.geode.cache30.ClientServerCacheOperationDUnitTest >
> largeObjectPutWithReadTimeoutThrowsException FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache30.ClientServerCacheOperationDUnitTest$$Lambda$69/1107577048.run
> in VM 2 running on Host b3fa8968947d with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:448)
> at
> org.apache.geode.cache30.ClientServerCacheOperationDUnitTest.largeObjectPutWithReadTimeoutThrowsException(ClientServerCacheOperationDUnitTest.java:118)
> Caused by:
> org.apache.geode.cache.client.NoAvailableLocatorsException: Unable to
> connect to any locators in the list [HostAndPort[b3fa8968947d:34777],
> HostAndPort[localhost:34777]]
> at
> org.apache.geode.cache.client.internal.AutoConnectionSourceImpl.findServer(AutoConnectionSourceImpl.java:174)
> at
> org.apache.geode.cache.client.internal.ConnectionFactoryImpl.createClientToServerConnection(ConnectionFactoryImpl.java:198)
> at
> org.apache.geode.cache.client.internal.pooling.ConnectionManagerImpl.createPooledConnection(ConnectionManagerImpl.java:196)
> at
> org.apache.geode.cache.client.internal.pooling.ConnectionManagerImpl.createPooledConnection(ConnectionManagerImpl.java:190)
> at
> org.apache.geode.cache.client.internal.pooling.ConnectionManagerImpl.borrowConnection(ConnectionManagerImpl.java:276)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:129)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:112)
> at
> org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:797)
> at
> org.apache.geode.cache.client.internal.GetOp.execute(GetOp.java:91)
> at
> org.apache.geode.cache.client.internal.ServerRegionProxy.get(ServerRegionProxy.java:114)
> at
> org.apache.geode.internal.cache.LocalRegion.findObjectInSystem(LocalRegion.java:2802)
> at
> org.apache.geode.internal.cache.LocalRegion.getObject(LocalRegion.java:1469)
> at
> org.apache.geode.internal.cache.LocalRegion.nonTxnFindObject(LocalRegion.java:1442)
> at
> org.apache.geode.internal.cache.LocalRegionDataView.findObject(LocalRegionDataView.java:197)
> at
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1379)
> at
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1318)
> at
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1303)
> at
> org.apache.geode.internal.cache.AbstractRegion.get(AbstractRegion.java:439)
> at
> org.apache.geode.cache30.ClientServerCacheOperationDUnitTest.lambda$largeObjectPutWithReadTimeoutThrowsException$3ab01cf6$2(ClientServerCacheOperationDUnitTest.java:121){noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> [*http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0116/test-results/distributedTest/1617652711/*]
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> [*http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0116/test-artifacts/1617652711/distributedtestfiles-OpenJDK8-1.15.0-build.0116.tgz*]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-9120) CI: ClientServerCacheOperationDUnitTest > largeObjectPutWithReadTimeoutThrowsException FAILED due with NoAvailableLocatorsException: Unable to connect to any locators in
[
https://issues.apache.org/jira/browse/GEODE-9120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-9120:
-
Labels: (was: GeodeOperationAPI)
> CI: ClientServerCacheOperationDUnitTest >
> largeObjectPutWithReadTimeoutThrowsException FAILED due with
> NoAvailableLocatorsException: Unable to connect to any locators in the list
> --
>
> Key: GEODE-9120
> URL: https://issues.apache.org/jira/browse/GEODE-9120
> Project: Geode
> Issue Type: Bug
> Components: membership
>Reporter: Nabarun Nag
>Priority: Major
>
>
> {noformat}
> org.apache.geode.cache30.ClientServerCacheOperationDUnitTest >
> largeObjectPutWithReadTimeoutThrowsException FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache30.ClientServerCacheOperationDUnitTest$$Lambda$69/1107577048.run
> in VM 2 running on Host b3fa8968947d with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:448)
> at
> org.apache.geode.cache30.ClientServerCacheOperationDUnitTest.largeObjectPutWithReadTimeoutThrowsException(ClientServerCacheOperationDUnitTest.java:118)
> Caused by:
> org.apache.geode.cache.client.NoAvailableLocatorsException: Unable to
> connect to any locators in the list [HostAndPort[b3fa8968947d:34777],
> HostAndPort[localhost:34777]]
> at
> org.apache.geode.cache.client.internal.AutoConnectionSourceImpl.findServer(AutoConnectionSourceImpl.java:174)
> at
> org.apache.geode.cache.client.internal.ConnectionFactoryImpl.createClientToServerConnection(ConnectionFactoryImpl.java:198)
> at
> org.apache.geode.cache.client.internal.pooling.ConnectionManagerImpl.createPooledConnection(ConnectionManagerImpl.java:196)
> at
> org.apache.geode.cache.client.internal.pooling.ConnectionManagerImpl.createPooledConnection(ConnectionManagerImpl.java:190)
> at
> org.apache.geode.cache.client.internal.pooling.ConnectionManagerImpl.borrowConnection(ConnectionManagerImpl.java:276)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:129)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:112)
> at
> org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:797)
> at
> org.apache.geode.cache.client.internal.GetOp.execute(GetOp.java:91)
> at
> org.apache.geode.cache.client.internal.ServerRegionProxy.get(ServerRegionProxy.java:114)
> at
> org.apache.geode.internal.cache.LocalRegion.findObjectInSystem(LocalRegion.java:2802)
> at
> org.apache.geode.internal.cache.LocalRegion.getObject(LocalRegion.java:1469)
> at
> org.apache.geode.internal.cache.LocalRegion.nonTxnFindObject(LocalRegion.java:1442)
> at
> org.apache.geode.internal.cache.LocalRegionDataView.findObject(LocalRegionDataView.java:197)
> at
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1379)
> at
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1318)
> at
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1303)
> at
> org.apache.geode.internal.cache.AbstractRegion.get(AbstractRegion.java:439)
> at
> org.apache.geode.cache30.ClientServerCacheOperationDUnitTest.lambda$largeObjectPutWithReadTimeoutThrowsException$3ab01cf6$2(ClientServerCacheOperationDUnitTest.java:121){noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> [*http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0116/test-results/distributedTest/1617652711/*]
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> [*http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0116/test-artifacts/1617652711/distributedtestfiles-OpenJDK8-1.15.0-build.0116.tgz*]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-8616) ClientServerCacheOperationDUnitTest > largeObjectPutWithReadTimeoutThrowsException fails with ServerConnectivityException : Pool unexpected socket timed out on client
[
https://issues.apache.org/jira/browse/GEODE-8616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-8616:
-
Labels: GeodeOperationAPI flaky-test (was: flaky-test)
> ClientServerCacheOperationDUnitTest >
> largeObjectPutWithReadTimeoutThrowsException fails with
> ServerConnectivityException : Pool unexpected socket timed out on client
> --
>
> Key: GEODE-8616
> URL: https://issues.apache.org/jira/browse/GEODE-8616
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.12.1
>Reporter: Donal Evans
>Priority: Major
> Labels: GeodeOperationAPI, flaky-test
>
> {noformat}
> > Task :geode-core:distributedTest
> org.apache.geode.cache30.ClientServerCacheOperationDUnitTest >
> largeObjectPutWithReadTimeoutThrowsException FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache30.ClientServerCacheOperationDUnitTest$$Lambda$177/0x000100b52040.run
> in VM 2 running on Host c1346ab7b3e3 with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:610)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:437)
> at
> org.apache.geode.cache30.ClientServerCacheOperationDUnitTest.largeObjectPutWithReadTimeoutThrowsException(ClientServerCacheOperationDUnitTest.java:117)
> Caused by:
> org.apache.geode.cache.client.ServerConnectivityException: Pool
> unexpected socket timed out on client connection=Pooled Connection to
> c1346ab7b3e3:35437: Connection[DESTROYED]). Server unreachable: could not
> connect after 1 attempts
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:659)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:501)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:153)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:108)
> at
> org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:774)
> at
> org.apache.geode.cache.client.internal.GetOp.execute(GetOp.java:91)
> at
> org.apache.geode.cache.client.internal.ServerRegionProxy.get(ServerRegionProxy.java:116)
> at
> org.apache.geode.internal.cache.LocalRegion.findObjectInSystem(LocalRegion.java:2795)
> at
> org.apache.geode.internal.cache.LocalRegion.getObject(LocalRegion.java:1472)
> at
> org.apache.geode.internal.cache.LocalRegion.nonTxnFindObject(LocalRegion.java:1445)
> at
> org.apache.geode.internal.cache.LocalRegionDataView.findObject(LocalRegionDataView.java:196)
> at
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1382)
> at
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1321)
> at
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1306)
> at
> org.apache.geode.internal.cache.AbstractRegion.get(AbstractRegion.java:436)
> at
> org.apache.geode.cache30.ClientServerCacheOperationDUnitTest.lambda$largeObjectPutWithReadTimeoutThrowsException$3ab01cf6$2(ClientServerCacheOperationDUnitTest.java:120)
> {noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.1-build.0106/test-results/distributedTest/1601514101/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.1-build.0106/test-artifacts/1601514101/distributedtestfiles-OpenJDK11-1.12.1-build.0106.tgz
> This is a flaky failure.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-8616) ClientServerCacheOperationDUnitTest > largeObjectPutWithReadTimeoutThrowsException fails with ServerConnectivityException : Pool unexpected socket timed out on client
[
https://issues.apache.org/jira/browse/GEODE-8616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-8616:
-
Summary: ClientServerCacheOperationDUnitTest >
largeObjectPutWithReadTimeoutThrowsException fails with
ServerConnectivityException : Pool unexpected socket timed out on client (was:
ClientServerCacheOperationDUnitTest >
largeObjectPutWithReadTimeoutThrowsException fails with "Pool unexpected socket
timed out on client")
> ClientServerCacheOperationDUnitTest >
> largeObjectPutWithReadTimeoutThrowsException fails with
> ServerConnectivityException : Pool unexpected socket timed out on client
> --
>
> Key: GEODE-8616
> URL: https://issues.apache.org/jira/browse/GEODE-8616
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.12.1
>Reporter: Donal Evans
>Priority: Major
> Labels: flaky-test
>
> {noformat}
> > Task :geode-core:distributedTest
> org.apache.geode.cache30.ClientServerCacheOperationDUnitTest >
> largeObjectPutWithReadTimeoutThrowsException FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache30.ClientServerCacheOperationDUnitTest$$Lambda$177/0x000100b52040.run
> in VM 2 running on Host c1346ab7b3e3 with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:610)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:437)
> at
> org.apache.geode.cache30.ClientServerCacheOperationDUnitTest.largeObjectPutWithReadTimeoutThrowsException(ClientServerCacheOperationDUnitTest.java:117)
> Caused by:
> org.apache.geode.cache.client.ServerConnectivityException: Pool
> unexpected socket timed out on client connection=Pooled Connection to
> c1346ab7b3e3:35437: Connection[DESTROYED]). Server unreachable: could not
> connect after 1 attempts
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:659)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:501)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:153)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:108)
> at
> org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:774)
> at
> org.apache.geode.cache.client.internal.GetOp.execute(GetOp.java:91)
> at
> org.apache.geode.cache.client.internal.ServerRegionProxy.get(ServerRegionProxy.java:116)
> at
> org.apache.geode.internal.cache.LocalRegion.findObjectInSystem(LocalRegion.java:2795)
> at
> org.apache.geode.internal.cache.LocalRegion.getObject(LocalRegion.java:1472)
> at
> org.apache.geode.internal.cache.LocalRegion.nonTxnFindObject(LocalRegion.java:1445)
> at
> org.apache.geode.internal.cache.LocalRegionDataView.findObject(LocalRegionDataView.java:196)
> at
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1382)
> at
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1321)
> at
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1306)
> at
> org.apache.geode.internal.cache.AbstractRegion.get(AbstractRegion.java:436)
> at
> org.apache.geode.cache30.ClientServerCacheOperationDUnitTest.lambda$largeObjectPutWithReadTimeoutThrowsException$3ab01cf6$2(ClientServerCacheOperationDUnitTest.java:120)
> {noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.1-build.0106/test-results/distributedTest/1601514101/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.1-build.0106/test-artifacts/1601514101/distributedtestfiles-OpenJDK11-1.12.1-build.0106.tgz
> This is a flaky failure.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-8616) ClientServerCacheOperationDUnitTest > largeObjectPutWithReadTimeoutThrowsException fails with ServerConnectivityException : Pool unexpected socket timed out on client
[
https://issues.apache.org/jira/browse/GEODE-8616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17319617#comment-17319617
]
Geode Integration commented on GEODE-8616:
--
Seen in [DistributedTestOpenJDK8
#143|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/143]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0131/test-results/distributedTest/1618011029/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0131/test-artifacts/1618011029/distributedtestfiles-OpenJDK8-1.15.0-build.0131.tgz].
> ClientServerCacheOperationDUnitTest >
> largeObjectPutWithReadTimeoutThrowsException fails with
> ServerConnectivityException : Pool unexpected socket timed out on client
> --
>
> Key: GEODE-8616
> URL: https://issues.apache.org/jira/browse/GEODE-8616
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.12.1
>Reporter: Donal Evans
>Priority: Major
> Labels: flaky-test
>
> {noformat}
> > Task :geode-core:distributedTest
> org.apache.geode.cache30.ClientServerCacheOperationDUnitTest >
> largeObjectPutWithReadTimeoutThrowsException FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache30.ClientServerCacheOperationDUnitTest$$Lambda$177/0x000100b52040.run
> in VM 2 running on Host c1346ab7b3e3 with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:610)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:437)
> at
> org.apache.geode.cache30.ClientServerCacheOperationDUnitTest.largeObjectPutWithReadTimeoutThrowsException(ClientServerCacheOperationDUnitTest.java:117)
> Caused by:
> org.apache.geode.cache.client.ServerConnectivityException: Pool
> unexpected socket timed out on client connection=Pooled Connection to
> c1346ab7b3e3:35437: Connection[DESTROYED]). Server unreachable: could not
> connect after 1 attempts
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:659)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:501)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:153)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:108)
> at
> org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:774)
> at
> org.apache.geode.cache.client.internal.GetOp.execute(GetOp.java:91)
> at
> org.apache.geode.cache.client.internal.ServerRegionProxy.get(ServerRegionProxy.java:116)
> at
> org.apache.geode.internal.cache.LocalRegion.findObjectInSystem(LocalRegion.java:2795)
> at
> org.apache.geode.internal.cache.LocalRegion.getObject(LocalRegion.java:1472)
> at
> org.apache.geode.internal.cache.LocalRegion.nonTxnFindObject(LocalRegion.java:1445)
> at
> org.apache.geode.internal.cache.LocalRegionDataView.findObject(LocalRegionDataView.java:196)
> at
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1382)
> at
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1321)
> at
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1306)
> at
> org.apache.geode.internal.cache.AbstractRegion.get(AbstractRegion.java:436)
> at
> org.apache.geode.cache30.ClientServerCacheOperationDUnitTest.lambda$largeObjectPutWithReadTimeoutThrowsException$3ab01cf6$2(ClientServerCacheOperationDUnitTest.java:120)
> {noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.1-build.0106/test-results/distributedTest/1601514101/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.1-build.0106/test-artifacts/1601514101/distributedtestfiles-OpenJDK11-1.12.1-build.0106.tgz
> This is a flaky failure.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-9120) CI: ClientServerCacheOperationDUnitTest > largeObjectPutWithReadTimeoutThrowsException FAILED due with NoAvailableLocatorsException
[
https://issues.apache.org/jira/browse/GEODE-9120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-9120:
-
Summary: CI: ClientServerCacheOperationDUnitTest >
largeObjectPutWithReadTimeoutThrowsException FAILED due with
NoAvailableLocatorsException (was: CI: ClientServerCacheOperationDUnitTest >
largeObjectPutWithReadTimeoutThrowsException FAILED due to
NoAvailableLocatorsException)
> CI: ClientServerCacheOperationDUnitTest >
> largeObjectPutWithReadTimeoutThrowsException FAILED due with
> NoAvailableLocatorsException
> ---
>
> Key: GEODE-9120
> URL: https://issues.apache.org/jira/browse/GEODE-9120
> Project: Geode
> Issue Type: Bug
> Components: membership
>Reporter: Nabarun Nag
>Priority: Major
>
>
> {noformat}
> org.apache.geode.cache30.ClientServerCacheOperationDUnitTest >
> largeObjectPutWithReadTimeoutThrowsException FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache30.ClientServerCacheOperationDUnitTest$$Lambda$69/1107577048.run
> in VM 2 running on Host b3fa8968947d with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:448)
> at
> org.apache.geode.cache30.ClientServerCacheOperationDUnitTest.largeObjectPutWithReadTimeoutThrowsException(ClientServerCacheOperationDUnitTest.java:118)
> Caused by:
> org.apache.geode.cache.client.NoAvailableLocatorsException: Unable to
> connect to any locators in the list [HostAndPort[b3fa8968947d:34777],
> HostAndPort[localhost:34777]]
> at
> org.apache.geode.cache.client.internal.AutoConnectionSourceImpl.findServer(AutoConnectionSourceImpl.java:174)
> at
> org.apache.geode.cache.client.internal.ConnectionFactoryImpl.createClientToServerConnection(ConnectionFactoryImpl.java:198)
> at
> org.apache.geode.cache.client.internal.pooling.ConnectionManagerImpl.createPooledConnection(ConnectionManagerImpl.java:196)
> at
> org.apache.geode.cache.client.internal.pooling.ConnectionManagerImpl.createPooledConnection(ConnectionManagerImpl.java:190)
> at
> org.apache.geode.cache.client.internal.pooling.ConnectionManagerImpl.borrowConnection(ConnectionManagerImpl.java:276)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:129)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:112)
> at
> org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:797)
> at
> org.apache.geode.cache.client.internal.GetOp.execute(GetOp.java:91)
> at
> org.apache.geode.cache.client.internal.ServerRegionProxy.get(ServerRegionProxy.java:114)
> at
> org.apache.geode.internal.cache.LocalRegion.findObjectInSystem(LocalRegion.java:2802)
> at
> org.apache.geode.internal.cache.LocalRegion.getObject(LocalRegion.java:1469)
> at
> org.apache.geode.internal.cache.LocalRegion.nonTxnFindObject(LocalRegion.java:1442)
> at
> org.apache.geode.internal.cache.LocalRegionDataView.findObject(LocalRegionDataView.java:197)
> at
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1379)
> at
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1318)
> at
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1303)
> at
> org.apache.geode.internal.cache.AbstractRegion.get(AbstractRegion.java:439)
> at
> org.apache.geode.cache30.ClientServerCacheOperationDUnitTest.lambda$largeObjectPutWithReadTimeoutThrowsException$3ab01cf6$2(ClientServerCacheOperationDUnitTest.java:121){noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> [*http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0116/test-results/distributedTest/1617652711/*]
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> [*http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0116/test-artifacts/1617652711/distributedtestfiles-OpenJDK8-1.15.0-build.0116.tgz*]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-9120) CI: ClientServerCacheOperationDUnitTest > largeObjectPutWithReadTimeoutThrowsException FAILED due with NoAvailableLocatorsException: Unable to connect to any locators in
[
https://issues.apache.org/jira/browse/GEODE-9120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-9120:
-
Summary: CI: ClientServerCacheOperationDUnitTest >
largeObjectPutWithReadTimeoutThrowsException FAILED due with
NoAvailableLocatorsException: Unable to connect to any locators in the list
(was: CI: ClientServerCacheOperationDUnitTest >
largeObjectPutWithReadTimeoutThrowsException FAILED due with
NoAvailableLocatorsException)
> CI: ClientServerCacheOperationDUnitTest >
> largeObjectPutWithReadTimeoutThrowsException FAILED due with
> NoAvailableLocatorsException: Unable to connect to any locators in the list
> --
>
> Key: GEODE-9120
> URL: https://issues.apache.org/jira/browse/GEODE-9120
> Project: Geode
> Issue Type: Bug
> Components: membership
>Reporter: Nabarun Nag
>Priority: Major
>
>
> {noformat}
> org.apache.geode.cache30.ClientServerCacheOperationDUnitTest >
> largeObjectPutWithReadTimeoutThrowsException FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache30.ClientServerCacheOperationDUnitTest$$Lambda$69/1107577048.run
> in VM 2 running on Host b3fa8968947d with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:448)
> at
> org.apache.geode.cache30.ClientServerCacheOperationDUnitTest.largeObjectPutWithReadTimeoutThrowsException(ClientServerCacheOperationDUnitTest.java:118)
> Caused by:
> org.apache.geode.cache.client.NoAvailableLocatorsException: Unable to
> connect to any locators in the list [HostAndPort[b3fa8968947d:34777],
> HostAndPort[localhost:34777]]
> at
> org.apache.geode.cache.client.internal.AutoConnectionSourceImpl.findServer(AutoConnectionSourceImpl.java:174)
> at
> org.apache.geode.cache.client.internal.ConnectionFactoryImpl.createClientToServerConnection(ConnectionFactoryImpl.java:198)
> at
> org.apache.geode.cache.client.internal.pooling.ConnectionManagerImpl.createPooledConnection(ConnectionManagerImpl.java:196)
> at
> org.apache.geode.cache.client.internal.pooling.ConnectionManagerImpl.createPooledConnection(ConnectionManagerImpl.java:190)
> at
> org.apache.geode.cache.client.internal.pooling.ConnectionManagerImpl.borrowConnection(ConnectionManagerImpl.java:276)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:129)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:112)
> at
> org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:797)
> at
> org.apache.geode.cache.client.internal.GetOp.execute(GetOp.java:91)
> at
> org.apache.geode.cache.client.internal.ServerRegionProxy.get(ServerRegionProxy.java:114)
> at
> org.apache.geode.internal.cache.LocalRegion.findObjectInSystem(LocalRegion.java:2802)
> at
> org.apache.geode.internal.cache.LocalRegion.getObject(LocalRegion.java:1469)
> at
> org.apache.geode.internal.cache.LocalRegion.nonTxnFindObject(LocalRegion.java:1442)
> at
> org.apache.geode.internal.cache.LocalRegionDataView.findObject(LocalRegionDataView.java:197)
> at
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1379)
> at
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1318)
> at
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1303)
> at
> org.apache.geode.internal.cache.AbstractRegion.get(AbstractRegion.java:439)
> at
> org.apache.geode.cache30.ClientServerCacheOperationDUnitTest.lambda$largeObjectPutWithReadTimeoutThrowsException$3ab01cf6$2(ClientServerCacheOperationDUnitTest.java:121){noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> [*http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0116/test-results/distributedTest/1617652711/*]
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> [*http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0116/test-artifacts/1617652711/distributedtestfiles-OpenJDK8-1.15.0-build.0116.tgz*]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-9120) CI: ClientServerCacheOperationDUnitTest > largeObjectPutWithReadTimeoutThrowsException FAILED due to NoAvailableLocatorsException
[
https://issues.apache.org/jira/browse/GEODE-9120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-9120:
-
Summary: CI: ClientServerCacheOperationDUnitTest >
largeObjectPutWithReadTimeoutThrowsException FAILED due to
NoAvailableLocatorsException (was: CI: ClientServerCacheOperationDUnitTest >
largeObjectPutWithReadTimeoutThrowsException FAILED)
> CI: ClientServerCacheOperationDUnitTest >
> largeObjectPutWithReadTimeoutThrowsException FAILED due to
> NoAvailableLocatorsException
> -
>
> Key: GEODE-9120
> URL: https://issues.apache.org/jira/browse/GEODE-9120
> Project: Geode
> Issue Type: Bug
> Components: membership
>Reporter: Nabarun Nag
>Priority: Major
>
>
> {noformat}
> org.apache.geode.cache30.ClientServerCacheOperationDUnitTest >
> largeObjectPutWithReadTimeoutThrowsException FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache30.ClientServerCacheOperationDUnitTest$$Lambda$69/1107577048.run
> in VM 2 running on Host b3fa8968947d with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:448)
> at
> org.apache.geode.cache30.ClientServerCacheOperationDUnitTest.largeObjectPutWithReadTimeoutThrowsException(ClientServerCacheOperationDUnitTest.java:118)
> Caused by:
> org.apache.geode.cache.client.NoAvailableLocatorsException: Unable to
> connect to any locators in the list [HostAndPort[b3fa8968947d:34777],
> HostAndPort[localhost:34777]]
> at
> org.apache.geode.cache.client.internal.AutoConnectionSourceImpl.findServer(AutoConnectionSourceImpl.java:174)
> at
> org.apache.geode.cache.client.internal.ConnectionFactoryImpl.createClientToServerConnection(ConnectionFactoryImpl.java:198)
> at
> org.apache.geode.cache.client.internal.pooling.ConnectionManagerImpl.createPooledConnection(ConnectionManagerImpl.java:196)
> at
> org.apache.geode.cache.client.internal.pooling.ConnectionManagerImpl.createPooledConnection(ConnectionManagerImpl.java:190)
> at
> org.apache.geode.cache.client.internal.pooling.ConnectionManagerImpl.borrowConnection(ConnectionManagerImpl.java:276)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:129)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:112)
> at
> org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:797)
> at
> org.apache.geode.cache.client.internal.GetOp.execute(GetOp.java:91)
> at
> org.apache.geode.cache.client.internal.ServerRegionProxy.get(ServerRegionProxy.java:114)
> at
> org.apache.geode.internal.cache.LocalRegion.findObjectInSystem(LocalRegion.java:2802)
> at
> org.apache.geode.internal.cache.LocalRegion.getObject(LocalRegion.java:1469)
> at
> org.apache.geode.internal.cache.LocalRegion.nonTxnFindObject(LocalRegion.java:1442)
> at
> org.apache.geode.internal.cache.LocalRegionDataView.findObject(LocalRegionDataView.java:197)
> at
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1379)
> at
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1318)
> at
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1303)
> at
> org.apache.geode.internal.cache.AbstractRegion.get(AbstractRegion.java:439)
> at
> org.apache.geode.cache30.ClientServerCacheOperationDUnitTest.lambda$largeObjectPutWithReadTimeoutThrowsException$3ab01cf6$2(ClientServerCacheOperationDUnitTest.java:121){noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> [*http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0116/test-results/distributedTest/1617652711/*]
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> [*http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0116/test-artifacts/1617652711/distributedtestfiles-OpenJDK8-1.15.0-build.0116.tgz*]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9006) MemoryStatsNativeRedisAcceptanceTest CI failure
[
https://issues.apache.org/jira/browse/GEODE-9006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17319614#comment-17319614
]
Geode Integration commented on GEODE-9006:
--
Seen in [AcceptanceTestOpenJDK11
#138.1|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/AcceptanceTestOpenJDK11/builds/138.1]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0131/test-results/acceptanceTest/1618019493/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0131/test-artifacts/1618019493/acceptancetestfiles-OpenJDK11-1.15.0-build.0131.tgz].
> MemoryStatsNativeRedisAcceptanceTest CI failure
> ---
>
> Key: GEODE-9006
> URL: https://issues.apache.org/jira/browse/GEODE-9006
> Project: Geode
> Issue Type: New Feature
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Ray Ingles
>Assignee: John Hutchison
>Priority: Major
>
> CI failure:
> {{org.apache.geode.redis.internal.executor.server.MemoryStatsNativeRedisAcceptanceTest
> > usedMemory_shouldReflectActualMemoryUsage FAILED
> java.lang.AssertionError:
> Expecting:
> 854912L
> to be greater than:
> 855176L}}
> http://hydradb.gemfire.pivotal.io/hdb/testresult/9637883
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/AcceptanceTestOpenJDK11/builds/51
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-8990) CI Failure: Jetty9CachingClientServerTest.shouldCacheSessionOnClient
[
https://issues.apache.org/jira/browse/GEODE-8990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17319613#comment-17319613
]
Geode Integration commented on GEODE-8990:
--
Seen in [DistributedTestOpenJDK8
#142.2|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/142.2]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0129/test-results/distributedTest/1618023171/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0129/test-artifacts/1618023171/distributedtestfiles-OpenJDK8-1.15.0-build.0129.tgz].
> CI Failure: Jetty9CachingClientServerTest.shouldCacheSessionOnClient
>
>
> Key: GEODE-8990
> URL: https://issues.apache.org/jira/browse/GEODE-8990
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Assignee: Mark Hanson
>Priority: Major
> Labels: pull-request-available
>
> {noformat}
> org.apache.geode.session.tests.Jetty9CachingClientServerTest >
> shouldCacheSessionOnClient FAILED
> org.junit.ComparisonFailure: expected:<[Foo]> but was:<[bogus]>
> at org.junit.Assert.assertEquals(Assert.java:117)
> at org.junit.Assert.assertEquals(Assert.java:146)
> at
> org.apache.geode.session.tests.Jetty9CachingClientServerTest.shouldCacheSessionOnClient(Jetty9CachingClientServerTest.java:65)
> 371 tests completed, 1 failed
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0023/test-results/distributedTest/1614646829/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0023/test-artifacts/1614646829/distributedtestfiles-OpenJDK8-1.15.0-build.0023.tgz
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-8990) CI Failure: Jetty9CachingClientServerTest.shouldCacheSessionOnClient
[
https://issues.apache.org/jira/browse/GEODE-8990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17319610#comment-17319610
]
Geode Integration commented on GEODE-8990:
--
Seen in [DistributedTestOpenJDK8
#142.4|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/142.4]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0129/test-results/distributedTest/1618051016/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0129/test-artifacts/1618051016/distributedtestfiles-OpenJDK8-1.15.0-build.0129.tgz].
> CI Failure: Jetty9CachingClientServerTest.shouldCacheSessionOnClient
>
>
> Key: GEODE-8990
> URL: https://issues.apache.org/jira/browse/GEODE-8990
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Assignee: Mark Hanson
>Priority: Major
> Labels: pull-request-available
>
> {noformat}
> org.apache.geode.session.tests.Jetty9CachingClientServerTest >
> shouldCacheSessionOnClient FAILED
> org.junit.ComparisonFailure: expected:<[Foo]> but was:<[bogus]>
> at org.junit.Assert.assertEquals(Assert.java:117)
> at org.junit.Assert.assertEquals(Assert.java:146)
> at
> org.apache.geode.session.tests.Jetty9CachingClientServerTest.shouldCacheSessionOnClient(Jetty9CachingClientServerTest.java:65)
> 371 tests completed, 1 failed
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0023/test-results/distributedTest/1614646829/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0023/test-artifacts/1614646829/distributedtestfiles-OpenJDK8-1.15.0-build.0023.tgz
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-8320) SerialWANStatsDUnitTest.testReplicatedSerialPropagationHAWithGroupTransactionEvents is failiing
[
https://issues.apache.org/jira/browse/GEODE-8320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17319612#comment-17319612
]
Geode Integration commented on GEODE-8320:
--
Seen in [DistributedTestOpenJDK8
#142.3|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/142.3]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0129/test-results/distributedTest/1618032831/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0129/test-artifacts/1618032831/distributedtestfiles-OpenJDK8-1.15.0-build.0129.tgz].
> SerialWANStatsDUnitTest.testReplicatedSerialPropagationHAWithGroupTransactionEvents
> is failiing
> ---
>
> Key: GEODE-8320
> URL: https://issues.apache.org/jira/browse/GEODE-8320
> Project: Geode
> Issue Type: Bug
> Components: wan
>Reporter: Mark Hanson
>Assignee: Alberto Gomez
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.14.0
>
>
> {noformat}
> org.apache.geode.internal.cache.wan.serial.SerialWANStatsDUnitTest >
> testReplicatedSerialPropagationHAWithGroupTransactionEvents FAILED
> 11:55:01
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.wan.serial.SerialWANStatsDUnitTest$$Lambda$134/1929719983.run
> in VM 2 running on Host 249227cf2774 with 8 VMs
> 11:55:01
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:610)
> 11:55:01
> at org.apache.geode.test.dunit.VM.invoke(VM.java:437)
> 11:55:01
> at
> org.apache.geode.internal.cache.wan.serial.SerialWANStatsDUnitTest.testReplicatedSerialPropagationHAWithGroupTransactionEvents(SerialWANStatsDUnitTest.java:578)
> 11:55:01
> 11:55:01
> Caused by:
> 11:55:01
> org.awaitility.core.ConditionTimeoutException: Assertion condition defined
> as a lambda expression in org.apache.geode.internal.cache.wan.WANTestBase
> that uses int, intorg.apache.geode.cache.Region Expected region entries:
> 2 but actual entries: 1 present region keyset [7435200, <*
> Intentionally cut out by Jira submitter *> 8851200] expected:<2> but
> was:<1> within 5 minutes.
> 11:55:01
> at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165)
> 11:55:01
> at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
> 11:55:01
> at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
> 11:55:01
> at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:895)
> 11:55:01
> at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:679)
> 11:55:01
> at
> org.apache.geode.internal.cache.wan.WANTestBase.validateRegionSize(WANTestBase.java:2942)
> 11:55:01
> at
> org.apache.geode.internal.cache.wan.serial.SerialWANStatsDUnitTest.lambda$testReplicatedSerialPropagationHAWithGroupTransactionEvents$bb17a952$8(SerialWANStatsDUnitTest.java:578)
> 11:55:01
> 11:55:01
> Caused by:
> 11:55:01
> java.lang.AssertionError: Expected region entries: 2 but actual entries:
> 1 present region keyset [7435200, <*Intentionally cut out by Jira
> submitter*> ] expected:<2> but was:<1>
> 12:31:11
> {noformat}
>
>
>
>
> {noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0193/test-results/distributedTest/1593463337/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0193/test-artifacts/1593463337/distributedtestfiles-OpenJDK8-1.14.0-build.0193.tgz
> {noformat}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-8899) Update dockerized test plugin
[ https://issues.apache.org/jira/browse/GEODE-8899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17319590#comment-17319590 ] ASF subversion and git services commented on GEODE-8899: Commit 75bb0d297b0624120fd62bea2ee9d5dfc400a18f in geode's branch refs/heads/develop from Dale Emery [ https://gitbox.apache.org/repos/asf?p=geode.git;h=75bb0d2 ] GEODE-8899: Upgrade to Gradle v6.8.3 (#6280) * GEODE-8899: Upgrade to Gradle v6.8.3 Updated Geode's build system to use Gradle 6.8.3: - Updated the gradle wrapper to use Gradle 6.8.3. - Updated geode-assembly/build.gradle to make the ivy "repository" compatible with Gradle 6.8.3. - Changed ./gradle.properties to specify 'minimumGradleVersion=6.8'. - Updated the expected-pom.xml file to the format that Gradle 6.8.3 produces. - Updated all Gradle plugins to the latest versions. - In buildSrc/build.gradle, added groovy source sets for testing, to allow running tests of plugin code. - Updated common "test isolation" code to be compatible with Gradle 6.8.3. See below for details. - Updated the RepeatTest task to be compatible with Gradle 6.8.3. See below for details. - Rewrote the Dockerized test plugin to be compatible with Gradle 6.8.3. See below for details. - Added a new 'dunitDockerJVM' project property to allow developers run tests in Docker on macOS. To do this, use -PtestJVM to identify the mac's JVM, and use -PdunitDockerJVM to specify the JVM for the test worker process running in Docker. - Updated the BUILDING.md file for Gradle 6.8.3. As part of this I added two versions of the Apache copyright notice to the etc dir: A plain text version and an xml version that IntelliJ IDEA can import into its copyright settings. = Test isolation code = Some code for isolating tests is used by the RepeatTest task and the Dockerized test plugin. This code was updated to be compatible with Gradle v6.8.3, and to somewhat reduce its dependence on Gradle internal implementation details: - WorkingDirectoryIsolator adjusts a given ProcessBuilder to give it a unique working directory. - AdjustableProcessLauncher applies a given Consumer (such as the isolator, above) to adjust each ProcessBuilder before launching the process. - LauncherProxyWorkerProcessBuilder and LauncherProcessWorkerProcessFactory forcefully update each Gradle exec handle to use a given ProcessLauncher to launch test worker processes. - Executers and Workers offer convenience methods for constructing TestExecuters and ProcessWorker builders and factories. = RepeatTest task update = Geode's RepeatTest task uses a custom TestExecuter that was copied from Gradle 5.5 (or earlier) and modified. This custom class is now updated to be compatible with Gradle 6.8.3, and renamed from OverriddenTestExecutor to RepeatableTestExecuter. = Dockerized test plugin rewrite = Removed the modified copy of pedjak's Dockerized test plugin. Configuration - - Rewrote gradle/docker.gradle and renamed it as gradle/multi-process-test.gradle. - Moved the code that translates project properties into configuration settings from the plugin to the config class. Renamed the config class as DockerTestWorkerConfig. - Moved code that configures command lines and environments for Docker test workers based on project properties. Thise code was defiend as a closure in a build script. It is now a method in DockerTestWorkerConfig. - Changed command line options that CI scripts pass to Gradle to run tests in Docker: - Specify the --max-workers Gradle option to configure the maximum number of workers. - Specify the 'testMaxParallelForks' project property to configure the maximum number of forks for each test task. - Remove the 'dunitParallelForks' option. Implementation -- The Dockerized test plugin uses these classes to launches processes in Docker containers: - DockerProcess overrides java.lang.Process to represent a test worker process running in Docker. - DockerProcessLauncher launches each test worker process in a Docker container, and creates a DockerProcess to represent and manage it. - Other classes described in the "Test isolation code" section, above. The plugin overrides several of Gradle's internal classes to allow test worker processes running in Docker containers to communicate with Gradle: - DockerConnectionAcceptor implements Gradle's ConnectionAcceptor, which (among other responsibilities), produces a "multi-choice address" that a test worker process can use to connect to Gradle's messaging server. Gradle's default implementation produces multi-choice addresses that processes in Docker containers cannot use. - DockerMessagingServer implements Gradle's MessagingServer using DockerConnectionAcceotpr. - WildcardBindingInetAddressFactory overrides Gradle's InetAddressFactory to instruct messaging
[jira] [Commented] (GEODE-8899) Update dockerized test plugin
[ https://issues.apache.org/jira/browse/GEODE-8899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17319589#comment-17319589 ] ASF subversion and git services commented on GEODE-8899: Commit 75bb0d297b0624120fd62bea2ee9d5dfc400a18f in geode's branch refs/heads/develop from Dale Emery [ https://gitbox.apache.org/repos/asf?p=geode.git;h=75bb0d2 ] GEODE-8899: Upgrade to Gradle v6.8.3 (#6280) * GEODE-8899: Upgrade to Gradle v6.8.3 Updated Geode's build system to use Gradle 6.8.3: - Updated the gradle wrapper to use Gradle 6.8.3. - Updated geode-assembly/build.gradle to make the ivy "repository" compatible with Gradle 6.8.3. - Changed ./gradle.properties to specify 'minimumGradleVersion=6.8'. - Updated the expected-pom.xml file to the format that Gradle 6.8.3 produces. - Updated all Gradle plugins to the latest versions. - In buildSrc/build.gradle, added groovy source sets for testing, to allow running tests of plugin code. - Updated common "test isolation" code to be compatible with Gradle 6.8.3. See below for details. - Updated the RepeatTest task to be compatible with Gradle 6.8.3. See below for details. - Rewrote the Dockerized test plugin to be compatible with Gradle 6.8.3. See below for details. - Added a new 'dunitDockerJVM' project property to allow developers run tests in Docker on macOS. To do this, use -PtestJVM to identify the mac's JVM, and use -PdunitDockerJVM to specify the JVM for the test worker process running in Docker. - Updated the BUILDING.md file for Gradle 6.8.3. As part of this I added two versions of the Apache copyright notice to the etc dir: A plain text version and an xml version that IntelliJ IDEA can import into its copyright settings. = Test isolation code = Some code for isolating tests is used by the RepeatTest task and the Dockerized test plugin. This code was updated to be compatible with Gradle v6.8.3, and to somewhat reduce its dependence on Gradle internal implementation details: - WorkingDirectoryIsolator adjusts a given ProcessBuilder to give it a unique working directory. - AdjustableProcessLauncher applies a given Consumer (such as the isolator, above) to adjust each ProcessBuilder before launching the process. - LauncherProxyWorkerProcessBuilder and LauncherProcessWorkerProcessFactory forcefully update each Gradle exec handle to use a given ProcessLauncher to launch test worker processes. - Executers and Workers offer convenience methods for constructing TestExecuters and ProcessWorker builders and factories. = RepeatTest task update = Geode's RepeatTest task uses a custom TestExecuter that was copied from Gradle 5.5 (or earlier) and modified. This custom class is now updated to be compatible with Gradle 6.8.3, and renamed from OverriddenTestExecutor to RepeatableTestExecuter. = Dockerized test plugin rewrite = Removed the modified copy of pedjak's Dockerized test plugin. Configuration - - Rewrote gradle/docker.gradle and renamed it as gradle/multi-process-test.gradle. - Moved the code that translates project properties into configuration settings from the plugin to the config class. Renamed the config class as DockerTestWorkerConfig. - Moved code that configures command lines and environments for Docker test workers based on project properties. Thise code was defiend as a closure in a build script. It is now a method in DockerTestWorkerConfig. - Changed command line options that CI scripts pass to Gradle to run tests in Docker: - Specify the --max-workers Gradle option to configure the maximum number of workers. - Specify the 'testMaxParallelForks' project property to configure the maximum number of forks for each test task. - Remove the 'dunitParallelForks' option. Implementation -- The Dockerized test plugin uses these classes to launches processes in Docker containers: - DockerProcess overrides java.lang.Process to represent a test worker process running in Docker. - DockerProcessLauncher launches each test worker process in a Docker container, and creates a DockerProcess to represent and manage it. - Other classes described in the "Test isolation code" section, above. The plugin overrides several of Gradle's internal classes to allow test worker processes running in Docker containers to communicate with Gradle: - DockerConnectionAcceptor implements Gradle's ConnectionAcceptor, which (among other responsibilities), produces a "multi-choice address" that a test worker process can use to connect to Gradle's messaging server. Gradle's default implementation produces multi-choice addresses that processes in Docker containers cannot use. - DockerMessagingServer implements Gradle's MessagingServer using DockerConnectionAcceotpr. - WildcardBindingInetAddressFactory overrides Gradle's InetAddressFactory to instruct messaging
[jira] [Assigned] (GEODE-9133) refactor current notifyGatewaySender to support regionEvent
[ https://issues.apache.org/jira/browse/GEODE-9133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaojian Zhou reassigned GEODE-9133: Assignee: Xiaojian Zhou > refactor current notifyGatewaySender to support regionEvent > --- > > Key: GEODE-9133 > URL: https://issues.apache.org/jira/browse/GEODE-9133 > Project: Geode > Issue Type: Bug >Reporter: Xiaojian Zhou >Assignee: Xiaojian Zhou >Priority: Major > Labels: GeodeOperationAPI > > Current notifyGatewaySender hard-coded to use EntryEventImpl. There's a > requirement to notify gateway senders or AEQs with regionEvent, such as clear > region event. > To support that, we have to refactor the related classes to use > InternalCacheEvent interface instead of using EntryEventImpl. > With that refactoring, we can send a clear region event to an AEQ, to lucene > index, or even to remote site via WAN. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9133) refactor current notifyGatewaySender to support regionEvent
[ https://issues.apache.org/jira/browse/GEODE-9133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaojian Zhou updated GEODE-9133: - Labels: GeodeOperationAPI (was: ) > refactor current notifyGatewaySender to support regionEvent > --- > > Key: GEODE-9133 > URL: https://issues.apache.org/jira/browse/GEODE-9133 > Project: Geode > Issue Type: Bug >Reporter: Xiaojian Zhou >Priority: Major > Labels: GeodeOperationAPI > > Current notifyGatewaySender hard-coded to use EntryEventImpl. There's a > requirement to notify gateway senders or AEQs with regionEvent, such as clear > region event. > To support that, we have to refactor the related classes to use > InternalCacheEvent interface instead of using EntryEventImpl. > With that refactoring, we can send a clear region event to an AEQ, to lucene > index, or even to remote site via WAN. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-9138) Add warning in server logs when data event is ignored as a duplicate
Diane Hardman created GEODE-9138: Summary: Add warning in server logs when data event is ignored as a duplicate Key: GEODE-9138 URL: https://issues.apache.org/jira/browse/GEODE-9138 Project: Geode Issue Type: Bug Components: client/server Reporter: Diane Hardman Under certain rare conditions, a client may send or resend a data event with an eventId that causes the server to interpret it as a duplicate event and discard it. It is currently impossible to trace when this happens without extra logging added. >From Barry: No, if the server thinks it has seen the event, it silently eats it. See DistributedEventTracker.hasSeenEvent. It has a trace log message but thats it. The log message that tracks this behavior in the server needs to be added permanently. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-8859) Redis data structures may not accurately reflect their size in Geode stats
[
https://issues.apache.org/jira/browse/GEODE-8859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Hutchison reassigned GEODE-8859:
-
Assignee: (was: John Hutchison)
> Redis data structures may not accurately reflect their size in Geode stats
> --
>
> Key: GEODE-8859
> URL: https://issues.apache.org/jira/browse/GEODE-8859
> Project: Geode
> Issue Type: Bug
> Components: redis, statistics
>Affects Versions: 1.14.0
>Reporter: Jens Deppe
>Priority: Major
> Labels: blocks-1.14.0, pull-request-available, release-blocker
>
> Here is a comment from Darrel regarding this issue. For some background, the
> Redis structures implement {{Delta}}.
>
> {quote}I was playing around with RedisInsight and was able to get most the
> the overview dashboard and the data browser working with geode redis. But I
> found a problem with how we are using geode that causes the geode stats that
> track how much data is stored in a partitioned region to be wrong and the
> bucket sizes used for rebalancing are also wrong. Basically when we do create
> ops on the region the stats track it okay. But when we do updates then geode
> always thinks that nothing (size wise) changed. So for example I created a
> string by doing a redis “set” command. I saw the size of the string accounted
> for in dataStoreBytesInUse. But then I kept doing redis “append” commands on
> that key and the dataStoreBytesInUse did not change at all. I think the
> problem is in how we are updating the data structure in place instead of
> getting a copy, modifying it, and then putting the copy into the region.
> Avoiding this copy gives us MUCH better performance but it messes up geode
> when it is trying to calculate the memory increase or decrease. It is
> possible that this is only an issue on the primary and that the secondary
> sizing may be correct. If so that could lead to other problems because for a
> given bucket our primary size would be different than the secondary. The
> bucket sizes are used when you do a rebalance but basically we can have a
> bunch of memory that is “untracked” so we might see the JVM heaps unbalanced
> but geode will think the buckets are balanced. I’m not sure what we should do
> about this.
> {quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-8741) Filter out CQ Create/Update/Destroy notifications
[ https://issues.apache.org/jira/browse/GEODE-8741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mario Ivanac updated GEODE-8741: Description: Clients subscribe to server-side events by using SQL-type query filtering. The server sends all events that modify the query results. CQ event delivery uses the client/server subscription framework. We want possibility for each client to block/suppress CQ Create/Update/Destroy event (notification). was:We want possibility to block/suppress CQ Create/Update/Destroy notifications. > Filter out CQ Create/Update/Destroy notifications > - > > Key: GEODE-8741 > URL: https://issues.apache.org/jira/browse/GEODE-8741 > Project: Geode > Issue Type: Wish > Components: cq >Reporter: Mario Ivanac >Assignee: Mario Ivanac >Priority: Minor > Labels: pull-request-available > > Clients subscribe to server-side events by using SQL-type query filtering. > The server sends all events that modify the query results. CQ event delivery > uses the client/server subscription framework. > We want possibility for each client to block/suppress CQ > Create/Update/Destroy event (notification). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8991) Cached regions are not cleaned up whenever the connection to the cluster is lost
[ https://issues.apache.org/jira/browse/GEODE-8991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17319452#comment-17319452 ] ASF GitHub Bot commented on GEODE-8991: --- gaussianrecurrence commented on pull request #757: URL: https://github.com/apache/geode-native/pull/757#issuecomment-817797516 > Seeing this failure in tests: > > ``` > The following tests FAILED: > 50 - PdxTypeRegistryTest.cleanupOnClusterRestart (SEGFAULT) > Errors while running CTest > ``` > > Is this perhaps GEODE-8968? Maybe rebasing onto develop again will fix it. Sorry for the delay, been kind of busy lately. The problem was that this test was triggering the cleanup but the registered region did not have caching enabled. When caching is not enabled m_entries is nullptr and that was causing a coredump. I added a check to verify that if caching is not enabled for a region, don't execute the entries cleanup on it. -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Cached regions are not cleaned up whenever the connection to the cluster is > lost > > > Key: GEODE-8991 > URL: https://issues.apache.org/jira/browse/GEODE-8991 > Project: Geode > Issue Type: Bug > Components: native client >Affects Versions: 1.15.0 >Reporter: Mario Salazar de Torres >Assignee: Mario Salazar de Torres >Priority: Major > Labels: pull-request-available > > Under a cluster restart scenario it can't be guaranteed that all the entries > that existed before, exist after the restart. Hence if geode-native client > has any cached region registered it should be cleared after the connection is > lost towards the cluster in order to ensure cache consistency. > This is happenig in the case of the Java client, as described in this part of > the documentation: > [https://geode.apache.org/docs/guide/12/developing/events/how_client_server_distribution_works.html#how_client_server_distribution_works__section_928BB60066414BEB9FAA7FB3120334A3] > However, this is not the case for the native client -- This message was sent by Atlassian Jira (v8.3.4#803005)
