[jira] [Assigned] (GEODE-9987) Mass-Test_Run: HostedLocatorsDUnitTest > testGetAllHostedLocators FAILED
[
https://issues.apache.org/jira/browse/GEODE-9987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nabarun Nag reassigned GEODE-9987:
--
Assignee: Nabarun Nag
> Mass-Test_Run: HostedLocatorsDUnitTest > testGetAllHostedLocators FAILED
>
>
> Key: GEODE-9987
> URL: https://issues.apache.org/jira/browse/GEODE-9987
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Kristen
>Assignee: Nabarun Nag
>Priority: Major
> Labels: needsTriage, pull-request-available
>
> {code:java}
> HostedLocatorsDUnitTest > testGetAllHostedLocators FAILED
> org.gradle.internal.exceptions.DefaultMultiCauseException: Multiple
> Failures (2 failures)
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.distributed.HostedLocatorsDUnitTest$1.call in VM 3 running
> on Host
> heavy-lifter-a104d1cf-827a-5a63-b549-400f89cd9204.c.apachegeode-ci.internal
> with 4 VMs
> 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 'dunit_suspect-vm3.log' at line 458
> [fatal 2022/01/22 17:02:39.638 UTC receiver,heavy-lifter-a104d1cf-827a-5a63-b549-400f89cd9204-65003> tid=125]
> Membership service failure: Member isn't responding to heartbeat requests
>
> org.apache.geode.distributed.internal.membership.api.MemberDisconnectedException:
> Member isn't responding to heartbeat requests
> at
> org.apache.geode.distributed.internal.membership.gms.GMSMembership$ManagerImpl.forceDisconnect(GMSMembership.java:1806)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.forceDisconnect(GMSJoinLeave.java:1120)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.processRemoveMemberMessage(GMSJoinLeave.java:723)
> ...
> Caused by:
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.distributed.HostedLocatorsDUnitTest$1.call in VM 3 running
> on Host
> heavy-lifter-a104d1cf-827a-5a63-b549-400f89cd9204.c.apachegeode-ci.internal
> with 4 VMs
> at
> org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:473)
> at
> org.apache.geode.distributed.HostedLocatorsDUnitTest.testGetAllHostedLocators(HostedLocatorsDUnitTest.java:92)
> Caused by:
>
> org.apache.geode.distributed.DistributedSystemDisconnectedException:
> Distribution manager on
> heavy-lifter-a104d1cf-827a-5a63-b549-400f89cd9204(heavy-lifter-a104d1cf-827a-5a63-b549-400f89cd9204.c.apachegeode-ci.internal_HostedLocatorsDUnitTest_testGetAllHostedLocators-3:115919:locator):59339
> started at Sat Jan 22 17:02:21 UTC 2022: Member isn't responding to
> heartbeat requests, caused by org.apache.geode.ForcedDisconnectException:
> Member isn't responding to heartbeat requests
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager$Stopper.generateCancelledException(ClusterDistributionManager.java:2893)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem$Stopper.generateCancelledException(InternalDistributedSystem.java:1177)
> at
> org.apache.geode.CancelCriterion.checkCancelInProgress(CancelCriterion.java:83)
> at
> org.apache.geode.distributed.internal.locks.DLockService.create(DLockService.java:2686)
> at
> org.apache.geode.distributed.internal.locks.DLockService.create(DLockService.java:2660)
> at
> org.apache.geode.distributed.internal.locks.DLockService.getOrCreateService(DLockService.java:2641)
> at
> org.apache.geode.distributed.internal.InternalConfigurationPersistenceService.(InternalConfigurationPersistenceService.java:131)
> at
> org.apache.geode.distributed.internal.InternalLocator.startConfigurationPersistenceService(InternalLocator.java:1390)
> at
> org.apache.geode.distributed.internal.InternalLocator.startClusterManagementService(InternalLocator.java:792)
> at
> org.apache.geode.distributed.internal.InternalLocator.startCache(InternalLocator.java:787)
> at
> org.apache.geode.distributed.internal.InternalLocator.startDistributedSystem(InternalLocator.java:768)
> at
> org.apache.geode.distributed.internal.InternalLocator.startLocator(InternalLocator.java:399)
> at
> org.apache.geode.distributed.LocatorLauncher.start(LocatorLauncher.java:734)
> at
>
[jira] [Updated] (GEODE-9987) Mass-Test_Run: HostedLocatorsDUnitTest > testGetAllHostedLocators FAILED
[
https://issues.apache.org/jira/browse/GEODE-9987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-9987:
--
Labels: needsTriage pull-request-available (was: needsTriage)
> Mass-Test_Run: HostedLocatorsDUnitTest > testGetAllHostedLocators FAILED
>
>
> Key: GEODE-9987
> URL: https://issues.apache.org/jira/browse/GEODE-9987
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Kristen
>Priority: Major
> Labels: needsTriage, pull-request-available
>
> {code:java}
> HostedLocatorsDUnitTest > testGetAllHostedLocators FAILED
> org.gradle.internal.exceptions.DefaultMultiCauseException: Multiple
> Failures (2 failures)
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.distributed.HostedLocatorsDUnitTest$1.call in VM 3 running
> on Host
> heavy-lifter-a104d1cf-827a-5a63-b549-400f89cd9204.c.apachegeode-ci.internal
> with 4 VMs
> 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 'dunit_suspect-vm3.log' at line 458
> [fatal 2022/01/22 17:02:39.638 UTC receiver,heavy-lifter-a104d1cf-827a-5a63-b549-400f89cd9204-65003> tid=125]
> Membership service failure: Member isn't responding to heartbeat requests
>
> org.apache.geode.distributed.internal.membership.api.MemberDisconnectedException:
> Member isn't responding to heartbeat requests
> at
> org.apache.geode.distributed.internal.membership.gms.GMSMembership$ManagerImpl.forceDisconnect(GMSMembership.java:1806)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.forceDisconnect(GMSJoinLeave.java:1120)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.processRemoveMemberMessage(GMSJoinLeave.java:723)
> ...
> Caused by:
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.distributed.HostedLocatorsDUnitTest$1.call in VM 3 running
> on Host
> heavy-lifter-a104d1cf-827a-5a63-b549-400f89cd9204.c.apachegeode-ci.internal
> with 4 VMs
> at
> org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:473)
> at
> org.apache.geode.distributed.HostedLocatorsDUnitTest.testGetAllHostedLocators(HostedLocatorsDUnitTest.java:92)
> Caused by:
>
> org.apache.geode.distributed.DistributedSystemDisconnectedException:
> Distribution manager on
> heavy-lifter-a104d1cf-827a-5a63-b549-400f89cd9204(heavy-lifter-a104d1cf-827a-5a63-b549-400f89cd9204.c.apachegeode-ci.internal_HostedLocatorsDUnitTest_testGetAllHostedLocators-3:115919:locator):59339
> started at Sat Jan 22 17:02:21 UTC 2022: Member isn't responding to
> heartbeat requests, caused by org.apache.geode.ForcedDisconnectException:
> Member isn't responding to heartbeat requests
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager$Stopper.generateCancelledException(ClusterDistributionManager.java:2893)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem$Stopper.generateCancelledException(InternalDistributedSystem.java:1177)
> at
> org.apache.geode.CancelCriterion.checkCancelInProgress(CancelCriterion.java:83)
> at
> org.apache.geode.distributed.internal.locks.DLockService.create(DLockService.java:2686)
> at
> org.apache.geode.distributed.internal.locks.DLockService.create(DLockService.java:2660)
> at
> org.apache.geode.distributed.internal.locks.DLockService.getOrCreateService(DLockService.java:2641)
> at
> org.apache.geode.distributed.internal.InternalConfigurationPersistenceService.(InternalConfigurationPersistenceService.java:131)
> at
> org.apache.geode.distributed.internal.InternalLocator.startConfigurationPersistenceService(InternalLocator.java:1390)
> at
> org.apache.geode.distributed.internal.InternalLocator.startClusterManagementService(InternalLocator.java:792)
> at
> org.apache.geode.distributed.internal.InternalLocator.startCache(InternalLocator.java:787)
> at
> org.apache.geode.distributed.internal.InternalLocator.startDistributedSystem(InternalLocator.java:768)
> at
> org.apache.geode.distributed.internal.InternalLocator.startLocator(InternalLocator.java:399)
> at
> org.apache.geode.distributed.LocatorLauncher.start(LocatorLauncher.java:734)
> at
[jira] [Commented] (GEODE-9982) Native clients older than 1.15 fail to read longer version ordinal from 1.15 servers.
[
https://issues.apache.org/jira/browse/GEODE-9982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17481484#comment-17481484
]
Jacob Barrett commented on GEODE-9982:
--
Unlike the Java clients, which when released, match the server version ordinal,
the native library has not increased it's protocol version since Geode 1.0.0.
This means one could just upgrade to the Geode Native 1.15 client prior to
upgrading the servers to manage upgrades.
> Native clients older than 1.15 fail to read longer version ordinal from 1.15
> servers.
> -
>
> Key: GEODE-9982
> URL: https://issues.apache.org/jira/browse/GEODE-9982
> Project: Geode
> Issue Type: Bug
> Components: native client
>Affects Versions: 1.12.8, 1.13.7, 1.14.0, 1.14.1, 1.14.2, 1.14.3, 1.14.4
>Reporter: Jacob Barrett
>Priority: Critical
>
> Geode Native C++ client v1.14.0 fails execution of
> testThinClientTransactionsWithoutSticky against current develop branch
> server. C++ client v1.14.0 does not fail when talking to a v1.14.0 server.
> Current develop branch C++ client does not fail when talking to a develop
> branch server. It appears there may be a protocol incompatibly issue between
> these two versions. More investigations to narrow down the version matrix is
> necessary.
> The following error is logged when the test fails:
> {{Error during send for endpoint 192.168.68.56:18539 due to
> apache::geode::client::IllegalStateException: Unregistered type in
> deserialization}}
> ||Server Versions|1.14.0|1.15.0|
> ||Client Versions||
> |1.14.0|P|F|
> |1.15.0|-|P|
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (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
]
Nabarun Nag reassigned GEODE-8616:
--
Assignee: Nabarun Nag
> 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, 1.13.7, 1.14.3, 1.15.0
>Reporter: Donal Evans
>Assignee: Nabarun Nag
>Priority: Major
> Labels: GeodeOperationAPI, flaky-test, pull-request-available
> Attachments: hansonm-findfailures-11-10-2021-23-52-38-logs.tgz,
> hansonm-findfailures-11-10-2021-23-52-45-logs.tgz
>
>
> {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.20.1#820001)
[jira] [Resolved] (GEODE-6751) CI failure: AcceptanceTestOpenJDK8 ConnectCommandAcceptanceTest.useCurrentGfshToConnectToOlderLocator failure
[ https://issues.apache.org/jira/browse/GEODE-6751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nabarun Nag resolved GEODE-6751. Fix Version/s: 1.15.0 Resolution: Fixed > CI failure: AcceptanceTestOpenJDK8 > ConnectCommandAcceptanceTest.useCurrentGfshToConnectToOlderLocator failure > - > > Key: GEODE-6751 > URL: https://issues.apache.org/jira/browse/GEODE-6751 > Project: Geode > Issue Type: Bug > Components: management >Affects Versions: 1.15.0 >Reporter: Scott Jewell >Assignee: Nabarun Nag >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > Assertion failure in > ConnectCommandAcceptanceTest.useCurrentGfshToConnectToOlderLocator > Appears to be a new bug > org.apache.geode.management.internal.cli.commands.ConnectCommandAcceptanceTest > > useCurrentGfshToConnectToOlderLocator FAILED > java.lang.AssertionError: > Expecting: > <" > (1) Executing - connect > Connecting to Locator at [host=localhost, port=10334] .. > Exception caused JMX Manager startup to fail because: 'HTTP service > failed to start' > "> > to contain: > <"Cannot use a"> > at > org.apache.geode.management.internal.cli.commands.ConnectCommandAcceptanceTest.useCurrentGfshToConnectToOlderLocator(ConnectCommandAcceptanceTest.java:50) > 60 tests completed, 1 failed > =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > [*http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0258/test-results/acceptanceTest/1557290414/*] > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Test report artifacts from this job are available at: > [*http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0258/test-artifacts/1557290414/acceptancetestfiles-OpenJDK8-1.10.0-SNAPSHOT.0258.tgz*] > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-6751) CI failure: AcceptanceTestOpenJDK8 ConnectCommandAcceptanceTest.useCurrentGfshToConnectToOlderLocator failure
[ https://issues.apache.org/jira/browse/GEODE-6751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17481483#comment-17481483 ] ASF subversion and git services commented on GEODE-6751: Commit 085b616dab895cdaa9f61f796405b11af82ffd80 in geode's branch refs/heads/develop from Nabarun Nag [ https://gitbox.apache.org/repos/asf?p=geode.git;h=085b616 ] GEODE-6751: Improved the tests for locator-gfsh compatibility (#7289) * Previously the tests only checked with 1.3.0 version of locator * The test now checks the behavior of the all the versions * New version gfsh could not connect with locators versions below 1.10.0 * New version gfsh are now able to connect with locators 1.10.0 and above. * This is now reflected in the test. * Previously a race condition between the execution of the two scripts caused the second script to be executed before the locator startup had completed. * Now the locator is started using the cluster startup rule. > CI failure: AcceptanceTestOpenJDK8 > ConnectCommandAcceptanceTest.useCurrentGfshToConnectToOlderLocator failure > - > > Key: GEODE-6751 > URL: https://issues.apache.org/jira/browse/GEODE-6751 > Project: Geode > Issue Type: Bug > Components: management >Affects Versions: 1.15.0 >Reporter: Scott Jewell >Assignee: Nabarun Nag >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > Assertion failure in > ConnectCommandAcceptanceTest.useCurrentGfshToConnectToOlderLocator > Appears to be a new bug > org.apache.geode.management.internal.cli.commands.ConnectCommandAcceptanceTest > > useCurrentGfshToConnectToOlderLocator FAILED > java.lang.AssertionError: > Expecting: > <" > (1) Executing - connect > Connecting to Locator at [host=localhost, port=10334] .. > Exception caused JMX Manager startup to fail because: 'HTTP service > failed to start' > "> > to contain: > <"Cannot use a"> > at > org.apache.geode.management.internal.cli.commands.ConnectCommandAcceptanceTest.useCurrentGfshToConnectToOlderLocator(ConnectCommandAcceptanceTest.java:50) > 60 tests completed, 1 failed > =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > [*http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0258/test-results/acceptanceTest/1557290414/*] > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Test report artifacts from this job are available at: > [*http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0258/test-artifacts/1557290414/acceptancetestfiles-OpenJDK8-1.10.0-SNAPSHOT.0258.tgz*] > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9907) Geode-for-redis example failed with JedisNoReachableClusterNodeException: No reachable node in cluster
[
https://issues.apache.org/jira/browse/GEODE-9907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17481481#comment-17481481
]
Geode Integration commented on GEODE-9907:
--
Seen in [test-examples
#154|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-examples/jobs/test-examples/builds/154].
> Geode-for-redis example failed with JedisNoReachableClusterNodeException: No
> reachable node in cluster
> --
>
> Key: GEODE-9907
> URL: https://issues.apache.org/jira/browse/GEODE-9907
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Kristen
>Assignee: Eric Zoerner
>Priority: Major
> Labels: release-blocker
> Fix For: 1.15.0
>
>
>
> {code:java}
> > Task :geodeForRedis:run FAILED
> Exception in thread "main"
> redis.clients.jedis.exceptions.JedisNoReachableClusterNodeException: No
> reachable node in cluster
> at
> redis.clients.jedis.JedisSlotBasedConnectionHandler.getConnection(JedisSlotBasedConnectionHandler.java:117)
> at
> redis.clients.jedis.JedisSlotBasedConnectionHandler.getConnectionFromSlot(JedisSlotBasedConnectionHandler.java:139)
> at
> redis.clients.jedis.JedisClusterCommand.runWithRetries(JedisClusterCommand.java:118)
> at redis.clients.jedis.JedisClusterCommand.run(JedisClusterCommand.java:45)
> at redis.clients.jedis.JedisCluster.zadd(JedisCluster.java:1106)
> at
> org.apache.geode_examples.geodeForRedis.Example.populateSortedSet(Example.java:53)
> at org.apache.geode_examples.geodeForRedis.Example.main(Example.java:30)
> FAILURE: Build failed with an exception.
> * What went wrong:
> Execution failed for task ':geodeForRedis:run'.
> > Process 'command '/usr/lib/jvm/bellsoft-java8-amd64/bin/java'' finished
> >with non-zero exit value 1
> {code}
>
> This might be related to [https://github.com/apache/geode-examples/pull/110]
> due to the location of the failure of the test
> org.apache.geode_examples.geodeForRedis.Example.main.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-9830) SINTERSTORE Command Supported
[ https://issues.apache.org/jira/browse/GEODE-9830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-9830: -- Labels: pull-request-available (was: ) > SINTERSTORE Command Supported > - > > Key: GEODE-9830 > URL: https://issues.apache.org/jira/browse/GEODE-9830 > Project: Geode > Issue Type: Improvement > Components: redis >Reporter: Wayne >Assignee: Kristen >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > The SINTERSTORE command has been implemented but lacks sufficient testing to > ensure that the implementation is robust and does not regress in the future. > > Write unit/integration tests that run against both Geode Redis and native > Redis, and dunit tests which test multiple concurrent clients accessing > different servers. > > +Acceptance Criteria+ > > Passing Unit/integration tests for both Geode and native Redis. The > RedisCommandType class and > README/redis_api_for_[geode.html.md.erb|http://geode.html.md.erb/] updated to > make command "supported". Stories in the backlog to fix the identified issues > (with JIRA tickets) and problem tests that are ignored should be fixed and > enabled. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-9957) Redis INFO command returns incorrect information
[
https://issues.apache.org/jira/browse/GEODE-9957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donal Evans updated GEODE-9957:
---
Labels: (was: blocks-1.15.0)
> Redis INFO command returns incorrect information
>
>
> Key: GEODE-9957
> URL: https://issues.apache.org/jira/browse/GEODE-9957
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Assignee: Jens Deppe
>Priority: Major
> Fix For: 1.15.0
>
>
> The geode-for-redis {{INFO}} command is supported, but has not been
> maintained or updated since the geode-for-redis module moved from standalone
> to cluster mode. As such, several fields returned by the command such as
> {{cluster_enabled}} and {{redis_mode}} return incorrect values.
> The output of the INFO command should be modified to return correct values
> for the current geode-for-redis configuration.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Resolved] (GEODE-9923) User Guide: add Log Message troubleshooting section
[ https://issues.apache.org/jira/browse/GEODE-9923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-9923. Fix Version/s: 1.12.9 1.13.8 1.14.4 1.15.0 Resolution: Fixed > User Guide: add Log Message troubleshooting section > --- > > Key: GEODE-9923 > URL: https://issues.apache.org/jira/browse/GEODE-9923 > Project: Geode > Issue Type: Improvement > Components: docs >Affects Versions: 1.14.2 >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Labels: pull-request-available > Fix For: 1.12.9, 1.13.8, 1.14.4, 1.15.0 > > > GemFire support team (who are also Geode community members) have compiled a > troubleshooting guide that maps log messages to suggested solutions. > They have contributed this to Geode in the form of a Google doc. > Reformat the Google doc and add it to the Geode user guide. There's an > existing section under Managing Apache Geode called Troubleshooting and > System Recovery that would be a good location for this material. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9987) Mass-Test_Run: HostedLocatorsDUnitTest > testGetAllHostedLocators FAILED
[
https://issues.apache.org/jira/browse/GEODE-9987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17481452#comment-17481452
]
Geode Integration commented on GEODE-9987:
--
Seen in [distributed-test-openjdk8
#761|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/761]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0806/test-results/distributedTest/1642874948/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0806/test-artifacts/1642874948/distributedtestfiles-openjdk8-1.15.0-build.0806.tgz].
> Mass-Test_Run: HostedLocatorsDUnitTest > testGetAllHostedLocators FAILED
>
>
> Key: GEODE-9987
> URL: https://issues.apache.org/jira/browse/GEODE-9987
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Kristen
>Priority: Major
> Labels: needsTriage
>
> {code:java}
> HostedLocatorsDUnitTest > testGetAllHostedLocators FAILED
> org.gradle.internal.exceptions.DefaultMultiCauseException: Multiple
> Failures (2 failures)
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.distributed.HostedLocatorsDUnitTest$1.call in VM 3 running
> on Host
> heavy-lifter-a104d1cf-827a-5a63-b549-400f89cd9204.c.apachegeode-ci.internal
> with 4 VMs
> 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 'dunit_suspect-vm3.log' at line 458
> [fatal 2022/01/22 17:02:39.638 UTC receiver,heavy-lifter-a104d1cf-827a-5a63-b549-400f89cd9204-65003> tid=125]
> Membership service failure: Member isn't responding to heartbeat requests
>
> org.apache.geode.distributed.internal.membership.api.MemberDisconnectedException:
> Member isn't responding to heartbeat requests
> at
> org.apache.geode.distributed.internal.membership.gms.GMSMembership$ManagerImpl.forceDisconnect(GMSMembership.java:1806)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.forceDisconnect(GMSJoinLeave.java:1120)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.processRemoveMemberMessage(GMSJoinLeave.java:723)
> ...
> Caused by:
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.distributed.HostedLocatorsDUnitTest$1.call in VM 3 running
> on Host
> heavy-lifter-a104d1cf-827a-5a63-b549-400f89cd9204.c.apachegeode-ci.internal
> with 4 VMs
> at
> org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:473)
> at
> org.apache.geode.distributed.HostedLocatorsDUnitTest.testGetAllHostedLocators(HostedLocatorsDUnitTest.java:92)
> Caused by:
>
> org.apache.geode.distributed.DistributedSystemDisconnectedException:
> Distribution manager on
> heavy-lifter-a104d1cf-827a-5a63-b549-400f89cd9204(heavy-lifter-a104d1cf-827a-5a63-b549-400f89cd9204.c.apachegeode-ci.internal_HostedLocatorsDUnitTest_testGetAllHostedLocators-3:115919:locator):59339
> started at Sat Jan 22 17:02:21 UTC 2022: Member isn't responding to
> heartbeat requests, caused by org.apache.geode.ForcedDisconnectException:
> Member isn't responding to heartbeat requests
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager$Stopper.generateCancelledException(ClusterDistributionManager.java:2893)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem$Stopper.generateCancelledException(InternalDistributedSystem.java:1177)
> at
> org.apache.geode.CancelCriterion.checkCancelInProgress(CancelCriterion.java:83)
> at
> org.apache.geode.distributed.internal.locks.DLockService.create(DLockService.java:2686)
> at
> org.apache.geode.distributed.internal.locks.DLockService.create(DLockService.java:2660)
> at
> org.apache.geode.distributed.internal.locks.DLockService.getOrCreateService(DLockService.java:2641)
> at
> org.apache.geode.distributed.internal.InternalConfigurationPersistenceService.(InternalConfigurationPersistenceService.java:131)
> at
> org.apache.geode.distributed.internal.InternalLocator.startConfigurationPersistenceService(InternalLocator.java:1390)
> at
> org.apache.geode.distributed.internal.InternalLocator.startClusterManagementService(InternalLocator.java:792)
>
[jira] [Updated] (GEODE-9987) Mass-Test_Run: HostedLocatorsDUnitTest > testGetAllHostedLocators FAILED
[
https://issues.apache.org/jira/browse/GEODE-9987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Murmann updated GEODE-9987:
-
Labels: needsTriage (was: )
> Mass-Test_Run: HostedLocatorsDUnitTest > testGetAllHostedLocators FAILED
>
>
> Key: GEODE-9987
> URL: https://issues.apache.org/jira/browse/GEODE-9987
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Kristen
>Priority: Major
> Labels: needsTriage
>
> {code:java}
> HostedLocatorsDUnitTest > testGetAllHostedLocators FAILED
> org.gradle.internal.exceptions.DefaultMultiCauseException: Multiple
> Failures (2 failures)
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.distributed.HostedLocatorsDUnitTest$1.call in VM 3 running
> on Host
> heavy-lifter-a104d1cf-827a-5a63-b549-400f89cd9204.c.apachegeode-ci.internal
> with 4 VMs
> 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 'dunit_suspect-vm3.log' at line 458
> [fatal 2022/01/22 17:02:39.638 UTC receiver,heavy-lifter-a104d1cf-827a-5a63-b549-400f89cd9204-65003> tid=125]
> Membership service failure: Member isn't responding to heartbeat requests
>
> org.apache.geode.distributed.internal.membership.api.MemberDisconnectedException:
> Member isn't responding to heartbeat requests
> at
> org.apache.geode.distributed.internal.membership.gms.GMSMembership$ManagerImpl.forceDisconnect(GMSMembership.java:1806)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.forceDisconnect(GMSJoinLeave.java:1120)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.processRemoveMemberMessage(GMSJoinLeave.java:723)
> ...
> Caused by:
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.distributed.HostedLocatorsDUnitTest$1.call in VM 3 running
> on Host
> heavy-lifter-a104d1cf-827a-5a63-b549-400f89cd9204.c.apachegeode-ci.internal
> with 4 VMs
> at
> org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:473)
> at
> org.apache.geode.distributed.HostedLocatorsDUnitTest.testGetAllHostedLocators(HostedLocatorsDUnitTest.java:92)
> Caused by:
>
> org.apache.geode.distributed.DistributedSystemDisconnectedException:
> Distribution manager on
> heavy-lifter-a104d1cf-827a-5a63-b549-400f89cd9204(heavy-lifter-a104d1cf-827a-5a63-b549-400f89cd9204.c.apachegeode-ci.internal_HostedLocatorsDUnitTest_testGetAllHostedLocators-3:115919:locator):59339
> started at Sat Jan 22 17:02:21 UTC 2022: Member isn't responding to
> heartbeat requests, caused by org.apache.geode.ForcedDisconnectException:
> Member isn't responding to heartbeat requests
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager$Stopper.generateCancelledException(ClusterDistributionManager.java:2893)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem$Stopper.generateCancelledException(InternalDistributedSystem.java:1177)
> at
> org.apache.geode.CancelCriterion.checkCancelInProgress(CancelCriterion.java:83)
> at
> org.apache.geode.distributed.internal.locks.DLockService.create(DLockService.java:2686)
> at
> org.apache.geode.distributed.internal.locks.DLockService.create(DLockService.java:2660)
> at
> org.apache.geode.distributed.internal.locks.DLockService.getOrCreateService(DLockService.java:2641)
> at
> org.apache.geode.distributed.internal.InternalConfigurationPersistenceService.(InternalConfigurationPersistenceService.java:131)
> at
> org.apache.geode.distributed.internal.InternalLocator.startConfigurationPersistenceService(InternalLocator.java:1390)
> at
> org.apache.geode.distributed.internal.InternalLocator.startClusterManagementService(InternalLocator.java:792)
> at
> org.apache.geode.distributed.internal.InternalLocator.startCache(InternalLocator.java:787)
> at
> org.apache.geode.distributed.internal.InternalLocator.startDistributedSystem(InternalLocator.java:768)
> at
> org.apache.geode.distributed.internal.InternalLocator.startLocator(InternalLocator.java:399)
> at
> org.apache.geode.distributed.LocatorLauncher.start(LocatorLauncher.java:734)
> at
>
[jira] [Created] (GEODE-9987) Mass-Test_Run: HostedLocatorsDUnitTest > testGetAllHostedLocators FAILED
Kristen created GEODE-9987:
--
Summary: Mass-Test_Run: HostedLocatorsDUnitTest >
testGetAllHostedLocators FAILED
Key: GEODE-9987
URL: https://issues.apache.org/jira/browse/GEODE-9987
Project: Geode
Issue Type: Bug
Affects Versions: 1.15.0
Reporter: Kristen
{code:java}
HostedLocatorsDUnitTest > testGetAllHostedLocators FAILED
org.gradle.internal.exceptions.DefaultMultiCauseException: Multiple
Failures (2 failures)
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.distributed.HostedLocatorsDUnitTest$1.call in VM 3 running on
Host
heavy-lifter-a104d1cf-827a-5a63-b549-400f89cd9204.c.apachegeode-ci.internal
with 4 VMs
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 'dunit_suspect-vm3.log' at line 458
[fatal 2022/01/22 17:02:39.638 UTC tid=125]
Membership service failure: Member isn't responding to heartbeat requests
org.apache.geode.distributed.internal.membership.api.MemberDisconnectedException:
Member isn't responding to heartbeat requests
at
org.apache.geode.distributed.internal.membership.gms.GMSMembership$ManagerImpl.forceDisconnect(GMSMembership.java:1806)
at
org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.forceDisconnect(GMSJoinLeave.java:1120)
at
org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.processRemoveMemberMessage(GMSJoinLeave.java:723)
...
Caused by:
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.distributed.HostedLocatorsDUnitTest$1.call in VM 3 running on
Host
heavy-lifter-a104d1cf-827a-5a63-b549-400f89cd9204.c.apachegeode-ci.internal
with 4 VMs
at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631)
at org.apache.geode.test.dunit.VM.invoke(VM.java:473)
at
org.apache.geode.distributed.HostedLocatorsDUnitTest.testGetAllHostedLocators(HostedLocatorsDUnitTest.java:92)
Caused by:
org.apache.geode.distributed.DistributedSystemDisconnectedException:
Distribution manager on
heavy-lifter-a104d1cf-827a-5a63-b549-400f89cd9204(heavy-lifter-a104d1cf-827a-5a63-b549-400f89cd9204.c.apachegeode-ci.internal_HostedLocatorsDUnitTest_testGetAllHostedLocators-3:115919:locator):59339
started at Sat Jan 22 17:02:21 UTC 2022: Member isn't responding to heartbeat
requests, caused by org.apache.geode.ForcedDisconnectException: Member isn't
responding to heartbeat requests
at
org.apache.geode.distributed.internal.ClusterDistributionManager$Stopper.generateCancelledException(ClusterDistributionManager.java:2893)
at
org.apache.geode.distributed.internal.InternalDistributedSystem$Stopper.generateCancelledException(InternalDistributedSystem.java:1177)
at
org.apache.geode.CancelCriterion.checkCancelInProgress(CancelCriterion.java:83)
at
org.apache.geode.distributed.internal.locks.DLockService.create(DLockService.java:2686)
at
org.apache.geode.distributed.internal.locks.DLockService.create(DLockService.java:2660)
at
org.apache.geode.distributed.internal.locks.DLockService.getOrCreateService(DLockService.java:2641)
at
org.apache.geode.distributed.internal.InternalConfigurationPersistenceService.(InternalConfigurationPersistenceService.java:131)
at
org.apache.geode.distributed.internal.InternalLocator.startConfigurationPersistenceService(InternalLocator.java:1390)
at
org.apache.geode.distributed.internal.InternalLocator.startClusterManagementService(InternalLocator.java:792)
at
org.apache.geode.distributed.internal.InternalLocator.startCache(InternalLocator.java:787)
at
org.apache.geode.distributed.internal.InternalLocator.startDistributedSystem(InternalLocator.java:768)
at
org.apache.geode.distributed.internal.InternalLocator.startLocator(InternalLocator.java:399)
at
org.apache.geode.distributed.LocatorLauncher.start(LocatorLauncher.java:734)
at
org.apache.geode.distributed.HostedLocatorsDUnitTest$1.call(HostedLocatorsDUnitTest.java:108)
Caused by:
org.apache.geode.ForcedDisconnectException: Member isn't
responding to heartbeat requests
at
org.apache.geode.distributed.internal.DistributionImpl$LifecycleListenerImpl.forcedDisconnect(DistributionImpl.java:941)
at
org.apache.geode.distributed.internal.membership.gms.GMSMembership$ManagerImpl.lambda$uncleanShutdownDS$0(GMSMembership.java:1792)
at
[jira] [Commented] (GEODE-9923) User Guide: add Log Message troubleshooting section
[ https://issues.apache.org/jira/browse/GEODE-9923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17481448#comment-17481448 ] ASF subversion and git services commented on GEODE-9923: Commit 3430c56d418e9f5fa1d3b5afdf35a61345228530 in geode's branch refs/heads/support/1.13 from Dave Barnes [ https://gitbox.apache.org/repos/asf?p=geode.git;h=3430c56 ] GEODE-9923: Add log message troubleshooting info from support team community (#7296) > User Guide: add Log Message troubleshooting section > --- > > Key: GEODE-9923 > URL: https://issues.apache.org/jira/browse/GEODE-9923 > Project: Geode > Issue Type: Improvement > Components: docs >Affects Versions: 1.14.2 >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Labels: pull-request-available > > GemFire support team (who are also Geode community members) have compiled a > troubleshooting guide that maps log messages to suggested solutions. > They have contributed this to Geode in the form of a Google doc. > Reformat the Google doc and add it to the Geode user guide. There's an > existing section under Managing Apache Geode called Troubleshooting and > System Recovery that would be a good location for this material. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9923) User Guide: add Log Message troubleshooting section
[ https://issues.apache.org/jira/browse/GEODE-9923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17481446#comment-17481446 ] ASF subversion and git services commented on GEODE-9923: Commit 1de8e770587aa8d1ebcc5e03a2236262200c5055 in geode's branch refs/heads/support/1.12 from Dave Barnes [ https://gitbox.apache.org/repos/asf?p=geode.git;h=1de8e77 ] GEODE-9923: Add log message troubleshooting info from support team community (#7296) > User Guide: add Log Message troubleshooting section > --- > > Key: GEODE-9923 > URL: https://issues.apache.org/jira/browse/GEODE-9923 > Project: Geode > Issue Type: Improvement > Components: docs >Affects Versions: 1.14.2 >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Labels: pull-request-available > > GemFire support team (who are also Geode community members) have compiled a > troubleshooting guide that maps log messages to suggested solutions. > They have contributed this to Geode in the form of a Google doc. > Reformat the Google doc and add it to the Geode user guide. There's an > existing section under Managing Apache Geode called Troubleshooting and > System Recovery that would be a good location for this material. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-9982) Native clients older than 1.15 fail to read longer version ordinal from 1.15 servers.
[
https://issues.apache.org/jira/browse/GEODE-9982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacob Barrett updated GEODE-9982:
-
Summary: Native clients older than 1.15 fail to read longer version ordinal
from 1.15 servers. (was: Native clients older than 1.15 fail do decode longer
version ordinal from 1.15 servers.)
> Native clients older than 1.15 fail to read longer version ordinal from 1.15
> servers.
> -
>
> Key: GEODE-9982
> URL: https://issues.apache.org/jira/browse/GEODE-9982
> Project: Geode
> Issue Type: Bug
> Components: native client
>Affects Versions: 1.12.8, 1.13.7, 1.14.0, 1.14.1, 1.14.2, 1.14.3, 1.14.4
>Reporter: Jacob Barrett
>Priority: Critical
>
> Geode Native C++ client v1.14.0 fails execution of
> testThinClientTransactionsWithoutSticky against current develop branch
> server. C++ client v1.14.0 does not fail when talking to a v1.14.0 server.
> Current develop branch C++ client does not fail when talking to a develop
> branch server. It appears there may be a protocol incompatibly issue between
> these two versions. More investigations to narrow down the version matrix is
> necessary.
> The following error is logged when the test fails:
> {{Error during send for endpoint 192.168.68.56:18539 due to
> apache::geode::client::IllegalStateException: Unregistered type in
> deserialization}}
> ||Server Versions|1.14.0|1.15.0|
> ||Client Versions||
> |1.14.0|P|F|
> |1.15.0|-|P|
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-9982) Native clients older than 1.15 fail do decode longer version ordinal from 1.15 servers.
[
https://issues.apache.org/jira/browse/GEODE-9982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacob Barrett updated GEODE-9982:
-
Summary: Native clients older than 1.15 fail do decode longer version
ordinal from 1.15 servers. (was: Backwards compatibility failure between older
C++ client and newer server.)
> Native clients older than 1.15 fail do decode longer version ordinal from
> 1.15 servers.
> ---
>
> Key: GEODE-9982
> URL: https://issues.apache.org/jira/browse/GEODE-9982
> Project: Geode
> Issue Type: Bug
> Components: native client
>Affects Versions: 1.12.8, 1.13.7, 1.14.0, 1.14.1, 1.14.2, 1.14.3, 1.14.4
>Reporter: Jacob Barrett
>Priority: Critical
>
> Geode Native C++ client v1.14.0 fails execution of
> testThinClientTransactionsWithoutSticky against current develop branch
> server. C++ client v1.14.0 does not fail when talking to a v1.14.0 server.
> Current develop branch C++ client does not fail when talking to a develop
> branch server. It appears there may be a protocol incompatibly issue between
> these two versions. More investigations to narrow down the version matrix is
> necessary.
> The following error is logged when the test fails:
> {{Error during send for endpoint 192.168.68.56:18539 due to
> apache::geode::client::IllegalStateException: Unregistered type in
> deserialization}}
> ||Server Versions|1.14.0|1.15.0|
> ||Client Versions||
> |1.14.0|P|F|
> |1.15.0|-|P|
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-9982) Backwards compatibility failure between older C++ client and newer server.
[
https://issues.apache.org/jira/browse/GEODE-9982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacob Barrett updated GEODE-9982:
-
Affects Version/s: 1.14.2
1.14.1
1.13.7
1.12.8
1.14.3
1.14.4
(was: 1.15.0)
> Backwards compatibility failure between older C++ client and newer server.
> --
>
> Key: GEODE-9982
> URL: https://issues.apache.org/jira/browse/GEODE-9982
> Project: Geode
> Issue Type: Bug
> Components: native client
>Affects Versions: 1.12.8, 1.13.7, 1.14.0, 1.14.1, 1.14.2, 1.14.3, 1.14.4
>Reporter: Jacob Barrett
>Priority: Critical
>
> Geode Native C++ client v1.14.0 fails execution of
> testThinClientTransactionsWithoutSticky against current develop branch
> server. C++ client v1.14.0 does not fail when talking to a v1.14.0 server.
> Current develop branch C++ client does not fail when talking to a develop
> branch server. It appears there may be a protocol incompatibly issue between
> these two versions. More investigations to narrow down the version matrix is
> necessary.
> The following error is logged when the test fails:
> {{Error during send for endpoint 192.168.68.56:18539 due to
> apache::geode::client::IllegalStateException: Unregistered type in
> deserialization}}
> ||Server Versions|1.14.0|1.15.0|
> ||Client Versions||
> |1.14.0|P|F|
> |1.15.0|-|P|
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-9982) Backwards compatibility failure between older C++ client and newer server.
[
https://issues.apache.org/jira/browse/GEODE-9982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacob Barrett updated GEODE-9982:
-
Priority: Critical (was: Blocker)
> Backwards compatibility failure between older C++ client and newer server.
> --
>
> Key: GEODE-9982
> URL: https://issues.apache.org/jira/browse/GEODE-9982
> Project: Geode
> Issue Type: Bug
> Components: native client
>Affects Versions: 1.14.0, 1.15.0
>Reporter: Jacob Barrett
>Priority: Critical
> Labels: blocks-1.15.0
>
> Geode Native C++ client v1.14.0 fails execution of
> testThinClientTransactionsWithoutSticky against current develop branch
> server. C++ client v1.14.0 does not fail when talking to a v1.14.0 server.
> Current develop branch C++ client does not fail when talking to a develop
> branch server. It appears there may be a protocol incompatibly issue between
> these two versions. More investigations to narrow down the version matrix is
> necessary.
> The following error is logged when the test fails:
> {{Error during send for endpoint 192.168.68.56:18539 due to
> apache::geode::client::IllegalStateException: Unregistered type in
> deserialization}}
> ||Server Versions|1.14.0|1.15.0|
> ||Client Versions||
> |1.14.0|P|F|
> |1.15.0|-|P|
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-9982) Backwards compatibility failure between older C++ client and newer server.
[
https://issues.apache.org/jira/browse/GEODE-9982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacob Barrett updated GEODE-9982:
-
Labels: (was: blocks-1.15.0)
> Backwards compatibility failure between older C++ client and newer server.
> --
>
> Key: GEODE-9982
> URL: https://issues.apache.org/jira/browse/GEODE-9982
> Project: Geode
> Issue Type: Bug
> Components: native client
>Affects Versions: 1.14.0, 1.15.0
>Reporter: Jacob Barrett
>Priority: Critical
>
> Geode Native C++ client v1.14.0 fails execution of
> testThinClientTransactionsWithoutSticky against current develop branch
> server. C++ client v1.14.0 does not fail when talking to a v1.14.0 server.
> Current develop branch C++ client does not fail when talking to a develop
> branch server. It appears there may be a protocol incompatibly issue between
> these two versions. More investigations to narrow down the version matrix is
> necessary.
> The following error is logged when the test fails:
> {{Error during send for endpoint 192.168.68.56:18539 due to
> apache::geode::client::IllegalStateException: Unregistered type in
> deserialization}}
> ||Server Versions|1.14.0|1.15.0|
> ||Client Versions||
> |1.14.0|P|F|
> |1.15.0|-|P|
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-9982) Backwards compatibility failure between older C++ client and newer server.
[
https://issues.apache.org/jira/browse/GEODE-9982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17481438#comment-17481438
]
Jacob Barrett commented on GEODE-9982:
--
Since the issue isn't in 1.15 and no change could be made to 1.15 to address
older clients I am going to remove the blocker and adjust the versions affected.
> Backwards compatibility failure between older C++ client and newer server.
> --
>
> Key: GEODE-9982
> URL: https://issues.apache.org/jira/browse/GEODE-9982
> Project: Geode
> Issue Type: Bug
> Components: native client
>Affects Versions: 1.14.0, 1.15.0
>Reporter: Jacob Barrett
>Priority: Blocker
> Labels: blocks-1.15.0
>
> Geode Native C++ client v1.14.0 fails execution of
> testThinClientTransactionsWithoutSticky against current develop branch
> server. C++ client v1.14.0 does not fail when talking to a v1.14.0 server.
> Current develop branch C++ client does not fail when talking to a develop
> branch server. It appears there may be a protocol incompatibly issue between
> these two versions. More investigations to narrow down the version matrix is
> necessary.
> The following error is logged when the test fails:
> {{Error during send for endpoint 192.168.68.56:18539 due to
> apache::geode::client::IllegalStateException: Unregistered type in
> deserialization}}
> ||Server Versions|1.14.0|1.15.0|
> ||Client Versions||
> |1.14.0|P|F|
> |1.15.0|-|P|
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-9982) Backwards compatibility failure between older C++ client and newer server.
[
https://issues.apache.org/jira/browse/GEODE-9982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17481436#comment-17481436
]
Jacob Barrett commented on GEODE-9982:
--
The issue was introduced about 4 years ago but only manifests now that the
server's ordinal value is 2 bytes long. The statement to read the short value
was omitted by logging guard embedded in a macro. This patch will need to be
applied to any previous version of Geode Native we want to support server
upgrades beyond 1.14.0. Any version of Geode that has any version ordinal
greater than 127 will result in this short read error.
It is also very interesting that this issue only affected these transaction
tests and not other tests that likely transmit the member id.
> Backwards compatibility failure between older C++ client and newer server.
> --
>
> Key: GEODE-9982
> URL: https://issues.apache.org/jira/browse/GEODE-9982
> Project: Geode
> Issue Type: Bug
> Components: native client
>Affects Versions: 1.14.0, 1.15.0
>Reporter: Jacob Barrett
>Priority: Blocker
> Labels: blocks-1.15.0
>
> Geode Native C++ client v1.14.0 fails execution of
> testThinClientTransactionsWithoutSticky against current develop branch
> server. C++ client v1.14.0 does not fail when talking to a v1.14.0 server.
> Current develop branch C++ client does not fail when talking to a develop
> branch server. It appears there may be a protocol incompatibly issue between
> these two versions. More investigations to narrow down the version matrix is
> necessary.
> The following error is logged when the test fails:
> {{Error during send for endpoint 192.168.68.56:18539 due to
> apache::geode::client::IllegalStateException: Unregistered type in
> deserialization}}
> ||Server Versions|1.14.0|1.15.0|
> ||Client Versions||
> |1.14.0|P|F|
> |1.15.0|-|P|
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-9973) Documentation: socket-lease-time is not used to return sockets to a pool but to close them
[ https://issues.apache.org/jira/browse/GEODE-9973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17481425#comment-17481425 ] Dave Barnes commented on GEODE-9973: Apologies if I merged prematurely. I'll hold off on the documentation back-ports until the described behavior has been verified. > Documentation: socket-lease-time is not used to return sockets to a pool but > to close them > -- > > Key: GEODE-9973 > URL: https://issues.apache.org/jira/browse/GEODE-9973 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Alberto Gomez >Assignee: Donal Evans >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > The "Making sure you have enough sockets" Geode documentation section says > the following about socket-lease-time (check underlined sentence): > > Peer-to-peer. For peer-to-peer threads that do not share sockets, you can use > the socket-lease-time to make sure that no socket sits idle for too long. > +When a socket that belongs to an individual thread remains unused for this > time period, the system automatically returns it to the pool.+ The next time > the thread needs a socket, it creates a new socket. > > Actually, the system automatically closes the connection in the situation > described instead of returning it to any pool. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9973) Documentation: socket-lease-time is not used to return sockets to a pool but to close them
[ https://issues.apache.org/jira/browse/GEODE-9973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17481410#comment-17481410 ] Donal Evans commented on GEODE-9973: [~alberto.gomez] Would it be possible to get an explanation of how to see in the codebase that this documentation was incorrect? A test showing that the socket is closed rather than returned to a pool would be ideal, but just indicating the code path that causes this behaviour would be fine too. > Documentation: socket-lease-time is not used to return sockets to a pool but > to close them > -- > > Key: GEODE-9973 > URL: https://issues.apache.org/jira/browse/GEODE-9973 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Alberto Gomez >Assignee: Donal Evans >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > The "Making sure you have enough sockets" Geode documentation section says > the following about socket-lease-time (check underlined sentence): > > Peer-to-peer. For peer-to-peer threads that do not share sockets, you can use > the socket-lease-time to make sure that no socket sits idle for too long. > +When a socket that belongs to an individual thread remains unused for this > time period, the system automatically returns it to the pool.+ The next time > the thread needs a socket, it creates a new socket. > > Actually, the system automatically closes the connection in the situation > described instead of returning it to any pool. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9973) Documentation: socket-lease-time is not used to return sockets to a pool but to close them
[ https://issues.apache.org/jira/browse/GEODE-9973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17481408#comment-17481408 ] Donal Evans commented on GEODE-9973: The PR was already merged by [~dbarnes], so I'll mark this ticket as resolved. If, on further investigation it turns out that this ticket was not accurate, I'll revert the change. > Documentation: socket-lease-time is not used to return sockets to a pool but > to close them > -- > > Key: GEODE-9973 > URL: https://issues.apache.org/jira/browse/GEODE-9973 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Alberto Gomez >Assignee: Donal Evans >Priority: Major > Labels: pull-request-available > > The "Making sure you have enough sockets" Geode documentation section says > the following about socket-lease-time (check underlined sentence): > > Peer-to-peer. For peer-to-peer threads that do not share sockets, you can use > the socket-lease-time to make sure that no socket sits idle for too long. > +When a socket that belongs to an individual thread remains unused for this > time period, the system automatically returns it to the pool.+ The next time > the thread needs a socket, it creates a new socket. > > Actually, the system automatically closes the connection in the situation > described instead of returning it to any pool. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (GEODE-9973) Documentation: socket-lease-time is not used to return sockets to a pool but to close them
[ https://issues.apache.org/jira/browse/GEODE-9973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donal Evans resolved GEODE-9973. Fix Version/s: 1.15.0 Resolution: Fixed > Documentation: socket-lease-time is not used to return sockets to a pool but > to close them > -- > > Key: GEODE-9973 > URL: https://issues.apache.org/jira/browse/GEODE-9973 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Alberto Gomez >Assignee: Donal Evans >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > The "Making sure you have enough sockets" Geode documentation section says > the following about socket-lease-time (check underlined sentence): > > Peer-to-peer. For peer-to-peer threads that do not share sockets, you can use > the socket-lease-time to make sure that no socket sits idle for too long. > +When a socket that belongs to an individual thread remains unused for this > time period, the system automatically returns it to the pool.+ The next time > the thread needs a socket, it creates a new socket. > > Actually, the system automatically closes the connection in the situation > described instead of returning it to any pool. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-9986) Mass-Test-Run: StartLocatorCommandDUnitTest > executionError FAILED
[
https://issues.apache.org/jira/browse/GEODE-9986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristen updated GEODE-9986:
---
Summary: Mass-Test-Run: StartLocatorCommandDUnitTest > executionError
FAILED (was: Mass-Test-Run StartLocatorCommandDUnitTest > executionError
FAILED)
> Mass-Test-Run: StartLocatorCommandDUnitTest > executionError FAILED
> ---
>
> Key: GEODE-9986
> URL: https://issues.apache.org/jira/browse/GEODE-9986
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Kristen
>Priority: Major
> Labels: needsTriage
>
> {code:java}
> > Task :geode-assembly:distributedTest
> StartLocatorCommandDUnitTest > testWithAvailablePort FAILED
> org.opentest4j.AssertionFailedError: [The Locator process terminated
> unexpectedly with exit status 1. Please refer to the log file in
> /tmp/junit4212781718034424448/junit8849905322533733269 for full details.
> Exception in thread "main"
> org.apache.geode.distributed.DistributedSystemDisconnectedException:
> Distribution manager on
> heavy-lifter-501890ca-346e-5a45-9c21-2e28585dba8b(testWithAvailablePort:37687:locator):41001
> started at Sat Jan 22 08:31:19 UTC 2022: Message distribution has
> terminated, caused by org.apache.geode.ForcedDisconnectException: Member
> isn't responding to heartbeat requests
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager$Stopper.generateCancelledException(ClusterDistributionManager.java:2893)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem$Stopper.generateCancelledException(InternalDistributedSystem.java:1177)
> at
> org.apache.geode.CancelCriterion.checkCancelInProgress(CancelCriterion.java:83)
> at
> org.apache.geode.distributed.internal.locks.DLockService.create(DLockService.java:2686)
> at
> org.apache.geode.distributed.internal.locks.DLockService.create(DLockService.java:2660)
> at
> org.apache.geode.distributed.internal.locks.DLockService.getOrCreateService(DLockService.java:2641)
> at
> org.apache.geode.distributed.internal.InternalConfigurationPersistenceService.(InternalConfigurationPersistenceService.java:131)
> at
> org.apache.geode.distributed.internal.InternalLocator.startConfigurationPersistenceService(InternalLocator.java:1390)
> at
> org.apache.geode.distributed.internal.InternalLocator.startClusterManagementService(InternalLocator.java:792)
> at
> org.apache.geode.distributed.internal.InternalLocator.startCache(InternalLocator.java:787)
> at
> org.apache.geode.distributed.internal.InternalLocator.startDistributedSystem(InternalLocator.java:768)
> at
> org.apache.geode.distributed.internal.InternalLocator.startLocator(InternalLocator.java:399)
> at
> org.apache.geode.distributed.LocatorLauncher.start(LocatorLauncher.java:734)
> at
> org.apache.geode.distributed.LocatorLauncher.run(LocatorLauncher.java:637)
> at
> org.apache.geode.distributed.LocatorLauncher.main(LocatorLauncher.java:220)
> Caused by: org.apache.geode.ForcedDisconnectException: Member isn't
> responding to heartbeat requests
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager$DMListener.membershipFailure(ClusterDistributionManager.java:2319)
> at
> org.apache.geode.distributed.internal.membership.gms.GMSMembership.uncleanShutdown(GMSMembership.java:1190)
> at
> org.apache.geode.distributed.internal.membership.gms.GMSMembership$ManagerImpl.lambda$uncleanShutdownDS$0(GMSMembership.java:1793)
> at java.lang.Thread.run(Thread.java:750)
> ]
> expected: OK
> but was: ERROR
> 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.assertions.CommandResultAssert.statusIsSuccess(CommandResultAssert.java:104)
> at
> org.apache.geode.management.internal.cli.commands.StartLocatorCommandDUnitTest.testWithAvailablePort(StartLocatorCommandDUnitTest.java:219)
> StartLocatorCommandDUnitTest > executionError 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 'dunit_suspect-vm0.log' at line 591
> [fatal 2022/01/22 08:31:40.041 UTC
> tid=58] Possible loss of quorum due to the loss of 1 cache processes:
>
[jira] [Updated] (GEODE-9985) Mass-Test-Run: SlowDispatcherDUnitTest > registeredInterest_durableClient_kill_primarySever_receives_marker FAILED
[
https://issues.apache.org/jira/browse/GEODE-9985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristen updated GEODE-9985:
---
Summary: Mass-Test-Run: SlowDispatcherDUnitTest >
registeredInterest_durableClient_kill_primarySever_receives_marker FAILED
(was: Mass-Test-Run SlowDispatcherDUnitTest >
registeredInterest_durableClient_kill_primarySever_receives_marker FAILED)
> Mass-Test-Run: SlowDispatcherDUnitTest >
> registeredInterest_durableClient_kill_primarySever_receives_marker FAILED
> --
>
> Key: GEODE-9985
> URL: https://issues.apache.org/jira/browse/GEODE-9985
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Kristen
>Priority: Major
> Labels: needsTriage
>
> {code:java}
> SlowDispatcherDUnitTest >
> registeredInterest_durableClient_kill_primarySever_receives_marker FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.tier.sockets.SlowDispatcherDUnitTest$$Lambda$299/1561169457.run
> in VM 3 running on Host
> heavy-lifter-f18312bf-ecf3-5384-8b36-e5d91bf8ebb9.c.apachegeode-ci.internal
> with 5 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.test.junit.rules.VMProvider.invoke(VMProvider.java:96)
> at
> org.apache.geode.internal.cache.tier.sockets.SlowDispatcherDUnitTest.registeredInterest_durableClient_kill_primarySever_receives_marker(SlowDispatcherDUnitTest.java:135)
> Caused by:
> org.awaitility.core.ConditionTimeoutException: Assertion condition
> defined as a
> org.apache.geode.internal.cache.tier.sockets.SlowDispatcherDUnitTest
> expected: 49
> but was: 40 within 5 minutes.
> at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:164)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
> at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:939)
> at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:723)
> at
> org.apache.geode.internal.cache.tier.sockets.SlowDispatcherDUnitTest.lambda$registeredInterest_durableClient_kill_primarySever_receives_marker$bb17a952$2(SlowDispatcherDUnitTest.java:137)
> Caused by:
> org.opentest4j.AssertionFailedError:
> expected: 49
> but was: 40
> at
> sun.reflect.GeneratedConstructorAccessor21.newInstance(Unknown Source)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.internal.cache.tier.sockets.SlowDispatcherDUnitTest.lambda$null$2(SlowDispatcherDUnitTest.java:137)
> 8357 tests completed, 1 failed, 414 skipped
> {code}
> Test report artifacts from {color:#172b4d}this{color} job are available at:
> http:{color:#172b4d}//files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0806/test-artifacts/1642831372/distributedtestfiles-openjdk8-1.15.0-build.0806.tgz{color}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-9984) Mass-Test-Run: WanCopyRegionCommandDUnitTest > testCommandDoesNotCopyEntriesUpdatedAfterCommandStarted FAILED
[ https://issues.apache.org/jira/browse/GEODE-9984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristen updated GEODE-9984: --- Summary: Mass-Test-Run: WanCopyRegionCommandDUnitTest > testCommandDoesNotCopyEntriesUpdatedAfterCommandStarted FAILED (was: Mass-Test-Run WanCopyRegionCommandDUnitTest > testCommandDoesNotCopyEntriesUpdatedAfterCommandStarted FAILED) > Mass-Test-Run: WanCopyRegionCommandDUnitTest > > testCommandDoesNotCopyEntriesUpdatedAfterCommandStarted FAILED > - > > Key: GEODE-9984 > URL: https://issues.apache.org/jira/browse/GEODE-9984 > Project: Geode > Issue Type: Bug >Affects Versions: 1.15.0 >Reporter: Kristen >Priority: Major > Labels: needsTriage > > WanCopyRegionCommandDUnitTest > > testCommandDoesNotCopyEntriesUpdatedAfterCommandStarted(true, true) [0] FAILED > org.opentest4j.AssertionFailedError: > expected: 5 > but was: 50001 > 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.cache.wan.internal.cli.commands.WanCopyRegionCommandDUnitTest.testCommandDoesNotCopyEntriesUpdatedAfterCommandStarted(WanCopyRegionCommandDUnitTest.java:884) > 948 tests completed, 1 failed, 59 skipped > Test report artifacts from this job are available at: > [*http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0806/test-artifacts/1642850654/distributedtestfiles-openjdk8-1.15.0-build.0806.tgz*] > > > > May be an issue similar or related to > https://issues.apache.org/jira/browse/GEODE-9859. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-9986) Mass-Test-Run StartLocatorCommandDUnitTest > executionError FAILED
[
https://issues.apache.org/jira/browse/GEODE-9986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Murmann updated GEODE-9986:
-
Labels: needsTriage (was: )
> Mass-Test-Run StartLocatorCommandDUnitTest > executionError FAILED
> --
>
> Key: GEODE-9986
> URL: https://issues.apache.org/jira/browse/GEODE-9986
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Kristen
>Priority: Major
> Labels: needsTriage
>
> {code:java}
> > Task :geode-assembly:distributedTest
> StartLocatorCommandDUnitTest > testWithAvailablePort FAILED
> org.opentest4j.AssertionFailedError: [The Locator process terminated
> unexpectedly with exit status 1. Please refer to the log file in
> /tmp/junit4212781718034424448/junit8849905322533733269 for full details.
> Exception in thread "main"
> org.apache.geode.distributed.DistributedSystemDisconnectedException:
> Distribution manager on
> heavy-lifter-501890ca-346e-5a45-9c21-2e28585dba8b(testWithAvailablePort:37687:locator):41001
> started at Sat Jan 22 08:31:19 UTC 2022: Message distribution has
> terminated, caused by org.apache.geode.ForcedDisconnectException: Member
> isn't responding to heartbeat requests
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager$Stopper.generateCancelledException(ClusterDistributionManager.java:2893)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem$Stopper.generateCancelledException(InternalDistributedSystem.java:1177)
> at
> org.apache.geode.CancelCriterion.checkCancelInProgress(CancelCriterion.java:83)
> at
> org.apache.geode.distributed.internal.locks.DLockService.create(DLockService.java:2686)
> at
> org.apache.geode.distributed.internal.locks.DLockService.create(DLockService.java:2660)
> at
> org.apache.geode.distributed.internal.locks.DLockService.getOrCreateService(DLockService.java:2641)
> at
> org.apache.geode.distributed.internal.InternalConfigurationPersistenceService.(InternalConfigurationPersistenceService.java:131)
> at
> org.apache.geode.distributed.internal.InternalLocator.startConfigurationPersistenceService(InternalLocator.java:1390)
> at
> org.apache.geode.distributed.internal.InternalLocator.startClusterManagementService(InternalLocator.java:792)
> at
> org.apache.geode.distributed.internal.InternalLocator.startCache(InternalLocator.java:787)
> at
> org.apache.geode.distributed.internal.InternalLocator.startDistributedSystem(InternalLocator.java:768)
> at
> org.apache.geode.distributed.internal.InternalLocator.startLocator(InternalLocator.java:399)
> at
> org.apache.geode.distributed.LocatorLauncher.start(LocatorLauncher.java:734)
> at
> org.apache.geode.distributed.LocatorLauncher.run(LocatorLauncher.java:637)
> at
> org.apache.geode.distributed.LocatorLauncher.main(LocatorLauncher.java:220)
> Caused by: org.apache.geode.ForcedDisconnectException: Member isn't
> responding to heartbeat requests
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager$DMListener.membershipFailure(ClusterDistributionManager.java:2319)
> at
> org.apache.geode.distributed.internal.membership.gms.GMSMembership.uncleanShutdown(GMSMembership.java:1190)
> at
> org.apache.geode.distributed.internal.membership.gms.GMSMembership$ManagerImpl.lambda$uncleanShutdownDS$0(GMSMembership.java:1793)
> at java.lang.Thread.run(Thread.java:750)
> ]
> expected: OK
> but was: ERROR
> 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.assertions.CommandResultAssert.statusIsSuccess(CommandResultAssert.java:104)
> at
> org.apache.geode.management.internal.cli.commands.StartLocatorCommandDUnitTest.testWithAvailablePort(StartLocatorCommandDUnitTest.java:219)
> StartLocatorCommandDUnitTest > executionError 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 'dunit_suspect-vm0.log' at line 591
> [fatal 2022/01/22 08:31:40.041 UTC
> tid=58] Possible loss of quorum due to the loss of 1 cache processes:
> [heavy-lifter-501890ca-346e-5a45-9c21-2e28585dba8b(testWithAvailablePort:37687:locator):41001]
>
[jira] [Created] (GEODE-9986) Mass-Test-Run StartLocatorCommandDUnitTest > executionError FAILED
Kristen created GEODE-9986:
--
Summary: Mass-Test-Run StartLocatorCommandDUnitTest >
executionError FAILED
Key: GEODE-9986
URL: https://issues.apache.org/jira/browse/GEODE-9986
Project: Geode
Issue Type: Bug
Affects Versions: 1.15.0
Reporter: Kristen
{code:java}
> Task :geode-assembly:distributedTest
StartLocatorCommandDUnitTest > testWithAvailablePort FAILED
org.opentest4j.AssertionFailedError: [The Locator process terminated
unexpectedly with exit status 1. Please refer to the log file in
/tmp/junit4212781718034424448/junit8849905322533733269 for full details.
Exception in thread "main"
org.apache.geode.distributed.DistributedSystemDisconnectedException:
Distribution manager on
heavy-lifter-501890ca-346e-5a45-9c21-2e28585dba8b(testWithAvailablePort:37687:locator):41001
started at Sat Jan 22 08:31:19 UTC 2022: Message distribution has terminated,
caused by org.apache.geode.ForcedDisconnectException: Member isn't responding
to heartbeat requests
at
org.apache.geode.distributed.internal.ClusterDistributionManager$Stopper.generateCancelledException(ClusterDistributionManager.java:2893)
at
org.apache.geode.distributed.internal.InternalDistributedSystem$Stopper.generateCancelledException(InternalDistributedSystem.java:1177)
at
org.apache.geode.CancelCriterion.checkCancelInProgress(CancelCriterion.java:83)
at
org.apache.geode.distributed.internal.locks.DLockService.create(DLockService.java:2686)
at
org.apache.geode.distributed.internal.locks.DLockService.create(DLockService.java:2660)
at
org.apache.geode.distributed.internal.locks.DLockService.getOrCreateService(DLockService.java:2641)
at
org.apache.geode.distributed.internal.InternalConfigurationPersistenceService.(InternalConfigurationPersistenceService.java:131)
at
org.apache.geode.distributed.internal.InternalLocator.startConfigurationPersistenceService(InternalLocator.java:1390)
at
org.apache.geode.distributed.internal.InternalLocator.startClusterManagementService(InternalLocator.java:792)
at
org.apache.geode.distributed.internal.InternalLocator.startCache(InternalLocator.java:787)
at
org.apache.geode.distributed.internal.InternalLocator.startDistributedSystem(InternalLocator.java:768)
at
org.apache.geode.distributed.internal.InternalLocator.startLocator(InternalLocator.java:399)
at
org.apache.geode.distributed.LocatorLauncher.start(LocatorLauncher.java:734)
at
org.apache.geode.distributed.LocatorLauncher.run(LocatorLauncher.java:637)
at
org.apache.geode.distributed.LocatorLauncher.main(LocatorLauncher.java:220)
Caused by: org.apache.geode.ForcedDisconnectException: Member isn't
responding to heartbeat requests
at
org.apache.geode.distributed.internal.ClusterDistributionManager$DMListener.membershipFailure(ClusterDistributionManager.java:2319)
at
org.apache.geode.distributed.internal.membership.gms.GMSMembership.uncleanShutdown(GMSMembership.java:1190)
at
org.apache.geode.distributed.internal.membership.gms.GMSMembership$ManagerImpl.lambda$uncleanShutdownDS$0(GMSMembership.java:1793)
at java.lang.Thread.run(Thread.java:750)
]
expected: OK
but was: ERROR
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.assertions.CommandResultAssert.statusIsSuccess(CommandResultAssert.java:104)
at
org.apache.geode.management.internal.cli.commands.StartLocatorCommandDUnitTest.testWithAvailablePort(StartLocatorCommandDUnitTest.java:219)
StartLocatorCommandDUnitTest > executionError 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 'dunit_suspect-vm0.log' at line 591
[fatal 2022/01/22 08:31:40.041 UTC tid=58]
Possible loss of quorum due to the loss of 1 cache processes:
[heavy-lifter-501890ca-346e-5a45-9c21-2e28585dba8b(testWithAvailablePort:37687:locator):41001]
---
Found suspect string in 'dunit_suspect-vm0.log' at line 601
[fatal 2022/01/22 08:31:41.062 UTC tid=58]
Membership service failure: Exiting due to possible network partition event due
to loss of 1 cache processes:
[heavy-lifter-501890ca-346e-5a45-9c21-2e28585dba8b(testWithAvailablePort:37687:locator):41001]
org.apache.geode.distributed.internal.membership.api.MemberDisconnectedException:
Exiting
[jira] [Commented] (GEODE-9986) Mass-Test-Run StartLocatorCommandDUnitTest > executionError FAILED
[
https://issues.apache.org/jira/browse/GEODE-9986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17481364#comment-17481364
]
Geode Integration commented on GEODE-9986:
--
Seen in [distributed-test-openjdk8
#734|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/734]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0806/test-results/distributedTest/1642848640/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0806/test-artifacts/1642848640/distributedtestfiles-openjdk8-1.15.0-build.0806.tgz].
> Mass-Test-Run StartLocatorCommandDUnitTest > executionError FAILED
> --
>
> Key: GEODE-9986
> URL: https://issues.apache.org/jira/browse/GEODE-9986
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Kristen
>Priority: Major
> Labels: needsTriage
>
> {code:java}
> > Task :geode-assembly:distributedTest
> StartLocatorCommandDUnitTest > testWithAvailablePort FAILED
> org.opentest4j.AssertionFailedError: [The Locator process terminated
> unexpectedly with exit status 1. Please refer to the log file in
> /tmp/junit4212781718034424448/junit8849905322533733269 for full details.
> Exception in thread "main"
> org.apache.geode.distributed.DistributedSystemDisconnectedException:
> Distribution manager on
> heavy-lifter-501890ca-346e-5a45-9c21-2e28585dba8b(testWithAvailablePort:37687:locator):41001
> started at Sat Jan 22 08:31:19 UTC 2022: Message distribution has
> terminated, caused by org.apache.geode.ForcedDisconnectException: Member
> isn't responding to heartbeat requests
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager$Stopper.generateCancelledException(ClusterDistributionManager.java:2893)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem$Stopper.generateCancelledException(InternalDistributedSystem.java:1177)
> at
> org.apache.geode.CancelCriterion.checkCancelInProgress(CancelCriterion.java:83)
> at
> org.apache.geode.distributed.internal.locks.DLockService.create(DLockService.java:2686)
> at
> org.apache.geode.distributed.internal.locks.DLockService.create(DLockService.java:2660)
> at
> org.apache.geode.distributed.internal.locks.DLockService.getOrCreateService(DLockService.java:2641)
> at
> org.apache.geode.distributed.internal.InternalConfigurationPersistenceService.(InternalConfigurationPersistenceService.java:131)
> at
> org.apache.geode.distributed.internal.InternalLocator.startConfigurationPersistenceService(InternalLocator.java:1390)
> at
> org.apache.geode.distributed.internal.InternalLocator.startClusterManagementService(InternalLocator.java:792)
> at
> org.apache.geode.distributed.internal.InternalLocator.startCache(InternalLocator.java:787)
> at
> org.apache.geode.distributed.internal.InternalLocator.startDistributedSystem(InternalLocator.java:768)
> at
> org.apache.geode.distributed.internal.InternalLocator.startLocator(InternalLocator.java:399)
> at
> org.apache.geode.distributed.LocatorLauncher.start(LocatorLauncher.java:734)
> at
> org.apache.geode.distributed.LocatorLauncher.run(LocatorLauncher.java:637)
> at
> org.apache.geode.distributed.LocatorLauncher.main(LocatorLauncher.java:220)
> Caused by: org.apache.geode.ForcedDisconnectException: Member isn't
> responding to heartbeat requests
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager$DMListener.membershipFailure(ClusterDistributionManager.java:2319)
> at
> org.apache.geode.distributed.internal.membership.gms.GMSMembership.uncleanShutdown(GMSMembership.java:1190)
> at
> org.apache.geode.distributed.internal.membership.gms.GMSMembership$ManagerImpl.lambda$uncleanShutdownDS$0(GMSMembership.java:1793)
> at java.lang.Thread.run(Thread.java:750)
> ]
> expected: OK
> but was: ERROR
> 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.assertions.CommandResultAssert.statusIsSuccess(CommandResultAssert.java:104)
> at
> org.apache.geode.management.internal.cli.commands.StartLocatorCommandDUnitTest.testWithAvailablePort(StartLocatorCommandDUnitTest.java:219)
> StartLocatorCommandDUnitTest > executionError FAILED
> java.lang.AssertionError: Suspicious strings were written to the log
[jira] [Commented] (GEODE-9985) Mass-Test-Run SlowDispatcherDUnitTest > registeredInterest_durableClient_kill_primarySever_receives_marker FAILED
[
https://issues.apache.org/jira/browse/GEODE-9985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17481345#comment-17481345
]
Geode Integration commented on GEODE-9985:
--
Seen in [distributed-test-openjdk8
#718|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/718]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0806/test-results/distributedTest/1642831372/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0806/test-artifacts/1642831372/distributedtestfiles-openjdk8-1.15.0-build.0806.tgz].
> Mass-Test-Run SlowDispatcherDUnitTest >
> registeredInterest_durableClient_kill_primarySever_receives_marker FAILED
> -
>
> Key: GEODE-9985
> URL: https://issues.apache.org/jira/browse/GEODE-9985
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Kristen
>Priority: Major
> Labels: needsTriage
>
> {code:java}
> SlowDispatcherDUnitTest >
> registeredInterest_durableClient_kill_primarySever_receives_marker FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.tier.sockets.SlowDispatcherDUnitTest$$Lambda$299/1561169457.run
> in VM 3 running on Host
> heavy-lifter-f18312bf-ecf3-5384-8b36-e5d91bf8ebb9.c.apachegeode-ci.internal
> with 5 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.test.junit.rules.VMProvider.invoke(VMProvider.java:96)
> at
> org.apache.geode.internal.cache.tier.sockets.SlowDispatcherDUnitTest.registeredInterest_durableClient_kill_primarySever_receives_marker(SlowDispatcherDUnitTest.java:135)
> Caused by:
> org.awaitility.core.ConditionTimeoutException: Assertion condition
> defined as a
> org.apache.geode.internal.cache.tier.sockets.SlowDispatcherDUnitTest
> expected: 49
> but was: 40 within 5 minutes.
> at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:164)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
> at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:939)
> at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:723)
> at
> org.apache.geode.internal.cache.tier.sockets.SlowDispatcherDUnitTest.lambda$registeredInterest_durableClient_kill_primarySever_receives_marker$bb17a952$2(SlowDispatcherDUnitTest.java:137)
> Caused by:
> org.opentest4j.AssertionFailedError:
> expected: 49
> but was: 40
> at
> sun.reflect.GeneratedConstructorAccessor21.newInstance(Unknown Source)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.internal.cache.tier.sockets.SlowDispatcherDUnitTest.lambda$null$2(SlowDispatcherDUnitTest.java:137)
> 8357 tests completed, 1 failed, 414 skipped
> {code}
> Test report artifacts from {color:#172b4d}this{color} job are available at:
> http:{color:#172b4d}//files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0806/test-artifacts/1642831372/distributedtestfiles-openjdk8-1.15.0-build.0806.tgz{color}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-9985) Mass-Test-Run SlowDispatcherDUnitTest > registeredInterest_durableClient_kill_primarySever_receives_marker FAILED
[
https://issues.apache.org/jira/browse/GEODE-9985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristen updated GEODE-9985:
---
Description:
{code:java}
SlowDispatcherDUnitTest >
registeredInterest_durableClient_kill_primarySever_receives_marker FAILED
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.internal.cache.tier.sockets.SlowDispatcherDUnitTest$$Lambda$299/1561169457.run
in VM 3 running on Host
heavy-lifter-f18312bf-ecf3-5384-8b36-e5d91bf8ebb9.c.apachegeode-ci.internal
with 5 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.test.junit.rules.VMProvider.invoke(VMProvider.java:96)
at
org.apache.geode.internal.cache.tier.sockets.SlowDispatcherDUnitTest.registeredInterest_durableClient_kill_primarySever_receives_marker(SlowDispatcherDUnitTest.java:135)
Caused by:
org.awaitility.core.ConditionTimeoutException: Assertion condition
defined as a
org.apache.geode.internal.cache.tier.sockets.SlowDispatcherDUnitTest
expected: 49
but was: 40 within 5 minutes.
at
org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:164)
at
org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
at
org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
at
org.awaitility.core.ConditionFactory.until(ConditionFactory.java:939)
at
org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:723)
at
org.apache.geode.internal.cache.tier.sockets.SlowDispatcherDUnitTest.lambda$registeredInterest_durableClient_kill_primarySever_receives_marker$bb17a952$2(SlowDispatcherDUnitTest.java:137)
Caused by:
org.opentest4j.AssertionFailedError:
expected: 49
but was: 40
at
sun.reflect.GeneratedConstructorAccessor21.newInstance(Unknown Source)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at
org.apache.geode.internal.cache.tier.sockets.SlowDispatcherDUnitTest.lambda$null$2(SlowDispatcherDUnitTest.java:137)
8357 tests completed, 1 failed, 414 skipped
{code}
Test report artifacts from {color:#172b4d}this{color} job are available at:
http:{color:#172b4d}//files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0806/test-artifacts/1642831372/distributedtestfiles-openjdk8-1.15.0-build.0806.tgz{color}
was:
{code:java}
SlowDispatcherDUnitTest >
registeredInterest_durableClient_kill_primarySever_receives_marker FAILED
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.internal.cache.tier.sockets.SlowDispatcherDUnitTest$$Lambda$299/1561169457.run
in VM 3 running on Host
heavy-lifter-f18312bf-ecf3-5384-8b36-e5d91bf8ebb9.c.apachegeode-ci.internal
with 5 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.test.junit.rules.VMProvider.invoke(VMProvider.java:96)
at
org.apache.geode.internal.cache.tier.sockets.SlowDispatcherDUnitTest.registeredInterest_durableClient_kill_primarySever_receives_marker(SlowDispatcherDUnitTest.java:135)
Caused by:
org.awaitility.core.ConditionTimeoutException: Assertion condition
defined as a
org.apache.geode.internal.cache.tier.sockets.SlowDispatcherDUnitTest
expected: 49
but was: 40 within 5 minutes.
at
org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:164)
at
org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
at
org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
at
org.awaitility.core.ConditionFactory.until(ConditionFactory.java:939)
at
org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:723)
at
org.apache.geode.internal.cache.tier.sockets.SlowDispatcherDUnitTest.lambda$registeredInterest_durableClient_kill_primarySever_receives_marker$bb17a952$2(SlowDispatcherDUnitTest.java:137)
Caused by:
org.opentest4j.AssertionFailedError:
expected: 49
but was: 40
at
sun.reflect.GeneratedConstructorAccessor21.newInstance(Unknown Source)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at
org.apache.geode.internal.cache.tier.sockets.SlowDispatcherDUnitTest.lambda$null$2(SlowDispatcherDUnitTest.java:137)
8357 tests completed, 1 failed, 414 skipped
Test report artifacts from this job are available at:
[jira] [Created] (GEODE-9985) Mass-Test-Run SlowDispatcherDUnitTest > registeredInterest_durableClient_kill_primarySever_receives_marker FAILED
Kristen created GEODE-9985:
--
Summary: Mass-Test-Run SlowDispatcherDUnitTest >
registeredInterest_durableClient_kill_primarySever_receives_marker FAILED
Key: GEODE-9985
URL: https://issues.apache.org/jira/browse/GEODE-9985
Project: Geode
Issue Type: Bug
Affects Versions: 1.15.0
Reporter: Kristen
{code:java}
SlowDispatcherDUnitTest >
registeredInterest_durableClient_kill_primarySever_receives_marker FAILED
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.internal.cache.tier.sockets.SlowDispatcherDUnitTest$$Lambda$299/1561169457.run
in VM 3 running on Host
heavy-lifter-f18312bf-ecf3-5384-8b36-e5d91bf8ebb9.c.apachegeode-ci.internal
with 5 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.test.junit.rules.VMProvider.invoke(VMProvider.java:96)
at
org.apache.geode.internal.cache.tier.sockets.SlowDispatcherDUnitTest.registeredInterest_durableClient_kill_primarySever_receives_marker(SlowDispatcherDUnitTest.java:135)
Caused by:
org.awaitility.core.ConditionTimeoutException: Assertion condition
defined as a
org.apache.geode.internal.cache.tier.sockets.SlowDispatcherDUnitTest
expected: 49
but was: 40 within 5 minutes.
at
org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:164)
at
org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
at
org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
at
org.awaitility.core.ConditionFactory.until(ConditionFactory.java:939)
at
org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:723)
at
org.apache.geode.internal.cache.tier.sockets.SlowDispatcherDUnitTest.lambda$registeredInterest_durableClient_kill_primarySever_receives_marker$bb17a952$2(SlowDispatcherDUnitTest.java:137)
Caused by:
org.opentest4j.AssertionFailedError:
expected: 49
but was: 40
at
sun.reflect.GeneratedConstructorAccessor21.newInstance(Unknown Source)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at
org.apache.geode.internal.cache.tier.sockets.SlowDispatcherDUnitTest.lambda$null$2(SlowDispatcherDUnitTest.java:137)
8357 tests completed, 1 failed, 414 skipped
Test report artifacts from this job are available at:
http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0806/test-artifacts/1642831372/distributedtestfiles-openjdk8-1.15.0-build.0806.tgz{code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-9985) Mass-Test-Run SlowDispatcherDUnitTest > registeredInterest_durableClient_kill_primarySever_receives_marker FAILED
[
https://issues.apache.org/jira/browse/GEODE-9985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Murmann updated GEODE-9985:
-
Labels: needsTriage (was: )
> Mass-Test-Run SlowDispatcherDUnitTest >
> registeredInterest_durableClient_kill_primarySever_receives_marker FAILED
> -
>
> Key: GEODE-9985
> URL: https://issues.apache.org/jira/browse/GEODE-9985
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Kristen
>Priority: Major
> Labels: needsTriage
>
> {code:java}
> SlowDispatcherDUnitTest >
> registeredInterest_durableClient_kill_primarySever_receives_marker FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.tier.sockets.SlowDispatcherDUnitTest$$Lambda$299/1561169457.run
> in VM 3 running on Host
> heavy-lifter-f18312bf-ecf3-5384-8b36-e5d91bf8ebb9.c.apachegeode-ci.internal
> with 5 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.test.junit.rules.VMProvider.invoke(VMProvider.java:96)
> at
> org.apache.geode.internal.cache.tier.sockets.SlowDispatcherDUnitTest.registeredInterest_durableClient_kill_primarySever_receives_marker(SlowDispatcherDUnitTest.java:135)
> Caused by:
> org.awaitility.core.ConditionTimeoutException: Assertion condition
> defined as a
> org.apache.geode.internal.cache.tier.sockets.SlowDispatcherDUnitTest
> expected: 49
> but was: 40 within 5 minutes.
> at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:164)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
> at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:939)
> at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:723)
> at
> org.apache.geode.internal.cache.tier.sockets.SlowDispatcherDUnitTest.lambda$registeredInterest_durableClient_kill_primarySever_receives_marker$bb17a952$2(SlowDispatcherDUnitTest.java:137)
> Caused by:
> org.opentest4j.AssertionFailedError:
> expected: 49
> but was: 40
> at
> sun.reflect.GeneratedConstructorAccessor21.newInstance(Unknown Source)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.internal.cache.tier.sockets.SlowDispatcherDUnitTest.lambda$null$2(SlowDispatcherDUnitTest.java:137)
> 8357 tests completed, 1 failed, 414 skipped
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0806/test-artifacts/1642831372/distributedtestfiles-openjdk8-1.15.0-build.0806.tgz{code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-8411) CI Failure: Jetty9CachingClientServerTest. containersShouldShareDataRemovals() fails with comparison failure
[
https://issues.apache.org/jira/browse/GEODE-8411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17481340#comment-17481340
]
Geode Integration commented on GEODE-8411:
--
Seen in [distributed-test-openjdk8
#747|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/747]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0806/test-results/distributedTest/1642858377/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0806/test-artifacts/1642858377/distributedtestfiles-openjdk8-1.15.0-build.0806.tgz].
> CI Failure: Jetty9CachingClientServerTest.
> containersShouldShareDataRemovals() fails with comparison failure
>
>
> Key: GEODE-8411
> URL: https://issues.apache.org/jira/browse/GEODE-8411
> Project: Geode
> Issue Type: Bug
>Reporter: Benjamin P Ross
>Assignee: Benjamin P Ross
>Priority: Major
>
> We saw Jetty9CachingClientServerTest fail with a Comparison failure in a CI
> run.
> {code:java}
> org.apache.geode.session.tests.Jetty9CachingClientServerTest >
> containersShouldShareDataRemovals FAILED
> org.junit.ComparisonFailure: expected:<"[]"> but was:<"[Foo]">
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-9984) Mass-Test-Run WanCopyRegionCommandDUnitTest > testCommandDoesNotCopyEntriesUpdatedAfterCommandStarted FAILED
[ https://issues.apache.org/jira/browse/GEODE-9984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristen updated GEODE-9984: --- Description: WanCopyRegionCommandDUnitTest > testCommandDoesNotCopyEntriesUpdatedAfterCommandStarted(true, true) [0] FAILED org.opentest4j.AssertionFailedError: expected: 5 but was: 50001 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.cache.wan.internal.cli.commands.WanCopyRegionCommandDUnitTest.testCommandDoesNotCopyEntriesUpdatedAfterCommandStarted(WanCopyRegionCommandDUnitTest.java:884) 948 tests completed, 1 failed, 59 skipped Test report artifacts from this job are available at: [*http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0806/test-artifacts/1642850654/distributedtestfiles-openjdk8-1.15.0-build.0806.tgz*] May be an issue similar or related to https://issues.apache.org/jira/browse/GEODE-9859. was: WanCopyRegionCommandDUnitTest > testCommandDoesNotCopyEntriesUpdatedAfterCommandStarted(true, true) [0] FAILED org.opentest4j.AssertionFailedError: expected: 5 but was: 50001 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.cache.wan.internal.cli.commands.WanCopyRegionCommandDUnitTest.testCommandDoesNotCopyEntriesUpdatedAfterCommandStarted(WanCopyRegionCommandDUnitTest.java:884) 948 tests completed, 1 failed, 59 skipped Test report artifacts from this job are available at: [*http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0806/test-artifacts/1642850654/distributedtestfiles-openjdk8-1.15.0-build.0806.tgz*] May be a similar issue to https://issues.apache.org/jira/browse/GEODE-9859. > Mass-Test-Run WanCopyRegionCommandDUnitTest > > testCommandDoesNotCopyEntriesUpdatedAfterCommandStarted FAILED > > > Key: GEODE-9984 > URL: https://issues.apache.org/jira/browse/GEODE-9984 > Project: Geode > Issue Type: Bug >Affects Versions: 1.15.0 >Reporter: Kristen >Priority: Major > Labels: needsTriage > > WanCopyRegionCommandDUnitTest > > testCommandDoesNotCopyEntriesUpdatedAfterCommandStarted(true, true) [0] FAILED > org.opentest4j.AssertionFailedError: > expected: 5 > but was: 50001 > 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.cache.wan.internal.cli.commands.WanCopyRegionCommandDUnitTest.testCommandDoesNotCopyEntriesUpdatedAfterCommandStarted(WanCopyRegionCommandDUnitTest.java:884) > 948 tests completed, 1 failed, 59 skipped > Test report artifacts from this job are available at: > [*http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0806/test-artifacts/1642850654/distributedtestfiles-openjdk8-1.15.0-build.0806.tgz*] > > > > May be an issue similar or related to > https://issues.apache.org/jira/browse/GEODE-9859. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-9984) Mass-Test-Run WanCopyRegionCommandDUnitTest > testCommandDoesNotCopyEntriesUpdatedAfterCommandStarted FAILED
[ https://issues.apache.org/jira/browse/GEODE-9984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristen updated GEODE-9984: --- Description: WanCopyRegionCommandDUnitTest > testCommandDoesNotCopyEntriesUpdatedAfterCommandStarted(true, true) [0] FAILED org.opentest4j.AssertionFailedError: expected: 5 but was: 50001 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.cache.wan.internal.cli.commands.WanCopyRegionCommandDUnitTest.testCommandDoesNotCopyEntriesUpdatedAfterCommandStarted(WanCopyRegionCommandDUnitTest.java:884) 948 tests completed, 1 failed, 59 skipped Test report artifacts from this job are available at: [*http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0806/test-artifacts/1642850654/distributedtestfiles-openjdk8-1.15.0-build.0806.tgz*] May be a similar issue to https://issues.apache.org/jira/browse/GEODE-9859. was: WanCopyRegionCommandDUnitTest > testCommandDoesNotCopyEntriesUpdatedAfterCommandStarted(true, true) [0] FAILED org.opentest4j.AssertionFailedError: expected: 5 but was: 50001 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.cache.wan.internal.cli.commands.WanCopyRegionCommandDUnitTest.testCommandDoesNotCopyEntriesUpdatedAfterCommandStarted(WanCopyRegionCommandDUnitTest.java:884) 948 tests completed, 1 failed, 59 skipped Test report artifacts from this job are available at: [*http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0806/test-artifacts/1642850654/distributedtestfiles-openjdk8-1.15.0-build.0806.tgz*] > Mass-Test-Run WanCopyRegionCommandDUnitTest > > testCommandDoesNotCopyEntriesUpdatedAfterCommandStarted FAILED > > > Key: GEODE-9984 > URL: https://issues.apache.org/jira/browse/GEODE-9984 > Project: Geode > Issue Type: Bug >Affects Versions: 1.15.0 >Reporter: Kristen >Priority: Major > Labels: needsTriage > > WanCopyRegionCommandDUnitTest > > testCommandDoesNotCopyEntriesUpdatedAfterCommandStarted(true, true) [0] FAILED > org.opentest4j.AssertionFailedError: > expected: 5 > but was: 50001 > 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.cache.wan.internal.cli.commands.WanCopyRegionCommandDUnitTest.testCommandDoesNotCopyEntriesUpdatedAfterCommandStarted(WanCopyRegionCommandDUnitTest.java:884) > 948 tests completed, 1 failed, 59 skipped > Test report artifacts from this job are available at: > [*http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0806/test-artifacts/1642850654/distributedtestfiles-openjdk8-1.15.0-build.0806.tgz*] > > > > May be a similar issue to https://issues.apache.org/jira/browse/GEODE-9859. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9984) Mass-Test-Run WanCopyRegionCommandDUnitTest > testCommandDoesNotCopyEntriesUpdatedAfterCommandStarted FAILED
[ https://issues.apache.org/jira/browse/GEODE-9984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17481336#comment-17481336 ] Geode Integration commented on GEODE-9984: -- Seen in [distributed-test-openjdk8 #737|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/737] ... see [test results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0806/test-results/distributedTest/1642850654/] or download [artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0806/test-artifacts/1642850654/distributedtestfiles-openjdk8-1.15.0-build.0806.tgz]. > Mass-Test-Run WanCopyRegionCommandDUnitTest > > testCommandDoesNotCopyEntriesUpdatedAfterCommandStarted FAILED > > > Key: GEODE-9984 > URL: https://issues.apache.org/jira/browse/GEODE-9984 > Project: Geode > Issue Type: Bug >Affects Versions: 1.15.0 >Reporter: Kristen >Priority: Major > Labels: needsTriage > > WanCopyRegionCommandDUnitTest > > testCommandDoesNotCopyEntriesUpdatedAfterCommandStarted(true, true) [0] FAILED > org.opentest4j.AssertionFailedError: > expected: 5 > but was: 50001 > 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.cache.wan.internal.cli.commands.WanCopyRegionCommandDUnitTest.testCommandDoesNotCopyEntriesUpdatedAfterCommandStarted(WanCopyRegionCommandDUnitTest.java:884) > 948 tests completed, 1 failed, 59 skipped > Test report artifacts from this job are available at: > [*http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0806/test-artifacts/1642850654/distributedtestfiles-openjdk8-1.15.0-build.0806.tgz*] > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-9984) Mass-Test-Run WanCopyRegionCommandDUnitTest > testCommandDoesNotCopyEntriesUpdatedAfterCommandStarted FAILED
Kristen created GEODE-9984: -- Summary: Mass-Test-Run WanCopyRegionCommandDUnitTest > testCommandDoesNotCopyEntriesUpdatedAfterCommandStarted FAILED Key: GEODE-9984 URL: https://issues.apache.org/jira/browse/GEODE-9984 Project: Geode Issue Type: Bug Affects Versions: 1.15.0 Reporter: Kristen WanCopyRegionCommandDUnitTest > testCommandDoesNotCopyEntriesUpdatedAfterCommandStarted(true, true) [0] FAILED org.opentest4j.AssertionFailedError: expected: 5 but was: 50001 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.cache.wan.internal.cli.commands.WanCopyRegionCommandDUnitTest.testCommandDoesNotCopyEntriesUpdatedAfterCommandStarted(WanCopyRegionCommandDUnitTest.java:884) 948 tests completed, 1 failed, 59 skipped Test report artifacts from this job are available at: [*http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0806/test-artifacts/1642850654/distributedtestfiles-openjdk8-1.15.0-build.0806.tgz*] -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-9984) Mass-Test-Run WanCopyRegionCommandDUnitTest > testCommandDoesNotCopyEntriesUpdatedAfterCommandStarted FAILED
[ https://issues.apache.org/jira/browse/GEODE-9984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-9984: - Labels: needsTriage (was: ) > Mass-Test-Run WanCopyRegionCommandDUnitTest > > testCommandDoesNotCopyEntriesUpdatedAfterCommandStarted FAILED > > > Key: GEODE-9984 > URL: https://issues.apache.org/jira/browse/GEODE-9984 > Project: Geode > Issue Type: Bug >Affects Versions: 1.15.0 >Reporter: Kristen >Priority: Major > Labels: needsTriage > > WanCopyRegionCommandDUnitTest > > testCommandDoesNotCopyEntriesUpdatedAfterCommandStarted(true, true) [0] FAILED > org.opentest4j.AssertionFailedError: > expected: 5 > but was: 50001 > 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.cache.wan.internal.cli.commands.WanCopyRegionCommandDUnitTest.testCommandDoesNotCopyEntriesUpdatedAfterCommandStarted(WanCopyRegionCommandDUnitTest.java:884) > 948 tests completed, 1 failed, 59 skipped > Test report artifacts from this job are available at: > [*http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0806/test-artifacts/1642850654/distributedtestfiles-openjdk8-1.15.0-build.0806.tgz*] > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9739) CI: WANRollingUpgradeCreateGatewaySenderMixedSiteOneCurrentSiteTwo failed with MemberDisconnectedException
[
https://issues.apache.org/jira/browse/GEODE-9739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hale Bales reassigned GEODE-9739:
-
Assignee: Hale Bales
> CI: WANRollingUpgradeCreateGatewaySenderMixedSiteOneCurrentSiteTwo failed
> with MemberDisconnectedException
> --
>
> Key: GEODE-9739
> URL: https://issues.apache.org/jira/browse/GEODE-9739
> Project: Geode
> Issue Type: Bug
> Components: membership, wan
>Affects Versions: 1.15.0
>Reporter: Kamilla Aslami
>Assignee: Hale Bales
>Priority: Major
> Labels: needsTriage
>
> {noformat}
> WANRollingUpgradeCreateGatewaySenderMixedSiteOneCurrentSiteTwo >
> CreateGatewaySenderMixedSiteOneCurrentSiteTwo[from_v1.12.2] 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 'dunit_suspect-vm6.log' at line 481[fatal
> 2021/10/13 23:34:55.115 UTC receiver,heavy-lifter-f2dde05e-a413-5672-b192-2396306457b3-37210> tid=830]
> Membership service failure: Membership coordinator
> heavy-lifter-f2dde05e-a413-5672-b192-2396306457b3(39325:locator):53919
> has declared that a network partition has occurred
>
> org.apache.geode.distributed.internal.membership.api.MemberDisconnectedException:
> Membership coordinator
> heavy-lifter-f2dde05e-a413-5672-b192-2396306457b3(39325:locator):53919
> has declared that a network partition has occurred
> at
> org.apache.geode.distributed.internal.membership.gms.GMSMembership$ManagerImpl.forceDisconnect(GMSMembership.java:1807)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.forceDisconnect(GMSJoinLeave.java:1122)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.processNetworkPartitionMessage(GMSJoinLeave.java:1466)
> at
> org.apache.geode.distributed.internal.membership.gms.messenger.JGroupsMessenger$JGroupsReceiver.receive(JGroupsMessenger.java:1367)
> at
> org.apache.geode.distributed.internal.membership.gms.messenger.JGroupsMessenger$JGroupsReceiver.receive(JGroupsMessenger.java:1303)
> at org.jgroups.JChannel.invokeCallback(JChannel.java:816)
> at org.jgroups.JChannel.up(JChannel.java:741)
> at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:1030)
> at org.jgroups.protocols.FRAG2.up(FRAG2.java:165)
> at org.jgroups.protocols.FlowControl.up(FlowControl.java:390)
> at org.jgroups.protocols.UNICAST3.deliverMessage(UNICAST3.java:1077)
> at
> org.jgroups.protocols.UNICAST3.handleDataReceived(UNICAST3.java:792)
> at org.jgroups.protocols.UNICAST3.up(UNICAST3.java:433)
> at
> org.apache.geode.distributed.internal.membership.gms.messenger.StatRecorder.up(StatRecorder.java:72)
> at
> org.apache.geode.distributed.internal.membership.gms.messenger.AddressManager.up(AddressManager.java:70)
> at org.jgroups.protocols.TP.passMessageUp(TP.java:1658)
> at org.jgroups.protocols.TP$SingleMessageHandler.run(TP.java:1876)
> at org.jgroups.util.DirectExecutor.execute(DirectExecutor.java:10)
> at org.jgroups.protocols.TP.handleSingleMessage(TP.java:1789)
> at org.jgroups.protocols.TP.receive(TP.java:1714)
> at
> org.apache.geode.distributed.internal.membership.gms.messenger.Transport.receive(Transport.java:160)
> at org.jgroups.protocols.UDP$PacketReceiver.run(UDP.java:701)
> at java.base/java.lang.Thread.run(Thread.java:829)
> ---
> Found suspect string in 'dunit_suspect-vm4.log' at line 549[fatal
> 2021/10/13 23:34:54.989 UTC tid=858] Possible
> loss of quorum due to the loss of 1 cache processes:
> [heavy-lifter-f2dde05e-a413-5672-b192-2396306457b3(41092):53920]
> ---
> Found suspect string in 'dunit_suspect-vm4.log' at line 551[fatal
> 2021/10/13 23:34:56.179 UTC tid=858]
> Membership service failure: Exiting due to possible network partition event
> due to loss of 1 cache processes:
> [heavy-lifter-f2dde05e-a413-5672-b192-2396306457b3(41092):53920]
>
> org.apache.geode.distributed.internal.membership.api.MemberDisconnectedException:
> Exiting due to possible network partition event due to loss of 1 cache
> processes:
> [heavy-lifter-f2dde05e-a413-5672-b192-2396306457b3(41092):53920]
> at
>
[jira] [Commented] (GEODE-9923) User Guide: add Log Message troubleshooting section
[ https://issues.apache.org/jira/browse/GEODE-9923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17481325#comment-17481325 ] ASF subversion and git services commented on GEODE-9923: Commit 95210d19b5088dd0e62d4f815855d1776cd6eec7 in geode's branch refs/heads/develop from Dave Barnes [ https://gitbox.apache.org/repos/asf?p=geode.git;h=95210d1 ] GEODE-9923: Add log message troubleshooting info from support team community (#7296) > User Guide: add Log Message troubleshooting section > --- > > Key: GEODE-9923 > URL: https://issues.apache.org/jira/browse/GEODE-9923 > Project: Geode > Issue Type: Improvement > Components: docs >Affects Versions: 1.14.2 >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Labels: pull-request-available > > GemFire support team (who are also Geode community members) have compiled a > troubleshooting guide that maps log messages to suggested solutions. > They have contributed this to Geode in the form of a Google doc. > Reformat the Google doc and add it to the Geode user guide. There's an > existing section under Managing Apache Geode called Troubleshooting and > System Recovery that would be a good location for this material. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[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=17481324#comment-17481324
]
Geode Integration commented on GEODE-8616:
--
Seen in [distributed-test-openjdk8
#784|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/784]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0806/test-results/distributedTest/1642891540/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0806/test-artifacts/1642891540/distributedtestfiles-openjdk8-1.15.0-build.0806.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, 1.13.7, 1.14.3, 1.15.0
>Reporter: Donal Evans
>Priority: Major
> Labels: GeodeOperationAPI, flaky-test, pull-request-available
> Attachments: hansonm-findfailures-11-10-2021-23-52-38-logs.tgz,
> hansonm-findfailures-11-10-2021-23-52-45-logs.tgz
>
>
> {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.20.1#820001)
[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=17481322#comment-17481322
]
Geode Integration commented on GEODE-8616:
--
Seen in [distributed-test-openjdk8
#799|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/799]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0806/test-results/distributedTest/1642906128/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0806/test-artifacts/1642906128/distributedtestfiles-openjdk8-1.15.0-build.0806.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, 1.13.7, 1.14.3, 1.15.0
>Reporter: Donal Evans
>Priority: Major
> Labels: GeodeOperationAPI, flaky-test, pull-request-available
> Attachments: hansonm-findfailures-11-10-2021-23-52-38-logs.tgz,
> hansonm-findfailures-11-10-2021-23-52-45-logs.tgz
>
>
> {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.20.1#820001)
[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=17481320#comment-17481320
]
Geode Integration commented on GEODE-8616:
--
Seen in [distributed-test-openjdk8
#742|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/742]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0806/test-results/distributedTest/1642857086/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0806/test-artifacts/1642857086/distributedtestfiles-openjdk8-1.15.0-build.0806.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, 1.13.7, 1.14.3, 1.15.0
>Reporter: Donal Evans
>Priority: Major
> Labels: GeodeOperationAPI, flaky-test, pull-request-available
> Attachments: hansonm-findfailures-11-10-2021-23-52-38-logs.tgz,
> hansonm-findfailures-11-10-2021-23-52-45-logs.tgz
>
>
> {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.20.1#820001)
[jira] [Commented] (GEODE-8392) CI Failure: Jetty9CachingClientServerTest > sessionPicksUpSessionTimeoutConfiguredInWebXml
[ https://issues.apache.org/jira/browse/GEODE-8392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17481319#comment-17481319 ] Geode Integration commented on GEODE-8392: -- Seen in [distributed-test-openjdk8 #750|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/750] ... see [test results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0806/test-results/distributedTest/1642860083/] or download [artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0806/test-artifacts/1642860083/distributedtestfiles-openjdk8-1.15.0-build.0806.tgz]. > CI Failure: Jetty9CachingClientServerTest > > sessionPicksUpSessionTimeoutConfiguredInWebXml > -- > > Key: GEODE-8392 > URL: https://issues.apache.org/jira/browse/GEODE-8392 > Project: Geode > Issue Type: Bug > Components: http session >Reporter: Owen Nichols >Priority: Major > > Failure: [DistributedTestOpenJDK11 > #381|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/381#A] > org.apache.geode.session.tests.Jetty9CachingClientServerTest > > sessionPicksUpSessionTimeoutConfiguredInWebXml FAILED > org.awaitility.core.ConditionTimeoutException: Condition with lambda > expression in org.apache.geode.session.tests.CargoTestBase was not fulfilled > within 5 minutes. > =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > [*http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0247/test-results/distributedTest/1596061367/*] > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Test report artifacts from this job are available at: > [*http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0247/test-artifacts/1596061367/distributedtestfiles-OpenJDK11-1.14.0-build.0247.tgz*] -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9843) CI failure: DistributedSystemMXBeanWithAlertsDistributedTest.managerMissesAnyAlertsBeforeItStarts failed with TooFewActualInvocations
[
https://issues.apache.org/jira/browse/GEODE-9843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17481316#comment-17481316
]
Geode Integration commented on GEODE-9843:
--
Seen in [distributed-test-openjdk8
#771|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/771]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0806/test-results/distributedTest/1642883232/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0806/test-artifacts/1642883232/distributedtestfiles-openjdk8-1.15.0-build.0806.tgz].
> CI failure:
> DistributedSystemMXBeanWithAlertsDistributedTest.managerMissesAnyAlertsBeforeItStarts
> failed with TooFewActualInvocations
> -
>
> Key: GEODE-9843
> URL: https://issues.apache.org/jira/browse/GEODE-9843
> Project: Geode
> Issue Type: Bug
> Components: core, management
>Affects Versions: 1.15.0
>Reporter: Kamilla Aslami
>Priority: Major
>
> {noformat}
> DistributedSystemMXBeanWithAlertsDistributedTest >
> managerMissesAnyAlertsBeforeItStarts FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.management.DistributedSystemMXBeanWithAlertsDistributedTest$$Lambda$301/390135366.run
> in VM 0 running on Host
> heavy-lifter-993df0f4-3655-560f-82a7-0c09d04efdd9.c.apachegeode-ci.internal
> 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.management.DistributedSystemMXBeanWithAlertsDistributedTest.managerMissesAnyAlertsBeforeItStarts(DistributedSystemMXBeanWithAlertsDistributedTest.java:379)
> Caused by:
> org.mockito.exceptions.verification.TooFewActualInvocations:
> notificationListener.handleNotification(
> ,
> isNull()
> );
> Wanted 3 times:
> -> at
> org.apache.geode.management.DistributedSystemMXBeanWithAlertsDistributedTest.captureAllNotifications(DistributedSystemMXBeanWithAlertsDistributedTest.java:439)
> But was 2 times:
> -> at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor$ListenerWrapper.handleNotification(DefaultMBeanServerInterceptor.java:1754)
> -> at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor$ListenerWrapper.handleNotification(DefaultMBeanServerInterceptor.java:1754)
> at
> org.apache.geode.management.DistributedSystemMXBeanWithAlertsDistributedTest.captureAllNotifications(DistributedSystemMXBeanWithAlertsDistributedTest.java:439)
> at
> org.apache.geode.management.DistributedSystemMXBeanWithAlertsDistributedTest.captureAllAlerts(DistributedSystemMXBeanWithAlertsDistributedTest.java:451)
> at
> org.apache.geode.management.DistributedSystemMXBeanWithAlertsDistributedTest.lambda$managerMissesAnyAlertsBeforeItStarts$bb17a952$6(DistributedSystemMXBeanWithAlertsDistributedTest.java:380)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-7183) CI Failure: ClientServerFunctionExecutionDUnitTest > testServerExecution_SocketTimeOut_WithoutRegister[ExecuteFunctionById] failed with AssertionError
[
https://issues.apache.org/jira/browse/GEODE-7183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17481315#comment-17481315
]
Geode Integration commented on GEODE-7183:
--
Seen in [distributed-test-openjdk8
#781|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/781]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0806/test-results/distributedTest/1642892903/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0806/test-artifacts/1642892903/distributedtestfiles-openjdk8-1.15.0-build.0806.tgz].
> CI Failure: ClientServerFunctionExecutionDUnitTest >
> testServerExecution_SocketTimeOut_WithoutRegister[ExecuteFunctionById] failed
> with AssertionError
> --
>
> Key: GEODE-7183
> URL: https://issues.apache.org/jira/browse/GEODE-7183
> Project: Geode
> Issue Type: Bug
> Components: functions
>Reporter: Barrett Oglesby
>Priority: Major
>
> {noformat}
> org.apache.geode.internal.cache.execute.ClientServerFunctionExecutionDUnitTest
> > testServerExecution_SocketTimeOut_WithoutRegister[ExecuteFunctionById]
> FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.execute.ClientServerFunctionExecutionDUnitTest$$Lambda$68/1900027546.run
> in VM 3 running on Host 6c6dc0c2627c 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.internal.cache.execute.ClientServerFunctionExecutionDUnitTest.testServerExecution_SocketTimeOut_WithoutRegister(ClientServerFunctionExecutionDUnitTest.java:339)
> Caused by:
> java.lang.AssertionError: Test failed after the execute operation
> at org.junit.Assert.fail(Assert.java:88)
> at
> org.apache.geode.internal.cache.execute.ClientServerFunctionExecutionDUnitTest.allServerExecution(ClientServerFunctionExecutionDUnitTest.java:891)
> at
> org.apache.geode.internal.cache.execute.ClientServerFunctionExecutionDUnitTest.lambda$testServerExecution_SocketTimeOut_WithoutRegister$bb17a952$2(ClientServerFunctionExecutionDUnitTest.java:339)
> {noformat}
> The test logs this exception right before the failure:
> {noformat}
> [vm3] [info 2019/09/09 18:00:10.793 GMT RMI TCP
> Connection(26)-172.17.0.19 tid=0xb1] Exception :
> [vm3] org.apache.geode.cache.client.ServerConnectivityException: Pool
> unexpected SocketException connection=Pooled Connection to
> 6c6dc0c2627c:25980: Connection[DESTROYED]). Server unreachable: could not
> connect after 1 attempts
> [vm3] at
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:659)
> [vm3] at
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:501)
> [vm3] at
> org.apache.geode.cache.client.internal.OpExecutorImpl.executeOnServer(OpExecutorImpl.java:331)
> [vm3] at
> org.apache.geode.cache.client.internal.OpExecutorImpl.executeOn(OpExecutorImpl.java:300)
> [vm3] at
> org.apache.geode.cache.client.internal.PoolImpl.executeOn(PoolImpl.java:814)
> [vm3] at
> org.apache.geode.cache.client.internal.SingleHopOperationCallable.call(SingleHopOperationCallable.java:52)
> [vm3] at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> [vm3] at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> [vm3] at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> [vm3] at java.lang.Thread.run(Thread.java:748)
> [vm3] Caused by: java.net.SocketException: Socket is closed
> [vm3] at java.net.Socket.setSoTimeout(Socket.java:1137)
> [vm3] at
> org.apache.geode.cache.client.internal.AbstractOpWithTimeout.attempt(AbstractOpWithTimeout.java:48)
> [vm3] at
> org.apache.geode.cache.client.internal.ConnectionImpl.execute(ConnectionImpl.java:263)
> [vm3] at
> org.apache.geode.cache.client.internal.pooling.PooledConnection.execute(PooledConnection.java:353)
> [vm3] at
> org.apache.geode.cache.client.internal.OpExecutorImpl.executeWithPossibleReAuthentication(OpExecutorImpl.java:750)
> [vm3] at
> org.apache.geode.cache.client.internal.OpExecutorImpl.executeOnServer(OpExecutorImpl.java:329)
> [vm3] ... 7 more
> {noformat}
> https://concourse.gemfire-ci.info/teams/main/pipelines/gemfire-develop-main/jobs/DistributedTestOpenJDK8/builds/952
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test
[jira] [Commented] (GEODE-7710) CI Failure: JMXMBeanReconnectDUnitTest aka JmxServerReconnectDistributedTest fails intermittently because one locator is missing the LockServiceMXBean
[
https://issues.apache.org/jira/browse/GEODE-7710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17481310#comment-17481310
]
Geode Integration commented on GEODE-7710:
--
Seen in [distributed-test-openjdk8
#756|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/756]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0806/test-results/distributedTest/1642865650/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0806/test-artifacts/1642865650/distributedtestfiles-openjdk8-1.15.0-build.0806.tgz].
> CI Failure: JMXMBeanReconnectDUnitTest aka JmxServerReconnectDistributedTest
> fails intermittently because one locator is missing the LockServiceMXBean
> --
>
> Key: GEODE-7710
> URL: https://issues.apache.org/jira/browse/GEODE-7710
> Project: Geode
> Issue Type: Bug
> Components: tests
>Affects Versions: 1.13.0, 1.14.0, 1.15.0
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
> Labels: GeodeOperationAPI, flaky, pull-request-available
> Time Spent: 5h
> Remaining Estimate: 0h
>
> This test fails due to GEODE-7739. Enter new failures against that ticket.
> Multiple tests in JMXMBeanReconnectDUnitTest may fail an await due to one of
> the locators missing the LockServiceMXBean for the cluster config service.
> {noformat}
> but could not find:
>
> <[GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator1]>
> {noformat}
> These test failures are caused by *GEODE-7739*.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-7710) CI Failure: JMXMBeanReconnectDUnitTest aka JmxServerReconnectDistributedTest fails intermittently because one locator is missing the LockServiceMXBean
[
https://issues.apache.org/jira/browse/GEODE-7710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17481311#comment-17481311
]
Geode Integration commented on GEODE-7710:
--
Seen in [distributed-test-openjdk8
#744|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/744]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0806/test-results/distributedTest/1642856973/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0806/test-artifacts/1642856973/distributedtestfiles-openjdk8-1.15.0-build.0806.tgz].
> CI Failure: JMXMBeanReconnectDUnitTest aka JmxServerReconnectDistributedTest
> fails intermittently because one locator is missing the LockServiceMXBean
> --
>
> Key: GEODE-7710
> URL: https://issues.apache.org/jira/browse/GEODE-7710
> Project: Geode
> Issue Type: Bug
> Components: tests
>Affects Versions: 1.13.0, 1.14.0, 1.15.0
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
> Labels: GeodeOperationAPI, flaky, pull-request-available
> Time Spent: 5h
> Remaining Estimate: 0h
>
> This test fails due to GEODE-7739. Enter new failures against that ticket.
> Multiple tests in JMXMBeanReconnectDUnitTest may fail an await due to one of
> the locators missing the LockServiceMXBean for the cluster config service.
> {noformat}
> but could not find:
>
> <[GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator1]>
> {noformat}
> These test failures are caused by *GEODE-7739*.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-7710) CI Failure: JMXMBeanReconnectDUnitTest aka JmxServerReconnectDistributedTest fails intermittently because one locator is missing the LockServiceMXBean
[
https://issues.apache.org/jira/browse/GEODE-7710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17481309#comment-17481309
]
Geode Integration commented on GEODE-7710:
--
Seen in [distributed-test-openjdk8
#791|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/791]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0806/test-results/distributedTest/1642902404/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0806/test-artifacts/1642902404/distributedtestfiles-openjdk8-1.15.0-build.0806.tgz].
> CI Failure: JMXMBeanReconnectDUnitTest aka JmxServerReconnectDistributedTest
> fails intermittently because one locator is missing the LockServiceMXBean
> --
>
> Key: GEODE-7710
> URL: https://issues.apache.org/jira/browse/GEODE-7710
> Project: Geode
> Issue Type: Bug
> Components: tests
>Affects Versions: 1.13.0, 1.14.0, 1.15.0
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
> Labels: GeodeOperationAPI, flaky, pull-request-available
> Time Spent: 5h
> Remaining Estimate: 0h
>
> This test fails due to GEODE-7739. Enter new failures against that ticket.
> Multiple tests in JMXMBeanReconnectDUnitTest may fail an await due to one of
> the locators missing the LockServiceMXBean for the cluster config service.
> {noformat}
> but could not find:
>
> <[GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator1]>
> {noformat}
> These test failures are caused by *GEODE-7739*.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-7822) MemoryThresholdsOffHeapDUnitTest has failures
[
https://issues.apache.org/jira/browse/GEODE-7822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17481308#comment-17481308
]
Geode Integration commented on GEODE-7822:
--
Seen in [distributed-test-openjdk8
#119|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/distributed-test-openjdk8/builds/119]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0805/test-results/distributedTest/1642817769/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0805/test-artifacts/1642817769/distributedtestfiles-openjdk8-1.15.0-build.0805.tgz].
> MemoryThresholdsOffHeapDUnitTest has failures
> -
>
> Key: GEODE-7822
> URL: https://issues.apache.org/jira/browse/GEODE-7822
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Mark Hanson
>Priority: Major
> Labels: flaky
>
> These two failures were seen in mass test runs...
> {noformat}
> testPRLoadRejection
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-mass-test-run-main/jobs/DistributedTestOpenJDK8/builds/674
> {noformat}
> {noformat}
> org.apache.geode.cache.management.MemoryThresholdsOffHeapDUnitTest >
> testPRLoadRejection FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache.management.MemoryThresholdsOffHeapDUnitTest$31.call in
> VM 2 running on Host a57bd8581b8d with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:610)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:462)
> at
> org.apache.geode.cache.management.MemoryThresholdsOffHeapDUnitTest.testPRLoadRejection(MemoryThresholdsOffHeapDUnitTest.java:1045)
> Caused by:
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertFalse(Assert.java:64)
> at org.junit.Assert.assertFalse(Assert.java:74)
> at
> org.apache.geode.cache.management.MemoryThresholdsOffHeapDUnitTest$31.call(MemoryThresholdsOffHeapDUnitTest.java:1077){noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> [http://files.apachegeode-ci.info/builds/apache-mass-test-run-main/1.12.0-SNAPSHOT.0005/test-results/distributedTest/1582515952/]
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> [http://files.apachegeode-ci.info/builds/apache-mass-test-run-main/1.12.0-SNAPSHOT.0005/test-artifacts/1582515952/distributedtestfiles-OpenJDK8-1.12.0-SNAPSHOT.0005.tgz]
> {noformat}
> testDRLoadRejection
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-mass-test-run-main/jobs/DistributedTestOpenJDK8/builds/742
> {noformat}
> {noformat}
> org.apache.geode.cache.management.MemoryThresholdsOffHeapDUnitTest >
> testDRLoadRejection FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache.management.MemoryThresholdsOffHeapDUnitTest$18.call in
> VM 2 running on Host b2c673017cde with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:610)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:462)
> at
> org.apache.geode.cache.management.MemoryThresholdsOffHeapDUnitTest.testDRLoadRejection(MemoryThresholdsOffHeapDUnitTest.java:667)
> Caused by:
>java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertFalse(Assert.java:64)
> at org.junit.Assert.assertFalse(Assert.java:74)
> at
> org.apache.geode.cache.management.MemoryThresholdsOffHeapDUnitTest$18.call(MemoryThresholdsOffHeapDUnitTest.java:673)
> {noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-mass-test-run-main/1.12.0-SNAPSHOT.0005/test-results/distributedTest/1582626992/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-mass-test-run-main/1.12.0-SNAPSHOT.0005/test-artifacts/1582626992/distributedtestfiles-OpenJDK8-1.12.0-SNAPSHOT.0005.tgz
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-9973) Documentation: socket-lease-time is not used to return sockets to a pool but to close them
[ https://issues.apache.org/jira/browse/GEODE-9973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17481305#comment-17481305 ] Dave Barnes commented on GEODE-9973: I approved the PR to modify the docs on the basis of correct format and grammar. I am not qualified to verify that the documented behavior is, in fact, accurate. Reassigning to [~donalevans] to follow-through on the technical verification. > Documentation: socket-lease-time is not used to return sockets to a pool but > to close them > -- > > Key: GEODE-9973 > URL: https://issues.apache.org/jira/browse/GEODE-9973 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Alberto Gomez >Assignee: Donal Evans >Priority: Major > Labels: pull-request-available > > The "Making sure you have enough sockets" Geode documentation section says > the following about socket-lease-time (check underlined sentence): > > Peer-to-peer. For peer-to-peer threads that do not share sockets, you can use > the socket-lease-time to make sure that no socket sits idle for too long. > +When a socket that belongs to an individual thread remains unused for this > time period, the system automatically returns it to the pool.+ The next time > the thread needs a socket, it creates a new socket. > > Actually, the system automatically closes the connection in the situation > described instead of returning it to any pool. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9973) Documentation: socket-lease-time is not used to return sockets to a pool but to close them
[ https://issues.apache.org/jira/browse/GEODE-9973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes reassigned GEODE-9973: -- Assignee: Donal Evans (was: Dave Barnes) > Documentation: socket-lease-time is not used to return sockets to a pool but > to close them > -- > > Key: GEODE-9973 > URL: https://issues.apache.org/jira/browse/GEODE-9973 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Alberto Gomez >Assignee: Donal Evans >Priority: Major > Labels: pull-request-available > > The "Making sure you have enough sockets" Geode documentation section says > the following about socket-lease-time (check underlined sentence): > > Peer-to-peer. For peer-to-peer threads that do not share sockets, you can use > the socket-lease-time to make sure that no socket sits idle for too long. > +When a socket that belongs to an individual thread remains unused for this > time period, the system automatically returns it to the pool.+ The next time > the thread needs a socket, it creates a new socket. > > Actually, the system automatically closes the connection in the situation > described instead of returning it to any pool. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-9809) Memory leak in PersistentBucketRecoverer
[ https://issues.apache.org/jira/browse/GEODE-9809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mario Ivanac updated GEODE-9809: Component/s: persistence (was: memcached) > Memory leak in PersistentBucketRecoverer > > > Key: GEODE-9809 > URL: https://issues.apache.org/jira/browse/GEODE-9809 > Project: Geode > Issue Type: Bug > Components: persistence >Affects Versions: 1.14.0 >Reporter: Mario Ivanac >Assignee: Mario Ivanac >Priority: Major > Labels: pull-request-available > > When performing consecutive create/destroy colocated persistent partitioned > regions, memory leak is observed. > In our test, in cluster with 50 servers, we have leader persisted partitioned > region with more than 1000 buckets, and colocated 2 persisted regions. If we > consecutively create and destroy child regions, memory leak is observed. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9809) Memory leak in PersistentBucketRecoverer
[ https://issues.apache.org/jira/browse/GEODE-9809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17481259#comment-17481259 ] Darrel Schneider commented on GEODE-9809: - why is the component for this ticket "memcached"? I think "persistence" makes more sense. > Memory leak in PersistentBucketRecoverer > > > Key: GEODE-9809 > URL: https://issues.apache.org/jira/browse/GEODE-9809 > Project: Geode > Issue Type: Bug > Components: memcached >Affects Versions: 1.14.0 >Reporter: Mario Ivanac >Assignee: Mario Ivanac >Priority: Major > Labels: pull-request-available > > When performing consecutive create/destroy colocated persistent partitioned > regions, memory leak is observed. > In our test, in cluster with 50 servers, we have leader persisted partitioned > region with more than 1000 buckets, and colocated 2 persisted regions. If we > consecutively create and destroy child regions, memory leak is observed. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-9830) SINTERSTORE Command Supported
[ https://issues.apache.org/jira/browse/GEODE-9830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristen updated GEODE-9830: --- Fix Version/s: 1.15.0 > SINTERSTORE Command Supported > - > > Key: GEODE-9830 > URL: https://issues.apache.org/jira/browse/GEODE-9830 > Project: Geode > Issue Type: Improvement > Components: redis >Reporter: Wayne >Assignee: Kristen >Priority: Major > Fix For: 1.15.0 > > > The SINTERSTORE command has been implemented but lacks sufficient testing to > ensure that the implementation is robust and does not regress in the future. > > Write unit/integration tests that run against both Geode Redis and native > Redis, and dunit tests which test multiple concurrent clients accessing > different servers. > > +Acceptance Criteria+ > > Passing Unit/integration tests for both Geode and native Redis. The > RedisCommandType class and > README/redis_api_for_[geode.html.md.erb|http://geode.html.md.erb/] updated to > make command "supported". Stories in the backlog to fix the identified issues > (with JIRA tickets) and problem tests that are ignored should be fixed and > enabled. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-9833) SPOP Command Supported
[ https://issues.apache.org/jira/browse/GEODE-9833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristen updated GEODE-9833: --- Fix Version/s: 1.15.0 > SPOP Command Supported > -- > > Key: GEODE-9833 > URL: https://issues.apache.org/jira/browse/GEODE-9833 > Project: Geode > Issue Type: Improvement > Components: redis >Reporter: Wayne >Assignee: Kristen >Priority: Major > Fix For: 1.15.0 > > > The SPOP command has been implemented but lacks sufficient testing to ensure > that the implementation is robust and does not regress in the future. > > Write unit/integration tests that run against both Geode Redis and native > Redis, and dunit tests which test multiple concurrent clients accessing > different servers. > > +Acceptance Criteria+ > > Passing Unit/integration tests for both Geode and native Redis. The > RedisCommandType class and > README/redis_api_for_[geode.html.md.erb|http://geode.html.md.erb/] updated to > make command "supported". Stories in the backlog to fix the identified issues > (with JIRA tickets) and problem tests that are ignored should be fixed and > enabled. > > The current implementation of RedisSet spop and srandmember always copy the > entire MemberSet. So if you have a redis set with a million items, and than > ask for one random one, instead of it reading just one of the items out of > the set it first copies the entire set. > The call that makes the copy is "members.toArray". It should be pretty easy > to add spop and srandmember support to the MemberSet super class. Since > MemberSet uses a flat array to store its items it should work well with > supporting indexing of its array to get a random element. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-9983) Implement RPOPLPUSH Command
Wayne created GEODE-9983: Summary: Implement RPOPLPUSH Command Key: GEODE-9983 URL: https://issues.apache.org/jira/browse/GEODE-9983 Project: Geode Issue Type: New Feature Components: redis Reporter: Wayne Implement the [RPOPLPUSH|https://redis.io/commands/RPOPLPUSH] command. +Acceptance Criteria+ The command has been implemented along with appropriate unit and system tests. The command has been tested using the redis-cli tool and verified against native redis. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-9982) Backwards compatibility failure between older C++ client and newer server.
[
https://issues.apache.org/jira/browse/GEODE-9982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Murmann updated GEODE-9982:
-
Labels: blocks-1.15.0 (was: )
> Backwards compatibility failure between older C++ client and newer server.
> --
>
> Key: GEODE-9982
> URL: https://issues.apache.org/jira/browse/GEODE-9982
> Project: Geode
> Issue Type: Bug
> Components: native client
>Affects Versions: 1.14.0, 1.15.0
>Reporter: Jacob Barrett
>Priority: Blocker
> Labels: blocks-1.15.0
>
> Geode Native C++ client v1.14.0 fails execution of
> testThinClientTransactionsWithoutSticky against current develop branch
> server. C++ client v1.14.0 does not fail when talking to a v1.14.0 server.
> Current develop branch C++ client does not fail when talking to a develop
> branch server. It appears there may be a protocol incompatibly issue between
> these two versions. More investigations to narrow down the version matrix is
> necessary.
> The following error is logged when the test fails:
> {{Error during send for endpoint 192.168.68.56:18539 due to
> apache::geode::client::IllegalStateException: Unregistered type in
> deserialization}}
> ||Server Versions|1.14.0|1.15.0|
> ||Client Versions||
> |1.14.0|P|F|
> |1.15.0|-|P|
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
