[jira] [Resolved] (GEODE-9776) geode-for-redis README.md can be simplified
[
https://issues.apache.org/jira/browse/GEODE-9776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wayne resolved GEODE-9776.
--
Resolution: Won't Fix
> geode-for-redis README.md can be simplified
> ---
>
> Key: GEODE-9776
> URL: https://issues.apache.org/jira/browse/GEODE-9776
> Project: Geode
> Issue Type: Improvement
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Darrel Schneider
>Priority: Major
>
> The geode-for-redis README.md is more complicated than it needs to be.
> When starting a server for redis in gfsh I recommend just the following:
>
> {noformat}
> start server --geode-for-redis-port= --disable-default-server=true
> {noformat}
> No need for --name. No need for --geode-for-redis-bind-address. No need for
> --locators.
> I suggest the "--disable-default-server=true" so that it will not also try to
> listen for geode clients on 40404 which can cause a failure if that port is
> already in use. This also prepares the way for the second server they start
> which will not need "--server-port=0". We don't need to tell them "If any of
> the options..." right after the start server. This is not a reference manual.
> Just tell them how to start the server.
> Also the README.md should mention that gfsh supports tab completion which can
> help with some of these long option names.
> The section that tells them to run redis-cli only needs to mention "-c -p
> ". No need for the "-h" since the server is listening on all local
> addresses. It should tell them to run redis-cli on the same machine as gfsh.
> Also it should mention (for rookies) that redis-cli is part of the native
> redis distribution which they may need to install. It does not come with
> geode. Also the README.md does not need to mention ""
> in the "Replace" sentence.
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Assigned] (GEODE-10138) Add Versioning Support for LPUSH
[ https://issues.apache.org/jira/browse/GEODE-10138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wayne reassigned GEODE-10138: - Assignee: Bala Tripura Sundari Kaza Venkata > Add Versioning Support for LPUSH > > > Key: GEODE-10138 > URL: https://issues.apache.org/jira/browse/GEODE-10138 > Project: Geode > Issue Type: Improvement > Components: redis >Reporter: Wayne >Assignee: Bala Tripura Sundari Kaza Venkata >Priority: Major > > Add versioning support for the LPUSH command. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-10138) Add Versioning Support for LPUSH
Wayne created GEODE-10138: - Summary: Add Versioning Support for LPUSH Key: GEODE-10138 URL: https://issues.apache.org/jira/browse/GEODE-10138 Project: Geode Issue Type: Improvement Components: redis Reporter: Wayne Add versioning support for the LPUSH command. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-10135) Redis Benchmarks
Wayne created GEODE-10135: - Summary: Redis Benchmarks Key: GEODE-10135 URL: https://issues.apache.org/jira/browse/GEODE-10135 Project: Geode Issue Type: Improvement Components: redis Reporter: Wayne Remove Redis benchmarks from the Geode benchmark job. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-10126) Refactor Configuration To Use System Properties
Wayne created GEODE-10126: - Summary: Refactor Configuration To Use System Properties Key: GEODE-10126 URL: https://issues.apache.org/jira/browse/GEODE-10126 Project: Geode Issue Type: Improvement Components: redis Reporter: Wayne The properties currently being used by the Redis module are defined in Geode core. These properties need to be removed from Geode core and refactored to system properties. Validators must also be added for the system properties to ensure that users provide correct values. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-10125) Refactor Redis to Use Public DataSerializable Framework
Wayne created GEODE-10125: - Summary: Refactor Redis to Use Public DataSerializable Framework Key: GEODE-10125 URL: https://issues.apache.org/jira/browse/GEODE-10125 Project: Geode Issue Type: Improvement Components: redis Reporter: Wayne Refactor Redis to use the public DataSerializable framework instead of the DataSerializableFixedId serialization framework. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-10124) Refactor Geode-DUnit as a Class Library
Wayne created GEODE-10124: - Summary: Refactor Geode-DUnit as a Class Library Key: GEODE-10124 URL: https://issues.apache.org/jira/browse/GEODE-10124 Project: Geode Issue Type: Improvement Components: redis Reporter: Wayne Refactor Dunit so that it can be used as a standalone class library. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (GEODE-9967) The Geode wiki page about the "Redis Adaptor" should be updated
[ https://issues.apache.org/jira/browse/GEODE-9967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wayne resolved GEODE-9967. -- Resolution: Won't Fix > The Geode wiki page about the "Redis Adaptor" should be updated > --- > > Key: GEODE-9967 > URL: https://issues.apache.org/jira/browse/GEODE-9967 > Project: Geode > Issue Type: Improvement > Components: redis >Affects Versions: 1.15.0 >Reporter: Eric Zoerner >Assignee: Ray Ingles >Priority: Major > > This wiki page is out of date for the 1.15 release and should be updated: > https://cwiki.apache.org/confluence/display/GEODE/Geode+Redis+Adapter -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-10108) Duplicate Ops During GII/Delta Updates
[ https://issues.apache.org/jira/browse/GEODE-10108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wayne reassigned GEODE-10108: - Assignee: Jens Deppe > Duplicate Ops During GII/Delta Updates > --- > > Key: GEODE-10108 > URL: https://issues.apache.org/jira/browse/GEODE-10108 > Project: Geode > Issue Type: Bug > Components: redis >Reporter: Wayne >Assignee: Jens Deppe >Priority: Major > Labels: blocks-1.15.0 > > When Redis commands are ongoing and a server that was previously not hosting > a bucket becomes the host of the primary bucket for a key, there exists a > time window where that server is performing GII but also receiving delta > updates from the previous primary bucket. This can lead to the delta being > applied to a data structure that is already in the “correct” state, resulting > in the command being applied twice. This can result in duplicated appends, > increments/decrements, and in the case of LTRIP and RPOP especially, > IndexOutOfBoundsException on the member applying the delta, as the index to > which the delta refers has already been removed. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10108) Duplicate Ops During GII/Delta Updates
[ https://issues.apache.org/jira/browse/GEODE-10108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wayne updated GEODE-10108: -- Labels: blocks-1.15.0 (was: ) > Duplicate Ops During GII/Delta Updates > --- > > Key: GEODE-10108 > URL: https://issues.apache.org/jira/browse/GEODE-10108 > Project: Geode > Issue Type: Bug > Components: redis >Reporter: Wayne >Priority: Major > Labels: blocks-1.15.0 > > When Redis commands are ongoing and a server that was previously not hosting > a bucket becomes the host of the primary bucket for a key, there exists a > time window where that server is performing GII but also receiving delta > updates from the previous primary bucket. This can lead to the delta being > applied to a data structure that is already in the “correct” state, resulting > in the command being applied twice. This can result in duplicated appends, > increments/decrements, and in the case of LTRIP and RPOP especially, > IndexOutOfBoundsException on the member applying the delta, as the index to > which the delta refers has already been removed. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10108) Duplicate Ops During GII/Delta Updates
[ https://issues.apache.org/jira/browse/GEODE-10108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wayne updated GEODE-10108: -- Labels: (was: needsTriage) > Duplicate Ops During GII/Delta Updates > --- > > Key: GEODE-10108 > URL: https://issues.apache.org/jira/browse/GEODE-10108 > Project: Geode > Issue Type: Bug > Components: redis >Reporter: Wayne >Priority: Major > > When Redis commands are ongoing and a server that was previously not hosting > a bucket becomes the host of the primary bucket for a key, there exists a > time window where that server is performing GII but also receiving delta > updates from the previous primary bucket. This can lead to the delta being > applied to a data structure that is already in the “correct” state, resulting > in the command being applied twice. This can result in duplicated appends, > increments/decrements, and in the case of LTRIP and RPOP especially, > IndexOutOfBoundsException on the member applying the delta, as the index to > which the delta refers has already been removed. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-10108) Duplicate Ops During GII/Delta Updates
Wayne created GEODE-10108: - Summary: Duplicate Ops During GII/Delta Updates Key: GEODE-10108 URL: https://issues.apache.org/jira/browse/GEODE-10108 Project: Geode Issue Type: Bug Components: redis Reporter: Wayne When Redis commands are ongoing and a server that was previously not hosting a bucket becomes the host of the primary bucket for a key, there exists a time window where that server is performing GII but also receiving delta updates from the previous primary bucket. This can lead to the delta being applied to a data structure that is already in the “correct” state, resulting in the command being applied twice. This can result in duplicated appends, increments/decrements, and in the case of LTRIP and RPOP especially, IndexOutOfBoundsException on the member applying the delta, as the index to which the delta refers has already been removed. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (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 ] Wayne updated GEODE-6751: - Component/s: tests > 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, tests >Affects Versions: 1.15.0 >Reporter: Scott Jewell >Assignee: Nabarun Nag >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0, 1.16.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] [Updated] (GEODE-8719) CI Failure: org.apache.geode.redis.internal.executor.CrashAndNoRepeatDUnitTest > givenServerCrashesDuringAPPEND_thenDataIsNotLost
[
https://issues.apache.org/jira/browse/GEODE-8719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wayne updated GEODE-8719:
-
Labels: flaky-test unreleased (was: flaky-test)
> CI Failure:
> org.apache.geode.redis.internal.executor.CrashAndNoRepeatDUnitTest >
> givenServerCrashesDuringAPPEND_thenDataIsNotLost
> -
>
> Key: GEODE-8719
> URL: https://issues.apache.org/jira/browse/GEODE-8719
> Project: Geode
> Issue Type: Bug
> Components: redis, tests
>Affects Versions: 1.14.0, 1.15.0
>Reporter: Sarah Abbey
>Assignee: Jens Deppe
>Priority: Minor
> Labels: flaky-test, unreleased
> Fix For: 1.15.0
>
>
> CI failure: https://concourse.apachegeode-ci.info/builds/207449
> {code:java}
> org.apache.geode.redis.internal.executor.CrashAndNoRepeatDUnitTest >
> givenServerCrashesDuringAPPEND_thenDataIsNotLost FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.test.dunit.internal.IdentifiableCallable.call in VM 2
> running on Host e0e2f6af9445 with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:623)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:460)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:268)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:261)
> at
> org.apache.geode.redis.internal.executor.CrashAndNoRepeatDUnitTest.startRedisVM(CrashAndNoRepeatDUnitTest.java:131)
> at
> org.apache.geode.redis.internal.executor.CrashAndNoRepeatDUnitTest.givenServerCrashesDuringAPPEND_thenDataIsNotLost(CrashAndNoRepeatDUnitTest.java:164)
> Caused by:
> org.apache.geode.management.ManagementException: Could not start
> Redis Server using bind address: localhost/127.0.0.1 and port: 44579. Please
> make sure nothing else is running on this address/port combination.
> Caused by:
> java.net.BindException: Address already in use
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-9069) CI Failure: org.apache.geode.redis.internal.executor.hash.HExistsDUnitTest > testConcurrentHExists_whileAddingValues FAILED
[
https://issues.apache.org/jira/browse/GEODE-9069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wayne updated GEODE-9069:
-
Labels: pull-request-available unreleased (was: pull-request-available)
> CI Failure: org.apache.geode.redis.internal.executor.hash.HExistsDUnitTest >
> testConcurrentHExists_whileAddingValues FAILED
> ---
>
> Key: GEODE-9069
> URL: https://issues.apache.org/jira/browse/GEODE-9069
> Project: Geode
> Issue Type: Bug
> Components: redis, tests
>Reporter: Jens Deppe
>Assignee: Hale Bales
>Priority: Major
> Labels: pull-request-available, unreleased
> Fix For: 1.14.0, 1.15.0
>
>
> {noformat}
> org.apache.geode.redis.internal.executor.hash.HExistsDUnitTest >
> testConcurrentHExists_whileAddingValues FAILED
> 00:56:20java.lang.RuntimeException:
> java.util.concurrent.ExecutionException:
> org.awaitility.core.ConditionTimeoutException: Assertion condition defined as
> a lambda expression in
> org.apache.geode.redis.internal.executor.hash.HExistsDUnitTest that uses
> java.lang.String, java.lang.Stringjava.lang.Integer null within 1 seconds.
> 00:56:20at
> org.apache.geode.redis.ConcurrentLoopingThreads.await(ConcurrentLoopingThreads.java:77)
> 00:56:20at
> org.apache.geode.redis.ConcurrentLoopingThreads.runInLockstep(ConcurrentLoopingThreads.java:96)
> 00:56:20at
> org.apache.geode.redis.internal.executor.hash.HExistsDUnitTest.testConcurrentHExists_whileAddingValues(HExistsDUnitTest.java:121)
> 00:56:20
> 00:56:20Caused by:
> 00:56:20java.util.concurrent.ExecutionException:
> org.awaitility.core.ConditionTimeoutException: Assertion condition defined as
> a lambda expression in
> org.apache.geode.redis.internal.executor.hash.HExistsDUnitTest that uses
> java.lang.String, java.lang.Stringjava.lang.Integer null within 1 seconds.
> 00:56:20at
> java.util.concurrent.FutureTask.report(FutureTask.java:122)
> 00:56:20at
> java.util.concurrent.FutureTask.get(FutureTask.java:205)
> 00:56:20at
> org.apache.geode.redis.ConcurrentLoopingThreads.await(ConcurrentLoopingThreads.java:73)
> 00:56:20... 2 more
> 00:56:20
> 00:56:20Caused by:
> 00:56:20org.awaitility.core.ConditionTimeoutException: Assertion
> condition defined as a lambda expression in
> org.apache.geode.redis.internal.executor.hash.HExistsDUnitTest that uses
> java.lang.String, java.lang.Stringjava.lang.Integer null within 1 seconds.
> 00:56:20at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165)
> 00:56:20at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
> 00:56:20at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
> 00:56:20at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:895)
> 00:56:20at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:679)
> 00:56:20at
> org.apache.geode.redis.internal.executor.hash.HExistsDUnitTest.lambda$testConcurrentHExists_whileAddingValues$5(HExistsDUnitTest.java:120)
> 00:56:20
> 00:56:20Caused by:
> 00:56:20java.util.concurrent.TimeoutException
> 00:56:20at
> java.util.concurrent.FutureTask.get(FutureTask.java:204)
> 00:56:20at
> org.awaitility.core.Uninterruptibles.getUninterruptibly(Uninterruptibles.java:101)
> 00:56:20at
> org.awaitility.core.Uninterruptibles.getUninterruptibly(Uninterruptibles.java:81)
> 00:56:20at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:101)
> 00:56:20... 5 more {noformat}
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0081/test-results/distributedTest/161436/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0081/test-artifacts/161436/distributedtestfiles-OpenJDK11-1.15.0-build.0081.tgz
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-8719) CI Failure: org.apache.geode.redis.internal.executor.CrashAndNoRepeatDUnitTest > givenServerCrashesDuringAPPEND_thenDataIsNotLost
[
https://issues.apache.org/jira/browse/GEODE-8719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wayne updated GEODE-8719:
-
Component/s: tests
> CI Failure:
> org.apache.geode.redis.internal.executor.CrashAndNoRepeatDUnitTest >
> givenServerCrashesDuringAPPEND_thenDataIsNotLost
> -
>
> Key: GEODE-8719
> URL: https://issues.apache.org/jira/browse/GEODE-8719
> Project: Geode
> Issue Type: Bug
> Components: redis, tests
>Affects Versions: 1.14.0, 1.15.0
>Reporter: Sarah Abbey
>Assignee: Jens Deppe
>Priority: Minor
> Labels: flaky-test
> Fix For: 1.15.0
>
>
> CI failure: https://concourse.apachegeode-ci.info/builds/207449
> {code:java}
> org.apache.geode.redis.internal.executor.CrashAndNoRepeatDUnitTest >
> givenServerCrashesDuringAPPEND_thenDataIsNotLost FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.test.dunit.internal.IdentifiableCallable.call in VM 2
> running on Host e0e2f6af9445 with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:623)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:460)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:268)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:261)
> at
> org.apache.geode.redis.internal.executor.CrashAndNoRepeatDUnitTest.startRedisVM(CrashAndNoRepeatDUnitTest.java:131)
> at
> org.apache.geode.redis.internal.executor.CrashAndNoRepeatDUnitTest.givenServerCrashesDuringAPPEND_thenDataIsNotLost(CrashAndNoRepeatDUnitTest.java:164)
> Caused by:
> org.apache.geode.management.ManagementException: Could not start
> Redis Server using bind address: localhost/127.0.0.1 and port: 44579. Please
> make sure nothing else is running on this address/port combination.
> Caused by:
> java.net.BindException: Address already in use
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-9069) CI Failure: org.apache.geode.redis.internal.executor.hash.HExistsDUnitTest > testConcurrentHExists_whileAddingValues FAILED
[
https://issues.apache.org/jira/browse/GEODE-9069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wayne updated GEODE-9069:
-
Component/s: tests
> CI Failure: org.apache.geode.redis.internal.executor.hash.HExistsDUnitTest >
> testConcurrentHExists_whileAddingValues FAILED
> ---
>
> Key: GEODE-9069
> URL: https://issues.apache.org/jira/browse/GEODE-9069
> Project: Geode
> Issue Type: Bug
> Components: redis, tests
>Reporter: Jens Deppe
>Assignee: Hale Bales
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.14.0, 1.15.0
>
>
> {noformat}
> org.apache.geode.redis.internal.executor.hash.HExistsDUnitTest >
> testConcurrentHExists_whileAddingValues FAILED
> 00:56:20java.lang.RuntimeException:
> java.util.concurrent.ExecutionException:
> org.awaitility.core.ConditionTimeoutException: Assertion condition defined as
> a lambda expression in
> org.apache.geode.redis.internal.executor.hash.HExistsDUnitTest that uses
> java.lang.String, java.lang.Stringjava.lang.Integer null within 1 seconds.
> 00:56:20at
> org.apache.geode.redis.ConcurrentLoopingThreads.await(ConcurrentLoopingThreads.java:77)
> 00:56:20at
> org.apache.geode.redis.ConcurrentLoopingThreads.runInLockstep(ConcurrentLoopingThreads.java:96)
> 00:56:20at
> org.apache.geode.redis.internal.executor.hash.HExistsDUnitTest.testConcurrentHExists_whileAddingValues(HExistsDUnitTest.java:121)
> 00:56:20
> 00:56:20Caused by:
> 00:56:20java.util.concurrent.ExecutionException:
> org.awaitility.core.ConditionTimeoutException: Assertion condition defined as
> a lambda expression in
> org.apache.geode.redis.internal.executor.hash.HExistsDUnitTest that uses
> java.lang.String, java.lang.Stringjava.lang.Integer null within 1 seconds.
> 00:56:20at
> java.util.concurrent.FutureTask.report(FutureTask.java:122)
> 00:56:20at
> java.util.concurrent.FutureTask.get(FutureTask.java:205)
> 00:56:20at
> org.apache.geode.redis.ConcurrentLoopingThreads.await(ConcurrentLoopingThreads.java:73)
> 00:56:20... 2 more
> 00:56:20
> 00:56:20Caused by:
> 00:56:20org.awaitility.core.ConditionTimeoutException: Assertion
> condition defined as a lambda expression in
> org.apache.geode.redis.internal.executor.hash.HExistsDUnitTest that uses
> java.lang.String, java.lang.Stringjava.lang.Integer null within 1 seconds.
> 00:56:20at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165)
> 00:56:20at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
> 00:56:20at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
> 00:56:20at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:895)
> 00:56:20at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:679)
> 00:56:20at
> org.apache.geode.redis.internal.executor.hash.HExistsDUnitTest.lambda$testConcurrentHExists_whileAddingValues$5(HExistsDUnitTest.java:120)
> 00:56:20
> 00:56:20Caused by:
> 00:56:20java.util.concurrent.TimeoutException
> 00:56:20at
> java.util.concurrent.FutureTask.get(FutureTask.java:204)
> 00:56:20at
> org.awaitility.core.Uninterruptibles.getUninterruptibly(Uninterruptibles.java:101)
> 00:56:20at
> org.awaitility.core.Uninterruptibles.getUninterruptibly(Uninterruptibles.java:81)
> 00:56:20at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:101)
> 00:56:20... 5 more {noformat}
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0081/test-results/distributedTest/161436/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0081/test-artifacts/161436/distributedtestfiles-OpenJDK11-1.15.0-build.0081.tgz
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-9252) CI failure: NativeRedisClusterTestRule incorrect primary node count (expected 3 but was 2)
[
https://issues.apache.org/jira/browse/GEODE-9252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wayne updated GEODE-9252:
-
Labels: flaky-test pull-request-available unreleased (was:
pull-request-available unreleased)
> CI failure: NativeRedisClusterTestRule incorrect primary node count (expected
> 3 but was 2)
> --
>
> Key: GEODE-9252
> URL: https://issues.apache.org/jira/browse/GEODE-9252
> Project: Geode
> Issue Type: Bug
> Components: redis, tests
>Reporter: Owen Nichols
>Assignee: Jens Deppe
>Priority: Major
> Labels: flaky-test, pull-request-available, unreleased
> Fix For: 1.15.0
>
>
> {noformat}
> org.apache.geode.redis.internal.executor.hash.HashesNativeRedisAcceptanceTest
> > classMethod FAILED
> org.junit.ComparisonFailure: [Incorrect primary node count]
> expected:<[3]> but was:<[2]>
> at
> org.apache.geode.redis.NativeRedisClusterTestRule$1.evaluate(NativeRedisClusterTestRule.java:93)
> {noformat}
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-9252) CI failure: NativeRedisClusterTestRule incorrect primary node count (expected 3 but was 2)
[
https://issues.apache.org/jira/browse/GEODE-9252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wayne updated GEODE-9252:
-
Component/s: tests
> CI failure: NativeRedisClusterTestRule incorrect primary node count (expected
> 3 but was 2)
> --
>
> Key: GEODE-9252
> URL: https://issues.apache.org/jira/browse/GEODE-9252
> Project: Geode
> Issue Type: Bug
> Components: redis, tests
>Reporter: Owen Nichols
>Assignee: Jens Deppe
>Priority: Major
> Labels: pull-request-available, unreleased
> Fix For: 1.15.0
>
>
> {noformat}
> org.apache.geode.redis.internal.executor.hash.HashesNativeRedisAcceptanceTest
> > classMethod FAILED
> org.junit.ComparisonFailure: [Incorrect primary node count]
> expected:<[3]> but was:<[2]>
> at
> org.apache.geode.redis.NativeRedisClusterTestRule$1.evaluate(NativeRedisClusterTestRule.java:93)
> {noformat}
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-9252) CI failure: NativeRedisClusterTestRule incorrect primary node count (expected 3 but was 2)
[
https://issues.apache.org/jira/browse/GEODE-9252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wayne updated GEODE-9252:
-
Labels: pull-request-available unreleased (was: pull-request-available)
> CI failure: NativeRedisClusterTestRule incorrect primary node count (expected
> 3 but was 2)
> --
>
> Key: GEODE-9252
> URL: https://issues.apache.org/jira/browse/GEODE-9252
> Project: Geode
> Issue Type: Bug
> Components: redis
>Reporter: Owen Nichols
>Assignee: Jens Deppe
>Priority: Major
> Labels: pull-request-available, unreleased
> Fix For: 1.15.0
>
>
> {noformat}
> org.apache.geode.redis.internal.executor.hash.HashesNativeRedisAcceptanceTest
> > classMethod FAILED
> org.junit.ComparisonFailure: [Incorrect primary node count]
> expected:<[3]> but was:<[2]>
> at
> org.apache.geode.redis.NativeRedisClusterTestRule$1.evaluate(NativeRedisClusterTestRule.java:93)
> {noformat}
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-9299) CI Failure: WANRollingUpgradeSecondaryEventsNotReprocessedAfterOldSiteMemberFailover > testSecondaryEventsNotReprocessedAfterOldSiteMemberFailover
[
https://issues.apache.org/jira/browse/GEODE-9299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wayne updated GEODE-9299:
-
Component/s: tests
> CI Failure:
> WANRollingUpgradeSecondaryEventsNotReprocessedAfterOldSiteMemberFailover >
> testSecondaryEventsNotReprocessedAfterOldSiteMemberFailover
> --
>
> Key: GEODE-9299
> URL: https://issues.apache.org/jira/browse/GEODE-9299
> Project: Geode
> Issue Type: Bug
> Components: tests, wan
>Affects Versions: 1.15.0
>Reporter: Hale Bales
>Assignee: Barrett Oglesby
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> {code:java}
> org.apache.geode.cache.wan.WANRollingUpgradeSecondaryEventsNotReprocessedAfterOldSiteMemberFailover
> > testSecondaryEventsNotReprocessedAfterOldSiteMemberFailover[from_v1.12.2]
> FAILED
> java.lang.AssertionError: expected:<100> but was:<101>
> at org.junit.Assert.fail(Assert.java:89)
> at org.junit.Assert.failNotEquals(Assert.java:835)
> at org.junit.Assert.assertEquals(Assert.java:647)
> at org.junit.Assert.assertEquals(Assert.java:633)
> at
> org.apache.geode.cache.wan.WANRollingUpgradeDUnitTest.stopSenderAndVerifyEvents(WANRollingUpgradeDUnitTest.java:227)
> at
> org.apache.geode.cache.wan.WANRollingUpgradeSecondaryEventsNotReprocessedAfterOldSiteMemberFailover.testSecondaryEventsNotReprocessedAfterOldSiteMemberFailover(WANRollingUpgradeSecondaryEventsNotReprocessedAfterOldSiteMemberFailover.java:98)
> {code}
> CI Failure:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/UpgradeTestOpenJDK11/builds/229#B
> Artifacts Available here:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0253/test-results/upgradeTest/1621635640/
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-9442) CI Failure: acceptance-test-openjdk8 timed out
[ https://issues.apache.org/jira/browse/GEODE-9442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wayne updated GEODE-9442: - Component/s: tests > CI Failure: acceptance-test-openjdk8 timed out > -- > > Key: GEODE-9442 > URL: https://issues.apache.org/jira/browse/GEODE-9442 > Project: Geode > Issue Type: Bug > Components: redis, tests >Reporter: Eric Shu >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > This acceptance-test-openjdk8 failed due to timeout. > https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/acceptance-test-openjdk8/builds/88 > It does not appear to be one particular test hang -- as all running tests are > finished showing status of SUCCESS. > There are 1153 tests shown being run in this run. > Test Summary > 1153 > tests > The previous run showed 1295 tests were run. > Test Summary > 1295 > tests > However, it shows that gradle no able to shut down one test worker: > in daemon-4088.out.log under .gradle_logs directory following exception was > seen: > Daemon is stopping immediately stop command received > Daemon vm is shutting down... The daemon has exited normally or was > terminated in response to a user interrupt. > failed to abort Gradle Test Executor 143 > org.gradle.process.internal.ExecException: A problem occurred waiting for > process 'Gradle Test Executor 143' to complete. > at > org.gradle.process.internal.DefaultExecHandle.execExceptionFor(DefaultExecHandle.java:241) > at > org.gradle.process.internal.DefaultExecHandle.setEndStateInfo(DefaultExecHandle.java:218) > at > org.gradle.process.internal.DefaultExecHandle.failed(DefaultExecHandle.java:369) > at > org.gradle.process.internal.ExecHandleRunner.run(ExecHandleRunner.java:87) > at > org.gradle.internal.operations.CurrentBuildOperationPreservingRunnable.run(CurrentBuildOperationPreservingRunnable.java:42) > at > org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64) > at > org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:48) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at > org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:56) > at java.lang.Thread.run(Thread.java:748) > Caused by: java.lang.IllegalStateException: Shutdown in progress > at > java.lang.ApplicationShutdownHooks.remove(ApplicationShutdownHooks.java:82) > at java.lang.Runtime.removeShutdownHook(Runtime.java:239) > at > org.gradle.process.internal.shutdown.ShutdownHooks.removeShutdownHook(ShutdownHooks.java:33) > at > org.gradle.process.internal.DefaultExecHandle.setEndStateInfo(DefaultExecHandle.java:208) > at > org.gradle.process.internal.DefaultExecHandle.aborted(DefaultExecHandle.java:365) > at > org.gradle.process.internal.ExecHandleRunner.completed(ExecHandleRunner.java:108) > at > org.gradle.process.internal.ExecHandleRunner.run(ExecHandleRunner.java:84) > ... 7 more > Also, in > geode-apis-compatible-with-redis/build/test-results/acceptanceTest/binary > output.bin file that Redis container was started but no further information > for its shutdown. No sure if this is normal or not. > ^A<9c>^H^@<8a>^A[info 2021/07/20 16:55:00.011 UTC tid=0xa] > Ryuk started - will monitor and terminate Testcontainers containers on JVM > exit > ^A<9c>^H^@^A > ^A<9c>^H^@Q[info 2021/07/20 16:55:00.012 UTC tid=0xa] Checking > the system... > ^A<9c>^H^@^A > ^A<9c>^H^@p[info 2021/07/20 16:55:00.013 UTC tid=0xa] > â<9c><94>ï¸<8e> Docker server version should be at least 1.6.0 > ^A<9c>^H^@^A > ^A<9c>^H^@~[info 2021/07/20 16:55:00.142 UTC tid=0xa] > â<9c><94>ï¸<8e> Docker environment should have more than 2GB free disk space > ^A<9c>^H^@^A > ^A<9c>^H^@d[info 2021/07/20 16:55:00.161 UTC tid=0xa] Creating > container for image: redis:5.0.6 > ^A<9c>^H^@^A > ^A<9c>^H^@<97>^A[info 2021/07/20 16:55:00.218 UTC tid=0xa] > Starting container with ID: > 3d1530c27f0b4f6e526bfc48b8232708abd3e0de55f188c74e007db30a19d634 > ^A<9c>^H^@^A > ^A<9c>^H^@<9e>^A[info 2021/07/20 16:55:00.658 UTC tid=0xa] > Container redis:5.0.6 is starting: > 3d1530c27f0b4f6e526bfc48b8232708abd3e0de55f188c74e007db30a19d634 > ^A<9c>^H^@^A > ^A<9c>^H^@d[info 2021/07/20 16:55:00.789 UTC tid=0xa] > Container redis:5.0.6 started in PT0.644S > ^A<9c>^H^@^A > ^A<9c>^H^@r[info 2021/07/20 16:55:00.791 UTC tid=0xa] Started > redis container with exposed port 6379 -> 33290 > Someone has more knowledge of
[jira] [Updated] (GEODE-9442) CI Failure: acceptance-test-openjdk8 timed out
[ https://issues.apache.org/jira/browse/GEODE-9442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wayne updated GEODE-9442: - Labels: pull-request-available unreleased (was: pull-request-available) > CI Failure: acceptance-test-openjdk8 timed out > -- > > Key: GEODE-9442 > URL: https://issues.apache.org/jira/browse/GEODE-9442 > Project: Geode > Issue Type: Bug > Components: redis, tests >Reporter: Eric Shu >Priority: Major > Labels: pull-request-available, unreleased > Fix For: 1.15.0 > > > This acceptance-test-openjdk8 failed due to timeout. > https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/acceptance-test-openjdk8/builds/88 > It does not appear to be one particular test hang -- as all running tests are > finished showing status of SUCCESS. > There are 1153 tests shown being run in this run. > Test Summary > 1153 > tests > The previous run showed 1295 tests were run. > Test Summary > 1295 > tests > However, it shows that gradle no able to shut down one test worker: > in daemon-4088.out.log under .gradle_logs directory following exception was > seen: > Daemon is stopping immediately stop command received > Daemon vm is shutting down... The daemon has exited normally or was > terminated in response to a user interrupt. > failed to abort Gradle Test Executor 143 > org.gradle.process.internal.ExecException: A problem occurred waiting for > process 'Gradle Test Executor 143' to complete. > at > org.gradle.process.internal.DefaultExecHandle.execExceptionFor(DefaultExecHandle.java:241) > at > org.gradle.process.internal.DefaultExecHandle.setEndStateInfo(DefaultExecHandle.java:218) > at > org.gradle.process.internal.DefaultExecHandle.failed(DefaultExecHandle.java:369) > at > org.gradle.process.internal.ExecHandleRunner.run(ExecHandleRunner.java:87) > at > org.gradle.internal.operations.CurrentBuildOperationPreservingRunnable.run(CurrentBuildOperationPreservingRunnable.java:42) > at > org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64) > at > org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:48) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at > org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:56) > at java.lang.Thread.run(Thread.java:748) > Caused by: java.lang.IllegalStateException: Shutdown in progress > at > java.lang.ApplicationShutdownHooks.remove(ApplicationShutdownHooks.java:82) > at java.lang.Runtime.removeShutdownHook(Runtime.java:239) > at > org.gradle.process.internal.shutdown.ShutdownHooks.removeShutdownHook(ShutdownHooks.java:33) > at > org.gradle.process.internal.DefaultExecHandle.setEndStateInfo(DefaultExecHandle.java:208) > at > org.gradle.process.internal.DefaultExecHandle.aborted(DefaultExecHandle.java:365) > at > org.gradle.process.internal.ExecHandleRunner.completed(ExecHandleRunner.java:108) > at > org.gradle.process.internal.ExecHandleRunner.run(ExecHandleRunner.java:84) > ... 7 more > Also, in > geode-apis-compatible-with-redis/build/test-results/acceptanceTest/binary > output.bin file that Redis container was started but no further information > for its shutdown. No sure if this is normal or not. > ^A<9c>^H^@<8a>^A[info 2021/07/20 16:55:00.011 UTC tid=0xa] > Ryuk started - will monitor and terminate Testcontainers containers on JVM > exit > ^A<9c>^H^@^A > ^A<9c>^H^@Q[info 2021/07/20 16:55:00.012 UTC tid=0xa] Checking > the system... > ^A<9c>^H^@^A > ^A<9c>^H^@p[info 2021/07/20 16:55:00.013 UTC tid=0xa] > â<9c><94>ï¸<8e> Docker server version should be at least 1.6.0 > ^A<9c>^H^@^A > ^A<9c>^H^@~[info 2021/07/20 16:55:00.142 UTC tid=0xa] > â<9c><94>ï¸<8e> Docker environment should have more than 2GB free disk space > ^A<9c>^H^@^A > ^A<9c>^H^@d[info 2021/07/20 16:55:00.161 UTC tid=0xa] Creating > container for image: redis:5.0.6 > ^A<9c>^H^@^A > ^A<9c>^H^@<97>^A[info 2021/07/20 16:55:00.218 UTC tid=0xa] > Starting container with ID: > 3d1530c27f0b4f6e526bfc48b8232708abd3e0de55f188c74e007db30a19d634 > ^A<9c>^H^@^A > ^A<9c>^H^@<9e>^A[info 2021/07/20 16:55:00.658 UTC tid=0xa] > Container redis:5.0.6 is starting: > 3d1530c27f0b4f6e526bfc48b8232708abd3e0de55f188c74e007db30a19d634 > ^A<9c>^H^@^A > ^A<9c>^H^@d[info 2021/07/20 16:55:00.789 UTC tid=0xa] > Container redis:5.0.6 started in PT0.644S > ^A<9c>^H^@^A > ^A<9c>^H^@r[info 2021/07/20 16:55:00.791 UTC tid=0xa] Started > redis container
[jira] [Updated] (GEODE-9506) CI Failure: BindException in SessionsAndCrashesDUnitTest
[
https://issues.apache.org/jira/browse/GEODE-9506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wayne updated GEODE-9506:
-
Component/s: tests
> CI Failure: BindException in SessionsAndCrashesDUnitTest
>
>
> Key: GEODE-9506
> URL: https://issues.apache.org/jira/browse/GEODE-9506
> Project: Geode
> Issue Type: Bug
> Components: redis, tests
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Assignee: Donal Evans
>Priority: Major
> Labels: flaky-test, pull-request-available
> Fix For: 1.15.0
>
>
> {noformat}
> org.apache.geode.redis.session.SessionsAndCrashesDUnitTest >
> sessionOperationsDoNotFail_whileServersAreRestarted FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.test.dunit.internal.IdentifiableCallable.call in VM 3
> running on Host
> heavy-lifter-48e50679-1ba5-54cd-8da2-5aadbb3287e4.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:461)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:270)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:262)
> at
> org.apache.geode.test.dunit.rules.RedisClusterStartupRule.startRedisVM(RedisClusterStartupRule.java:82)
> at
> org.apache.geode.redis.session.SessionsAndCrashesDUnitTest.startRedisVM(SessionsAndCrashesDUnitTest.java:93)
> at
> org.apache.geode.redis.session.SessionsAndCrashesDUnitTest.sessionOperationsDoNotFail_whileServersAreRestarted(SessionsAndCrashesDUnitTest.java:154)
> Caused by:
> org.apache.geode.management.ManagementException: Could not start
> server compatible with Redis using bind address: /127.0.0.1 and port: 35275.
> Please make sure nothing else is running on this address/port combination.
> at
> org.apache.geode.redis.internal.netty.NettyRedisServer.createBoundChannel(NettyRedisServer.java:222)
> at
> org.apache.geode.redis.internal.netty.NettyRedisServer.createChannel(NettyRedisServer.java:137)
> at
> org.apache.geode.redis.internal.netty.NettyRedisServer.(NettyRedisServer.java:116)
> at
> org.apache.geode.redis.internal.GeodeRedisServer.(GeodeRedisServer.java:94)
> at
> org.apache.geode.redis.internal.GeodeRedisService.startRedisServer(GeodeRedisService.java:112)
> at
> org.apache.geode.redis.internal.GeodeRedisService.handleEvent(GeodeRedisService.java:96)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.notifyResourceEventListeners(InternalDistributedSystem.java:2088)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.handleResourceEvent(InternalDistributedSystem.java:644)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.initialize(GemFireCacheImpl.java:1471)
> at
> org.apache.geode.internal.cache.InternalCacheBuilder.create(InternalCacheBuilder.java:191)
> at
> org.apache.geode.internal.cache.InternalCacheBuilder.create(InternalCacheBuilder.java:158)
> at
> org.apache.geode.cache.CacheFactory.create(CacheFactory.java:142)
> at
> org.apache.geode.test.junit.rules.ServerStarterRule.startServer(ServerStarterRule.java:204)
> at
> org.apache.geode.test.junit.rules.ServerStarterRule.before(ServerStarterRule.java:99)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.lambda$startServerVM$6d6c10c2$1(ClusterStartupRule.java:278)
> at
> org.apache.geode.test.dunit.internal.IdentifiableCallable.call(IdentifiableCallable.java:41)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.geode.test.dunit.internal.MethodInvoker.executeObject(MethodInvoker.java:123)
> at
> org.apache.geode.test.dunit.internal.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:78)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
>
[jira] [Updated] (GEODE-9506) CI Failure: BindException in SessionsAndCrashesDUnitTest
[
https://issues.apache.org/jira/browse/GEODE-9506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wayne updated GEODE-9506:
-
Labels: flaky-test pull-request-available unreleased (was: flaky-test
pull-request-available)
> CI Failure: BindException in SessionsAndCrashesDUnitTest
>
>
> Key: GEODE-9506
> URL: https://issues.apache.org/jira/browse/GEODE-9506
> Project: Geode
> Issue Type: Bug
> Components: redis, tests
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Assignee: Donal Evans
>Priority: Major
> Labels: flaky-test, pull-request-available, unreleased
> Fix For: 1.15.0
>
>
> {noformat}
> org.apache.geode.redis.session.SessionsAndCrashesDUnitTest >
> sessionOperationsDoNotFail_whileServersAreRestarted FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.test.dunit.internal.IdentifiableCallable.call in VM 3
> running on Host
> heavy-lifter-48e50679-1ba5-54cd-8da2-5aadbb3287e4.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:461)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:270)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:262)
> at
> org.apache.geode.test.dunit.rules.RedisClusterStartupRule.startRedisVM(RedisClusterStartupRule.java:82)
> at
> org.apache.geode.redis.session.SessionsAndCrashesDUnitTest.startRedisVM(SessionsAndCrashesDUnitTest.java:93)
> at
> org.apache.geode.redis.session.SessionsAndCrashesDUnitTest.sessionOperationsDoNotFail_whileServersAreRestarted(SessionsAndCrashesDUnitTest.java:154)
> Caused by:
> org.apache.geode.management.ManagementException: Could not start
> server compatible with Redis using bind address: /127.0.0.1 and port: 35275.
> Please make sure nothing else is running on this address/port combination.
> at
> org.apache.geode.redis.internal.netty.NettyRedisServer.createBoundChannel(NettyRedisServer.java:222)
> at
> org.apache.geode.redis.internal.netty.NettyRedisServer.createChannel(NettyRedisServer.java:137)
> at
> org.apache.geode.redis.internal.netty.NettyRedisServer.(NettyRedisServer.java:116)
> at
> org.apache.geode.redis.internal.GeodeRedisServer.(GeodeRedisServer.java:94)
> at
> org.apache.geode.redis.internal.GeodeRedisService.startRedisServer(GeodeRedisService.java:112)
> at
> org.apache.geode.redis.internal.GeodeRedisService.handleEvent(GeodeRedisService.java:96)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.notifyResourceEventListeners(InternalDistributedSystem.java:2088)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.handleResourceEvent(InternalDistributedSystem.java:644)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.initialize(GemFireCacheImpl.java:1471)
> at
> org.apache.geode.internal.cache.InternalCacheBuilder.create(InternalCacheBuilder.java:191)
> at
> org.apache.geode.internal.cache.InternalCacheBuilder.create(InternalCacheBuilder.java:158)
> at
> org.apache.geode.cache.CacheFactory.create(CacheFactory.java:142)
> at
> org.apache.geode.test.junit.rules.ServerStarterRule.startServer(ServerStarterRule.java:204)
> at
> org.apache.geode.test.junit.rules.ServerStarterRule.before(ServerStarterRule.java:99)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.lambda$startServerVM$6d6c10c2$1(ClusterStartupRule.java:278)
> at
> org.apache.geode.test.dunit.internal.IdentifiableCallable.call(IdentifiableCallable.java:41)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.geode.test.dunit.internal.MethodInvoker.executeObject(MethodInvoker.java:123)
> at
> org.apache.geode.test.dunit.internal.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:78)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at
[jira] [Updated] (GEODE-9528) CI Failure: DistributionAdvisorIntegrationTest > verifyMembershipListenerIsRemovedAfterForceDisconnect
[
https://issues.apache.org/jira/browse/GEODE-9528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wayne updated GEODE-9528:
-
Component/s: tests
> CI Failure: DistributionAdvisorIntegrationTest >
> verifyMembershipListenerIsRemovedAfterForceDisconnect
> --
>
> Key: GEODE-9528
> URL: https://issues.apache.org/jira/browse/GEODE-9528
> Project: Geode
> Issue Type: Bug
> Components: membership, tests
>Affects Versions: 1.12.5, 1.13.5, 1.14.0
>Reporter: Owen Nichols
>Assignee: Barrett Oglesby
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.12.9, 1.13.8, 1.14.4, 1.15.0
>
>
> {noformat}
> org.apache.geode.distributed.internal.DistributionAdvisorIntegrationTest >
> verifyMembershipListenerIsRemovedAfterForceDisconnect FAILED
> org.junit.ComparisonFailure: expected:<[fals]e> but was:<[tru]e>
> at
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.distributed.internal.DistributionAdvisorIntegrationTest.verifyMembershipListenerIsRemovedAfterForceDisconnect(DistributionAdvisorIntegrationTest.java:57)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-9606) CI Failure: PubSubIntegrationTest.testPatternWithoutAGlob fails with AssertionError
[ https://issues.apache.org/jira/browse/GEODE-9606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wayne updated GEODE-9606: - Labels: flaky-test pull-request-available unreleased (was: pull-request-available) > CI Failure: PubSubIntegrationTest.testPatternWithoutAGlob fails with > AssertionError > --- > > Key: GEODE-9606 > URL: https://issues.apache.org/jira/browse/GEODE-9606 > Project: Geode > Issue Type: Bug > Components: redis, tests >Affects Versions: 1.15.0 >Reporter: Benjamin P Ross >Priority: Major > Labels: flaky-test, pull-request-available, unreleased > Fix For: 1.15.0 > > > The following failure occurred in a CI run: > org.apache.geode.redis.internal.executor.pubsub.PubSubIntegrationTest > > testPatternWithoutAGlob FAILED > java.lang.AssertionError: > Expecting actual: > [] > to contain exactly (and in same order): > ["hello"] > but could not find the following elements: > ["hello"] > at > org.apache.geode.redis.internal.executor.pubsub.AbstractPubSubIntegrationTest.testPatternWithoutAGlob(AbstractPubSubIntegrationTest.java:774) > at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native > Method) > at > jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:566) > at > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56) > at > org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at > org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306) > at > org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63) > at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329) > at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293) > at > org.apache.geode.test.junit.rules.serializable.SerializableExternalResource$1.evaluate(SerializableExternalResource.java:38) > at > org.apache.geode.test.junit.rules.serializable.SerializableExternalResource$1.evaluate(SerializableExternalResource.java:38) > at org.junit.rules.RunRules.evaluate(RunRules.java:20) > at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306) > at org.junit.runners.ParentRunner.run(ParentRunner.java:413) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:110) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38) > at > org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:62) > at > org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51) > at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native > Method) > at > jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:566) > at > org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:36) > at > org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) > at > org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:33) > at >
[jira] [Updated] (GEODE-9606) CI Failure: PubSubIntegrationTest.testPatternWithoutAGlob fails with AssertionError
[ https://issues.apache.org/jira/browse/GEODE-9606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wayne updated GEODE-9606: - Component/s: tests > CI Failure: PubSubIntegrationTest.testPatternWithoutAGlob fails with > AssertionError > --- > > Key: GEODE-9606 > URL: https://issues.apache.org/jira/browse/GEODE-9606 > Project: Geode > Issue Type: Bug > Components: redis, tests >Affects Versions: 1.15.0 >Reporter: Benjamin P Ross >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > The following failure occurred in a CI run: > org.apache.geode.redis.internal.executor.pubsub.PubSubIntegrationTest > > testPatternWithoutAGlob FAILED > java.lang.AssertionError: > Expecting actual: > [] > to contain exactly (and in same order): > ["hello"] > but could not find the following elements: > ["hello"] > at > org.apache.geode.redis.internal.executor.pubsub.AbstractPubSubIntegrationTest.testPatternWithoutAGlob(AbstractPubSubIntegrationTest.java:774) > at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native > Method) > at > jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:566) > at > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56) > at > org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at > org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306) > at > org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63) > at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329) > at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293) > at > org.apache.geode.test.junit.rules.serializable.SerializableExternalResource$1.evaluate(SerializableExternalResource.java:38) > at > org.apache.geode.test.junit.rules.serializable.SerializableExternalResource$1.evaluate(SerializableExternalResource.java:38) > at org.junit.rules.RunRules.evaluate(RunRules.java:20) > at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306) > at org.junit.runners.ParentRunner.run(ParentRunner.java:413) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:110) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38) > at > org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:62) > at > org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51) > at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native > Method) > at > jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:566) > at > org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:36) > at > org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) > at > org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:33) > at >
[jira] [Updated] (GEODE-9675) CI: ClusterDistributionManagerDUnitTest > testConnectAfterBeingShunned FAILED
[
https://issues.apache.org/jira/browse/GEODE-9675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wayne updated GEODE-9675:
-
Labels: flaky-test pull-request-available (was: pull-request-available)
> CI: ClusterDistributionManagerDUnitTest > testConnectAfterBeingShunned FAILED
> -
>
> Key: GEODE-9675
> URL: https://issues.apache.org/jira/browse/GEODE-9675
> Project: Geode
> Issue Type: Bug
> Components: membership, tests
>Affects Versions: 1.15.0
>Reporter: Xiaojian Zhou
>Assignee: Bill Burcham
>Priority: Major
> Labels: flaky-test, pull-request-available
> Fix For: 1.15.0
>
> Attachments: screenshot-1.png
>
>
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/1983
> {code:java}
> ClusterDistributionManagerDUnitTest > testConnectAfterBeingShunned FAILED
> org.apache.geode.SystemConnectException: Problem starting up membership
> services
> at
> org.apache.geode.distributed.internal.DistributionImpl.start(DistributionImpl.java:186)
> at
> org.apache.geode.distributed.internal.DistributionImpl.createDistribution(DistributionImpl.java:222)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:466)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:499)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.create(ClusterDistributionManager.java:328)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:757)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.access$200(InternalDistributedSystem.java:133)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem$Builder.build(InternalDistributedSystem.java:3013)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.connectInternal(InternalDistributedSystem.java:283)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.connectInternal(InternalDistributedSystem.java:209)
> at
> org.apache.geode.distributed.DistributedSystem.connect(DistributedSystem.java:159)
> at
> org.apache.geode.test.dunit.internal.JUnit4DistributedTestCase.getSystem(JUnit4DistributedTestCase.java:180)
> at
> org.apache.geode.test.dunit.internal.JUnit4DistributedTestCase.getSystem(JUnit4DistributedTestCase.java:256)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManagerDUnitTest.testConnectAfterBeingShunned(ClusterDistributionManagerDUnitTest.java:170)
> Caused by:
>
> org.apache.geode.distributed.internal.membership.api.MemberStartupException:
> unable to create jgroups channel
> at
> org.apache.geode.distributed.internal.membership.gms.messenger.JGroupsMessenger.start(JGroupsMessenger.java:401)
> at
> org.apache.geode.distributed.internal.membership.gms.Services.start(Services.java:203)
> at
> org.apache.geode.distributed.internal.membership.gms.GMSMembership.start(GMSMembership.java:1642)
> at
> org.apache.geode.distributed.internal.DistributionImpl.start(DistributionImpl.java:171)
> ... 13 more
> Caused by:
> java.lang.Exception: failed to open a port in range 41003-41003
> at
> org.jgroups.protocols.UDP.createMulticastSocketWithBindPort(UDP.java:503)
> at org.jgroups.protocols.UDP.createSockets(UDP.java:348)
> at org.jgroups.protocols.UDP.start(UDP.java:266)
> at
> org.jgroups.stack.ProtocolStack.startStack(ProtocolStack.java:966)
> at org.jgroups.JChannel.startStack(JChannel.java:889)
> at org.jgroups.JChannel._preConnect(JChannel.java:553)
> at org.jgroups.JChannel.connect(JChannel.java:288)
> at org.jgroups.JChannel.connect(JChannel.java:279)
> at
> org.apache.geode.distributed.internal.membership.gms.messenger.JGroupsMessenger.start(JGroupsMessenger.java:397)
> ... 16 more
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-9675) CI: ClusterDistributionManagerDUnitTest > testConnectAfterBeingShunned FAILED
[
https://issues.apache.org/jira/browse/GEODE-9675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wayne updated GEODE-9675:
-
Component/s: tests
> CI: ClusterDistributionManagerDUnitTest > testConnectAfterBeingShunned FAILED
> -
>
> Key: GEODE-9675
> URL: https://issues.apache.org/jira/browse/GEODE-9675
> Project: Geode
> Issue Type: Bug
> Components: membership, tests
>Affects Versions: 1.15.0
>Reporter: Xiaojian Zhou
>Assignee: Bill Burcham
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
> Attachments: screenshot-1.png
>
>
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/1983
> {code:java}
> ClusterDistributionManagerDUnitTest > testConnectAfterBeingShunned FAILED
> org.apache.geode.SystemConnectException: Problem starting up membership
> services
> at
> org.apache.geode.distributed.internal.DistributionImpl.start(DistributionImpl.java:186)
> at
> org.apache.geode.distributed.internal.DistributionImpl.createDistribution(DistributionImpl.java:222)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:466)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:499)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.create(ClusterDistributionManager.java:328)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:757)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.access$200(InternalDistributedSystem.java:133)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem$Builder.build(InternalDistributedSystem.java:3013)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.connectInternal(InternalDistributedSystem.java:283)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.connectInternal(InternalDistributedSystem.java:209)
> at
> org.apache.geode.distributed.DistributedSystem.connect(DistributedSystem.java:159)
> at
> org.apache.geode.test.dunit.internal.JUnit4DistributedTestCase.getSystem(JUnit4DistributedTestCase.java:180)
> at
> org.apache.geode.test.dunit.internal.JUnit4DistributedTestCase.getSystem(JUnit4DistributedTestCase.java:256)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManagerDUnitTest.testConnectAfterBeingShunned(ClusterDistributionManagerDUnitTest.java:170)
> Caused by:
>
> org.apache.geode.distributed.internal.membership.api.MemberStartupException:
> unable to create jgroups channel
> at
> org.apache.geode.distributed.internal.membership.gms.messenger.JGroupsMessenger.start(JGroupsMessenger.java:401)
> at
> org.apache.geode.distributed.internal.membership.gms.Services.start(Services.java:203)
> at
> org.apache.geode.distributed.internal.membership.gms.GMSMembership.start(GMSMembership.java:1642)
> at
> org.apache.geode.distributed.internal.DistributionImpl.start(DistributionImpl.java:171)
> ... 13 more
> Caused by:
> java.lang.Exception: failed to open a port in range 41003-41003
> at
> org.jgroups.protocols.UDP.createMulticastSocketWithBindPort(UDP.java:503)
> at org.jgroups.protocols.UDP.createSockets(UDP.java:348)
> at org.jgroups.protocols.UDP.start(UDP.java:266)
> at
> org.jgroups.stack.ProtocolStack.startStack(ProtocolStack.java:966)
> at org.jgroups.JChannel.startStack(JChannel.java:889)
> at org.jgroups.JChannel._preConnect(JChannel.java:553)
> at org.jgroups.JChannel.connect(JChannel.java:288)
> at org.jgroups.JChannel.connect(JChannel.java:279)
> at
> org.apache.geode.distributed.internal.membership.gms.messenger.JGroupsMessenger.start(JGroupsMessenger.java:397)
> ... 16 more
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-9729) CI Failure: PartitionedRegionSingleHopDUnitTest.testClientMetadataForPersistentPrs FAILED
[ https://issues.apache.org/jira/browse/GEODE-9729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wayne updated GEODE-9729: - Component/s: tests > CI Failure: > PartitionedRegionSingleHopDUnitTest.testClientMetadataForPersistentPrs FAILED > - > > Key: GEODE-9729 > URL: https://issues.apache.org/jira/browse/GEODE-9729 > Project: Geode > Issue Type: Bug > Components: client/server, tests >Affects Versions: 1.15.0 >Reporter: Eric Shu >Assignee: Xiaojian Zhou >Priority: Major > Labels: GeodeOperationAPI, pull-request-available > Fix For: 1.15.0 > > > org.apache.geode.cache.client.AllConnectionsInUseException > at > org.apache.geode.cache.client.internal.pooling.ConnectionManagerImpl.borrowConnection(ConnectionManagerImpl.java:304) > at > org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:137) > at > org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:120) > at > org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:805) > at > org.apache.geode.cache.client.internal.GetClientPRMetaDataOp.execute(GetClientPRMetaDataOp.java:53) > at > org.apache.geode.cache.client.internal.ClientMetadataService.getClientPRMetadata(ClientMetadataService.java:574) > at > org.apache.geode.internal.cache.PartitionedRegionSingleHopDUnitTest.lambda$testClientMetadataForPersistentPrs$26(PartitionedRegionSingleHopDUnitTest.java:972) > at > org.awaitility.core.AssertionCondition.lambda$new$0(AssertionCondition.java:53) > at > org.awaitility.core.ConditionAwaiter$ConditionPoller.call(ConditionAwaiter.java:234) > at > org.awaitility.core.ConditionAwaiter$ConditionPoller.call(ConditionAwaiter.java:221) > at java.util.concurrent.FutureTask.run(FutureTask.java:264) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) > at java.lang.Thread.run(Thread.java:829) -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-9810) CI: NativeRedisClusterTest testEachProxyReturnsExposedPorts failed
[
https://issues.apache.org/jira/browse/GEODE-9810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wayne updated GEODE-9810:
-
Labels: pull-request-available unreleased (was: pull-request-available)
> CI: NativeRedisClusterTest testEachProxyReturnsExposedPorts failed
> --
>
> Key: GEODE-9810
> URL: https://issues.apache.org/jira/browse/GEODE-9810
> Project: Geode
> Issue Type: Bug
> Components: redis
>Reporter: Xiaojian Zhou
>Assignee: Jens Deppe
>Priority: Major
> Labels: pull-request-available, unreleased
> Fix For: 1.15.0
>
>
>
> {code:java}
> > Task :geode-for-redis:acceptanceTest
> NativeRedisClusterTest > testEachProxyReturnsExposedPorts FAILED
> java.lang.AssertionError:
> Expecting actual:
> [44073, 45679, 36065, 40077, 42137]
> to contain exactly in any order:
> [40077, 45679, 33425, 36065, 42137, 44073]
> but could not find the following elements:
> [33425]
> at
> org.apache.geode.redis.NativeRedisClusterTest.testEachProxyReturnsExposedPorts(NativeRedisClusterTest.java:48)
> 1385 tests completed, 1 failed, 2 skipped
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0662/test-results/acceptanceTest/1637046056/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0662/test-artifacts/1637046056/acceptancetestfiles-openjdk8-1.15.0-build.0662.tgz
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-9871) CI failure: InfoStatsIntegrationTest > networkKiloBytesReadOverLastSecond_shouldBeCloseToBytesReadOverLastSecond
[
https://issues.apache.org/jira/browse/GEODE-9871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wayne updated GEODE-9871:
-
Labels: pull-request-available unreleased (was: pull-request-available)
> CI failure: InfoStatsIntegrationTest >
> networkKiloBytesReadOverLastSecond_shouldBeCloseToBytesReadOverLastSecond
>
>
> Key: GEODE-9871
> URL: https://issues.apache.org/jira/browse/GEODE-9871
> Project: Geode
> Issue Type: Bug
> Components: redis, statistics
>Affects Versions: 1.15.0
>Reporter: Bill Burcham
>Assignee: Jens Deppe
>Priority: Major
> Labels: pull-request-available, unreleased
> Fix For: 1.15.0
>
>
> link:
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/integration-test-openjdk8/builds/38]
> stack trace:
> {code:java}
> InfoStatsIntegrationTest >
> networkKiloBytesReadOverLastSecond_shouldBeCloseToBytesReadOverLastSecond
> FAILED
> org.opentest4j.AssertionFailedError:
> expected: 0.0
> but was: 0.01
> 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.redis.internal.commands.executor.server.AbstractRedisInfoStatsIntegrationTest.networkKiloBytesReadOverLastSecond_shouldBeCloseToBytesReadOverLastSecond(AbstractRedisInfoStatsIntegrationTest.java:228)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at
> org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
> at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
> at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.apache.geode.test.junit.rules.serializable.SerializableExternalResource$1.evaluate(SerializableExternalResource.java:38)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:115)
> at
> org.junit.vintage.engine.execution.RunnerExecutor.execute(RunnerExecutor.java:43)
> at
> java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:183)
> at
> java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193)
> at java.util.Iterator.forEachRemaining(Iterator.java:116)
> at
> java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1801)
> at
> java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:482)
> at
> java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:472)
> at
> java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:150)
> at
> java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:173)
> at
>
[jira] [Created] (GEODE-10064) Native Redis Acceptance Test Separate Job
Wayne created GEODE-10064: - Summary: Native Redis Acceptance Test Separate Job Key: GEODE-10064 URL: https://issues.apache.org/jira/browse/GEODE-10064 Project: Geode Issue Type: New Feature Components: redis Reporter: Wayne Split out into separate job. Only run if changes occurred to geode-for-redis integration test files. New sourceset name, integration-test-validation-test. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-10051) Create Configuration for Keyspace Notifications
Wayne created GEODE-10051: - Summary: Create Configuration for Keyspace Notifications Key: GEODE-10051 URL: https://issues.apache.org/jira/browse/GEODE-10051 Project: Geode Issue Type: New Feature Components: redis Reporter: Wayne [Keyspace Notifications|https://redis.io/topics/notifications#configuration] require a common infrastructure for configuration. +Acceptance Criteria+ The infrastructure for Keyspace Notifications has been created along with the appropriate unit testing and documentation updates. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-10050) Implement BLPOP
Wayne created GEODE-10050: - Summary: Implement BLPOP Key: GEODE-10050 URL: https://issues.apache.org/jira/browse/GEODE-10050 Project: Geode Issue Type: New Feature Components: redis Reporter: Wayne Implement the [BLPOP|https://redis.io/commands/blpop] Command. +Acceptance Criteria+ The BLPOP command has been. implemented, per specifications, along with all associated unit, acceptance, and system testing. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (GEODE-10033) Disable Geode Redis Stats Above Threshold
[ https://issues.apache.org/jira/browse/GEODE-10033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wayne resolved GEODE-10033. --- Resolution: Won't Fix We decided that this issue was unnecessary. > Disable Geode Redis Stats Above Threshold > - > > Key: GEODE-10033 > URL: https://issues.apache.org/jira/browse/GEODE-10033 > Project: Geode > Issue Type: Improvement > Components: redis >Reporter: Wayne >Priority: Major > > The current limit for Geode for Redis stats is 254. After we have reached > this threshold, stop publishing stats. This is a temporary change until we > can reorganize stats. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-10048) Create Common Infrastructure for Blocking Commands and Keyspace Event Notifications
Wayne created GEODE-10048: - Summary: Create Common Infrastructure for Blocking Commands and Keyspace Event Notifications Key: GEODE-10048 URL: https://issues.apache.org/jira/browse/GEODE-10048 Project: Geode Issue Type: New Feature Components: redis Reporter: Wayne Create the common infrastructure that will be used for implementing both Redis blocking commands and Keyspace Event Notifications. +Acceptance Criteria+ The common infrastructure has been implemented along with appropriate unit testing. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-10034) Organize Geode For Redis Stats By Data Structure
Wayne created GEODE-10034: - Summary: Organize Geode For Redis Stats By Data Structure Key: GEODE-10034 URL: https://issues.apache.org/jira/browse/GEODE-10034 Project: Geode Issue Type: Improvement Components: redis Reporter: Wayne The Geode for Redis Stats should be organized by Data Structure. For the stats not associated with a data structure, the stats should continue to be exposed under "GeodeForRedisStats". +Acceptance Criteria+ All stats, associated with a command specific to a data structure, should be exposed under that data structure (e.g. Strings, Sets, SortedSets, Hashes, Lists). All tests should pass. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-10033) Disable Geode Redis Stats Above Threshold
Wayne created GEODE-10033: - Summary: Disable Geode Redis Stats Above Threshold Key: GEODE-10033 URL: https://issues.apache.org/jira/browse/GEODE-10033 Project: Geode Issue Type: Improvement Components: redis Reporter: Wayne The current limit for Geode for Redis stats is 254. After we have reached this threshold, stop publishing stats. This is a temporary change until we can reorganize stats. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9835) SSCAN Command Supported
[ https://issues.apache.org/jira/browse/GEODE-9835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wayne reassigned GEODE-9835: Assignee: Steve Sienkowski > SSCAN Command Supported > --- > > Key: GEODE-9835 > URL: https://issues.apache.org/jira/browse/GEODE-9835 > Project: Geode > Issue Type: Improvement > Components: redis >Affects Versions: 1.15.0, 1.16.0 >Reporter: Wayne >Assignee: Steve Sienkowski >Priority: Major > Labels: blocks-1.15.0, pull-request-available > Fix For: 1.15.0, 1.16.0 > > > The SSCAN 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] [Assigned] (GEODE-9835) SSCAN Command Supported
[ https://issues.apache.org/jira/browse/GEODE-9835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wayne reassigned GEODE-9835: Assignee: (was: Bala Tripura Sundari Kaza Venkata) > SSCAN Command Supported > --- > > Key: GEODE-9835 > URL: https://issues.apache.org/jira/browse/GEODE-9835 > Project: Geode > Issue Type: Improvement > Components: redis >Affects Versions: 1.15.0, 1.16.0 >Reporter: Wayne >Priority: Major > Labels: blocks-1.15.0, pull-request-available > > The SSCAN 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-9999) Update the Geode for Redis documentation
[ https://issues.apache.org/jira/browse/GEODE-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wayne updated GEODE-: - Labels: backport blocks-1.15.0 pull-request-available (was: backport pull-request-available) > Update the Geode for Redis documentation > > > Key: GEODE- > URL: https://issues.apache.org/jira/browse/GEODE- > Project: Geode > Issue Type: Improvement > Components: redis >Affects Versions: 1.15.0, 1.16.0 >Reporter: John Martin >Priority: Major > Labels: backport, blocks-1.15.0, pull-request-available > > A few updates are needed to update the Geode for Redis documentation to > better reflect the current implementation of the Redis module. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-9835) SSCAN Command Supported
[ https://issues.apache.org/jira/browse/GEODE-9835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wayne updated GEODE-9835: - Labels: blocks-1.15.0 pull-request-available (was: pull-request-available) > SSCAN Command Supported > --- > > Key: GEODE-9835 > URL: https://issues.apache.org/jira/browse/GEODE-9835 > Project: Geode > Issue Type: Improvement > Components: redis >Reporter: Wayne >Priority: Major > Labels: blocks-1.15.0, pull-request-available > > The SSCAN 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 ] Wayne updated GEODE-9833: - Labels: blocks-1.15.0 pull-request-available (was: pull-request-available) > 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 > Labels: blocks-1.15.0, pull-request-available > > 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] [Resolved] (GEODE-9320) CI Failure: SetNXNativeRedisAcceptanceTest > classMethod FAILED
[
https://issues.apache.org/jira/browse/GEODE-9320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wayne resolved GEODE-9320.
--
Resolution: Cannot Reproduce
> CI Failure: SetNXNativeRedisAcceptanceTest > classMethod FAILED
> ---
>
> Key: GEODE-9320
> URL: https://issues.apache.org/jira/browse/GEODE-9320
> Project: Geode
> Issue Type: Bug
> Components: redis
>Reporter: Jens Deppe
>Priority: Major
> Labels: flaky-test
>
> {noformat}
> org.apache.geode.redis.internal.executor.string.SetNXNativeRedisAcceptanceTest
> > classMethod FAILED
> 13:40:47org.testcontainers.containers.ContainerLaunchException: Container
> startup failed
> 13:40:47at
> org.testcontainers.containers.GenericContainer.doStart(GenericContainer.java:330)
> 13:40:47at
> org.testcontainers.containers.GenericContainer.start(GenericContainer.java:311)
> 13:40:47at
> org.testcontainers.containers.DockerComposeContainer.startAmbassadorContainers(DockerComposeContainer.java:330)
> 13:40:47at
> org.testcontainers.containers.DockerComposeContainer.start(DockerComposeContainer.java:178)
> 13:40:47at
> org.apache.geode.redis.NativeRedisClusterTestRule$1.evaluate(NativeRedisClusterTestRule.java:85)
> 13:40:47at
> org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:54)
> 13:40:47at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> 13:40:47at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> 13:40:47at
> org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> 13:40:47at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
> 13:40:47at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:110)
> 13:40:47at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58)
> 13:40:47at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38)
> 13:40:47at
> org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:62)
> 13:40:47at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
> 13:40:47at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 13:40:47at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 13:40:47at
> jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 13:40:47at java.lang.reflect.Method.invoke(Method.java:566)
> 13:40:47at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:36)
> 13:40:47at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> 13:40:47at
> org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:33)
> 13:40:47at
> org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:94)
> 13:40:47at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> 13:40:47at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:119)
> 13:40:47at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 13:40:47at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 13:40:47at
> jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 13:40:47at java.lang.reflect.Method.invoke(Method.java:566)
> 13:40:47at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:36)
> 13:40:47at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> 13:40:47at
> org.gradle.internal.remote.internal.hub.MessageHubBackedObjectConnection$DispatchWrapper.dispatch(MessageHubBackedObjectConnection.java:182)
> 13:40:47at
> org.gradle.internal.remote.internal.hub.MessageHubBackedObjectConnection$DispatchWrapper.dispatch(MessageHubBackedObjectConnection.java:164)
> 13:40:47at
> org.gradle.internal.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:414)
> 13:40:47at
> org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64)
> 13:40:47at
> org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:48)
> 13:40:47at
>
[jira] [Created] (GEODE-9992) Migrate Redis Unit Tests to Use of JUnit5
Wayne created GEODE-9992: Summary: Migrate Redis Unit Tests to Use of JUnit5 Key: GEODE-9992 URL: https://issues.apache.org/jira/browse/GEODE-9992 Project: Geode Issue Type: Improvement Components: redis Reporter: Wayne Special attention must be made regarding JUnit4 Rules which are no longer supported in JUnit5. -- 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] [Commented] (GEODE-9883) Review and Cleanup geode_for_redis.html.md.erb
[ https://issues.apache.org/jira/browse/GEODE-9883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17479592#comment-17479592 ] Wayne commented on GEODE-9883: -- Per conversations with release management, removing release blocker label. > Review and Cleanup geode_for_redis.html.md.erb > -- > > Key: GEODE-9883 > URL: https://issues.apache.org/jira/browse/GEODE-9883 > Project: Geode > Issue Type: Task > Components: docs, redis >Affects Versions: 1.15.0 >Reporter: Wayne >Assignee: Eric Zoerner >Priority: Major > Labels: blocks-1.15.0, pull-request-available > > Looking at what we have in the geode docs, a few things that are out of date. > * This page still references the geode-for-redis-password, which doesn't > exist any more. It should probably talk about how redis interacts with the > security manager. > * Probably should mention how to configure TLS properties for > geode-for-redis. > * The redis-cli command I think is missing a -c option to use cluster mode. > * The supported redis commands listed in that page is incomplete > * Advantages section doesn't mention synchronous replication -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-9883) Review and Cleanup geode_for_redis.html.md.erb
[ https://issues.apache.org/jira/browse/GEODE-9883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wayne updated GEODE-9883: - Labels: pull-request-available (was: blocks-1.15.0 pull-request-available) > Review and Cleanup geode_for_redis.html.md.erb > -- > > Key: GEODE-9883 > URL: https://issues.apache.org/jira/browse/GEODE-9883 > Project: Geode > Issue Type: Task > Components: docs, redis >Affects Versions: 1.15.0 >Reporter: Wayne >Assignee: Eric Zoerner >Priority: Major > Labels: pull-request-available > > Looking at what we have in the geode docs, a few things that are out of date. > * This page still references the geode-for-redis-password, which doesn't > exist any more. It should probably talk about how redis interacts with the > security manager. > * Probably should mention how to configure TLS properties for > geode-for-redis. > * The redis-cli command I think is missing a -c option to use cluster mode. > * The supported redis commands listed in that page is incomplete > * Advantages section doesn't mention synchronous replication -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-9970) Decouple Redis Module From Geode Core
Wayne created GEODE-9970: Summary: Decouple Redis Module From Geode Core Key: GEODE-9970 URL: https://issues.apache.org/jira/browse/GEODE-9970 Project: Geode Issue Type: Improvement Components: redis Reporter: Wayne Decouple the Redis module from Geode Core to allow for the Redis module to evolve and be released independently from Geode Core. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-9737) CI failure in TomcatSessionBackwardsCompatibilityTomcat7079WithOldModulesMixedWithCurrentCanDoPutFromCurrentModuleTest
[
https://issues.apache.org/jira/browse/GEODE-9737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wayne updated GEODE-9737:
-
Labels: blocks-1.15.0 release-blocker (was: release-blocker)
> CI failure in
> TomcatSessionBackwardsCompatibilityTomcat7079WithOldModulesMixedWithCurrentCanDoPutFromCurrentModuleTest
> --
>
> Key: GEODE-9737
> URL: https://issues.apache.org/jira/browse/GEODE-9737
> Project: Geode
> Issue Type: Bug
> Components: http session
>Affects Versions: 1.15.0
>Reporter: Kamilla Aslami
>Assignee: Benjamin P Ross
>Priority: Major
> Labels: blocks-1.15.0, release-blocker
> Attachments: gemfire.log
>
>
> {noformat}
> TomcatSessionBackwardsCompatibilityTomcat7079WithOldModulesMixedWithCurrentCanDoPutFromCurrentModuleTest
> > test[0] FAILED
> java.lang.RuntimeException: Something very bad happened when trying to
> start container
> TOMCAT7_client-server_test0_1_dd13a1a6-effb-4430-8ccd-ee6c9142938c_
> at
> org.apache.geode.session.tests.ContainerManager.startContainer(ContainerManager.java:82)
> at
> org.apache.geode.session.tests.ContainerManager.startContainers(ContainerManager.java:93)
> at
> org.apache.geode.session.tests.ContainerManager.startAllInactiveContainers(ContainerManager.java:101)
> at
> org.apache.geode.session.tests.TomcatSessionBackwardsCompatibilityTestBase.doPutAndGetSessionOnAllClients(TomcatSessionBackwardsCompatibilityTestBase.java:187)
> at
> org.apache.geode.session.tests.TomcatSessionBackwardsCompatibilityTomcat7079WithOldModulesMixedWithCurrentCanDoPutFromCurrentModuleTest.test(TomcatSessionBackwardsCompatibilityTomcat7079WithOldModulesMixedWithCurrentCanDoPutFromCurrentModuleTest.java:36)
> Caused by:
> java.lang.RuntimeException: Something very bad happened to this
> container when starting. Check the cargo_logs folder for container logs.
> at
> org.apache.geode.session.tests.ServerContainer.start(ServerContainer.java:220)
> at
> org.apache.geode.session.tests.ContainerManager.startContainer(ContainerManager.java:79)
> ... 4 more
> Caused by:
> org.codehaus.cargo.container.ContainerException: Deployable
> [http://localhost:26322/cargocpc/index.html] failed to finish deploying
> within the timeout period [12]. The Deployable state is thus unknown.
> at
> org.codehaus.cargo.container.spi.deployer.DeployerWatchdog.watch(DeployerWatchdog.java:111)
> at
> org.codehaus.cargo.container.spi.AbstractLocalContainer.waitForCompletion(AbstractLocalContainer.java:387)
> at
> org.codehaus.cargo.container.spi.AbstractLocalContainer.start(AbstractLocalContainer.java:234)
> at
> org.apache.geode.session.tests.ServerContainer.start(ServerContainer.java:218)
> ... 5 more
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Closed] (GEODE-9963) Test
[ https://issues.apache.org/jira/browse/GEODE-9963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wayne closed GEODE-9963. This ticket was created as an experiment for attempting to diagnose Bala's Jira permission issues. > Test > > > Key: GEODE-9963 > URL: https://issues.apache.org/jira/browse/GEODE-9963 > Project: Geode > Issue Type: Bug >Reporter: Bala Tripura Sundari Kaza Venkata >Priority: Major > Labels: needsTriage > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-9962) SPIKE: Redis INFO Command Support for Cluster Mode
[ https://issues.apache.org/jira/browse/GEODE-9962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wayne updated GEODE-9962: - Labels: blocks-1.15.0 (was: ) > SPIKE: Redis INFO Command Support for Cluster Mode > -- > > Key: GEODE-9962 > URL: https://issues.apache.org/jira/browse/GEODE-9962 > Project: Geode > Issue Type: Task > Components: redis >Affects Versions: 1.15.0 >Reporter: Wayne >Priority: Major > Labels: blocks-1.15.0 > > The Redis INFO command does not show correct information for cluster mode. > > Research what changes must occur to support the correct information for > cluster mode and ensure tickets are created for tracking. > > +Acceptance Criteria+ > > Gaps in cluster mode supported are identified and tickets are created for > tracking. > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-9962) SPIKE: Redis INFO Command Support for Cluster Mode
Wayne created GEODE-9962: Summary: SPIKE: Redis INFO Command Support for Cluster Mode Key: GEODE-9962 URL: https://issues.apache.org/jira/browse/GEODE-9962 Project: Geode Issue Type: Task Components: redis Affects Versions: 1.15.0 Reporter: Wayne The Redis INFO command does not show correct information for cluster mode. Research what changes must occur to support the correct information for cluster mode and ensure tickets are created for tracking. +Acceptance Criteria+ Gaps in cluster mode supported are identified and tickets are created for tracking. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-9955) Implement RPUSHX
Wayne created GEODE-9955: Summary: Implement RPUSHX Key: GEODE-9955 URL: https://issues.apache.org/jira/browse/GEODE-9955 Project: Geode Issue Type: New Feature Components: redis Reporter: Wayne Implement the [RPUSHX|https://redis.io/commands/rpushx] 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] [Created] (GEODE-9954) Implement RPUSH
Wayne created GEODE-9954: Summary: Implement RPUSH Key: GEODE-9954 URL: https://issues.apache.org/jira/browse/GEODE-9954 Project: Geode Issue Type: New Feature Components: redis Reporter: Wayne Implement the [RPUSH|https://redis.io/commands/rpush] 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] [Created] (GEODE-9953) Implement LTRIM
Wayne created GEODE-9953: Summary: Implement LTRIM Key: GEODE-9953 URL: https://issues.apache.org/jira/browse/GEODE-9953 Project: Geode Issue Type: New Feature Components: redis Reporter: Wayne Implement the [LTRIM|https://redis.io/commands/ltrim] 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] [Created] (GEODE-9952) Implement LSET
Wayne created GEODE-9952: Summary: Implement LSET Key: GEODE-9952 URL: https://issues.apache.org/jira/browse/GEODE-9952 Project: Geode Issue Type: New Feature Components: redis Reporter: Wayne Implement the [LSET|https://redis.io/commands/lset] 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] [Created] (GEODE-9951) Implement RPOP
Wayne created GEODE-9951: Summary: Implement RPOP Key: GEODE-9951 URL: https://issues.apache.org/jira/browse/GEODE-9951 Project: Geode Issue Type: New Feature Components: redis Reporter: Wayne Implement the [RPOP|https://redis.io/commands/rpop] 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] [Created] (GEODE-9950) Implement LRANGE
Wayne created GEODE-9950: Summary: Implement LRANGE Key: GEODE-9950 URL: https://issues.apache.org/jira/browse/GEODE-9950 Project: Geode Issue Type: New Feature Components: redis Reporter: Wayne Implement the LRANGE 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] [Created] (GEODE-9949) Implement LPUSHX
Wayne created GEODE-9949: Summary: Implement LPUSHX Key: GEODE-9949 URL: https://issues.apache.org/jira/browse/GEODE-9949 Project: Geode Issue Type: New Feature Components: redis Reporter: Wayne Implement the [LPUSHX|https://redis.io/commands/lpushx] 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] [Created] (GEODE-9948) Implement LINSERT
Wayne created GEODE-9948: Summary: Implement LINSERT Key: GEODE-9948 URL: https://issues.apache.org/jira/browse/GEODE-9948 Project: Geode Issue Type: New Feature Components: redis Reporter: Wayne Implement the [LINSERT|http://https//redis.io/commands/linsert] 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] [Created] (GEODE-9947) Implement LINDEX
Wayne created GEODE-9947: Summary: Implement LINDEX Key: GEODE-9947 URL: https://issues.apache.org/jira/browse/GEODE-9947 Project: Geode Issue Type: New Feature Components: redis Reporter: Wayne Implement the [LINDEX|https://redis.io/commands/lindex] 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] [Created] (GEODE-9946) Implement LREM Command
Wayne created GEODE-9946: Summary: Implement LREM Command Key: GEODE-9946 URL: https://issues.apache.org/jira/browse/GEODE-9946 Project: Geode Issue Type: New Feature Components: redis Reporter: Wayne Implement the [LREM|https://redis.io/commands/lrem] 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] [Created] (GEODE-9945) Override Equality Checking for Redis Lists
Wayne created GEODE-9945: Summary: Override Equality Checking for Redis Lists Key: GEODE-9945 URL: https://issues.apache.org/jira/browse/GEODE-9945 Project: Geode Issue Type: New Feature Components: redis Reporter: Wayne Override methods in LinkedList that perform equality checking to account for our usage of byte[] content. +Acceptance Criteria+ At a minimum, the remove and indexof methods are overridden. Appropriate unit testing is added. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-9938) Optimize SRANDMEMBER
Wayne created GEODE-9938: Summary: Optimize SRANDMEMBER Key: GEODE-9938 URL: https://issues.apache.org/jira/browse/GEODE-9938 Project: Geode Issue Type: New Feature Components: redis Reporter: Wayne The SRANDMEMBER Command may require later optimization to minimally copy the target members to the result set. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9885) StringsDUnitTest.givenBucketsMoveDuringAppend_thenDataIsNotLost fails with duplicated append
[
https://issues.apache.org/jira/browse/GEODE-9885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17470083#comment-17470083
]
Wayne commented on GEODE-9885:
--
We have not yet determined if this is a product or test issue.
> StringsDUnitTest.givenBucketsMoveDuringAppend_thenDataIsNotLost fails with
> duplicated append
>
>
> Key: GEODE-9885
> URL: https://issues.apache.org/jira/browse/GEODE-9885
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Ray Ingles
>Priority: Major
> Labels: needsTriage
>
> The test appends a lot of strings to a key. It wound up adding (at least one)
> extra string to the stored string:
>
> {{java.util.concurrent.ExecutionException: java.lang.AssertionError:
> unexpected -\{append0}-key-3-27680- at index 27681 iterationCount=61995 in
> string}}
>
> The string "\{append0}-key-3-27680-" appeared twice in sequence.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-9885) StringsDUnitTest.givenBucketsMoveDuringAppend_thenDataIsNotLost fails with duplicated append
[
https://issues.apache.org/jira/browse/GEODE-9885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wayne updated GEODE-9885:
-
Labels: needsTriage (was: blocks-1.15.0)
> StringsDUnitTest.givenBucketsMoveDuringAppend_thenDataIsNotLost fails with
> duplicated append
>
>
> Key: GEODE-9885
> URL: https://issues.apache.org/jira/browse/GEODE-9885
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Ray Ingles
>Priority: Major
> Labels: needsTriage
>
> The test appends a lot of strings to a key. It wound up adding (at least one)
> extra string to the stored string:
>
> {{java.util.concurrent.ExecutionException: java.lang.AssertionError:
> unexpected -\{append0}-key-3-27680- at index 27681 iterationCount=61995 in
> string}}
>
> The string "\{append0}-key-3-27680-" appeared twice in sequence.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-9885) StringsDUnitTest.givenBucketsMoveDuringAppend_thenDataIsNotLost fails with duplicated append
[
https://issues.apache.org/jira/browse/GEODE-9885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wayne updated GEODE-9885:
-
Labels: blocks-1.15.0 (was: blocks-1.15.0 needsTriage)
> StringsDUnitTest.givenBucketsMoveDuringAppend_thenDataIsNotLost fails with
> duplicated append
>
>
> Key: GEODE-9885
> URL: https://issues.apache.org/jira/browse/GEODE-9885
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Ray Ingles
>Priority: Major
> Labels: blocks-1.15.0
>
> The test appends a lot of strings to a key. It wound up adding (at least one)
> extra string to the stored string:
>
> {{java.util.concurrent.ExecutionException: java.lang.AssertionError:
> unexpected -\{append0}-key-3-27680- at index 27681 iterationCount=61995 in
> string}}
>
> The string "\{append0}-key-3-27680-" appeared twice in sequence.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (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:all-tabpanel
]
Wayne updated GEODE-9907:
-
Labels: release-blocker (was: needsTriage)
> 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: Donal Evans
>Priority: Major
> Labels: release-blocker
>
>
> {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-9860) NativeRedisRenameRedirectionsDUnitTest. initializationError
[
https://issues.apache.org/jira/browse/GEODE-9860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wayne updated GEODE-9860:
-
Labels: needsTriage (was: )
> NativeRedisRenameRedirectionsDUnitTest. initializationError
> ---
>
> Key: GEODE-9860
> URL: https://issues.apache.org/jira/browse/GEODE-9860
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Mark Hanson
>Priority: Major
> Labels: needsTriage
>
> {noformat}
> NativeRedisRenameRedirectionsDUnitTest > initializationError FAILED
> java.lang.RuntimeException: java.lang.NullPointerException
> at org.rnorth.ducttape.timeouts.Timeouts.callFuture(Timeouts.java:68)
> at
> org.rnorth.ducttape.timeouts.Timeouts.doWithTimeout(Timeouts.java:60)
> at
> org.testcontainers.containers.wait.strategy.WaitAllStrategy.waitUntilReady(WaitAllStrategy.java:53)
> at
> org.testcontainers.containers.DockerComposeContainer.waitUntilServiceStarted(DockerComposeContainer.java:285)
> at
> java.util.concurrent.ConcurrentHashMap.forEach(ConcurrentHashMap.java:1597)
> at
> org.testcontainers.containers.DockerComposeContainer.waitUntilServiceStarted(DockerComposeContainer.java:265)
> at
> org.testcontainers.containers.DockerComposeContainer.start(DockerComposeContainer.java:179)
> at
> org.apache.geode.redis.NativeRedisClusterTestRule$1.evaluate(NativeRedisClusterTestRule.java:84)
> at
> org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:54)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:115)
> at
> org.junit.vintage.engine.execution.RunnerExecutor.execute(RunnerExecutor.java:43)
> at
> java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:183)
> at
> java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193)
> at java.util.Iterator.forEachRemaining(Iterator.java:116)
> at
> java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1801)
> at
> java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:482)
> at
> java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:472)
> at
> java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:150)
> at
> java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:173)
> at
> java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> at
> java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:485)
> at
> org.junit.vintage.engine.VintageTestEngine.executeAllChildren(VintageTestEngine.java:82)
> at
> org.junit.vintage.engine.VintageTestEngine.execute(VintageTestEngine.java:73)
> at
> org.junit.platform.launcher.core.EngineExecutionOrchestrator.execute(EngineExecutionOrchestrator.java:108)
> at
> org.junit.platform.launcher.core.EngineExecutionOrchestrator.execute(EngineExecutionOrchestrator.java:88)
> at
> org.junit.platform.launcher.core.EngineExecutionOrchestrator.lambda$execute$0(EngineExecutionOrchestrator.java:54)
> at
> org.junit.platform.launcher.core.EngineExecutionOrchestrator.withInterceptedStreams(EngineExecutionOrchestrator.java:67)
> at
> org.junit.platform.launcher.core.EngineExecutionOrchestrator.execute(EngineExecutionOrchestrator.java:52)
> at
> org.junit.platform.launcher.core.DefaultLauncher.execute(DefaultLauncher.java:96)
> at
> org.junit.platform.launcher.core.DefaultLauncher.execute(DefaultLauncher.java:75)
> at
> org.gradle.api.internal.tasks.testing.junitplatform.JUnitPlatformTestClassProcessor$CollectAllTestClassesExecutor.processAllTestClasses(JUnitPlatformTestClassProcessor.java:99)
> at
> org.gradle.api.internal.tasks.testing.junitplatform.JUnitPlatformTestClassProcessor$CollectAllTestClassesExecutor.access$000(JUnitPlatformTestClassProcessor.java:79)
> at
> org.gradle.api.internal.tasks.testing.junitplatform.JUnitPlatformTestClassProcessor.stop(JUnitPlatformTestClassProcessor.java:75)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.stop(SuiteTestClassProcessor.java:61)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
>
[jira] [Updated] (GEODE-9845) CI failure: Multiple tests in OutOfMemoryDUnitTest failed with ConnectException
[
https://issues.apache.org/jira/browse/GEODE-9845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wayne updated GEODE-9845:
-
Labels: needsTriage (was: )
> CI failure: Multiple tests in OutOfMemoryDUnitTest failed with
> ConnectException
> ---
>
> Key: GEODE-9845
> URL: https://issues.apache.org/jira/browse/GEODE-9845
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Kamilla Aslami
>Priority: Major
> Labels: needsTriage
>
> 4 tests in OutOfMemoryDUnitTest failed with `java.net.ConnectException:
> Connection refused`.
> {noformat}
> OutOfMemoryDUnitTest > shouldAllowDeleteOperations_afterThresholdReached
> FAILED
> java.lang.AssertionError:
> Expecting throwable message:
> "No more cluster attempts left."
> to contain:
> "OOM command not allowed"
> but did not.
> Throwable that failed the check:
> redis.clients.jedis.exceptions.JedisClusterMaxAttemptsException: No more
> cluster attempts left.
> at
> redis.clients.jedis.JedisClusterCommand.runWithRetries(JedisClusterCommand.java:156)
> at
> redis.clients.jedis.JedisClusterCommand.run(JedisClusterCommand.java:45)
> at redis.clients.jedis.JedisCluster.set(JedisCluster.java:293)
> at
> org.apache.geode.redis.OutOfMemoryDUnitTest.setRedisKeyAndValue(OutOfMemoryDUnitTest.java:228)
> at
> org.apache.geode.redis.OutOfMemoryDUnitTest.lambda$addMultipleKeys$5(OutOfMemoryDUnitTest.java:212)
> at
> org.assertj.core.api.ThrowableAssert.catchThrowable(ThrowableAssert.java:62)
> at
> org.assertj.core.api.AssertionsForClassTypes.catchThrowable(AssertionsForClassTypes.java:877)
> at
> org.apache.geode.redis.OutOfMemoryDUnitTest.addMultipleKeys(OutOfMemoryDUnitTest.java:210)
> at
> org.apache.geode.redis.OutOfMemoryDUnitTest.fillMemory(OutOfMemoryDUnitTest.java:201)
> at
> org.apache.geode.redis.OutOfMemoryDUnitTest.shouldAllowDeleteOperations_afterThresholdReached(OutOfMemoryDUnitTest.java:166)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.apache.geode.test.junit.rules.serializable.SerializableExternalResource$1.evaluate(SerializableExternalResource.java:38)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at
> org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
> at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
> at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule$1.evaluate(ClusterStartupRule.java:138)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:115)
> at
> org.junit.vintage.engine.execution.RunnerExecutor.execute(RunnerExecutor.java:43)
> at
> java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:183)
> at
> java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193)
> at java.util.Iterator.forEachRemaining(Iterator.java:116)
> at
>
[jira] [Updated] (GEODE-9904) RedisSet spop and srandmember should not copy entire MemberSet
[ https://issues.apache.org/jira/browse/GEODE-9904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wayne updated GEODE-9904: - Labels: release-blocker (was: ) > RedisSet spop and srandmember should not copy entire MemberSet > -- > > Key: GEODE-9904 > URL: https://issues.apache.org/jira/browse/GEODE-9904 > Project: Geode > Issue Type: Improvement > Components: redis >Affects Versions: 1.15.0 >Reporter: Darrel Schneider >Priority: Major > Labels: release-blocker > > 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] [Updated] (GEODE-9904) RedisSet spop and srandmember should not copy entire MemberSet
[ https://issues.apache.org/jira/browse/GEODE-9904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wayne updated GEODE-9904: - Affects Version/s: 1.15.0 > RedisSet spop and srandmember should not copy entire MemberSet > -- > > Key: GEODE-9904 > URL: https://issues.apache.org/jira/browse/GEODE-9904 > Project: Geode > Issue Type: Improvement > Components: redis >Affects Versions: 1.15.0 >Reporter: Darrel Schneider >Priority: Major > > 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] [Updated] (GEODE-9902) Modify ZUnionStore and ZInterStore storing methods
[ https://issues.apache.org/jira/browse/GEODE-9902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wayne updated GEODE-9902: - Description: Modify the way Redis SortedSets store the members for the ZUnionStore and ZInterStore. It should follow what Redis Sets are doing for SUnionStore and SInterStore. This is specifically related to the use of DeltaInfos. (was: Modify the way Redis SortedSets store the members for the ZUnionStore and ZInterStore. It should follow what Redis Sets are doing for SUnionStore and SInterStore.) > Modify ZUnionStore and ZInterStore storing methods > -- > > Key: GEODE-9902 > URL: https://issues.apache.org/jira/browse/GEODE-9902 > Project: Geode > Issue Type: Improvement > Components: redis >Affects Versions: 1.15.0 >Reporter: Kristen >Priority: Major > > Modify the way Redis SortedSets store the members for the ZUnionStore and > ZInterStore. It should follow what Redis Sets are doing for SUnionStore and > SInterStore. This is specifically related to the use of DeltaInfos. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-9902) Modify ZUnionStore and ZInterStore storing methods
[ https://issues.apache.org/jira/browse/GEODE-9902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wayne updated GEODE-9902: - Labels: release-blocker (was: ) > Modify ZUnionStore and ZInterStore storing methods > -- > > Key: GEODE-9902 > URL: https://issues.apache.org/jira/browse/GEODE-9902 > Project: Geode > Issue Type: Improvement > Components: redis >Affects Versions: 1.15.0 >Reporter: Kristen >Priority: Major > Labels: release-blocker > > Modify the way Redis SortedSets store the members for the ZUnionStore and > ZInterStore. It should follow what Redis Sets are doing for SUnionStore and > SInterStore. This is specifically related to the use of DeltaInfos. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-9885) StringsDUnitTest.givenBucketsMoveDuringAppend_thenDataIsNotLost fails with duplicated append
[
https://issues.apache.org/jira/browse/GEODE-9885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wayne updated GEODE-9885:
-
Labels: needsTriage (was: )
> StringsDUnitTest.givenBucketsMoveDuringAppend_thenDataIsNotLost fails with
> duplicated append
>
>
> Key: GEODE-9885
> URL: https://issues.apache.org/jira/browse/GEODE-9885
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Ray Ingles
>Priority: Major
> Labels: needsTriage
>
> The test appends a lot of strings to a key. It wound up adding (at least one)
> extra string to the stored string:
>
> {{java.util.concurrent.ExecutionException: java.lang.AssertionError:
> unexpected -\{append0}-key-3-27680- at index 27681 iterationCount=61995 in
> string}}
>
> The string "\{append0}-key-3-27680-" appeared twice in sequence.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-9899) Fix concurrency issue in RedisSet during GII
[
https://issues.apache.org/jira/browse/GEODE-9899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wayne updated GEODE-9899:
-
Labels: needsTriage (was: )
> Fix concurrency issue in RedisSet during GII
>
>
> Key: GEODE-9899
> URL: https://issues.apache.org/jira/browse/GEODE-9899
> Project: Geode
> Issue Type: Bug
> Components: redis
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
> Labels: needsTriage
>
> For the most part, access to Radish structures is performed through redis
> commands and thus concurrent access is protected through the
> {{{}StripedCoordinator{}}}. However access outside this protection can occur
> directly through Geode internal flows. In particular, a GII process will
> access the data structures via the {{toData}} and {{fromData}} calls.
> Exceptions can occur if the structure is being modified and, at the same time
> being read. For Example:
> {noformat}
> java.util.concurrent.ExecutionException: java.lang.NullPointerException at
> java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:192)
> at
> org.apache.geode.redis.internal.data.RedisSetTest.testConcurrency(RedisSetTest.java:350)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at
> org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
> at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
> at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
> at
> org.apache.geode.test.junit.rules.serializable.SerializableExternalResource$1.evaluate(SerializableExternalResource.java:38)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
> at
> com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:69)
> at
> com.intellij.rt.junit.IdeaTestRunner$Repeater$1.execute(IdeaTestRunner.java:38)
> at
> com.intellij.rt.execution.junit.TestsRepeater.repeat(TestsRepeater.java:30)
> at
> com.intellij.rt.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:35)
> at
> com.intellij.rt.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:235)
> at com.intellij.rt.junit.JUnitStarter.main(JUnitStarter.java:54)
> Caused by: java.lang.NullPointerException
> at
> it.unimi.dsi.fastutil.objects.ObjectOpenCustomHashSet$SetIterator.next(ObjectOpenCustomHashSet.java:422)
> at org.apache.geode.redis.internal.data.RedisSet.toData(RedisSet.java:211)
> at
> org.apache.geode.redis.internal.data.RedisSetTest.iterateOverSet(RedisSetTest.java:368)
> at
> org.apache.geode.redis.internal.data.RedisSetTest.lambda$testConcurrency$0(RedisSetTest.java:346)
> at
> org.apache.geode.test.junit.rules.ExecutorServiceRule.lambda$submit$2(ExecutorServiceRule.java:263)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748) {noformat}
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (GEODE-9892) Create Infrastructure for Redis Lists
Wayne created GEODE-9892: Summary: Create Infrastructure for Redis Lists Key: GEODE-9892 URL: https://issues.apache.org/jira/browse/GEODE-9892 Project: Geode Issue Type: New Feature Components: redis Reporter: Wayne Create the infrastructure for supporting Redis Lists including: * Use of the appropriate underlying Java collection * Implementing the [LPUSH|https://redis.io/commands/lpush] Command * Implementing the [LRANGE|https://redis.io/commands/lrange] command +Acceptance Critera+ The LPUSH and LRANGE commands have been implemented with appropriate unit testing. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-9883) Review and Cleanup geode_for_redis.html.md.erb
[ https://issues.apache.org/jira/browse/GEODE-9883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wayne updated GEODE-9883: - Labels: release-blocker (was: ) > Review and Cleanup geode_for_redis.html.md.erb > -- > > Key: GEODE-9883 > URL: https://issues.apache.org/jira/browse/GEODE-9883 > Project: Geode > Issue Type: Task > Components: redis >Affects Versions: 1.15.0 >Reporter: Wayne >Priority: Major > Labels: release-blocker > > Looking at what we have in the geode docs, a few things that are out of date. > * This page still references the geode-for-redis-password, which doesn't > exist any more. It should probably talk about how redis interacts with the > security manager. > * Probably should mention how to configure TLS properties for > geode-for-redis. > * The redis-cli command I think is missing a -c option to use cluster mode. > * The supported redis commands listed in that page is incomplete > * Advantages section doesn't mention synchronous replication -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-9883) Review and Cleanup geode_for_redis.html.md.erb
[ https://issues.apache.org/jira/browse/GEODE-9883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wayne updated GEODE-9883: - Affects Version/s: 1.15.0 > Review and Cleanup geode_for_redis.html.md.erb > -- > > Key: GEODE-9883 > URL: https://issues.apache.org/jira/browse/GEODE-9883 > Project: Geode > Issue Type: Task > Components: redis >Affects Versions: 1.15.0 >Reporter: Wayne >Priority: Major > > Looking at what we have in the geode docs, a few things that are out of date. > * This page still references the geode-for-redis-password, which doesn't > exist any more. It should probably talk about how redis interacts with the > security manager. > * Probably should mention how to configure TLS properties for > geode-for-redis. > * The redis-cli command I think is missing a -c option to use cluster mode. > * The supported redis commands listed in that page is incomplete > * Advantages section doesn't mention synchronous replication -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-9883) Review and Cleanup geode_for_redis.html.md.erb
Wayne created GEODE-9883: Summary: Review and Cleanup geode_for_redis.html.md.erb Key: GEODE-9883 URL: https://issues.apache.org/jira/browse/GEODE-9883 Project: Geode Issue Type: Task Components: redis Reporter: Wayne Looking at what we have in the geode docs, a few things that are out of date. * This page still references the geode-for-redis-password, which doesn't exist any more. It should probably talk about how redis interacts with the security manager. * Probably should mention how to configure TLS properties for geode-for-redis. * The redis-cli command I think is missing a -c option to use cluster mode. * The supported redis commands listed in that page is incomplete * Advantages section doesn't mention synchronous replication -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-9772) RedisString should consistently use a DeltaInfo for all write ops that update a RedisString
[ https://issues.apache.org/jira/browse/GEODE-9772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wayne updated GEODE-9772: - Labels: pull-request-available release-blocker (was: pull-request-available) > RedisString should consistently use a DeltaInfo for all write ops that update > a RedisString > --- > > Key: GEODE-9772 > URL: https://issues.apache.org/jira/browse/GEODE-9772 > Project: Geode > Issue Type: Improvement > Components: redis >Affects Versions: 1.15.0 >Reporter: Darrel Schneider >Assignee: Darrel Schneider >Priority: Major > Labels: pull-request-available, release-blocker > > Currently RedisString generates a DeltaInfo instance when it does an "append" > to an existing RedisString. But for all the other write ops on RedisString > the implementation does not generate a DeltaInfo instance. This causes the > entire RedisString instance to be serialized to the secondary. But the ops > that do this tend to change the entire string (for example "set" get rid of > the old value of the string and adds a brand new value). But even for these > types of ops being consistent about generating a DeltaInfo has the following > benefits: > 1. the memory usage on the region will be consistent between the primary and > secondary because the value will be stored in the same form on both of them. > Understand that for value classes that implement the Delta interface (which > all RedisData classes do) the primary will always store the value in > deserialized form. But it gets stored on the secondary in serialized from > until a value arrives on the secondary that is just the delta bytes. By > generating a DeltaInfo instance the secondary will receive data bytes. > 2. By keeping the values stored in the region in object form it causes > updates to not produce "old garbage". What happens when a DeltaInfo is sent > is that it modifies in place an object that is already in the JVM heap > memory. But without a DeltaInfo a whole new value is created and the old > value becomes garbage. That old value may have already been promoted to the > older generation and now the JVM may have to do more work to get it garbage > collected. It is best if object die young (sad but true). > RedisString has a number of ops that do not use generate a DeltaInfo. But > they could easily be changed to just generate a DeltaInfo that contains a > byte array that is the new value of the RedisString. This would even work for > "setrange" and "setbit" but those could be further optimized to only add a > subset of the bytes to the DeltaInfo along with an index. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-9737) CI failure in TomcatSessionBackwardsCompatibilityTomcat7079WithOldModulesMixedWithCurrentCanDoPutFromCurrentModuleTest
[
https://issues.apache.org/jira/browse/GEODE-9737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wayne updated GEODE-9737:
-
Labels: release-blocker (was: )
> CI failure in
> TomcatSessionBackwardsCompatibilityTomcat7079WithOldModulesMixedWithCurrentCanDoPutFromCurrentModuleTest
> --
>
> Key: GEODE-9737
> URL: https://issues.apache.org/jira/browse/GEODE-9737
> Project: Geode
> Issue Type: Bug
> Components: http session
>Affects Versions: 1.15.0
>Reporter: Kamilla Aslami
>Assignee: Benjamin P Ross
>Priority: Major
> Labels: release-blocker
> Attachments: gemfire.log
>
>
> {noformat}
> TomcatSessionBackwardsCompatibilityTomcat7079WithOldModulesMixedWithCurrentCanDoPutFromCurrentModuleTest
> > test[0] FAILED
> java.lang.RuntimeException: Something very bad happened when trying to
> start container
> TOMCAT7_client-server_test0_1_dd13a1a6-effb-4430-8ccd-ee6c9142938c_
> at
> org.apache.geode.session.tests.ContainerManager.startContainer(ContainerManager.java:82)
> at
> org.apache.geode.session.tests.ContainerManager.startContainers(ContainerManager.java:93)
> at
> org.apache.geode.session.tests.ContainerManager.startAllInactiveContainers(ContainerManager.java:101)
> at
> org.apache.geode.session.tests.TomcatSessionBackwardsCompatibilityTestBase.doPutAndGetSessionOnAllClients(TomcatSessionBackwardsCompatibilityTestBase.java:187)
> at
> org.apache.geode.session.tests.TomcatSessionBackwardsCompatibilityTomcat7079WithOldModulesMixedWithCurrentCanDoPutFromCurrentModuleTest.test(TomcatSessionBackwardsCompatibilityTomcat7079WithOldModulesMixedWithCurrentCanDoPutFromCurrentModuleTest.java:36)
> Caused by:
> java.lang.RuntimeException: Something very bad happened to this
> container when starting. Check the cargo_logs folder for container logs.
> at
> org.apache.geode.session.tests.ServerContainer.start(ServerContainer.java:220)
> at
> org.apache.geode.session.tests.ContainerManager.startContainer(ContainerManager.java:79)
> ... 4 more
> Caused by:
> org.codehaus.cargo.container.ContainerException: Deployable
> [http://localhost:26322/cargocpc/index.html] failed to finish deploying
> within the timeout period [12]. The Deployable state is thus unknown.
> at
> org.codehaus.cargo.container.spi.deployer.DeployerWatchdog.watch(DeployerWatchdog.java:111)
> at
> org.codehaus.cargo.container.spi.AbstractLocalContainer.waitForCompletion(AbstractLocalContainer.java:387)
> at
> org.codehaus.cargo.container.spi.AbstractLocalContainer.start(AbstractLocalContainer.java:234)
> at
> org.apache.geode.session.tests.ServerContainer.start(ServerContainer.java:218)
> ... 5 more
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (GEODE-9840) Improve Redundancy Level Log Message
Wayne created GEODE-9840: Summary: Improve Redundancy Level Log Message Key: GEODE-9840 URL: https://issues.apache.org/jira/browse/GEODE-9840 Project: Geode Issue Type: New Feature Components: redis Reporter: Wayne The current log message Configured redundancy of 2 copies has been restored to /GEODE_FOR_REDIS is confusing and not intuitive. This message should be changed to the following: "Configured redundancy of 2 copies has been restored to /region (1 primary and 1 secondary copies)"? -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-9839) Ability to Set Log Level for Specific Package
[ https://issues.apache.org/jira/browse/GEODE-9839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wayne updated GEODE-9839: - Summary: Ability to Set Log Level for Specific Package (was: Ability to Set Log Live for Specific Package) > Ability to Set Log Level for Specific Package > - > > Key: GEODE-9839 > URL: https://issues.apache.org/jira/browse/GEODE-9839 > Project: Geode > Issue Type: New Feature > Components: redis >Affects Versions: 1.15.0 >Reporter: Wayne >Priority: Major > > As a user of Geode, I would like the ability to use the alter runtime > --log-level command to set the logging level for a specific package. This > would allow me to turn on debug level logging for just the redis packages, > org.apache.geode.redis. > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-9839) Ability to Set Log Live for Specific Package
Wayne created GEODE-9839: Summary: Ability to Set Log Live for Specific Package Key: GEODE-9839 URL: https://issues.apache.org/jira/browse/GEODE-9839 Project: Geode Issue Type: New Feature Components: redis Affects Versions: 1.15.0 Reporter: Wayne As a user of Geode, I would like the ability to use the alter runtime --log-level command to set the logging level for a specific package. This would allow me to turn on debug level logging for just the redis packages, org.apache.geode.redis. -- 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 ] Wayne updated GEODE-9830: - Summary: SINTERSTORE Command Supported (was: SINTERSTORECOMMAND Supported) > SINTERSTORE Command Supported > - > > Key: GEODE-9830 > URL: https://issues.apache.org/jira/browse/GEODE-9830 > Project: Geode > Issue Type: Improvement > Components: redis >Reporter: Wayne >Priority: Major > > 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] [Created] (GEODE-9837) SUNIONSTORE Command Supported
Wayne created GEODE-9837: Summary: SUNIONSTORE Command Supported Key: GEODE-9837 URL: https://issues.apache.org/jira/browse/GEODE-9837 Project: Geode Issue Type: Improvement Components: redis Reporter: Wayne The SUNIONSTORE 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] [Created] (GEODE-9836) SUNION Command Supported
Wayne created GEODE-9836: Summary: SUNION Command Supported Key: GEODE-9836 URL: https://issues.apache.org/jira/browse/GEODE-9836 Project: Geode Issue Type: Improvement Components: redis Reporter: Wayne The SUNION 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] [Created] (GEODE-9835) SSCAN Command Supported
Wayne created GEODE-9835: Summary: SSCAN Command Supported Key: GEODE-9835 URL: https://issues.apache.org/jira/browse/GEODE-9835 Project: Geode Issue Type: Improvement Components: redis Reporter: Wayne The SSCAN 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] [Created] (GEODE-9834) SRANDMEMBER Command Supported
Wayne created GEODE-9834: Summary: SRANDMEMBER Command Supported Key: GEODE-9834 URL: https://issues.apache.org/jira/browse/GEODE-9834 Project: Geode Issue Type: Improvement Components: redis Reporter: Wayne The SRANDMEMBER 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] [Created] (GEODE-9833) SPOP Command Supported
Wayne created GEODE-9833: Summary: SPOP Command Supported Key: GEODE-9833 URL: https://issues.apache.org/jira/browse/GEODE-9833 Project: Geode Issue Type: Improvement Components: redis Reporter: Wayne 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. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-9832) SMOVE Command Supported
Wayne created GEODE-9832: Summary: SMOVE Command Supported Key: GEODE-9832 URL: https://issues.apache.org/jira/browse/GEODE-9832 Project: Geode Issue Type: Improvement Components: redis Reporter: Wayne The SMOVE 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] [Created] (GEODE-9831) SISMEMBER Command Supported
Wayne created GEODE-9831: Summary: SISMEMBER Command Supported Key: GEODE-9831 URL: https://issues.apache.org/jira/browse/GEODE-9831 Project: Geode Issue Type: Improvement Components: redis Reporter: Wayne The SISMEMBER 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] [Created] (GEODE-9830) SINTERSTORECOMMAND Supported
Wayne created GEODE-9830: Summary: SINTERSTORECOMMAND Supported Key: GEODE-9830 URL: https://issues.apache.org/jira/browse/GEODE-9830 Project: Geode Issue Type: Improvement Components: redis Reporter: Wayne 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] [Created] (GEODE-9829) SINTER Command Supported
Wayne created GEODE-9829: Summary: SINTER Command Supported Key: GEODE-9829 URL: https://issues.apache.org/jira/browse/GEODE-9829 Project: Geode Issue Type: Improvement Components: redis Reporter: Wayne The SINTER 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-9827) SDIFF Command Supported
[ https://issues.apache.org/jira/browse/GEODE-9827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wayne updated GEODE-9827: - Issue Type: Improvement (was: Test) > SDIFF Command Supported > --- > > Key: GEODE-9827 > URL: https://issues.apache.org/jira/browse/GEODE-9827 > Project: Geode > Issue Type: Improvement > Components: redis >Reporter: Wayne >Priority: Major > > The SDIFF 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-9826) SCARD Command Supported
[ https://issues.apache.org/jira/browse/GEODE-9826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wayne updated GEODE-9826: - Issue Type: Improvement (was: Test) > SCARD Command Supported > --- > > Key: GEODE-9826 > URL: https://issues.apache.org/jira/browse/GEODE-9826 > Project: Geode > Issue Type: Improvement > Components: redis >Reporter: Wayne >Priority: Major > > The SCARD 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)
