[jira] [Resolved] (GEODE-9006) MemoryStatsNativeRedisAcceptanceTest CI failure
[
https://issues.apache.org/jira/browse/GEODE-9006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Hutchison resolved GEODE-9006.
---
Resolution: Fixed
> MemoryStatsNativeRedisAcceptanceTest CI failure
> ---
>
> Key: GEODE-9006
> URL: https://issues.apache.org/jira/browse/GEODE-9006
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.14.0, 1.15.0
>Reporter: Ray Ingles
>Assignee: John Hutchison
>Priority: Major
> Labels: pull-request-available
>
> CI failure:
> {{org.apache.geode.redis.internal.executor.server.MemoryStatsNativeRedisAcceptanceTest
> > usedMemory_shouldReflectActualMemoryUsage FAILED
> java.lang.AssertionError:
> Expecting:
> 854912L
> to be greater than:
> 855176L}}
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/AcceptanceTestOpenJDK11/builds/51]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-9347) Make Publish and Subscribe use Map data structures
[ https://issues.apache.org/jira/browse/GEODE-9347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Hutchison updated GEODE-9347: -- Labels: (was: redis) > Make Publish and Subscribe use Map data structures > -- > > Key: GEODE-9347 > URL: https://issues.apache.org/jira/browse/GEODE-9347 > Project: Geode > Issue Type: Improvement > Components: redis >Reporter: John Hutchison >Priority: Major > > our current implementation of Publish and Subscribe use a list of > Subscription objects to maintain state. > @doevans noticed that native redis is using 2 maps to maintain state > in an effort to mimic native redis data structures and hopefully improve > performance, our publish and subscribe commands should also use maps 1) > (channel -> all subscribers). 2) subsrciber(client) -> all subscribed channels -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9347) Make Publish and Subscribe use Map data structures
[ https://issues.apache.org/jira/browse/GEODE-9347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Hutchison updated GEODE-9347: -- Component/s: redis > Make Publish and Subscribe use Map data structures > -- > > Key: GEODE-9347 > URL: https://issues.apache.org/jira/browse/GEODE-9347 > Project: Geode > Issue Type: Improvement > Components: redis >Reporter: John Hutchison >Priority: Major > Labels: redis > > our current implementation of Publish and Subscribe use a list of > Subscription objects to maintain state. > @doevans noticed that native redis is using 2 maps to maintain state > in an effort to mimic native redis data structures and hopefully improve > performance, our publish and subscribe commands should also use maps 1) > (channel -> all subscribers). 2) subsrciber(client) -> all subscribed channels -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9347) Make Publish and Subscribe use Map data structures
[ https://issues.apache.org/jira/browse/GEODE-9347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Hutchison updated GEODE-9347: -- Labels: redis (was: Redis) > Make Publish and Subscribe use Map data structures > -- > > Key: GEODE-9347 > URL: https://issues.apache.org/jira/browse/GEODE-9347 > Project: Geode > Issue Type: Improvement >Reporter: John Hutchison >Priority: Major > Labels: redis > > our current implementation of Publish and Subscribe use a list of > Subscription objects to maintain state. > @doevans noticed that native redis is using 2 maps to maintain state > in an effort to mimic native redis data structures and hopefully improve > performance, our publish and subscribe commands should also use maps 1) > (channel -> all subscribers). 2) subsrciber(client) -> all subscribed channels -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9347) Make Publish and Subscribe use Map data structures
[ https://issues.apache.org/jira/browse/GEODE-9347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Hutchison updated GEODE-9347: -- Labels: Redis (was: redis) > Make Publish and Subscribe use Map data structures > -- > > Key: GEODE-9347 > URL: https://issues.apache.org/jira/browse/GEODE-9347 > Project: Geode > Issue Type: Improvement >Reporter: John Hutchison >Priority: Major > Labels: Redis > > our current implementation of Publish and Subscribe use a list of > Subscription objects to maintain state. > @doevans noticed that native redis is using 2 maps to maintain state > in an effort to mimic native redis data structures and hopefully improve > performance, our publish and subscribe commands should also use maps 1) > (channel -> all subscribers). 2) subsrciber(client) -> all subscribed channels -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9347) Make Publish and Subscribe use Map data structures
[ https://issues.apache.org/jira/browse/GEODE-9347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Hutchison updated GEODE-9347: -- Labels: redis (was: ) > Make Publish and Subscribe use Map data structures > -- > > Key: GEODE-9347 > URL: https://issues.apache.org/jira/browse/GEODE-9347 > Project: Geode > Issue Type: Improvement >Reporter: John Hutchison >Priority: Major > Labels: redis > > our current implementation of Publish and Subscribe use a list of > Subscription objects to maintain state. > @doevans noticed that native redis is using 2 maps to maintain state > in an effort to mimic native redis data structures and hopefully improve > performance, our publish and subscribe commands should also use maps 1) > (channel -> all subscribers). 2) subsrciber(client) -> all subscribed channels -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-9347) Make Publish and Subscribe use Map data structures
John Hutchison created GEODE-9347: - Summary: Make Publish and Subscribe use Map data structures Key: GEODE-9347 URL: https://issues.apache.org/jira/browse/GEODE-9347 Project: Geode Issue Type: Improvement Reporter: John Hutchison our current implementation of Publish and Subscribe use a list of Subscription objects to maintain state. @doevans noticed that native redis is using 2 maps to maintain state in an effort to mimic native redis data structures and hopefully improve performance, our publish and subscribe commands should also use maps 1) (channel -> all subscribers). 2) subsrciber(client) -> all subscribed channels -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9006) MemoryStatsNativeRedisAcceptanceTest CI failure
[
https://issues.apache.org/jira/browse/GEODE-9006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17344026#comment-17344026
]
John Hutchison commented on GEODE-9006:
---
blocks-1.14 tag removed.
> MemoryStatsNativeRedisAcceptanceTest CI failure
> ---
>
> Key: GEODE-9006
> URL: https://issues.apache.org/jira/browse/GEODE-9006
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.14.0, 1.15.0
>Reporter: Ray Ingles
>Assignee: John Hutchison
>Priority: Major
> Labels: pull-request-available
>
> CI failure:
> {{org.apache.geode.redis.internal.executor.server.MemoryStatsNativeRedisAcceptanceTest
> > usedMemory_shouldReflectActualMemoryUsage FAILED
> java.lang.AssertionError:
> Expecting:
> 854912L
> to be greater than:
> 855176L}}
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/AcceptanceTestOpenJDK11/builds/51]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-9006) MemoryStatsNativeRedisAcceptanceTest CI failure
[
https://issues.apache.org/jira/browse/GEODE-9006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Hutchison updated GEODE-9006:
--
Labels: pull-request-available (was: blocks-1.14.0 pull-request-available)
> MemoryStatsNativeRedisAcceptanceTest CI failure
> ---
>
> Key: GEODE-9006
> URL: https://issues.apache.org/jira/browse/GEODE-9006
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.14.0, 1.15.0
>Reporter: Ray Ingles
>Assignee: John Hutchison
>Priority: Major
> Labels: pull-request-available
>
> CI failure:
> {{org.apache.geode.redis.internal.executor.server.MemoryStatsNativeRedisAcceptanceTest
> > usedMemory_shouldReflectActualMemoryUsage FAILED
> java.lang.AssertionError:
> Expecting:
> 854912L
> to be greater than:
> 855176L}}
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/AcceptanceTestOpenJDK11/builds/51]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (GEODE-8823) Refactor RedisStats IntegrationTest
[ https://issues.apache.org/jira/browse/GEODE-8823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Hutchison resolved GEODE-8823. --- Resolution: Fixed issue no longer relevant > Refactor RedisStats IntegrationTest > > > Key: GEODE-8823 > URL: https://issues.apache.org/jira/browse/GEODE-8823 > Project: Geode > Issue Type: Improvement > Components: redis >Reporter: John Hutchison >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9006) MemoryStatsNativeRedisAcceptanceTest CI failure
[
https://issues.apache.org/jira/browse/GEODE-9006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Hutchison updated GEODE-9006:
--
Labels: blocks-1.14.0 (was: pull-request-available)
> MemoryStatsNativeRedisAcceptanceTest CI failure
> ---
>
> Key: GEODE-9006
> URL: https://issues.apache.org/jira/browse/GEODE-9006
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.14.0, 1.15.0
>Reporter: Ray Ingles
>Assignee: John Hutchison
>Priority: Major
> Labels: blocks-1.14.0
>
> CI failure:
> {{org.apache.geode.redis.internal.executor.server.MemoryStatsNativeRedisAcceptanceTest
> > usedMemory_shouldReflectActualMemoryUsage FAILED
> java.lang.AssertionError:
> Expecting:
> 854912L
> to be greater than:
> 855176L}}
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/AcceptanceTestOpenJDK11/builds/51]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-9163) Redis: update docs to reflect that the api is experimental
[ https://issues.apache.org/jira/browse/GEODE-9163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Hutchison updated GEODE-9163: -- Fix Version/s: 1.14.0 > Redis: update docs to reflect that the api is experimental > -- > > Key: GEODE-9163 > URL: https://issues.apache.org/jira/browse/GEODE-9163 > Project: Geode > Issue Type: New Feature > Components: docs, redis >Affects Versions: 1.14.0, 1.15.0 >Reporter: Hale Bales >Assignee: John Hutchison >Priority: Major > Labels: blocks-1.14.0, pull-request-available > Fix For: 1.14.0, 1.15.0 > > > update the docs to reflect that the Geode api compatible with Redis is still > experimental. This depends on GEODE-9162 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9163) Redis: update docs to reflect that the api is experimental
[ https://issues.apache.org/jira/browse/GEODE-9163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Hutchison updated GEODE-9163: -- Fix Version/s: 1.15.0 > Redis: update docs to reflect that the api is experimental > -- > > Key: GEODE-9163 > URL: https://issues.apache.org/jira/browse/GEODE-9163 > Project: Geode > Issue Type: New Feature > Components: docs, redis >Affects Versions: 1.14.0, 1.15.0 >Reporter: Hale Bales >Assignee: John Hutchison >Priority: Major > Labels: blocks-1.14.0, pull-request-available > Fix For: 1.15.0 > > > update the docs to reflect that the Geode api compatible with Redis is still > experimental. This depends on GEODE-9162 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9163) Redis: update docs to reflect that the api is experimental
[ https://issues.apache.org/jira/browse/GEODE-9163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Hutchison updated GEODE-9163: -- Labels: blocks-1.14.0 pull-request-available (was: pull-request-available) > Redis: update docs to reflect that the api is experimental > -- > > Key: GEODE-9163 > URL: https://issues.apache.org/jira/browse/GEODE-9163 > Project: Geode > Issue Type: New Feature > Components: docs, redis >Affects Versions: 1.14.0, 1.15.0 >Reporter: Hale Bales >Assignee: John Hutchison >Priority: Major > Labels: blocks-1.14.0, pull-request-available > > update the docs to reflect that the Geode api compatible with Redis is still > experimental. This depends on GEODE-9162 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-9163) Redis: update docs to reflect that the api is experimental
[ https://issues.apache.org/jira/browse/GEODE-9163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Hutchison reassigned GEODE-9163: - Assignee: John Hutchison > Redis: update docs to reflect that the api is experimental > -- > > Key: GEODE-9163 > URL: https://issues.apache.org/jira/browse/GEODE-9163 > Project: Geode > Issue Type: New Feature > Components: docs, redis >Affects Versions: 1.14.0, 1.15.0 >Reporter: Hale Bales >Assignee: John Hutchison >Priority: Major > Labels: pull-request-available > > update the docs to reflect that the Geode api compatible with Redis is still > experimental. This depends on GEODE-9162 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-9163) Redis: update docs to reflect that the api is experimental
[ https://issues.apache.org/jira/browse/GEODE-9163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Hutchison resolved GEODE-9163. --- Resolution: Fixed > Redis: update docs to reflect that the api is experimental > -- > > Key: GEODE-9163 > URL: https://issues.apache.org/jira/browse/GEODE-9163 > Project: Geode > Issue Type: New Feature > Components: docs, redis >Affects Versions: 1.14.0, 1.15.0 >Reporter: Hale Bales >Priority: Major > Labels: pull-request-available > > update the docs to reflect that the Geode api compatible with Redis is still > experimental. This depends on GEODE-9162 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9199) Restructure String Dunit tests to work with compatible with Redis cluster mode
[ https://issues.apache.org/jira/browse/GEODE-9199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Hutchison updated GEODE-9199: -- Summary: Restructure String Dunit tests to work with compatible with Redis cluster mode (was: Restructure dunit tests to work with compatible with Redis cluster mode ) > Restructure String Dunit tests to work with compatible with Redis cluster > mode > --- > > Key: GEODE-9199 > URL: https://issues.apache.org/jira/browse/GEODE-9199 > Project: Geode > Issue Type: Task > Components: redis >Reporter: John Hutchison >Assignee: John Hutchison >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-6489) CI Failures with testDistributedDeadlock
[
https://issues.apache.org/jira/browse/GEODE-6489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17333501#comment-17333501
]
John Hutchison commented on GEODE-6489:
---
this seems to be the same issue as
https://issues.apache.org/jira/browse/GEODE-6222.
> CI Failures with testDistributedDeadlock
>
>
> Key: GEODE-6489
> URL: https://issues.apache.org/jira/browse/GEODE-6489
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Affects Versions: 1.10.0
>Reporter: Lynn Hughes-Godfrey
>Assignee: Jinmei Liao
>Priority: Major
> Labels: flaky
>
> In an single CI run, we see 3 failures all related to testDistributedDeadlock:
> {noformat}
> org.apache.geode.management.internal.cli.commands.ShowDeadlockOverHttpDUnitTest
> > testDistributedDeadlockWithFunction FAILED
> org.apache.geode.management.internal.cli.commands.ShowDeadlockOverHttpDUnitTest
> > testNoDeadlock FAILED
> org.apache.geode.distributed.internal.deadlock.GemFireDeadlockDetectorDUnitTest
> > testDistributedDeadlockWithDLock FAILED
> {noformat}
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/469
> {noformat}
> org.apache.geode.management.internal.cli.commands.ShowDeadlockOverHttpDUnitTest
> > testDistributedDeadlockWithFunction FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.management.internal.cli.commands.ShowDeadlockDistributedTestBase$$Lambda$68/829260532.run
> in VM 1 running on Host ceb4d948b5be with 4 VMs
> Caused by:
> org.awaitility.core.ConditionTimeoutException: Condition with
> org.apache.geode.management.internal.cli.commands.ShowDeadlockDistributedTestBase
> was not fulfilled within 300 seconds.
> org.apache.geode.management.internal.cli.commands.ShowDeadlockOverHttpDUnitTest
> > testNoDeadlock FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.management.internal.cli.commands.ShowDeadlockDistributedTestBase$$Lambda$68/829260532.run
> in VM 1 running on Host ceb4d948b5be with 4 VMs
> Caused by:
> org.awaitility.core.ConditionTimeoutException: Condition with
> org.apache.geode.management.internal.cli.commands.ShowDeadlockDistributedTestBase
> was not fulfilled within 300 seconds.
> 137 tests completed, 2 failed
> > Task :geode-web:distributedTest FAILED
> > Task :geode-core:distributedTest
> org.apache.geode.distributed.internal.deadlock.GemFireDeadlockDetectorDUnitTest
> > testDistributedDeadlockWithDLock FAILED
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertTrue(Assert.java:52)
> at
> org.apache.geode.distributed.internal.deadlock.GemFireDeadlockDetectorDUnitTest.testDistributedDeadlockWithDLock(GemFireDeadlockDetectorDUnitTest.java:201)
> {noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0019/test-results/distributedTest/1551833386/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0019/test-artifacts/1551833386/distributedtestfiles-OpenJDK8-1.10.0-SNAPSHOT.0019.tgz
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Reopened] (GEODE-8990) CI Failure: Jetty9CachingClientServerTest.shouldCacheSessionOnClient
[
https://issues.apache.org/jira/browse/GEODE-8990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Hutchison reopened GEODE-8990:
---
test failure occurred agin in ci run:
org.apache.geode.session.tests.Jetty9CachingClientServerTest >
shouldCacheSessionOnClient FAILED
org.junit.ComparisonFailure: expected:<"[Foo]"> but was:<"[bogus]">
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.session.tests.Jetty9CachingClientServerTest.shouldCacheSessionOnClient(Jetty9CachingClientServerTest.java:70)
=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0163/test-results/distributedTest/1619549466/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Test report artifacts from this job are available at:
http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0163/test-artifacts/1619549466/distributedtestfiles-OpenJDK8-1.15.0-build.0163.tgz
> CI Failure: Jetty9CachingClientServerTest.shouldCacheSessionOnClient
>
>
> Key: GEODE-8990
> URL: https://issues.apache.org/jira/browse/GEODE-8990
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Assignee: Benjamin P Ross
>Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
> Fix For: 1.15.0
>
>
> {noformat}
> org.apache.geode.session.tests.Jetty9CachingClientServerTest >
> shouldCacheSessionOnClient FAILED
> org.junit.ComparisonFailure: expected:<[Foo]> but was:<[bogus]>
> at org.junit.Assert.assertEquals(Assert.java:117)
> at org.junit.Assert.assertEquals(Assert.java:146)
> at
> org.apache.geode.session.tests.Jetty9CachingClientServerTest.shouldCacheSessionOnClient(Jetty9CachingClientServerTest.java:65)
> 371 tests completed, 1 failed
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0023/test-results/distributedTest/1614646829/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0023/test-artifacts/1614646829/distributedtestfiles-OpenJDK8-1.15.0-build.0023.tgz
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (GEODE-9199) Restructure dunit tests to work with compatible with Redis cluster mode
[ https://issues.apache.org/jira/browse/GEODE-9199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Hutchison reassigned GEODE-9199: - Assignee: John Hutchison > Restructure dunit tests to work with compatible with Redis cluster mode > > > Key: GEODE-9199 > URL: https://issues.apache.org/jira/browse/GEODE-9199 > Project: Geode > Issue Type: Task > Components: redis >Reporter: John Hutchison >Assignee: John Hutchison >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (GEODE-9106) CI Failure: Client Server Session Cache fails infrequently with ConditionTimeoutException
[ https://issues.apache.org/jira/browse/GEODE-9106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Hutchison reopened GEODE-9106: --- test failure in CI run org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest > preCreatedRegionIsNotCopiedToNewlyStartedServers FAILED org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest$$Lambda$52/2029192492.run in VM 1 running on Host e243b2a9bcec with 4 VMs at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631) at org.apache.geode.test.dunit.VM.invoke(VM.java:448) at org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest.preCreatedRegionIsNotCopiedToNewlyStartedServers(ClientServerSessionCacheDUnitTest.java:144) Caused by: org.awaitility.core.ConditionTimeoutException: Assertion condition defined as a lambda expression in org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest Expected size: 1 but was: 0 in: [] within 5 minutes. at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165) at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119) at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31) at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:895) at org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:679) at org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest.lambda$preCreatedRegionIsNotCopiedToNewlyStartedServers$bb17a952$1(ClientServerSessionCacheDUnitTest.java:144) Caused by: java.lang.AssertionError: Expected size: 1 but was: 0 in: [] =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0161/test-results/distributedTest/1619547582/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test report artifacts from this job are available at: http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0161/test-artifacts/1619547582/distributedtestfiles-OpenJDK8-1.15.0-build.0161.tgz > CI Failure: Client Server Session Cache fails infrequently with > ConditionTimeoutException > - > > Key: GEODE-9106 > URL: https://issues.apache.org/jira/browse/GEODE-9106 > Project: Geode > Issue Type: Bug >Affects Versions: 1.14.0 >Reporter: Benjamin P Ross >Assignee: Benjamin P Ross >Priority: Major > > org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest > > preCreatedRegionIsNotCopiedToNewlyStartedServers FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest$$Lambda$52/487544699.run > in VM 1 running on Host a1dde695db62 with 4 VMs > at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631) > at org.apache.geode.test.dunit.VM.invoke(VM.java:448) > at > org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest.preCreatedRegionIsNotCopiedToNewlyStartedServers(ClientServerSessionCacheDUnitTest.java:144) > Caused by: > org.awaitility.core.ConditionTimeoutException: Assertion condition > defined as a lambda expression in > org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest > Expected size: 1 but was: 0 in: > [] within 5 minutes. > at > org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165) > at > org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119) > at > org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31) > at > org.awaitility.core.ConditionFactory.until(ConditionFactory.java:895) > at > org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:679) > at > org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest.lambda$preCreatedRegionIsNotCopiedToNewlyStartedServers$bb17a952$1(ClientServerSessionCacheDUnitTest.java:144) > Caused by: > java.lang.AssertionError: > Expected size: 1 but was: 0 in: > [] > at > org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest.validateBootstrapped(ClientServerSessionCacheDUnitTest.java:258) > This issue seems to be specific to the method validateBootstrapped(). In this > method we attempt to verify that the BootstrappingFunction is being > registered as a Listener within the Distribution Manager (which is a part of > setting up the ClientServe
[jira] [Updated] (GEODE-9199) Restructure dunit tests to work with compatible with Redis cluster mode
[ https://issues.apache.org/jira/browse/GEODE-9199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Hutchison updated GEODE-9199: -- Summary: Restructure dunit tests to work with compatible with Redis cluster mode (was: restructure Dunit Tests to work with Compatible with Redis Cluster Mode ) > Restructure dunit tests to work with compatible with Redis cluster mode > > > Key: GEODE-9199 > URL: https://issues.apache.org/jira/browse/GEODE-9199 > Project: Geode > Issue Type: Task > Components: redis >Reporter: John Hutchison >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-9199) restructure Dunit Tests to work with Compatible with Redis Cluster Mode
John Hutchison created GEODE-9199: - Summary: restructure Dunit Tests to work with Compatible with Redis Cluster Mode Key: GEODE-9199 URL: https://issues.apache.org/jira/browse/GEODE-9199 Project: Geode Issue Type: Task Components: redis Reporter: John Hutchison -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (GEODE-8971) Batches with incomplete transactions when stopping the gateway sender
[ https://issues.apache.org/jira/browse/GEODE-8971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1717#comment-1717 ] John Hutchison edited comment on GEODE-8971 at 4/27/21, 2:51 PM: - test failure seen again in run https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/151.1 (unclear if this is reoccurrence of same issue or a new bug) =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0145/test-results/distributedTest/1618550176/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test report artifacts from this job are available at: http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0145/test-artifacts/1618550176/distributedtestfiles-OpenJDK8-1.15.0-build.0145.tgz was (Author: john hutch): test failure seen again in run https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/151.1 =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0145/test-results/distributedTest/1618550176/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test report artifacts from this job are available at: http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0145/test-artifacts/1618550176/distributedtestfiles-OpenJDK8-1.15.0-build.0145.tgz > Batches with incomplete transactions when stopping the gateway sender > - > > Key: GEODE-8971 > URL: https://issues.apache.org/jira/browse/GEODE-8971 > Project: Geode > Issue Type: Improvement > Components: wan >Affects Versions: 1.14.0 >Reporter: Alberto Gomez >Assignee: Alberto Gomez >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > When the gateway sender is stopped there is a high probability that batches > with incomplete transactions are sent even if group-transaction-events is > enabled. > The reason is that once the stop command reaches the gateway sender, it > immediately stops queueing events, and this could happen in the middle of > receiving events for the same transaction. If this is the case, some events > for the transaction may have reached the queue right before the stop command > was received and the rest of events for that transaction would not make it to > the queue (they would be dropped) because they arrived right after the stop > command was received at the gateway sender. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (GEODE-8971) Batches with incomplete transactions when stopping the gateway sender
[ https://issues.apache.org/jira/browse/GEODE-8971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Hutchison reopened GEODE-8971: --- test failure seen again in run https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/151.1 =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0145/test-results/distributedTest/1618550176/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test report artifacts from this job are available at: http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0145/test-artifacts/1618550176/distributedtestfiles-OpenJDK8-1.15.0-build.0145.tgz > Batches with incomplete transactions when stopping the gateway sender > - > > Key: GEODE-8971 > URL: https://issues.apache.org/jira/browse/GEODE-8971 > Project: Geode > Issue Type: Improvement > Components: wan >Affects Versions: 1.14.0 >Reporter: Alberto Gomez >Assignee: Alberto Gomez >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > When the gateway sender is stopped there is a high probability that batches > with incomplete transactions are sent even if group-transaction-events is > enabled. > The reason is that once the stop command reaches the gateway sender, it > immediately stops queueing events, and this could happen in the middle of > receiving events for the same transaction. If this is the case, some events > for the transaction may have reached the queue right before the stop command > was received and the rest of events for that transaction would not make it to > the queue (they would be dropped) because they arrived right after the stop > command was received at the gateway sender. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-9113) CI failure: org.apache.geode.redis.internal.data.RedisHashTest > hscanSnaphots_shouldExpireAfterExpiryPeriod
[
https://issues.apache.org/jira/browse/GEODE-9113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Hutchison resolved GEODE-9113.
---
Resolution: Fixed
expiration period increased; issue to be reopened if occurs again.
> CI failure: org.apache.geode.redis.internal.data.RedisHashTest >
> hscanSnaphots_shouldExpireAfterExpiryPeriod
>
>
> Key: GEODE-9113
> URL: https://issues.apache.org/jira/browse/GEODE-9113
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Ray Ingles
>Assignee: John Hutchison
>Priority: Major
> Labels: blocks-1.14.0, pull-request-available
>
> {{org.apache.geode.redis.internal.data.RedisHashTest >
> hscanSnaphots_shouldExpireAfterExpiryPeriod FAILED
> org.awaitility.core.ConditionTimeoutException: Assertion condition
> defined as a lambda expression in
> org.apache.geode.redis.internal.data.RedisHashTest that uses
> org.apache.geode.redis.internal.data.RedisHash null within 2 seconds.
> at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
> at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:895)
> at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:679)
> at
> org.apache.geode.redis.internal.data.RedisHashTest.hscanSnaphots_shouldExpireAfterExpiryPeriod(RedisHashTest.java:254)
> }}
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/WindowsUnitTestOpenJDK11/builds/117
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-9155) increase wait interval on PassiveExpirationManager
John Hutchison created GEODE-9155: - Summary: increase wait interval on PassiveExpirationManager Key: GEODE-9155 URL: https://issues.apache.org/jira/browse/GEODE-9155 Project: Geode Issue Type: Task Components: redis Reporter: John Hutchison currently this class is running through all keys every second and is consuming a lot of cpu cycles. Business needs do not seem to require keys to be removed from memory this quickly. This ticket will increase interval to every 30 minutes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-9144) rsync_code_down-OpenJDK11 CI failure
John Hutchison created GEODE-9144: - Summary: rsync_code_down-OpenJDK11 CI failure Key: GEODE-9144 URL: https://issues.apache.org/jira/browse/GEODE-9144 Project: Geode Issue Type: Task Reporter: John Hutchison appears to be infrequent infrastructure/network issue, but reporting here to allow for triage: build appears to complete successfully, but receives broken pipe error after build completes and is reported as hung test https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/WindowsIntegrationTestOpenJDK11/builds/29 Deprecated Gradle features were used in this build, making it incompatible with Gradle 6.0. Use '--warning-mode all' to show the individual deprecation warnings. See https://docs.gradle.org/5.4/userguide/command_line_interface.html#sec:command_line_warnings BUILD SUCCESSFUL in 25s 1 actionable task: 1 up-to-date + rsync -e 'ssh -i instance-data/sshkey -o ConnectTimeout=5 -o ConnectionAttempts=60 -o StrictHostKeyChecking=no' -ah geode@10.0.0.30:geode /tmp/build/1a3d1be6/geode-results/ rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(642) [generator=3.1.3] rsync: [generator] write error: Broken pipe (32) rsync error: received SIGUSR1 (code 19) at main.c(1440) [receiver=3.1.3] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9143) run_benchmarks_with_ssl failure
[ https://issues.apache.org/jira/browse/GEODE-9143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Hutchison updated GEODE-9143: -- Description: this seems like a network failure, but reporting to err on the side of caution: https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/Benchmark_with_ssl/builds/33 selected worker: 10d092c9-9d55-4cbd-91c7-8db6012018d3 ++ pwd + BASE_DIR=/tmp/build/2da2cadb + SOURCE=geode-ci/ci/scripts/run_benchmarks.sh + '[' -h geode-ci/ci/scripts/run_benchmarks.sh ']' +++ dirname geode-ci/ci/scripts/run_benchmarks.sh ++ cd -P geode-ci/ci/scripts ++ pwd + SCRIPTDIR=/tmp/build/2da2cadb/geode-ci/ci/scripts + source concourse-metadata-resource/concourse_metadata ++ export BUILD_ID=23741 ++ BUILD_ID=23741 ++ export BUILD_NAME=33 ++ BUILD_NAME=33 ++ export BUILD_JOB_NAME=Benchmark_with_ssl ++ BUILD_JOB_NAME=Benchmark_with_ssl ++ export BUILD_PIPELINE_NAME=apache-support-1-12-main ++ BUILD_PIPELINE_NAME=apache-support-1-12-main ++ export BUILD_TEAM_NAME=main ++ BUILD_TEAM_NAME=main ++ export ATC_EXTERNAL_URL=https://concourse.apachegeode-ci.info ++ ATC_EXTERNAL_URL=https://concourse.apachegeode-ci.info + CLUSTER_TAG=apache-support-1-12-main-Benchmark_with_ssl-33-23741_with_ssl ++ pwd + RESULTS_DIR=/tmp/build/2da2cadb/results/benchmarks-apache-support-1-12-main-Benchmark_with_ssl-33-23741_with_ssl + CLUSTER_COUNT=4 + BENCHMARKS_BRANCH=support/1.12 ++ cd geode ++ git remote get-url origin + GEODE_REPO=https://github.com/apache/geode.git + BASELINE_REPO=https://github.com/apache/geode.git + pushd geode /tmp/build/2da2cadb/geode /tmp/build/2da2cadb ++ git rev-parse --verify HEAD + GEODE_SHA=c12674883311b42955fbe9e8c5421db557efe08e + popd /tmp/build/2da2cadb ++ pwd + input=/tmp/build/2da2cadb/results/failedTests + pushd geode-benchmarks/infrastructure/scripts/aws/ /tmp/build/2da2cadb/geode-benchmarks/infrastructure/scripts/aws /tmp/build/2da2cadb + ./launch_cluster.sh -t apache-support-1-12-main-Benchmark_with_ssl-33-23741_with_ssl -c 4 --ci /tmp/build/2da2cadb/geode-benchmarks /tmp/build/2da2cadb/geode-benchmarks/infrastructure/scripts/aws % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 126M 100 126M0 0 111M 0 0:00:01 0:00:01 --:--:-- 155M ~/.gradle/wrapper/dists/gradle-5.4-all/a4530233ad2cedf73d5afc3b97eb8f71 /tmp/build/2da2cadb/geode-benchmarks /tmp/build/2da2cadb/geode-benchmarks Welcome to Gradle 5.4! Here are the highlights of this release: - Run builds with JDK12 - New API for Incremental Tasks - Updates to native projects, including Swift 5 support For more details see https://docs.gradle.org/5.4/release-notes.html Starting a Gradle Daemon (subsequent builds will be faster) > Task :infrastructure:compileJava > Task :infrastructure:processResources NO-SOURCE > Task :infrastructure:classes > Task :infrastructure:launchCluster FAILED FAILURE: Build failed with an exception. * What went wrong: Execution failed for task ':infrastructure:launchCluster'. > Could not resolve all files for configuration > ':infrastructure:runtimeClasspath'. > Could not download netty-reactive-streams.jar (com.typesafe.netty:netty-reactive-streams:2.0.0) > Could not get resource 'https://repo.maven.apache.org/maven2/com/typesafe/netty/netty-reactive-streams/2.0.0/netty-reactive-streams-2.0.0.jar'. > Could not GET 'https://repo.maven.apache.org/maven2/com/typesafe/netty/netty-reactive-streams/2.0.0/netty-reactive-streams-2.0.0.jar'. > Connection reset * Try: Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights. * Get more help at https://help.gradle.org Deprecated Gradle features were used in this build, making it incompatible with Gradle 6.0. Use '--warning-mode all' to show the individual deprecation warnings. See https://docs.gradle.org/5.4/userguide/command_line_interface.html#sec:command_line_warnings BUILD FAILED in 27s 2 actionable tasks: 2 executed was: this seems like a network failure, but reporting to err on the side of caution: selected worker: 10d092c9-9d55-4cbd-91c7-8db6012018d3 ++ pwd + BASE_DIR=/tmp/build/2da2cadb + SOURCE=geode-ci/ci/scripts/run_benchmarks.sh + '[' -h geode-ci/ci/scripts/run_benchmarks.sh ']' +++ dirname geode-ci/ci/scripts/run_benchmarks.sh ++ cd -P geode-ci/ci/scripts ++ pwd + SCRIPTDIR=/tmp/build/2da2cadb/geode-ci/ci/scripts + source concourse-metadata-resource/concourse_metadata ++ export BUILD_ID=23741 ++ BUILD_ID=23741 ++ export BUILD_NAME=33 ++ BUILD_NAME=33 ++ export BUILD_JOB_NAME=Benchmark_with_ssl ++ BUILD_JOB_NAME=Benchmark_with_ssl ++ export BUILD_PIPELINE_NAME=apache-support-1-12-main ++ BUILD_PIP
[jira] [Created] (GEODE-9143) run_benchmarks_with_ssl failure
John Hutchison created GEODE-9143: - Summary: run_benchmarks_with_ssl failure Key: GEODE-9143 URL: https://issues.apache.org/jira/browse/GEODE-9143 Project: Geode Issue Type: Task Reporter: John Hutchison this seems like a network failure, but reporting to err on the side of caution: selected worker: 10d092c9-9d55-4cbd-91c7-8db6012018d3 ++ pwd + BASE_DIR=/tmp/build/2da2cadb + SOURCE=geode-ci/ci/scripts/run_benchmarks.sh + '[' -h geode-ci/ci/scripts/run_benchmarks.sh ']' +++ dirname geode-ci/ci/scripts/run_benchmarks.sh ++ cd -P geode-ci/ci/scripts ++ pwd + SCRIPTDIR=/tmp/build/2da2cadb/geode-ci/ci/scripts + source concourse-metadata-resource/concourse_metadata ++ export BUILD_ID=23741 ++ BUILD_ID=23741 ++ export BUILD_NAME=33 ++ BUILD_NAME=33 ++ export BUILD_JOB_NAME=Benchmark_with_ssl ++ BUILD_JOB_NAME=Benchmark_with_ssl ++ export BUILD_PIPELINE_NAME=apache-support-1-12-main ++ BUILD_PIPELINE_NAME=apache-support-1-12-main ++ export BUILD_TEAM_NAME=main ++ BUILD_TEAM_NAME=main ++ export ATC_EXTERNAL_URL=https://concourse.apachegeode-ci.info ++ ATC_EXTERNAL_URL=https://concourse.apachegeode-ci.info + CLUSTER_TAG=apache-support-1-12-main-Benchmark_with_ssl-33-23741_with_ssl ++ pwd + RESULTS_DIR=/tmp/build/2da2cadb/results/benchmarks-apache-support-1-12-main-Benchmark_with_ssl-33-23741_with_ssl + CLUSTER_COUNT=4 + BENCHMARKS_BRANCH=support/1.12 ++ cd geode ++ git remote get-url origin + GEODE_REPO=https://github.com/apache/geode.git + BASELINE_REPO=https://github.com/apache/geode.git + pushd geode /tmp/build/2da2cadb/geode /tmp/build/2da2cadb ++ git rev-parse --verify HEAD + GEODE_SHA=c12674883311b42955fbe9e8c5421db557efe08e + popd /tmp/build/2da2cadb ++ pwd + input=/tmp/build/2da2cadb/results/failedTests + pushd geode-benchmarks/infrastructure/scripts/aws/ /tmp/build/2da2cadb/geode-benchmarks/infrastructure/scripts/aws /tmp/build/2da2cadb + ./launch_cluster.sh -t apache-support-1-12-main-Benchmark_with_ssl-33-23741_with_ssl -c 4 --ci /tmp/build/2da2cadb/geode-benchmarks /tmp/build/2da2cadb/geode-benchmarks/infrastructure/scripts/aws % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 126M 100 126M0 0 111M 0 0:00:01 0:00:01 --:--:-- 155M ~/.gradle/wrapper/dists/gradle-5.4-all/a4530233ad2cedf73d5afc3b97eb8f71 /tmp/build/2da2cadb/geode-benchmarks /tmp/build/2da2cadb/geode-benchmarks Welcome to Gradle 5.4! Here are the highlights of this release: - Run builds with JDK12 - New API for Incremental Tasks - Updates to native projects, including Swift 5 support For more details see https://docs.gradle.org/5.4/release-notes.html Starting a Gradle Daemon (subsequent builds will be faster) > Task :infrastructure:compileJava > Task :infrastructure:processResources NO-SOURCE > Task :infrastructure:classes > Task :infrastructure:launchCluster FAILED FAILURE: Build failed with an exception. * What went wrong: Execution failed for task ':infrastructure:launchCluster'. > Could not resolve all files for configuration > ':infrastructure:runtimeClasspath'. > Could not download netty-reactive-streams.jar (com.typesafe.netty:netty-reactive-streams:2.0.0) > Could not get resource 'https://repo.maven.apache.org/maven2/com/typesafe/netty/netty-reactive-streams/2.0.0/netty-reactive-streams-2.0.0.jar'. > Could not GET 'https://repo.maven.apache.org/maven2/com/typesafe/netty/netty-reactive-streams/2.0.0/netty-reactive-streams-2.0.0.jar'. > Connection reset * Try: Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights. * Get more help at https://help.gradle.org Deprecated Gradle features were used in this build, making it incompatible with Gradle 6.0. Use '--warning-mode all' to show the individual deprecation warnings. See https://docs.gradle.org/5.4/userguide/command_line_interface.html#sec:command_line_warnings BUILD FAILED in 27s 2 actionable tasks: 2 executed -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-8859) Redis data structures may not accurately reflect their size in Geode stats
[
https://issues.apache.org/jira/browse/GEODE-8859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Hutchison reassigned GEODE-8859:
-
Assignee: (was: John Hutchison)
> Redis data structures may not accurately reflect their size in Geode stats
> --
>
> Key: GEODE-8859
> URL: https://issues.apache.org/jira/browse/GEODE-8859
> Project: Geode
> Issue Type: Bug
> Components: redis, statistics
>Affects Versions: 1.14.0
>Reporter: Jens Deppe
>Priority: Major
> Labels: blocks-1.14.0, pull-request-available, release-blocker
>
> Here is a comment from Darrel regarding this issue. For some background, the
> Redis structures implement {{Delta}}.
>
> {quote}I was playing around with RedisInsight and was able to get most the
> the overview dashboard and the data browser working with geode redis. But I
> found a problem with how we are using geode that causes the geode stats that
> track how much data is stored in a partitioned region to be wrong and the
> bucket sizes used for rebalancing are also wrong. Basically when we do create
> ops on the region the stats track it okay. But when we do updates then geode
> always thinks that nothing (size wise) changed. So for example I created a
> string by doing a redis “set” command. I saw the size of the string accounted
> for in dataStoreBytesInUse. But then I kept doing redis “append” commands on
> that key and the dataStoreBytesInUse did not change at all. I think the
> problem is in how we are updating the data structure in place instead of
> getting a copy, modifying it, and then putting the copy into the region.
> Avoiding this copy gives us MUCH better performance but it messes up geode
> when it is trying to calculate the memory increase or decrease. It is
> possible that this is only an issue on the primary and that the secondary
> sizing may be correct. If so that could lead to other problems because for a
> given bucket our primary size would be different than the secondary. The
> bucket sizes are used when you do a rebalance but basically we can have a
> bunch of memory that is “untracked” so we might see the JVM heaps unbalanced
> but geode will think the buckets are balanced. I’m not sure what we should do
> about this.
> {quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (GEODE-9113) CI failure: org.apache.geode.redis.internal.data.RedisHashTest > hscanSnaphots_shouldExpireAfterExpiryPeriod
[
https://issues.apache.org/jira/browse/GEODE-9113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Hutchison reassigned GEODE-9113:
-
Assignee: John Hutchison
> CI failure: org.apache.geode.redis.internal.data.RedisHashTest >
> hscanSnaphots_shouldExpireAfterExpiryPeriod
>
>
> Key: GEODE-9113
> URL: https://issues.apache.org/jira/browse/GEODE-9113
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Ray Ingles
>Assignee: John Hutchison
>Priority: Major
>
> {{org.apache.geode.redis.internal.data.RedisHashTest >
> hscanSnaphots_shouldExpireAfterExpiryPeriod FAILED
> org.awaitility.core.ConditionTimeoutException: Assertion condition
> defined as a lambda expression in
> org.apache.geode.redis.internal.data.RedisHashTest that uses
> org.apache.geode.redis.internal.data.RedisHash null within 2 seconds.
> at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
> at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:895)
> at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:679)
> at
> org.apache.geode.redis.internal.data.RedisHashTest.hscanSnaphots_shouldExpireAfterExpiryPeriod(RedisHashTest.java:254)
> }}
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/WindowsUnitTestOpenJDK11/builds/117
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-9068) Update documents to show removal of unsupported commands category
[ https://issues.apache.org/jira/browse/GEODE-9068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Hutchison updated GEODE-9068: -- Summary: Update documents to show removal of unsupported commands category (was: Update Documents to show removal of unsupported commands category) > Update documents to show removal of unsupported commands category > - > > Key: GEODE-9068 > URL: https://issues.apache.org/jira/browse/GEODE-9068 > Project: Geode > Issue Type: Task > Components: redis >Reporter: John Hutchison >Assignee: John Hutchison >Priority: Major > Labels: blocks-1.14.0 > > update docs to represent changes in > https://issues.apache.org/jira/browse/GEODE-9037 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9068) Update Documents to show removal of unsupported commands category
[ https://issues.apache.org/jira/browse/GEODE-9068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Hutchison updated GEODE-9068: -- Labels: blocks-1.14.0 (was: 1) > Update Documents to show removal of unsupported commands category > - > > Key: GEODE-9068 > URL: https://issues.apache.org/jira/browse/GEODE-9068 > Project: Geode > Issue Type: Task > Components: redis >Reporter: John Hutchison >Assignee: John Hutchison >Priority: Major > Labels: blocks-1.14.0 > > update docs to represent changes in > https://issues.apache.org/jira/browse/GEODE-9037 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9068) Update Documents to show removal of unsupported commands category
[ https://issues.apache.org/jira/browse/GEODE-9068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Hutchison updated GEODE-9068: -- Labels: 1 (was: ) > Update Documents to show removal of unsupported commands category > - > > Key: GEODE-9068 > URL: https://issues.apache.org/jira/browse/GEODE-9068 > Project: Geode > Issue Type: Task > Components: redis >Reporter: John Hutchison >Assignee: John Hutchison >Priority: Major > Labels: 1 > > update docs to represent changes in > https://issues.apache.org/jira/browse/GEODE-9037 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-9068) Update Documents to show removal of unsupported commands category
[ https://issues.apache.org/jira/browse/GEODE-9068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Hutchison reassigned GEODE-9068: - Assignee: John Hutchison > Update Documents to show removal of unsupported commands category > - > > Key: GEODE-9068 > URL: https://issues.apache.org/jira/browse/GEODE-9068 > Project: Geode > Issue Type: Task > Components: redis >Reporter: John Hutchison >Assignee: John Hutchison >Priority: Major > > update docs to represent changes in > https://issues.apache.org/jira/browse/GEODE-9037 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-9037) Do not expose unsupported commands in Geode compatibility with Redis
[ https://issues.apache.org/jira/browse/GEODE-9037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Hutchison resolved GEODE-9037. --- Resolution: Fixed > Do not expose unsupported commands in Geode compatibility with Redis > > > Key: GEODE-9037 > URL: https://issues.apache.org/jira/browse/GEODE-9037 > Project: Geode > Issue Type: New Feature > Components: redis >Reporter: Ray Ingles >Assignee: Ray Ingles >Priority: Major > Labels: blocks-1.14.0, pull-request-available > > The distinction between 'supported' and 'unsupported' commands is no longer > useful and will be removed. Any commands still listed as unsupported will now > respond if they were unimplemented/unknown. > A system property will allow them to be enabled solely for tests. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9068) Update Documents to show removal of unsupported commands category
[ https://issues.apache.org/jira/browse/GEODE-9068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Hutchison updated GEODE-9068: -- Summary: Update Documents to show removal of unsupported commands category (was: Update Documents to show removal of unsupported commands feature) > Update Documents to show removal of unsupported commands category > - > > Key: GEODE-9068 > URL: https://issues.apache.org/jira/browse/GEODE-9068 > Project: Geode > Issue Type: Task > Components: redis >Reporter: John Hutchison >Priority: Major > > update docs to represent changes in > https://issues.apache.org/jira/browse/GEODE-9037 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9037) Do not expose unsupported commands in Geode compatibility with Redis
[ https://issues.apache.org/jira/browse/GEODE-9037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17308752#comment-17308752 ] John Hutchison commented on GEODE-9037: --- docs changes for this story under https://issues.apache.org/jira/browse/GEODE-9068 > Do not expose unsupported commands in Geode compatibility with Redis > > > Key: GEODE-9037 > URL: https://issues.apache.org/jira/browse/GEODE-9037 > Project: Geode > Issue Type: New Feature > Components: redis >Reporter: Ray Ingles >Assignee: Ray Ingles >Priority: Major > Labels: blocks-1.14.0, pull-request-available > > The distinction between 'supported' and 'unsupported' commands is no longer > useful and will be removed. Any commands still listed as unsupported will now > respond if they were unimplemented/unknown. > A system property will allow them to be enabled solely for tests. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9068) Update Documents to show removal of unsupported commands feature
[ https://issues.apache.org/jira/browse/GEODE-9068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Hutchison updated GEODE-9068: -- Description: update docs to represent changes in https://issues.apache.org/jira/browse/GEODE-9037 > Update Documents to show removal of unsupported commands feature > > > Key: GEODE-9068 > URL: https://issues.apache.org/jira/browse/GEODE-9068 > Project: Geode > Issue Type: Task > Components: redis >Reporter: John Hutchison >Priority: Major > > update docs to represent changes in > https://issues.apache.org/jira/browse/GEODE-9037 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-9068) Update Documents to show removal of unsupported commands feature
John Hutchison created GEODE-9068: - Summary: Update Documents to show removal of unsupported commands feature Key: GEODE-9068 URL: https://issues.apache.org/jira/browse/GEODE-9068 Project: Geode Issue Type: Task Components: redis Reporter: John Hutchison -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-9009) finish support for functionality compatible with Redis DECRBY command
[ https://issues.apache.org/jira/browse/GEODE-9009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Hutchison resolved GEODE-9009. --- Resolution: Fixed > finish support for functionality compatible with Redis DECRBY command > --- > > Key: GEODE-9009 > URL: https://issues.apache.org/jira/browse/GEODE-9009 > Project: Geode > Issue Type: Task >Reporter: John Hutchison >Assignee: John Hutchison >Priority: Major > Labels: blocks-1.14.0, pull-request-available > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-9001) Update documents related to compatable-with-redis component for 1.14 release
[ https://issues.apache.org/jira/browse/GEODE-9001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Hutchison reassigned GEODE-9001: - Assignee: John Hutchison > Update documents related to compatable-with-redis component for 1.14 release > - > > Key: GEODE-9001 > URL: https://issues.apache.org/jira/browse/GEODE-9001 > Project: Geode > Issue Type: Task > Components: redis >Reporter: John Hutchison >Assignee: John Hutchison >Priority: Major > Labels: blocks-1.14.0, pull-request-available > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9038) testShutdownAllWithMembersWaiting failure
[ https://issues.apache.org/jira/browse/GEODE-9038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17302008#comment-17302008 ] John Hutchison commented on GEODE-9038: --- =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0054/test-results/distributedTest/1615840743/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test report artifacts from this job are available at: http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0054/test-artifacts/1615840743/distributedtestfiles-OpenJDK11-1.15.0-build.0054.tgz > testShutdownAllWithMembersWaiting failure > - > > Key: GEODE-9038 > URL: https://issues.apache.org/jira/browse/GEODE-9038 > Project: Geode > Issue Type: Bug >Reporter: John Hutchison >Priority: Major > > https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/78 > org.apache.geode.internal.cache.partitioned.ShutdownAllDUnitTest > > testShutdownAllWithMembersWaiting FAILED > java.lang.AssertionError: Suspicious strings were written to the log > during this run. > Fix the strings or use IgnoredException.addIgnoredException to ignore. > --- > Found suspect string in 'dunit_suspect-vm0.log' at line 1246 > [fatal 2021/03/15 19:27:44.311 GMT > tid=1461] While pushing message unexpected exception during data cleanup" level WARNING> to recipients: > <172.17.0.7(179):41003> > org.apache.geode.alerting.internal.spi.AlertingIOException: > java.io.IOException: Cannot form connection to alert listener > 172.17.0.7(179):41003 > at > org.apache.geode.internal.tcp.TCPConduit.getConnection(TCPConduit.java:884) > at > org.apache.geode.distributed.internal.direct.DirectChannel.getConnections(DirectChannel.java:464) > at > org.apache.geode.distributed.internal.direct.DirectChannel.sendToMany(DirectChannel.java:280) > at > org.apache.geode.distributed.internal.direct.DirectChannel.sendToOne(DirectChannel.java:187) > at > org.apache.geode.distributed.internal.direct.DirectChannel.send(DirectChannel.java:523) > at > org.apache.geode.distributed.internal.DistributionImpl.directChannelSend(DistributionImpl.java:346) > at > org.apache.geode.distributed.internal.DistributionImpl.send(DistributionImpl.java:291) > at > org.apache.geode.distributed.internal.ClusterDistributionManager.sendViaMembershipManager(ClusterDistributionManager.java:2053) > at > org.apache.geode.distributed.internal.ClusterDistributionManager.sendOutgoing(ClusterDistributionManager.java:1981) > at > org.apache.geode.distributed.internal.ClusterDistributionManager.sendMessage(ClusterDistributionManager.java:2018) > at > org.apache.geode.distributed.internal.ClusterDistributionManager.putOutgoing(ClusterDistributionManager.java:1083) > at > org.apache.geode.alerting.internal.ClusterAlertMessaging.lambda$null$0(ClusterAlertMessaging.java:103) > at > org.apache.geode.alerting.internal.spi.AlertingAction.execute(AlertingAction.java:34) > at > org.apache.geode.alerting.internal.ClusterAlertMessaging.lambda$sendAlert$1(ClusterAlertMessaging.java:81) > at > java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) > at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) > at > java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) > at > java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) > at java.base/java.lang.Thread.run(Thread.java:834) > Caused by: java.io.IOException: Cannot form connection to alert listener > 172.17.0.7(179):41003 > at > org.apache.geode.internal.tcp.ConnectionTable.getSharedConnection(ConnectionTable.java:406) > at > org.apache.geode.internal.tcp.ConnectionTable.get(ConnectionTable.java:574) > at > org.apache.geode.internal.tcp.TCPConduit.getConnection(TCPConduit.java:803) > ... 18 more -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-9038) testShutdownAllWithMembersWaiting failure
John Hutchison created GEODE-9038: - Summary: testShutdownAllWithMembersWaiting failure Key: GEODE-9038 URL: https://issues.apache.org/jira/browse/GEODE-9038 Project: Geode Issue Type: Bug Reporter: John Hutchison https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/78 org.apache.geode.internal.cache.partitioned.ShutdownAllDUnitTest > testShutdownAllWithMembersWaiting FAILED java.lang.AssertionError: Suspicious strings were written to the log during this run. Fix the strings or use IgnoredException.addIgnoredException to ignore. --- Found suspect string in 'dunit_suspect-vm0.log' at line 1246 [fatal 2021/03/15 19:27:44.311 GMT tid=1461] While pushing message to recipients: <172.17.0.7(179):41003> org.apache.geode.alerting.internal.spi.AlertingIOException: java.io.IOException: Cannot form connection to alert listener 172.17.0.7(179):41003 at org.apache.geode.internal.tcp.TCPConduit.getConnection(TCPConduit.java:884) at org.apache.geode.distributed.internal.direct.DirectChannel.getConnections(DirectChannel.java:464) at org.apache.geode.distributed.internal.direct.DirectChannel.sendToMany(DirectChannel.java:280) at org.apache.geode.distributed.internal.direct.DirectChannel.sendToOne(DirectChannel.java:187) at org.apache.geode.distributed.internal.direct.DirectChannel.send(DirectChannel.java:523) at org.apache.geode.distributed.internal.DistributionImpl.directChannelSend(DistributionImpl.java:346) at org.apache.geode.distributed.internal.DistributionImpl.send(DistributionImpl.java:291) at org.apache.geode.distributed.internal.ClusterDistributionManager.sendViaMembershipManager(ClusterDistributionManager.java:2053) at org.apache.geode.distributed.internal.ClusterDistributionManager.sendOutgoing(ClusterDistributionManager.java:1981) at org.apache.geode.distributed.internal.ClusterDistributionManager.sendMessage(ClusterDistributionManager.java:2018) at org.apache.geode.distributed.internal.ClusterDistributionManager.putOutgoing(ClusterDistributionManager.java:1083) at org.apache.geode.alerting.internal.ClusterAlertMessaging.lambda$null$0(ClusterAlertMessaging.java:103) at org.apache.geode.alerting.internal.spi.AlertingAction.execute(AlertingAction.java:34) at org.apache.geode.alerting.internal.ClusterAlertMessaging.lambda$sendAlert$1(ClusterAlertMessaging.java:81) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:834) Caused by: java.io.IOException: Cannot form connection to alert listener 172.17.0.7(179):41003 at org.apache.geode.internal.tcp.ConnectionTable.getSharedConnection(ConnectionTable.java:406) at org.apache.geode.internal.tcp.ConnectionTable.get(ConnectionTable.java:574) at org.apache.geode.internal.tcp.TCPConduit.getConnection(TCPConduit.java:803) ... 18 more -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-8859) Redis data structures may not accurately reflect their size in Geode stats
[
https://issues.apache.org/jira/browse/GEODE-8859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Hutchison resolved GEODE-8859.
---
Resolution: Fixed
> Redis data structures may not accurately reflect their size in Geode stats
> --
>
> Key: GEODE-8859
> URL: https://issues.apache.org/jira/browse/GEODE-8859
> Project: Geode
> Issue Type: Bug
> Components: redis, statistics
>Affects Versions: 1.14.0
>Reporter: Jens Deppe
>Assignee: Raymond Ingles
>Priority: Major
> Labels: blocks-1.14.0, pull-request-available, release-blocker
>
> Here is a comment from Darrel regarding this issue. For some background, the
> Redis structures implement {{Delta}}.
>
> {quote}I was playing around with RedisInsight and was able to get most the
> the overview dashboard and the data browser working with geode redis. But I
> found a problem with how we are using geode that causes the geode stats that
> track how much data is stored in a partitioned region to be wrong and the
> bucket sizes used for rebalancing are also wrong. Basically when we do create
> ops on the region the stats track it okay. But when we do updates then geode
> always thinks that nothing (size wise) changed. So for example I created a
> string by doing a redis “set” command. I saw the size of the string accounted
> for in dataStoreBytesInUse. But then I kept doing redis “append” commands on
> that key and the dataStoreBytesInUse did not change at all. I think the
> problem is in how we are updating the data structure in place instead of
> getting a copy, modifying it, and then putting the copy into the region.
> Avoiding this copy gives us MUCH better performance but it messes up geode
> when it is trying to calculate the memory increase or decrease. It is
> possible that this is only an issue on the primary and that the secondary
> sizing may be correct. If so that could lead to other problems because for a
> given bucket our primary size would be different than the secondary. The
> bucket sizes are used when you do a rebalance but basically we can have a
> bunch of memory that is “untracked” so we might see the JVM heaps unbalanced
> but geode will think the buckets are balanced. I’m not sure what we should do
> about this.
> {quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-9009) finish support for functionality compatible with Redis DECRBY command
John Hutchison created GEODE-9009: - Summary: finish support for functionality compatible with Redis DECRBY command Key: GEODE-9009 URL: https://issues.apache.org/jira/browse/GEODE-9009 Project: Geode Issue Type: Task Reporter: John Hutchison -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-8864) finish implementation of Redis HScan Command
[ https://issues.apache.org/jira/browse/GEODE-8864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Hutchison resolved GEODE-8864. --- Resolution: Fixed > finish implementation of Redis HScan Command > > > Key: GEODE-8864 > URL: https://issues.apache.org/jira/browse/GEODE-8864 > Project: Geode > Issue Type: New Feature > Components: redis >Reporter: John Hutchison >Assignee: John Hutchison >Priority: Major > Labels: blocks-1.14.0, pull-request-available > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-8864) finish implementation of Redis HScan Command
[ https://issues.apache.org/jira/browse/GEODE-8864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Hutchison reassigned GEODE-8864: - Assignee: John Hutchison > finish implementation of Redis HScan Command > > > Key: GEODE-8864 > URL: https://issues.apache.org/jira/browse/GEODE-8864 > Project: Geode > Issue Type: New Feature > Components: redis >Reporter: John Hutchison >Assignee: John Hutchison >Priority: Major > Labels: blocks-1.14.0, pull-request-available > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-9001) Update documents related to compatable-with-redis component for 1.14 release
John Hutchison created GEODE-9001: - Summary: Update documents related to compatable-with-redis component for 1.14 release Key: GEODE-9001 URL: https://issues.apache.org/jira/browse/GEODE-9001 Project: Geode Issue Type: Task Components: redis Reporter: John Hutchison -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-8952) Redis Hash Paramaters should be configurable
[ https://issues.apache.org/jira/browse/GEODE-8952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Hutchison updated GEODE-8952: -- Component/s: redis > Redis Hash Paramaters should be configurable > > > Key: GEODE-8952 > URL: https://issues.apache.org/jira/browse/GEODE-8952 > Project: Geode > Issue Type: New Feature > Components: redis >Reporter: John Hutchison >Priority: Major > > the redis hash object has 2 fields: > HSCAN_SNAPSHOTS_EXPIRE_CHECK_FREQUENCY_MILLISECONDS > MINIMUM_MILLISECONDS_FOR_HSCAN_SNAPSHOTS_TO_LIVE > which should be configurable for end user. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-8952) Redis Hash Paramaters should be configurable
John Hutchison created GEODE-8952: - Summary: Redis Hash Paramaters should be configurable Key: GEODE-8952 URL: https://issues.apache.org/jira/browse/GEODE-8952 Project: Geode Issue Type: New Feature Reporter: John Hutchison the redis hash object has 2 fields: HSCAN_SNAPSHOTS_EXPIRE_CHECK_FREQUENCY_MILLISECONDS MINIMUM_MILLISECONDS_FOR_HSCAN_SNAPSHOTS_TO_LIVE which should be configurable for end user. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8869) Tomcat6SessionsTest CI Failure
[ https://issues.apache.org/jira/browse/GEODE-8869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17270423#comment-17270423 ] John Hutchison commented on GEODE-8869: --- test artifacts too big to upload. Contact author if unable to download http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0630/test-artifacts/1611347047/windows-integrationtestfiles-OpenJDK11-1.14.0-build.0630.tgz > Tomcat6SessionsTest CI Failure > -- > > Key: GEODE-8869 > URL: https://issues.apache.org/jira/browse/GEODE-8869 > Project: Geode > Issue Type: New Feature >Reporter: John Hutchison >Priority: Major > > org.apache.geode.modules.session.Tomcat6SessionsTest > classMethod FAILED > LifecycleException: Protocol handler initialization failed: > java.net.BindException: Address already in use: NET_Bind :49863 > at > org.apache.catalina.connector.Connector.initialize(Connector.java:1125) > at org.apache.catalina.startup.Embedded.start(Embedded.java:830) > at > org.apache.geode.modules.session.EmbeddedTomcat.startContainer(EmbeddedTomcat.java:98) > at > org.apache.geode.modules.session.AbstractSessionsTest.setupServer(AbstractSessionsTest.java:72) > at > org.apache.geode.modules.session.Tomcat6SessionsTest.setupClass(Tomcat6SessionsTest.java:29) > =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0630/test-results/integrationTest/1611347047/ > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-8869) Tomcat6SessionsTest CI Failure
John Hutchison created GEODE-8869: - Summary: Tomcat6SessionsTest CI Failure Key: GEODE-8869 URL: https://issues.apache.org/jira/browse/GEODE-8869 Project: Geode Issue Type: New Feature Reporter: John Hutchison org.apache.geode.modules.session.Tomcat6SessionsTest > classMethod FAILED LifecycleException: Protocol handler initialization failed: java.net.BindException: Address already in use: NET_Bind :49863 at org.apache.catalina.connector.Connector.initialize(Connector.java:1125) at org.apache.catalina.startup.Embedded.start(Embedded.java:830) at org.apache.geode.modules.session.EmbeddedTomcat.startContainer(EmbeddedTomcat.java:98) at org.apache.geode.modules.session.AbstractSessionsTest.setupServer(AbstractSessionsTest.java:72) at org.apache.geode.modules.session.Tomcat6SessionsTest.setupClass(Tomcat6SessionsTest.java:29) =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0630/test-results/integrationTest/1611347047/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7016) CI failure: ServerStartupRedundancyRecoveryNotificationTest > startupReportsOnlineOnlyAfterRedundancyRestored FAILED
[
https://issues.apache.org/jira/browse/GEODE-7016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17270366#comment-17270366
]
John Hutchison commented on GEODE-7016:
---
seen in CI Run - ticket re-opened.
org.apache.geode.launchers.ServerStartupValueRecoveryNotificationTest >
startupReportsOnlineOnlyAfterRedundancyRestored FAILED
org.junit.ComparisonFailure: [Exit value from process started by
[a3a70e5ecf4d838f: gfsh -e connect --locator=localhost[23137] -e start server
--name=server1 --dir=/tmp/junit2110431257149045019/server1secondfolder
--locators=localhost[23137]]] expected:<[0]> but was:<[1]>
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.test.junit.rules.gfsh.GfshExecution.awaitTermination(GfshExecution.java:103)
at
org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:143)
at
org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:152)
at
org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:118)
at
org.apache.geode.launchers.ServerStartupValueRecoveryNotificationTest.startupReportsOnlineOnlyAfterRedundancyRestored(ServerStartupValueRecoveryNotificationTest.java:146)
=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0628/test-results/acceptanceTest/1611279518/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
[^acceptancetestfiles-OpenJDK11-1.14.0-build.0628 (2).tgz]
> CI failure: ServerStartupRedundancyRecoveryNotificationTest >
> startupReportsOnlineOnlyAfterRedundancyRestored FAILED
>
>
> Key: GEODE-7016
> URL: https://issues.apache.org/jira/browse/GEODE-7016
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Affects Versions: 1.10.0
>Reporter: Anilkumar Gingade
>Assignee: Kirk Lund
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.14.0
>
> Attachments: acceptancetestfiles-OpenJDK11-1.14.0-build.0628 (1).tgz,
> acceptancetestfiles-OpenJDK11-1.14.0-build.0628 (2).tgz
>
>
> {noformat}
> org.apache.geode.launchers.ServerStartupRedundancyRecoveryNotificationTest >
> startupReportsOnlineOnlyAfterRedundancyRestored FAILED
> org.junit.ComparisonFailure: expected:<[0]> but was:<[1]>
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshExecution.awaitTermination(GfshExecution.java:125)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:125)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:112)
> at
> org.apache.geode.launchers.ServerStartupRedundancyRecoveryNotificationTest.startupReportsOnlineOnlyAfterRedundancyRestored(ServerStartupRedundancyRecoveryNotificationTest.java:142)
> org.junit.ComparisonFailure: expected:<[0]> but was:<[1]>
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshExecution.awaitTermination(GfshExecution.java:125)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:125)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:112)
> at
> org.apache.geode.launchers.ServerStartupRedundancyRecoveryNotificationTest.stopAllMembers(ServerStartupRedundancyRecoveryNotificationTest.java:128)
> {noformat}
> https://concourse.gemfire-ci.info/teams/main/pipelines/gemfire-develop-main/jobs/AcceptanceTestOpenJDK8/builds/797
> Test report artifacts from this job are available at:
> gs://gemfire-test-artifacts/builds/gemfire-develop-main/9.9.0-build.0258/test-artifacts/1564078711/acceptancetestfiles-OpenJDK8-9.9.0-build.0258.tgz
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-7016) CI failure: ServerStartupRedundancyRecoveryNotificationTest > startupReportsOnlineOnlyAfterRedundancyRestored FAILED
[
https://issues.apache.org/jira/browse/GEODE-7016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Hutchison updated GEODE-7016:
--
Attachment: acceptancetestfiles-OpenJDK11-1.14.0-build.0628 (2).tgz
> CI failure: ServerStartupRedundancyRecoveryNotificationTest >
> startupReportsOnlineOnlyAfterRedundancyRestored FAILED
>
>
> Key: GEODE-7016
> URL: https://issues.apache.org/jira/browse/GEODE-7016
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Affects Versions: 1.10.0
>Reporter: Anilkumar Gingade
>Assignee: Kirk Lund
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.14.0
>
> Attachments: acceptancetestfiles-OpenJDK11-1.14.0-build.0628 (1).tgz,
> acceptancetestfiles-OpenJDK11-1.14.0-build.0628 (2).tgz
>
>
> {noformat}
> org.apache.geode.launchers.ServerStartupRedundancyRecoveryNotificationTest >
> startupReportsOnlineOnlyAfterRedundancyRestored FAILED
> org.junit.ComparisonFailure: expected:<[0]> but was:<[1]>
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshExecution.awaitTermination(GfshExecution.java:125)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:125)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:112)
> at
> org.apache.geode.launchers.ServerStartupRedundancyRecoveryNotificationTest.startupReportsOnlineOnlyAfterRedundancyRestored(ServerStartupRedundancyRecoveryNotificationTest.java:142)
> org.junit.ComparisonFailure: expected:<[0]> but was:<[1]>
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshExecution.awaitTermination(GfshExecution.java:125)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:125)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:112)
> at
> org.apache.geode.launchers.ServerStartupRedundancyRecoveryNotificationTest.stopAllMembers(ServerStartupRedundancyRecoveryNotificationTest.java:128)
> {noformat}
> https://concourse.gemfire-ci.info/teams/main/pipelines/gemfire-develop-main/jobs/AcceptanceTestOpenJDK8/builds/797
> Test report artifacts from this job are available at:
> gs://gemfire-test-artifacts/builds/gemfire-develop-main/9.9.0-build.0258/test-artifacts/1564078711/acceptancetestfiles-OpenJDK8-9.9.0-build.0258.tgz
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-7016) CI failure: ServerStartupRedundancyRecoveryNotificationTest > startupReportsOnlineOnlyAfterRedundancyRestored FAILED
[
https://issues.apache.org/jira/browse/GEODE-7016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Hutchison updated GEODE-7016:
--
Attachment: acceptancetestfiles-OpenJDK11-1.14.0-build.0628 (1).tgz
> CI failure: ServerStartupRedundancyRecoveryNotificationTest >
> startupReportsOnlineOnlyAfterRedundancyRestored FAILED
>
>
> Key: GEODE-7016
> URL: https://issues.apache.org/jira/browse/GEODE-7016
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Affects Versions: 1.10.0
>Reporter: Anilkumar Gingade
>Assignee: Kirk Lund
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.14.0
>
> Attachments: acceptancetestfiles-OpenJDK11-1.14.0-build.0628 (1).tgz
>
>
> {noformat}
> org.apache.geode.launchers.ServerStartupRedundancyRecoveryNotificationTest >
> startupReportsOnlineOnlyAfterRedundancyRestored FAILED
> org.junit.ComparisonFailure: expected:<[0]> but was:<[1]>
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshExecution.awaitTermination(GfshExecution.java:125)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:125)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:112)
> at
> org.apache.geode.launchers.ServerStartupRedundancyRecoveryNotificationTest.startupReportsOnlineOnlyAfterRedundancyRestored(ServerStartupRedundancyRecoveryNotificationTest.java:142)
> org.junit.ComparisonFailure: expected:<[0]> but was:<[1]>
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshExecution.awaitTermination(GfshExecution.java:125)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:125)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:112)
> at
> org.apache.geode.launchers.ServerStartupRedundancyRecoveryNotificationTest.stopAllMembers(ServerStartupRedundancyRecoveryNotificationTest.java:128)
> {noformat}
> https://concourse.gemfire-ci.info/teams/main/pipelines/gemfire-develop-main/jobs/AcceptanceTestOpenJDK8/builds/797
> Test report artifacts from this job are available at:
> gs://gemfire-test-artifacts/builds/gemfire-develop-main/9.9.0-build.0258/test-artifacts/1564078711/acceptancetestfiles-OpenJDK8-9.9.0-build.0258.tgz
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Reopened] (GEODE-7016) CI failure: ServerStartupRedundancyRecoveryNotificationTest > startupReportsOnlineOnlyAfterRedundancyRestored FAILED
[
https://issues.apache.org/jira/browse/GEODE-7016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Hutchison reopened GEODE-7016:
---
> CI failure: ServerStartupRedundancyRecoveryNotificationTest >
> startupReportsOnlineOnlyAfterRedundancyRestored FAILED
>
>
> Key: GEODE-7016
> URL: https://issues.apache.org/jira/browse/GEODE-7016
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Affects Versions: 1.10.0
>Reporter: Anilkumar Gingade
>Assignee: Kirk Lund
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.14.0
>
>
> {noformat}
> org.apache.geode.launchers.ServerStartupRedundancyRecoveryNotificationTest >
> startupReportsOnlineOnlyAfterRedundancyRestored FAILED
> org.junit.ComparisonFailure: expected:<[0]> but was:<[1]>
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshExecution.awaitTermination(GfshExecution.java:125)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:125)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:112)
> at
> org.apache.geode.launchers.ServerStartupRedundancyRecoveryNotificationTest.startupReportsOnlineOnlyAfterRedundancyRestored(ServerStartupRedundancyRecoveryNotificationTest.java:142)
> org.junit.ComparisonFailure: expected:<[0]> but was:<[1]>
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshExecution.awaitTermination(GfshExecution.java:125)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:125)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:112)
> at
> org.apache.geode.launchers.ServerStartupRedundancyRecoveryNotificationTest.stopAllMembers(ServerStartupRedundancyRecoveryNotificationTest.java:128)
> {noformat}
> https://concourse.gemfire-ci.info/teams/main/pipelines/gemfire-develop-main/jobs/AcceptanceTestOpenJDK8/builds/797
> Test report artifacts from this job are available at:
> gs://gemfire-test-artifacts/builds/gemfire-develop-main/9.9.0-build.0258/test-artifacts/1564078711/acceptancetestfiles-OpenJDK8-9.9.0-build.0258.tgz
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-7017) CI failure: org.apache.geode.launchers.ServerStartupValueRecoveryNotificationTest > startupReportsOnlineOnlyAfterRedundancyRestored
[
https://issues.apache.org/jira/browse/GEODE-7017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Hutchison updated GEODE-7017:
--
Attachment: acceptancetestfiles-OpenJDK11-1.14.0-build.0628.tgz
> CI failure:
> org.apache.geode.launchers.ServerStartupValueRecoveryNotificationTest >
> startupReportsOnlineOnlyAfterRedundancyRestored
> ---
>
> Key: GEODE-7017
> URL: https://issues.apache.org/jira/browse/GEODE-7017
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Affects Versions: 1.10.0
>Reporter: Anilkumar Gingade
>Assignee: Mark Hanson
>Priority: Major
> Attachments: acceptancetestfiles-OpenJDK11-1.14.0-build.0628.tgz
>
>
> {noformat}
> org.apache.geode.launchers.ServerStartupValueRecoveryNotificationTest >
> startupReportsOnlineOnlyAfterRedundancyRestored FAILED
> org.junit.ComparisonFailure: expected:<[0]> but was:<[1]>
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshExecution.awaitTermination(GfshExecution.java:125)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:125)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:112)
> at
> org.apache.geode.launchers.ServerStartupValueRecoveryNotificationTest.persistentRegionThatRequiresValueRecovery(ServerStartupValueRecoveryNotificationTest.java:120)
> {noformat}
> https://concourse.gemfire-ci.info/teams/main/pipelines/gemfire-develop-main/jobs/AcceptanceTestOpenJDK8/builds/797
> Test report artifacts from this job are available at:
> gs://gemfire-test-artifacts/builds/gemfire-develop-main/9.9.0-build.0258/test-artifacts/1564078711/acceptancetestfiles-OpenJDK8-9.9.0-build.0258.tgz
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-7017) CI failure: org.apache.geode.launchers.ServerStartupValueRecoveryNotificationTest > startupReportsOnlineOnlyAfterRedundancyRestored
[
https://issues.apache.org/jira/browse/GEODE-7017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17270241#comment-17270241
]
John Hutchison commented on GEODE-7017:
---
seen in CI run :
org.apache.geode.launchers.ServerStartupValueRecoveryNotificationTest >
startupReportsOnlineOnlyAfterRedundancyRestored FAILED
org.junit.ComparisonFailure: [Exit value from process started by
[a3a70e5ecf4d838f: gfsh -e connect --locator=localhost[23137] -e start server
--name=server1 --dir=/tmp/junit2110431257149045019/server1secondfolder
--locators=localhost[23137]]] expected:<[0]> but was:<[1]>
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.test.junit.rules.gfsh.GfshExecution.awaitTermination(GfshExecution.java:103)
at
org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:143)
at
org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:152)
at
org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:118)
at
org.apache.geode.launchers.ServerStartupValueRecoveryNotificationTest.startupReportsOnlineOnlyAfterRedundancyRestored(ServerStartupValueRecoveryNotificationTest.java:146)
=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0628/test-results/acceptanceTest/1611279518/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> CI failure:
> org.apache.geode.launchers.ServerStartupValueRecoveryNotificationTest >
> startupReportsOnlineOnlyAfterRedundancyRestored
> ---
>
> Key: GEODE-7017
> URL: https://issues.apache.org/jira/browse/GEODE-7017
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Affects Versions: 1.10.0
>Reporter: Anilkumar Gingade
>Assignee: Mark Hanson
>Priority: Major
> Attachments: acceptancetestfiles-OpenJDK11-1.14.0-build.0628.tgz
>
>
> {noformat}
> org.apache.geode.launchers.ServerStartupValueRecoveryNotificationTest >
> startupReportsOnlineOnlyAfterRedundancyRestored FAILED
> org.junit.ComparisonFailure: expected:<[0]> but was:<[1]>
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshExecution.awaitTermination(GfshExecution.java:125)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:125)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:112)
> at
> org.apache.geode.launchers.ServerStartupValueRecoveryNotificationTest.persistentRegionThatRequiresValueRecovery(ServerStartupValueRecoveryNotificationTest.java:120)
> {noformat}
> https://concourse.gemfire-ci.info/teams/main/pipelines/gemfire-develop-main/jobs/AcceptanceTestOpenJDK8/builds/797
> Test report artifacts from this job are available at:
> gs://gemfire-test-artifacts/builds/gemfire-develop-main/9.9.0-build.0258/test-artifacts/1564078711/acceptancetestfiles-OpenJDK8-9.9.0-build.0258.tgz
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-8864) finish implementation of Redis HScan Command
John Hutchison created GEODE-8864: - Summary: finish implementation of Redis HScan Command Key: GEODE-8864 URL: https://issues.apache.org/jira/browse/GEODE-8864 Project: Geode Issue Type: New Feature Components: redis Reporter: John Hutchison -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-8840) implement redis RENAMENX command
John Hutchison created GEODE-8840: - Summary: implement redis RENAMENX command Key: GEODE-8840 URL: https://issues.apache.org/jira/browse/GEODE-8840 Project: Geode Issue Type: Improvement Components: redis Reporter: John Hutchison -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-8823) Refactor RedisStats IntegrationTest
John Hutchison created GEODE-8823: - Summary: Refactor RedisStats IntegrationTest Key: GEODE-8823 URL: https://issues.apache.org/jira/browse/GEODE-8823 Project: Geode Issue Type: Improvement Components: redis Reporter: John Hutchison -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8712) CI failure: testReplicatedSerialPropagationWithRemoteReceiverRestartedOnOtherNode
[ https://issues.apache.org/jira/browse/GEODE-8712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17260748#comment-17260748 ] John Hutchison commented on GEODE-8712: --- sorry about that- details filled in. > CI failure: > testReplicatedSerialPropagationWithRemoteReceiverRestartedOnOtherNode > - > > Key: GEODE-8712 > URL: https://issues.apache.org/jira/browse/GEODE-8712 > Project: Geode > Issue Type: Bug >Reporter: John Hutchison >Priority: Major > Labels: ci > > failed ci build : > https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/621 > > org.apache.geode.internal.cache.wan.offheap.SerialWANPropagationOffHeapDUnitTest > > testReplicatedSerialPropagationWithRemoteReceiverRestartedOnOtherNode > FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.internal.cache.wan.serial.SerialWANPropagationDUnitTest$$Lambda$181/1328086690.run > in VM 4 running on Host 3e4042fb1cd7 with 8 VMs > Caused by: > org.awaitility.core.ConditionTimeoutException: Assertion condition > defined as a lambda expression in > org.apache.geode.internal.cache.wan.WANTestBase that uses java.util.Set, > java.util.Setint Expected queue entries: 0 but actual entries: 8000 > expected:<0> but was:<8000> within 5 minutes. > Caused by: > java.lang.AssertionError: Expected queue entries: 0 but actual > entries: 8000 expected:<0> but was:<8000> > java.lang.AssertionError: Suspicious strings were written to the log > during this run. > Fix the strings or use IgnoredException.addIgnoredException to ignore. > Found suspect string in 'dunit_suspect-vm4.log' at line 686 > [fatal 2020/11/13 18:09:30.989 GMT for GatewaySender_ln> tid=619] Stopping the processor because the following > exception occurred while processing a batch: > java.lang.NullPointerException > at > org.apache.geode.internal.cache.wan.GatewaySenderEventRemoteDispatcher.getConnection(GatewaySenderEventRemoteDispatcher.java:299) > at > org.apache.geode.internal.cache.wan.GatewaySenderEventRemoteDispatcher.readAcknowledgement(GatewaySenderEventRemoteDispatcher.java:107) > at > org.apache.geode.internal.cache.wan.GatewaySenderEventRemoteDispatcher$AckReaderThread.run(GatewaySenderEventRemoteDispatcher.java:605) > =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0484/test-results/distributedTest/1605295952/ > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Test report artifacts from this job are available at: > http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0484/test-artifacts/1605295952/distributedtestfiles-OpenJDK8-1.14.0-build.0484.tgz > [test artifact too large to upload to jira; contact reporter for artifact if > needed] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-8712) CI failure: testReplicatedSerialPropagationWithRemoteReceiverRestartedOnOtherNode
[ https://issues.apache.org/jira/browse/GEODE-8712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Hutchison updated GEODE-8712: -- Description: failed ci build : https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/621 org.apache.geode.internal.cache.wan.offheap.SerialWANPropagationOffHeapDUnitTest > testReplicatedSerialPropagationWithRemoteReceiverRestartedOnOtherNode FAILED org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.internal.cache.wan.serial.SerialWANPropagationDUnitTest$$Lambda$181/1328086690.run in VM 4 running on Host 3e4042fb1cd7 with 8 VMs Caused by: org.awaitility.core.ConditionTimeoutException: Assertion condition defined as a lambda expression in org.apache.geode.internal.cache.wan.WANTestBase that uses java.util.Set, java.util.Setint Expected queue entries: 0 but actual entries: 8000 expected:<0> but was:<8000> within 5 minutes. Caused by: java.lang.AssertionError: Expected queue entries: 0 but actual entries: 8000 expected:<0> but was:<8000> java.lang.AssertionError: Suspicious strings were written to the log during this run. Fix the strings or use IgnoredException.addIgnoredException to ignore. Found suspect string in 'dunit_suspect-vm4.log' at line 686 [fatal 2020/11/13 18:09:30.989 GMT tid=619] Stopping the processor because the following exception occurred while processing a batch: java.lang.NullPointerException at org.apache.geode.internal.cache.wan.GatewaySenderEventRemoteDispatcher.getConnection(GatewaySenderEventRemoteDispatcher.java:299) at org.apache.geode.internal.cache.wan.GatewaySenderEventRemoteDispatcher.readAcknowledgement(GatewaySenderEventRemoteDispatcher.java:107) at org.apache.geode.internal.cache.wan.GatewaySenderEventRemoteDispatcher$AckReaderThread.run(GatewaySenderEventRemoteDispatcher.java:605) =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0484/test-results/distributedTest/1605295952/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test report artifacts from this job are available at: http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0484/test-artifacts/1605295952/distributedtestfiles-OpenJDK8-1.14.0-build.0484.tgz [test artifact too large to upload to jira; contact reporter for artifact if needed] was: failed ci build : https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/621 org.apache.geode.internal.cache.wan.offheap.SerialWANPropagationOffHeapDUnitTest > testReplicatedSerialPropagationWithRemoteReceiverRestartedOnOtherNode FAILED org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.internal.cache.wan.serial.SerialWANPropagationDUnitTest$$Lambda$181/1328086690.run in VM 4 running on Host 3e4042fb1cd7 with 8 VMs Caused by: org.awaitility.core.ConditionTimeoutException: Assertion condition defined as a lambda expression in org.apache.geode.internal.cache.wan.WANTestBase that uses java.util.Set, java.util.Setint Expected queue entries: 0 but actual entries: 8000 expected:<0> but was:<8000> within 5 minutes. Caused by: java.lang.AssertionError: Expected queue entries: 0 but actual entries: 8000 expected:<0> but was:<8000> java.lang.AssertionError: Suspicious strings were written to the log during this run. Fix the strings or use IgnoredException.addIgnoredException to ignore. Found suspect string in 'dunit_suspect-vm4.log' at line 686 [fatal 2020/11/13 18:09:30.989 GMT tid=619] Stopping the processor because the following exception occurred while processing a batch: java.lang.NullPointerException at org.apache.geode.internal.cache.wan.GatewaySenderEventRemoteDispatcher.getConnection(GatewaySenderEventRemoteDispatcher.java:299) at org.apache.geode.internal.cache.wan.GatewaySenderEventRemoteDispatcher.readAcknowledgement(GatewaySenderEventRemoteDispatcher.java:107) at org.apache.geode.internal.cache.wan.GatewaySenderEventRemoteDispatcher$AckReaderThread.run(GatewaySenderEventRemoteDispatcher.java:605) > CI failure: > testReplicatedSerialPropagationWithRemoteReceiverRestartedOnOtherNode > - > > Key: GEODE-8712 > URL: https://issues.apache.org/jira/browse/GEODE-8712 > Project: Geode > Issue Type: Bug >Reporter: John Hutchison >Priority: Major > > failed ci build : > https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/6
[jira] [Updated] (GEODE-8712) testReplicatedSerialPropagationWithRemoteReceiverRestartedOnOtherNode
[ https://issues.apache.org/jira/browse/GEODE-8712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Hutchison updated GEODE-8712: -- Description: failed ci build : https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/621 org.apache.geode.internal.cache.wan.offheap.SerialWANPropagationOffHeapDUnitTest > testReplicatedSerialPropagationWithRemoteReceiverRestartedOnOtherNode FAILED org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.internal.cache.wan.serial.SerialWANPropagationDUnitTest$$Lambda$181/1328086690.run in VM 4 running on Host 3e4042fb1cd7 with 8 VMs Caused by: org.awaitility.core.ConditionTimeoutException: Assertion condition defined as a lambda expression in org.apache.geode.internal.cache.wan.WANTestBase that uses java.util.Set, java.util.Setint Expected queue entries: 0 but actual entries: 8000 expected:<0> but was:<8000> within 5 minutes. Caused by: java.lang.AssertionError: Expected queue entries: 0 but actual entries: 8000 expected:<0> but was:<8000> java.lang.AssertionError: Suspicious strings were written to the log during this run. Fix the strings or use IgnoredException.addIgnoredException to ignore. Found suspect string in 'dunit_suspect-vm4.log' at line 686 [fatal 2020/11/13 18:09:30.989 GMT tid=619] Stopping the processor because the following exception occurred while processing a batch: java.lang.NullPointerException at org.apache.geode.internal.cache.wan.GatewaySenderEventRemoteDispatcher.getConnection(GatewaySenderEventRemoteDispatcher.java:299) at org.apache.geode.internal.cache.wan.GatewaySenderEventRemoteDispatcher.readAcknowledgement(GatewaySenderEventRemoteDispatcher.java:107) at org.apache.geode.internal.cache.wan.GatewaySenderEventRemoteDispatcher$AckReaderThread.run(GatewaySenderEventRemoteDispatcher.java:605) was: org.apache.geode.internal.cache.wan.offheap.SerialWANPropagationOffHeapDUnitTest > testReplicatedSerialPropagationWithRemoteReceiverRestartedOnOtherNode FAILED org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.internal.cache.wan.serial.SerialWANPropagationDUnitTest$$Lambda$181/1328086690.run in VM 4 running on Host 3e4042fb1cd7 with 8 VMs Caused by: org.awaitility.core.ConditionTimeoutException: Assertion condition defined as a lambda expression in org.apache.geode.internal.cache.wan.WANTestBase that uses java.util.Set, java.util.Setint Expected queue entries: 0 but actual entries: 8000 expected:<0> but was:<8000> within 5 minutes. Caused by: java.lang.AssertionError: Expected queue entries: 0 but actual entries: 8000 expected:<0> but was:<8000> java.lang.AssertionError: Suspicious strings were written to the log during this run. Fix the strings or use IgnoredException.addIgnoredException to ignore. Found suspect string in 'dunit_suspect-vm4.log' at line 686 [fatal 2020/11/13 18:09:30.989 GMT tid=619] Stopping the processor because the following exception occurred while processing a batch: java.lang.NullPointerException at org.apache.geode.internal.cache.wan.GatewaySenderEventRemoteDispatcher.getConnection(GatewaySenderEventRemoteDispatcher.java:299) at org.apache.geode.internal.cache.wan.GatewaySenderEventRemoteDispatcher.readAcknowledgement(GatewaySenderEventRemoteDispatcher.java:107) at org.apache.geode.internal.cache.wan.GatewaySenderEventRemoteDispatcher$AckReaderThread.run(GatewaySenderEventRemoteDispatcher.java:605) > testReplicatedSerialPropagationWithRemoteReceiverRestartedOnOtherNode > - > > Key: GEODE-8712 > URL: https://issues.apache.org/jira/browse/GEODE-8712 > Project: Geode > Issue Type: Bug >Reporter: John Hutchison >Priority: Major > > failed ci build : > https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/621 > > org.apache.geode.internal.cache.wan.offheap.SerialWANPropagationOffHeapDUnitTest > > testReplicatedSerialPropagationWithRemoteReceiverRestartedOnOtherNode > FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.internal.cache.wan.serial.SerialWANPropagationDUnitTest$$Lambda$181/1328086690.run > in VM 4 running on Host 3e4042fb1cd7 with 8 VMs > Caused by: > org.awaitility.core.ConditionTimeoutException: Assertion condition > defined as a lambda expression in > org.apache.geode.internal.cache.wan.WANTestBase that uses java.util.Set, > java.util.Setint Expected queue entries: 0 but actual entries: 8000 > expected:<0> but was:<8000> within 5 minutes. > Caused by: >
[jira] [Updated] (GEODE-8712) testReplicatedSerialPropagationWithRemoteReceiverRestartedOnOtherNode
[ https://issues.apache.org/jira/browse/GEODE-8712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Hutchison updated GEODE-8712: -- Description: org.apache.geode.internal.cache.wan.offheap.SerialWANPropagationOffHeapDUnitTest > testReplicatedSerialPropagationWithRemoteReceiverRestartedOnOtherNode FAILED org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.internal.cache.wan.serial.SerialWANPropagationDUnitTest$$Lambda$181/1328086690.run in VM 4 running on Host 3e4042fb1cd7 with 8 VMs Caused by: org.awaitility.core.ConditionTimeoutException: Assertion condition defined as a lambda expression in org.apache.geode.internal.cache.wan.WANTestBase that uses java.util.Set, java.util.Setint Expected queue entries: 0 but actual entries: 8000 expected:<0> but was:<8000> within 5 minutes. Caused by: java.lang.AssertionError: Expected queue entries: 0 but actual entries: 8000 expected:<0> but was:<8000> java.lang.AssertionError: Suspicious strings were written to the log during this run. Fix the strings or use IgnoredException.addIgnoredException to ignore. Found suspect string in 'dunit_suspect-vm4.log' at line 686 [fatal 2020/11/13 18:09:30.989 GMT tid=619] Stopping the processor because the following exception occurred while processing a batch: java.lang.NullPointerException at org.apache.geode.internal.cache.wan.GatewaySenderEventRemoteDispatcher.getConnection(GatewaySenderEventRemoteDispatcher.java:299) at org.apache.geode.internal.cache.wan.GatewaySenderEventRemoteDispatcher.readAcknowledgement(GatewaySenderEventRemoteDispatcher.java:107) at org.apache.geode.internal.cache.wan.GatewaySenderEventRemoteDispatcher$AckReaderThread.run(GatewaySenderEventRemoteDispatcher.java:605) > testReplicatedSerialPropagationWithRemoteReceiverRestartedOnOtherNode > - > > Key: GEODE-8712 > URL: https://issues.apache.org/jira/browse/GEODE-8712 > Project: Geode > Issue Type: Bug >Reporter: John Hutchison >Priority: Major > > org.apache.geode.internal.cache.wan.offheap.SerialWANPropagationOffHeapDUnitTest > > testReplicatedSerialPropagationWithRemoteReceiverRestartedOnOtherNode > FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.internal.cache.wan.serial.SerialWANPropagationDUnitTest$$Lambda$181/1328086690.run > in VM 4 running on Host 3e4042fb1cd7 with 8 VMs > Caused by: > org.awaitility.core.ConditionTimeoutException: Assertion condition > defined as a lambda expression in > org.apache.geode.internal.cache.wan.WANTestBase that uses java.util.Set, > java.util.Setint Expected queue entries: 0 but actual entries: 8000 > expected:<0> but was:<8000> within 5 minutes. > Caused by: > java.lang.AssertionError: Expected queue entries: 0 but actual > entries: 8000 expected:<0> but was:<8000> > java.lang.AssertionError: Suspicious strings were written to the log > during this run. > Fix the strings or use IgnoredException.addIgnoredException to ignore. > Found suspect string in 'dunit_suspect-vm4.log' at line 686 > [fatal 2020/11/13 18:09:30.989 GMT for GatewaySender_ln> tid=619] Stopping the processor because the following > exception occurred while processing a batch: > java.lang.NullPointerException > at > org.apache.geode.internal.cache.wan.GatewaySenderEventRemoteDispatcher.getConnection(GatewaySenderEventRemoteDispatcher.java:299) > at > org.apache.geode.internal.cache.wan.GatewaySenderEventRemoteDispatcher.readAcknowledgement(GatewaySenderEventRemoteDispatcher.java:107) > at > org.apache.geode.internal.cache.wan.GatewaySenderEventRemoteDispatcher$AckReaderThread.run(GatewaySenderEventRemoteDispatcher.java:605) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-8794) Support redis HELLO command
[
https://issues.apache.org/jira/browse/GEODE-8794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Hutchison resolved GEODE-8794.
---
Resolution: Fixed
> Support redis HELLO command
> ---
>
> Key: GEODE-8794
> URL: https://issues.apache.org/jira/browse/GEODE-8794
> Project: Geode
> Issue Type: New Feature
> Components: redis
>Reporter: Jens Deppe
>Priority: Major
> Labels: pull-request-available
>
> The latest lettuce client (v6) tries to determine which version of redis is
> being used by sending a {{HELLO}} command. When authentication is not enabled
> we will just return {{-ERR unknown command}} which will then cause lettuce to
> use the correct protocol. However, when auth is enabled, the first thing we
> expect is an {{AUTH}} command. If we receive anything else we'll respond with
> {{-NOAUTH}} which results in an error.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (GEODE-8784) Create matching Geode stats for all Redis INFO stats
[ https://issues.apache.org/jira/browse/GEODE-8784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Hutchison resolved GEODE-8784. --- Resolution: Fixed > Create matching Geode stats for all Redis INFO stats > > > Key: GEODE-8784 > URL: https://issues.apache.org/jira/browse/GEODE-8784 > Project: Geode > Issue Type: Bug > Components: redis >Reporter: John Hutchison >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-8784) Create matching Geode stats for all Redis INFO stats
John Hutchison created GEODE-8784: - Summary: Create matching Geode stats for all Redis INFO stats Key: GEODE-8784 URL: https://issues.apache.org/jira/browse/GEODE-8784 Project: Geode Issue Type: Bug Components: redis Reporter: John Hutchison -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-8766) dUnit Failure for Redis HashesIntegrationTest
[ https://issues.apache.org/jira/browse/GEODE-8766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Hutchison resolved GEODE-8766. --- Resolution: Fixed looks to be test issue. test code changed to reduce likelihood of collisions during test setup. https://github.com/apache/geode/pull/5841 > dUnit Failure for Redis HashesIntegrationTest > - > > Key: GEODE-8766 > URL: https://issues.apache.org/jira/browse/GEODE-8766 > Project: Geode > Issue Type: Bug > Components: redis >Reporter: John Hutchison >Assignee: John Hutchison >Priority: Major > Labels: pull-request-available > > [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/IntegrationTestOpenJDK11/builds/610] > org.apache.geode.redis.internal.executor.hash.HashesIntegrationTest > > testConcurrentHGetAll FAILED > > org.junit.ComparisonFailure: expected:<[800]0L> but was:<[]0L> > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-8766) dUnit Failure for Redis HashesIntegrationTest
[ https://issues.apache.org/jira/browse/GEODE-8766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Hutchison reassigned GEODE-8766: - Assignee: John Hutchison > dUnit Failure for Redis HashesIntegrationTest > - > > Key: GEODE-8766 > URL: https://issues.apache.org/jira/browse/GEODE-8766 > Project: Geode > Issue Type: Bug > Components: redis >Reporter: John Hutchison >Assignee: John Hutchison >Priority: Major > > [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/IntegrationTestOpenJDK11/builds/610] > org.apache.geode.redis.internal.executor.hash.HashesIntegrationTest > > testConcurrentHGetAll FAILED > > org.junit.ComparisonFailure: expected:<[800]0L> but was:<[]0L> > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (GEODE-8766) dUnit Failure for Redis HashesIntegrationTest
[ https://issues.apache.org/jira/browse/GEODE-8766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17243544#comment-17243544 ] John Hutchison edited comment on GEODE-8766 at 12/3/20, 10:18 PM: -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0532/test-results/integrationTest/1607020031/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test report artifacts from this job are available at: http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0532/test-artifacts/1607020031/integrationtestfiles-OpenJDK11-1.14.0-build.0532.tgz (if artifact is gone ask [~John Hutch] - was too large to fit in ticket was (Author: john hutch): =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0532/test-results/integrationTest/1607020031/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test report artifacts from this job are available at: http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0532/test-artifacts/1607020031/integrationtestfiles-OpenJDK11-1.14.0-build.0532.tgz (if artifact is gone ask [~John Hutch]hutchisonjo) - was too large to fit in ticket > dUnit Failure for Redis HashesIntegrationTest > - > > Key: GEODE-8766 > URL: https://issues.apache.org/jira/browse/GEODE-8766 > Project: Geode > Issue Type: Bug > Components: redis >Reporter: John Hutchison >Priority: Major > > [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/IntegrationTestOpenJDK11/builds/610] > org.apache.geode.redis.internal.executor.hash.HashesIntegrationTest > > testConcurrentHGetAll FAILED > > org.junit.ComparisonFailure: expected:<[800]0L> but was:<[]0L> > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (GEODE-8766) dUnit Failure for Redis HashesIntegrationTest
[ https://issues.apache.org/jira/browse/GEODE-8766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17243544#comment-17243544 ] John Hutchison edited comment on GEODE-8766 at 12/3/20, 10:17 PM: -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0532/test-results/integrationTest/1607020031/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test report artifacts from this job are available at: http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0532/test-artifacts/1607020031/integrationtestfiles-OpenJDK11-1.14.0-build.0532.tgz (if artifact is gone ask [~John Hutch]hutchisonjo) - was too large to fit in ticket was (Author: john hutch): =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0532/test-results/integrationTest/1607020031/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test report artifacts from this job are available at: http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0532/test-artifacts/1607020031/integrationtestfiles-OpenJDK11-1.14.0-build.0532.tgz > dUnit Failure for Redis HashesIntegrationTest > - > > Key: GEODE-8766 > URL: https://issues.apache.org/jira/browse/GEODE-8766 > Project: Geode > Issue Type: Bug > Components: redis >Reporter: John Hutchison >Priority: Major > > [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/IntegrationTestOpenJDK11/builds/610] > org.apache.geode.redis.internal.executor.hash.HashesIntegrationTest > > testConcurrentHGetAll FAILED > > org.junit.ComparisonFailure: expected:<[800]0L> but was:<[]0L> > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8766) dUnit Failure for Redis HashesIntegrationTest
[ https://issues.apache.org/jira/browse/GEODE-8766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17243544#comment-17243544 ] John Hutchison commented on GEODE-8766: --- =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0532/test-results/integrationTest/1607020031/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test report artifacts from this job are available at: http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0532/test-artifacts/1607020031/integrationtestfiles-OpenJDK11-1.14.0-build.0532.tgz > dUnit Failure for Redis HashesIntegrationTest > - > > Key: GEODE-8766 > URL: https://issues.apache.org/jira/browse/GEODE-8766 > Project: Geode > Issue Type: Bug > Components: redis >Reporter: John Hutchison >Priority: Major > > [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/IntegrationTestOpenJDK11/builds/610] > org.apache.geode.redis.internal.executor.hash.HashesIntegrationTest > > testConcurrentHGetAll FAILED > > org.junit.ComparisonFailure: expected:<[800]0L> but was:<[]0L> > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-8766) dUnit Failure for Redis HashesIntegrationTest
John Hutchison created GEODE-8766: - Summary: dUnit Failure for Redis HashesIntegrationTest Key: GEODE-8766 URL: https://issues.apache.org/jira/browse/GEODE-8766 Project: Geode Issue Type: Bug Components: redis Reporter: John Hutchison [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/IntegrationTestOpenJDK11/builds/610] org.apache.geode.redis.internal.executor.hash.HashesIntegrationTest > testConcurrentHGetAll FAILED org.junit.ComparisonFailure: expected:<[800]0L> but was:<[]0L> -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (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
]
John Hutchison resolved GEODE-8719.
---
Resolution: Fixed
> 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
>Reporter: Sarah Abbey
>Assignee: John Hutchison
>Priority: Minor
>
> 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.3.4#803005)
[jira] [Assigned] (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
]
John Hutchison reassigned GEODE-8719:
-
Assignee: John Hutchison
> 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
>Reporter: Sarah Abbey
>Assignee: John Hutchison
>Priority: Minor
>
> 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.3.4#803005)
[jira] [Resolved] (GEODE-8715) Redis INFO command 'Keyspace' section should not be present if no keys in database
[ https://issues.apache.org/jira/browse/GEODE-8715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Hutchison resolved GEODE-8715. --- Resolution: Fixed > Redis INFO command 'Keyspace' section should not be present if no keys in > database > -- > > Key: GEODE-8715 > URL: https://issues.apache.org/jira/browse/GEODE-8715 > Project: Geode > Issue Type: Improvement > Components: redis >Reporter: John Hutchison >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=17234071#comment-17234071
]
John Hutchison commented on GEODE-8719:
---
ran locally and in gcp with dunit runner multiple times, unable to replicate.
Closing ticket for now. Will investigate further if problem persists
> 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
>Reporter: Sarah Abbey
>Priority: Minor
>
> 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.3.4#803005)
[jira] [Created] (GEODE-8717) Redis INFO Command should only return specified sections when given parameter
John Hutchison created GEODE-8717: - Summary: Redis INFO Command should only return specified sections when given parameter Key: GEODE-8717 URL: https://issues.apache.org/jira/browse/GEODE-8717 Project: Geode Issue Type: Improvement Components: redis Reporter: John Hutchison -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-8715) Redis INFO command 'Keyspace' section should not be present if no keys in database
John Hutchison created GEODE-8715: - Summary: Redis INFO command 'Keyspace' section should not be present if no keys in database Key: GEODE-8715 URL: https://issues.apache.org/jira/browse/GEODE-8715 Project: Geode Issue Type: Improvement Components: redis Reporter: John Hutchison -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8706) testReplicatedSerialPropagationWithRemoteReceiverRestartedOnOtherNode failure in CI
[ https://issues.apache.org/jira/browse/GEODE-8706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17231853#comment-17231853 ] John Hutchison commented on GEODE-8706: --- possibly recurrence of https://issues.apache.org/jira/browse/GEODE-8485 > testReplicatedSerialPropagationWithRemoteReceiverRestartedOnOtherNode failure > in CI > --- > > Key: GEODE-8706 > URL: https://issues.apache.org/jira/browse/GEODE-8706 > Project: Geode > Issue Type: Improvement >Reporter: John Hutchison >Priority: Major > > __org.apache.geode.internal.cache.wan.offheap.SerialWANPropagationOffHeapDUnitTest > > testReplicatedSerialPropagationWithRemoteReceiverRestartedOnOtherNode > FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.internal.cache.wan.serial.SerialWANPropagationDUnitTest$$Lambda$181/1328086690.run > in VM 4 running on Host 3e4042fb1cd7 with 8 VMs > Caused by: > org.awaitility.core.ConditionTimeoutException: Assertion condition defined > as a lambda expression in org.apache.geode.internal.cache.wan.WANTestBase > that uses java.util.Set, java.util.Setint Expected queue entries: 0 but > actual entries: 8000 expected:<0> but was:<8000> within 5 minutes. > Caused by: > java.lang.AssertionError: Expected queue entries: 0 but actual entries: 8000 > expected:<0> but was:<8000> > java.lang.AssertionError: Suspicious strings were written to the log during > this run. > Fix the strings or use IgnoredException.addIgnoredException to ignore. > -- > Found suspect string in 'dunit_suspect-vm4.log' at line 68 > [fatal 2020/11/13 18:09:30.989 GMT for GatewaySender_ln> tid=619] Stopping the processor because the following > exception occurred while processing a batch: > java.lang.NullPointerException > at > org.apache.geode.internal.cache.wan.GatewaySenderEventRemoteDispatcher.getConnection(GatewaySenderEventRemoteDispatcher.java:299) > at > org.apache.geode.internal.cache.wan.GatewaySenderEventRemoteDispatcher.readAcknowledgement(GatewaySenderEventRemoteDispatcher.java:107) > at > org.apache.geode.internal.cache.wan.GatewaySenderEventRemoteDispatcher$AckReaderThread.run(GatewaySenderEventRemoteDispatcher.java:605) > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8706) testReplicatedSerialPropagationWithRemoteReceiverRestartedOnOtherNode failure in CI
[ https://issues.apache.org/jira/browse/GEODE-8706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17231803#comment-17231803 ] John Hutchison commented on GEODE-8706: --- =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0484/test-results/distributedTest/1605295952/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test report artifacts from this job are available at: http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0484/test-artifacts/1605295952/distributedtestfiles-OpenJDK8-1.14.0-build.0484.tgz > testReplicatedSerialPropagationWithRemoteReceiverRestartedOnOtherNode failure > in CI > --- > > Key: GEODE-8706 > URL: https://issues.apache.org/jira/browse/GEODE-8706 > Project: Geode > Issue Type: Improvement > Components: redis >Reporter: John Hutchison >Priority: Major > > __org.apache.geode.internal.cache.wan.offheap.SerialWANPropagationOffHeapDUnitTest > > testReplicatedSerialPropagationWithRemoteReceiverRestartedOnOtherNode > FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.internal.cache.wan.serial.SerialWANPropagationDUnitTest$$Lambda$181/1328086690.run > in VM 4 running on Host 3e4042fb1cd7 with 8 VMs > Caused by: > org.awaitility.core.ConditionTimeoutException: Assertion condition defined > as a lambda expression in org.apache.geode.internal.cache.wan.WANTestBase > that uses java.util.Set, java.util.Setint Expected queue entries: 0 but > actual entries: 8000 expected:<0> but was:<8000> within 5 minutes. > Caused by: > java.lang.AssertionError: Expected queue entries: 0 but actual entries: 8000 > expected:<0> but was:<8000> > java.lang.AssertionError: Suspicious strings were written to the log during > this run. > Fix the strings or use IgnoredException.addIgnoredException to ignore. > -- > Found suspect string in 'dunit_suspect-vm4.log' at line 68 > [fatal 2020/11/13 18:09:30.989 GMT for GatewaySender_ln> tid=619] Stopping the processor because the following > exception occurred while processing a batch: > java.lang.NullPointerException > at > org.apache.geode.internal.cache.wan.GatewaySenderEventRemoteDispatcher.getConnection(GatewaySenderEventRemoteDispatcher.java:299) > at > org.apache.geode.internal.cache.wan.GatewaySenderEventRemoteDispatcher.readAcknowledgement(GatewaySenderEventRemoteDispatcher.java:107) > at > org.apache.geode.internal.cache.wan.GatewaySenderEventRemoteDispatcher$AckReaderThread.run(GatewaySenderEventRemoteDispatcher.java:605) > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-8706) testReplicatedSerialPropagationWithRemoteReceiverRestartedOnOtherNode failure in CI
[ https://issues.apache.org/jira/browse/GEODE-8706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Hutchison updated GEODE-8706: -- Description: __org.apache.geode.internal.cache.wan.offheap.SerialWANPropagationOffHeapDUnitTest > testReplicatedSerialPropagationWithRemoteReceiverRestartedOnOtherNode FAILED org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.internal.cache.wan.serial.SerialWANPropagationDUnitTest$$Lambda$181/1328086690.run in VM 4 running on Host 3e4042fb1cd7 with 8 VMs Caused by: org.awaitility.core.ConditionTimeoutException: Assertion condition defined as a lambda expression in org.apache.geode.internal.cache.wan.WANTestBase that uses java.util.Set, java.util.Setint Expected queue entries: 0 but actual entries: 8000 expected:<0> but was:<8000> within 5 minutes. Caused by: java.lang.AssertionError: Expected queue entries: 0 but actual entries: 8000 expected:<0> but was:<8000> java.lang.AssertionError: Suspicious strings were written to the log during this run. Fix the strings or use IgnoredException.addIgnoredException to ignore. -- Found suspect string in 'dunit_suspect-vm4.log' at line 68 [fatal 2020/11/13 18:09:30.989 GMT tid=619] Stopping the processor because the following exception occurred while processing a batch: java.lang.NullPointerException at org.apache.geode.internal.cache.wan.GatewaySenderEventRemoteDispatcher.getConnection(GatewaySenderEventRemoteDispatcher.java:299) at org.apache.geode.internal.cache.wan.GatewaySenderEventRemoteDispatcher.readAcknowledgement(GatewaySenderEventRemoteDispatcher.java:107) at org.apache.geode.internal.cache.wan.GatewaySenderEventRemoteDispatcher$AckReaderThread.run(GatewaySenderEventRemoteDispatcher.java:605) > testReplicatedSerialPropagationWithRemoteReceiverRestartedOnOtherNode failure > in CI > --- > > Key: GEODE-8706 > URL: https://issues.apache.org/jira/browse/GEODE-8706 > Project: Geode > Issue Type: Improvement > Components: redis >Reporter: John Hutchison >Priority: Major > > __org.apache.geode.internal.cache.wan.offheap.SerialWANPropagationOffHeapDUnitTest > > testReplicatedSerialPropagationWithRemoteReceiverRestartedOnOtherNode > FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.internal.cache.wan.serial.SerialWANPropagationDUnitTest$$Lambda$181/1328086690.run > in VM 4 running on Host 3e4042fb1cd7 with 8 VMs > Caused by: > org.awaitility.core.ConditionTimeoutException: Assertion condition defined > as a lambda expression in org.apache.geode.internal.cache.wan.WANTestBase > that uses java.util.Set, java.util.Setint Expected queue entries: 0 but > actual entries: 8000 expected:<0> but was:<8000> within 5 minutes. > Caused by: > java.lang.AssertionError: Expected queue entries: 0 but actual entries: 8000 > expected:<0> but was:<8000> > java.lang.AssertionError: Suspicious strings were written to the log during > this run. > Fix the strings or use IgnoredException.addIgnoredException to ignore. > -- > Found suspect string in 'dunit_suspect-vm4.log' at line 68 > [fatal 2020/11/13 18:09:30.989 GMT for GatewaySender_ln> tid=619] Stopping the processor because the following > exception occurred while processing a batch: > java.lang.NullPointerException > at > org.apache.geode.internal.cache.wan.GatewaySenderEventRemoteDispatcher.getConnection(GatewaySenderEventRemoteDispatcher.java:299) > at > org.apache.geode.internal.cache.wan.GatewaySenderEventRemoteDispatcher.readAcknowledgement(GatewaySenderEventRemoteDispatcher.java:107) > at > org.apache.geode.internal.cache.wan.GatewaySenderEventRemoteDispatcher$AckReaderThread.run(GatewaySenderEventRemoteDispatcher.java:605) > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-8706) testReplicatedSerialPropagationWithRemoteReceiverRestartedOnOtherNode failure in CI
[ https://issues.apache.org/jira/browse/GEODE-8706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Hutchison updated GEODE-8706: -- Summary: testReplicatedSerialPropagationWithRemoteReceiverRestartedOnOtherNode failure in CI (was: Redis INFO command 'Keyspace' section should not be present if no keys in database) > testReplicatedSerialPropagationWithRemoteReceiverRestartedOnOtherNode failure > in CI > --- > > Key: GEODE-8706 > URL: https://issues.apache.org/jira/browse/GEODE-8706 > Project: Geode > Issue Type: Improvement > Components: redis >Reporter: John Hutchison >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-8712) testReplicatedSerialPropagationWithRemoteReceiverRestartedOnOtherNode
John Hutchison created GEODE-8712: - Summary: testReplicatedSerialPropagationWithRemoteReceiverRestartedOnOtherNode Key: GEODE-8712 URL: https://issues.apache.org/jira/browse/GEODE-8712 Project: Geode Issue Type: Bug Reporter: John Hutchison -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-8710) PartitionedFunctionExecutionBenchmark failure
[ https://issues.apache.org/jira/browse/GEODE-8710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Hutchison updated GEODE-8710: -- Description: =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= This benchmark run is the result of comparing 8f8cc7b62be9e7d3a20f18e38fe2cff3228a55bb with baseline 1.13.0 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Commit Message =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= commit 8f8cc7b62be9e7d3a20f18e38fe2cff3228a55bb Author: Sarah <41928668+sabbey37@users.noreply.github.comDate: Fri Nov 13 09:12:29 2020 -0500 GEODE-8704: many CI failures in Jetty9CachingClientServerTest (#5745) =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Benchmark Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= [http://files.apachegeode-ci.info/benchmarks/apache-develop-main/8f8cc7b62be9e7d3a20f18e38fe2cff3228a55bb/benchmarks-apache-develop-main-Benchmark_with_security_manager-456-206679_with_security_manager.tgz|http://files.apachegeode-ci.info/benchmarks/apache-develop-main/8f8cc7b62be9e7d3a20f18e38fe2cff3228a55bb/benchmarks-apache-develop-main-Benchmark_with_security_manager-456-206679_with_security_manager.tgz=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=] [=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=|http://files.apachegeode-ci.info/benchmarks/apache-develop-main/8f8cc7b62be9e7d3a20f18e38fe2cff3228a55bb/benchmarks-apache-develop-main-Benchmark_with_security_manager-456-206679_with_security_manager.tgz=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=] was: =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=This benchmark run is the result of comparing 8f8cc7b62be9e7d3a20f18e38fe2cff3228a55bb with baseline 1.13.0=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Commit Message =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=commit 8f8cc7b62be9e7d3a20f18e38fe2cff3228a55bbAuthor: Sarah <41928668+sabbey37@users.noreply.github.comDate: Fri Nov 13 09:12:29 2020 -0500GEODE-8704: many CI failures in Jetty9CachingClientServerTest (#5745) =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Benchmark Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= http://files.apachegeode-ci.info/benchmarks/apache-develop-main/8f8cc7b62be9e7d3a20f18e38fe2cff3228a55bb/benchmarks-apache-develop-main-Benchmark_with_security_manager-456-206679_with_security_manager.tgz=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > PartitionedFunctionExecutionBenchmark failure > -- > > Key: GEODE-8710 > URL: https://issues.apache.org/jira/browse/GEODE-8710 > Project: Geode > Issue Type: Bug >Reporter: John Hutchison >Priority: Major > > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > This benchmark run is the result of comparing > 8f8cc7b62be9e7d3a20f18e38fe2cff3228a55bb with baseline 1.13.0 > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Commit Message > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > commit 8f8cc7b62be9e7d3a20f18e38fe2cff3228a55bb > Author: Sarah <41928668+sabbey37@users.noreply.github.comDate: Fri Nov 13 > 09:12:29 2020 -0500 > GEODE-8704: many CI failures in Jetty9CachingClientServerTest (#5745) > > =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Benchmark Results URI > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > > [http://files.apachegeode-ci.info/benchmarks/apache-develop-main/8f8cc7b62be9e7d3a20f18e38fe2cff3228a55bb/benchmarks-apache-develop-main-Benchmark_with_security_manager-456-206679_with_security_manager.tgz|http://files.apachegeode-ci.info/benchmarks/apache-develop-main/8f8cc7b62be9e7d3a20f18e38fe2cff3228a55bb/benchmarks-apache-develop-main-Benchmark_with_security_manager-456-206679_with_security_manager.tgz=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=] > [=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=|http://files.apachegeode-ci.info/benchmarks/apache-develop-main/8f8cc7b62be9e7d3a20f18e38fe2cff3228a55bb/benchmarks-apache-develop-main-Benchmark_with_security_manager-456-206679_with_security_manager.tgz=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-8710) PartitionedFunctionExecutionBenchmark failure
John Hutchison created GEODE-8710: - Summary: PartitionedFunctionExecutionBenchmark failure Key: GEODE-8710 URL: https://issues.apache.org/jira/browse/GEODE-8710 Project: Geode Issue Type: Bug Reporter: John Hutchison =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=This benchmark run is the result of comparing 8f8cc7b62be9e7d3a20f18e38fe2cff3228a55bb with baseline 1.13.0=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Commit Message =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=commit 8f8cc7b62be9e7d3a20f18e38fe2cff3228a55bbAuthor: Sarah <41928668+sabbey37@users.noreply.github.comDate: Fri Nov 13 09:12:29 2020 -0500GEODE-8704: many CI failures in Jetty9CachingClientServerTest (#5745) =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Benchmark Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= http://files.apachegeode-ci.info/benchmarks/apache-develop-main/8f8cc7b62be9e7d3a20f18e38fe2cff3228a55bb/benchmarks-apache-develop-main-Benchmark_with_security_manager-456-206679_with_security_manager.tgz=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7710) JMXMBeanReconnectDUnitTest fails intermittently because one locator is missing the LockServiceMXBean
[
https://issues.apache.org/jira/browse/GEODE-7710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17231740#comment-17231740
]
John Hutchison commented on GEODE-7710:
---
11/13/20
=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0484/test-results/distributedTest/1605285407/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Test report artifacts from this job are available at:
http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0484/test-artifacts/1605285407/distributedtestfiles-OpenJDK8-1.14.0-build.0484.tgz
> JMXMBeanReconnectDUnitTest fails intermittently because one locator is
> missing the LockServiceMXBean
>
>
> Key: GEODE-7710
> URL: https://issues.apache.org/jira/browse/GEODE-7710
> Project: Geode
> Issue Type: Bug
> Components: tests
>Affects Versions: 1.13.0
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
> Labels: flaky
> Time Spent: 5h
> Remaining Estimate: 0h
>
> Multiple tests in JMXMBeanReconnectDUnitTest may fail an await due to one of
> the locators missing the LockServiceMXBean for the cluster config service.
> {noformat}
> but could not find:
>
> <[GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator1]>
> {noformat}
> These test failures are caused by *GEODE-7739*.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (GEODE-8709) ReplicatedFunctionExecutionBenchmark failing
[ https://issues.apache.org/jira/browse/GEODE-8709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17231593#comment-17231593 ] John Hutchison edited comment on GEODE-8709 at 11/13/20, 4:34 PM: -- [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/Benchmark_base/builds/455] This reverts commit f6605e0820ba9b858b8128cd31a03a29067b7710. =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Benchmark Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= [http://files.apachegeode-ci.info/benchmarks/apache-develop-main/f23e01a32213245dc684b417d97a14cf5a026741/benchmarks-apache-develop-main-Benchmark_base-455-206443_base.tgz] =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= was (Author: john hutch): [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/Benchmark_base/builds/455] This reverts commit f6605e0820ba9b858b8128cd31a03a29067b7710. =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Benchmark Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= http://files.apachegeode-ci.info/benchmarks/apache-develop-main/f23e01a32213245dc684b417d97a14cf5a026741/benchmarks-apache-develop-main-Benchmark_base-455-206443_base.tgz =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > ReplicatedFunctionExecutionBenchmark failing > - > > Key: GEODE-8709 > URL: https://issues.apache.org/jira/browse/GEODE-8709 > Project: Geode > Issue Type: Bug >Reporter: John Hutchison >Priority: Major > > > > org.apache.geode.benchmark.tests.ReplicatedFunctionExecutionWithFiltersBenchmark > > average ops/second Baseline: 546625.03 Test: 537316.10 Difference: -1.7% > ops/second standard error Baseline: 776.77 Test: 709.95 Difference: -8.6% > s/second standard deviation Baseline: 13431.54 Test: 12276.10 Difference: > -8.6% > YS 99th percentile latency Baseline: 1700.00 Test: 1750.00 Difference: +2.9% > median latency Baseline: 1213439.00 Test: 1215487.00 Difference: +0.2% > 90th percentile latency Baseline: 1465343.00 Test: 1518591.00 Difference: > +3.6% > 99th percentile latency Baseline: 4517887.00 Test: 4636671.00 Difference: > +2.6% > 99.9th percentile latency Baseline: 18202623.00 Test: 19234815.00 > Difference: +5.7% > average latency Baseline: 1315053.32 Test: 1337898.07 Difference: +1.7% > latency standard deviation Baseline: 1303983.91 Test: 1335112.23 Difference: > +2.4% > latency standard error Baseline: 101.85 Test: 105.17 Difference: +3.3% > average ops/second Baseline: 546531.56 Test: 537283.96 Difference: -1.7% > BENCHMARK FAILED: > org.apache.geode.benchmark.tests.ReplicatedFunctionExecutionBenchmark average > latency is 5% worse than baseline. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (GEODE-7616) ReplicatedPutAllBenchmark average latency is 5% worse than baseline
[
https://issues.apache.org/jira/browse/GEODE-7616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17231608#comment-17231608
]
John Hutchison edited comment on GEODE-7616 at 11/13/20, 4:29 PM:
--
occurred 11/13/20
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/Benchmark_base/builds/457
Comparing test result at
/tmp/build/2d6310e3/results/benchmarks-apache-develop-main-Benchmark_base-457-206639_base/branch/benchmarks_20201113090025
to baseline at
/tmp/build/2d6310e3/results/benchmarks-apache-develop-main-Benchmark_base-457-206639_base/baseline/benchmarks_20201113055501
org.apache.geode.benchmark.tests.ReplicatedPutAllLongBenchmark
average ops/second Baseline: 854.09 Test: 850.53 Difference: -0.4%
ops/second standard error Baseline: 2.82 Test: 2.52 Difference: -10.8%
ops/second standard deviation Baseline: 48.86 Test: 43.51 Difference: -10.9%
YS 99th percentile latency Baseline: 20099.00 Test: 20099.00 Difference: +0.0%
median latency Baseline: 164757503.00 Test: 165543935.00 Difference: +0.5%
90th percentile latency Baseline: 249036799.00 Test: 245366783.00 Difference:
-1.5%
99th percentile latency Baseline: 328466431.00 Test: 319029247.00 Difference:
-2.9%
99.9th percentile latency Baseline: 407896063.00 Test: 383778815.00
Difference: -5.9%
average latency Baseline: 168732913.71 Test: 169570366.99 Difference: +0.5%
latency standard deviation Baseline: 61216607.41 Test: 57135462.90 Difference:
-6.7%
latency standard error Baseline: 121028.48 Test: 113222.36 Difference: -6.4%
average ops/second Baseline: 852.91 Test: 848.79 Difference: -0.5%
BENCHMARK FAILED: org.apache.geode.benchmark.tests.ReplicatedPutAllBenchmark
average latency is 5% worse than baseline.
was (Author: john hutch):
11/3
org.apache.geode.benchmark.tests.ReplicatedPutAllLongBenchmark
average ops/second Baseline: 854.09 Test: 850.53 Difference: -0.4%
ops/second standard error Baseline: 2.82 Test: 2.52 Difference: -10.8%
ops/second standard deviation Baseline: 48.86 Test: 43.51 Difference: -10.9%
YS 99th percentile latency Baseline: 20099.00 Test: 20099.00 Difference: +0.0%
median latency Baseline: 164757503.00 Test: 165543935.00 Difference: +0.5%
90th percentile latency Baseline: 249036799.00 Test: 245366783.00 Difference:
-1.5%
99th percentile latency Baseline: 328466431.00 Test: 319029247.00 Difference:
-2.9%
99.9th percentile latency Baseline: 407896063.00 Test: 383778815.00
Difference: -5.9%
average latency Baseline: 168732913.71 Test: 169570366.99 Difference: +0.5%
latency standard deviation Baseline: 61216607.41 Test: 57135462.90 Difference:
-6.7%
latency standard error Baseline: 121028.48 Test: 113222.36 Difference: -6.4%
average ops/second Baseline: 852.91 Test: 848.79 Difference: -0.5%
BENCHMARK FAILED: org.apache.geode.benchmark.tests.ReplicatedPutAllBenchmark
average latency is 5% worse than baseline.
> ReplicatedPutAllBenchmark average latency is 5% worse than baseline
> ---
>
> Key: GEODE-7616
> URL: https://issues.apache.org/jira/browse/GEODE-7616
> Project: Geode
> Issue Type: Bug
> Components: benchmarks
>Reporter: Bill Burcham
>Assignee: Jacob Barrett
>Priority: Major
>
> Three runs in a row have failed with {{ReplicatedPutAllBenchmark average
> latency is 5% worse than baseline}} starting with:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/Benchmark_base/builds/23
> e.g.
> {code}
> org.apache.geode.benchmark.tests.ReplicatedPutAllBenchmark
> average ops/second Baseline: 900.64 Test: 828.40
> Difference: -8.0%
>ops/second standard error Baseline: 2.71 Test: 2.47
> Difference: -8.9%
>ops/second standard deviation Baseline:46.91 Test:42.76
> Difference: -8.9%
> YS 99th percentile latency Baseline: 20099.00 Test: 20099.00
> Difference: +0.0%
> median latency Baseline: 158728191.00 Test: 172359679.00
> Difference: +8.6%
> 90th percentile latency Baseline: 228458495.00 Test: 29279.00
> Difference: +7.0%
> 99th percentile latency Baseline: 299368447.00 Test: 319815679.00
> Difference: +6.8%
>99.9th percentile latency Baseline: 354156543.00 Test: 387710975.00
> Difference: +9.5%
> average latency Baseline: 160197744.39 Test: 174083983.05
> Difference: +8.7%
> latency standard deviation Baseline: 53484962.25 Test: 55775317.05
> Difference: +4.3%
> latency standard error Baseline:103053.88 Test:111997.05
> Difference: +8.7%
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#80
[jira] [Comment Edited] (GEODE-7616) ReplicatedPutAllBenchmark average latency is 5% worse than baseline
[
https://issues.apache.org/jira/browse/GEODE-7616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17231608#comment-17231608
]
John Hutchison edited comment on GEODE-7616 at 11/13/20, 4:28 PM:
--
11/3
org.apache.geode.benchmark.tests.ReplicatedPutAllLongBenchmark
average ops/second Baseline: 854.09 Test: 850.53 Difference: -0.4%
ops/second standard error Baseline: 2.82 Test: 2.52 Difference: -10.8%
ops/second standard deviation Baseline: 48.86 Test: 43.51 Difference: -10.9%
YS 99th percentile latency Baseline: 20099.00 Test: 20099.00 Difference: +0.0%
median latency Baseline: 164757503.00 Test: 165543935.00 Difference: +0.5%
90th percentile latency Baseline: 249036799.00 Test: 245366783.00 Difference:
-1.5%
99th percentile latency Baseline: 328466431.00 Test: 319029247.00 Difference:
-2.9%
99.9th percentile latency Baseline: 407896063.00 Test: 383778815.00
Difference: -5.9%
average latency Baseline: 168732913.71 Test: 169570366.99 Difference: +0.5%
latency standard deviation Baseline: 61216607.41 Test: 57135462.90 Difference:
-6.7%
latency standard error Baseline: 121028.48 Test: 113222.36 Difference: -6.4%
average ops/second Baseline: 852.91 Test: 848.79 Difference: -0.5%
BENCHMARK FAILED: org.apache.geode.benchmark.tests.ReplicatedPutAllBenchmark
average latency is 5% worse than baseline.
was (Author: john hutch):
11/3
org.apache.geode.benchmark.tests.ReplicatedPutAllLongBenchmark
average ops/second Baseline: 854.09 Test: 850.53 Difference: -0.4%
ops/second standard error Baseline: 2.82 Test: 2.52 Difference: -10.8%
ops/second standard deviation Baseline: 48.86 Test: 43.51 Difference: -10.9%
YS 99th percentile latency Baseline: 20099.00 Test: 20099.00 Difference: +0.0%
median latency Baseline: 164757503.00 Test: 165543935.00 Difference: +0.5%
90th percentile latency Baseline: 249036799.00 Test: 245366783.00 Difference:
-1.5%
99th percentile latency Baseline: 328466431.00 Test: 319029247.00 Difference:
-2.9%
99.9th percentile latency Baseline: 407896063.00 Test: 383778815.00
Difference: -5.9%
average latency Baseline: 168732913.71 Test: 169570366.99 Difference: +0.5%
latency standard deviation Baseline: 61216607.41 Test: 57135462.90 Difference:
-6.7%
latency standard error Baseline: 121028.48 Test: 113222.36 Difference: -6.4%
average ops/second Baseline: 852.91 Test: 848.79 Difference: -0.5%
BENCHMARK FAILED: org.apache.geode.benchmark.tests.ReplicatedPutAllBenchmark
average latency is 5% worse than baseline.
> ReplicatedPutAllBenchmark average latency is 5% worse than baseline
> ---
>
> Key: GEODE-7616
> URL: https://issues.apache.org/jira/browse/GEODE-7616
> Project: Geode
> Issue Type: Bug
> Components: benchmarks
>Reporter: Bill Burcham
>Assignee: Jacob Barrett
>Priority: Major
>
> Three runs in a row have failed with {{ReplicatedPutAllBenchmark average
> latency is 5% worse than baseline}} starting with:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/Benchmark_base/builds/23
> e.g.
> {code}
> org.apache.geode.benchmark.tests.ReplicatedPutAllBenchmark
> average ops/second Baseline: 900.64 Test: 828.40
> Difference: -8.0%
>ops/second standard error Baseline: 2.71 Test: 2.47
> Difference: -8.9%
>ops/second standard deviation Baseline:46.91 Test:42.76
> Difference: -8.9%
> YS 99th percentile latency Baseline: 20099.00 Test: 20099.00
> Difference: +0.0%
> median latency Baseline: 158728191.00 Test: 172359679.00
> Difference: +8.6%
> 90th percentile latency Baseline: 228458495.00 Test: 29279.00
> Difference: +7.0%
> 99th percentile latency Baseline: 299368447.00 Test: 319815679.00
> Difference: +6.8%
>99.9th percentile latency Baseline: 354156543.00 Test: 387710975.00
> Difference: +9.5%
> average latency Baseline: 160197744.39 Test: 174083983.05
> Difference: +8.7%
> latency standard deviation Baseline: 53484962.25 Test: 55775317.05
> Difference: +4.3%
> latency standard error Baseline:103053.88 Test:111997.05
> Difference: +8.7%
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-7616) ReplicatedPutAllBenchmark average latency is 5% worse than baseline
[
https://issues.apache.org/jira/browse/GEODE-7616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17231608#comment-17231608
]
John Hutchison commented on GEODE-7616:
---
11/3
org.apache.geode.benchmark.tests.ReplicatedPutAllLongBenchmark
average ops/second Baseline: 854.09 Test: 850.53 Difference: -0.4%
ops/second standard error Baseline: 2.82 Test: 2.52 Difference: -10.8%
ops/second standard deviation Baseline: 48.86 Test: 43.51 Difference: -10.9%
YS 99th percentile latency Baseline: 20099.00 Test: 20099.00 Difference: +0.0%
median latency Baseline: 164757503.00 Test: 165543935.00 Difference: +0.5%
90th percentile latency Baseline: 249036799.00 Test: 245366783.00 Difference:
-1.5%
99th percentile latency Baseline: 328466431.00 Test: 319029247.00 Difference:
-2.9%
99.9th percentile latency Baseline: 407896063.00 Test: 383778815.00
Difference: -5.9%
average latency Baseline: 168732913.71 Test: 169570366.99 Difference: +0.5%
latency standard deviation Baseline: 61216607.41 Test: 57135462.90 Difference:
-6.7%
latency standard error Baseline: 121028.48 Test: 113222.36 Difference: -6.4%
average ops/second Baseline: 852.91 Test: 848.79 Difference: -0.5%
BENCHMARK FAILED: org.apache.geode.benchmark.tests.ReplicatedPutAllBenchmark
average latency is 5% worse than baseline.
> ReplicatedPutAllBenchmark average latency is 5% worse than baseline
> ---
>
> Key: GEODE-7616
> URL: https://issues.apache.org/jira/browse/GEODE-7616
> Project: Geode
> Issue Type: Bug
> Components: benchmarks
>Reporter: Bill Burcham
>Assignee: Jacob Barrett
>Priority: Major
>
> Three runs in a row have failed with {{ReplicatedPutAllBenchmark average
> latency is 5% worse than baseline}} starting with:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/Benchmark_base/builds/23
> e.g.
> {code}
> org.apache.geode.benchmark.tests.ReplicatedPutAllBenchmark
> average ops/second Baseline: 900.64 Test: 828.40
> Difference: -8.0%
>ops/second standard error Baseline: 2.71 Test: 2.47
> Difference: -8.9%
>ops/second standard deviation Baseline:46.91 Test:42.76
> Difference: -8.9%
> YS 99th percentile latency Baseline: 20099.00 Test: 20099.00
> Difference: +0.0%
> median latency Baseline: 158728191.00 Test: 172359679.00
> Difference: +8.6%
> 90th percentile latency Baseline: 228458495.00 Test: 29279.00
> Difference: +7.0%
> 99th percentile latency Baseline: 299368447.00 Test: 319815679.00
> Difference: +6.8%
>99.9th percentile latency Baseline: 354156543.00 Test: 387710975.00
> Difference: +9.5%
> average latency Baseline: 160197744.39 Test: 174083983.05
> Difference: +8.7%
> latency standard deviation Baseline: 53484962.25 Test: 55775317.05
> Difference: +4.3%
> latency standard error Baseline:103053.88 Test:111997.05
> Difference: +8.7%
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (GEODE-7231) CI: BENCHMARK FAILED: org.apache.geode.benchmark.tests.PartitionedFunctionExecutionWithArgumentsBenchmark average latency is 5% worse than baseline.
[ https://issues.apache.org/jira/browse/GEODE-7231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17231601#comment-17231601 ] John Hutchison edited comment on GEODE-7231 at 11/13/20, 4:22 PM: -- occurred again in run [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/Benchmark_base/builds/457] org.apache.geode.benchmark.tests.PartitionedFunctionExecutionWithArgumentsBenchmark average ops/second Baseline: 288420.47 Test: 266334.08 Difference: -7.7% ops/second standard error Baseline: 706.84 Test: 639.07 Difference: -9.6% ops/second standard deviation Baseline: 1.36 Test: 11050.63 Difference: -9.6% YS 99th percentile latency Baseline: 1804.00 Test: 1905.00 Difference: +5.6% median latency Baseline: 697343.00 Test: 756735.00 Difference: +8.5% 90th percentile latency Baseline: 1295359.00 Test: 1354751.00 Difference: +4.6% 99th percentile latency Baseline: 8921087.00 Test: 9887743.00 Difference: +10.8% 99.9th percentile latency Baseline: 22659071.00 Test: 23740415.00 Difference: +4.8% average latency Baseline: 996875.28 Test: 1079779.99 Difference: +8.3% latency standard deviation Baseline: 1649168.77 Test: 1814626.40 Difference: +10.0% latency standard error Baseline: 177.33 Test: 203.06 Difference: +14.5% average ops/second Baseline: 288357.32 Test: 266245.32 Difference: -7.7% BENCHMARK FAILED: org.apache.geode.benchmark.tests.PartitionedFunctionExecutionWithArgumentsBenchmark average latency is 5% worse than baseline. was (Author: john hutch): occurred again in run [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/Benchmark_base/builds/457] org.apache.geode.benchmark.tests.PartitionedFunctionExecutionWithArgumentsBenchmark average ops/second Baseline: 288420.47 Test: 266334.08 Difference: -7.7% ops/second standard error Baseline: 706.84 Test: 639.07 Difference: -9.6% ops/second standard deviation Baseline: 1.36 Test: 11050.63 Difference: -9.6% YS 99th percentile latency Baseline: 1804.00 Test: 1905.00 Difference: +5.6% median latency Baseline: 697343.00 Test: 756735.00 Difference: +8.5% 90th percentile latency Baseline: 1295359.00 Test: 1354751.00 Difference: +4.6% 99th percentile latency Baseline: 8921087.00 Test: 9887743.00 Difference: +10.8% 99.9th percentile latency Baseline: 22659071.00 Test: 23740415.00 Difference: +4.8% average latency Baseline: 996875.28 Test: 1079779.99 Difference: +8.3% latency standard deviation Baseline: 1649168.77 Test: 1814626.40 Difference: +10.0% latency standard error Baseline: 177.33 Test: 203.06 Difference: +14.5% average ops/second Baseline: 288357.32 Test: 266245.32 Difference: -7.7% BENCHMARK FAILED: org.apache.geode.benchmark.tests.PartitionedFunctionExecutionWithArgumentsBenchmark average latency is 5% worse than baseline. > CI: BENCHMARK FAILED: > org.apache.geode.benchmark.tests.PartitionedFunctionExecutionWithArgumentsBenchmark > average latency is 5% worse than baseline. > > > Key: GEODE-7231 > URL: https://issues.apache.org/jira/browse/GEODE-7231 > Project: Geode > Issue Type: Bug > Components: benchmarks, ci >Reporter: Jinmei Liao >Assignee: Jacob Barrett >Priority: Major > > created by mistake -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7231) CI: BENCHMARK FAILED: org.apache.geode.benchmark.tests.PartitionedFunctionExecutionWithArgumentsBenchmark average latency is 5% worse than baseline.
[ https://issues.apache.org/jira/browse/GEODE-7231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17231601#comment-17231601 ] John Hutchison commented on GEODE-7231: --- occurred again in run [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/Benchmark_base/builds/457] org.apache.geode.benchmark.tests.PartitionedFunctionExecutionWithArgumentsBenchmark average ops/second Baseline: 288420.47 Test: 266334.08 Difference: -7.7% ops/second standard error Baseline: 706.84 Test: 639.07 Difference: -9.6% ops/second standard deviation Baseline: 1.36 Test: 11050.63 Difference: -9.6% YS 99th percentile latency Baseline: 1804.00 Test: 1905.00 Difference: +5.6% median latency Baseline: 697343.00 Test: 756735.00 Difference: +8.5% 90th percentile latency Baseline: 1295359.00 Test: 1354751.00 Difference: +4.6% 99th percentile latency Baseline: 8921087.00 Test: 9887743.00 Difference: +10.8% 99.9th percentile latency Baseline: 22659071.00 Test: 23740415.00 Difference: +4.8% average latency Baseline: 996875.28 Test: 1079779.99 Difference: +8.3% latency standard deviation Baseline: 1649168.77 Test: 1814626.40 Difference: +10.0% latency standard error Baseline: 177.33 Test: 203.06 Difference: +14.5% average ops/second Baseline: 288357.32 Test: 266245.32 Difference: -7.7% BENCHMARK FAILED: org.apache.geode.benchmark.tests.PartitionedFunctionExecutionWithArgumentsBenchmark average latency is 5% worse than baseline. > CI: BENCHMARK FAILED: > org.apache.geode.benchmark.tests.PartitionedFunctionExecutionWithArgumentsBenchmark > average latency is 5% worse than baseline. > > > Key: GEODE-7231 > URL: https://issues.apache.org/jira/browse/GEODE-7231 > Project: Geode > Issue Type: Bug > Components: benchmarks, ci >Reporter: Jinmei Liao >Assignee: Jacob Barrett >Priority: Major > > created by mistake -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8709) ReplicatedFunctionExecutionBenchmark failing
[ https://issues.apache.org/jira/browse/GEODE-8709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17231593#comment-17231593 ] John Hutchison commented on GEODE-8709: --- [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/Benchmark_base/builds/455] This reverts commit f6605e0820ba9b858b8128cd31a03a29067b7710. =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Benchmark Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= http://files.apachegeode-ci.info/benchmarks/apache-develop-main/f23e01a32213245dc684b417d97a14cf5a026741/benchmarks-apache-develop-main-Benchmark_base-455-206443_base.tgz =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > ReplicatedFunctionExecutionBenchmark failing > - > > Key: GEODE-8709 > URL: https://issues.apache.org/jira/browse/GEODE-8709 > Project: Geode > Issue Type: Bug >Reporter: John Hutchison >Priority: Major > > > > org.apache.geode.benchmark.tests.ReplicatedFunctionExecutionWithFiltersBenchmark > > average ops/second Baseline: 546625.03 Test: 537316.10 Difference: -1.7% > ops/second standard error Baseline: 776.77 Test: 709.95 Difference: -8.6% > s/second standard deviation Baseline: 13431.54 Test: 12276.10 Difference: > -8.6% > YS 99th percentile latency Baseline: 1700.00 Test: 1750.00 Difference: +2.9% > median latency Baseline: 1213439.00 Test: 1215487.00 Difference: +0.2% > 90th percentile latency Baseline: 1465343.00 Test: 1518591.00 Difference: > +3.6% > 99th percentile latency Baseline: 4517887.00 Test: 4636671.00 Difference: > +2.6% > 99.9th percentile latency Baseline: 18202623.00 Test: 19234815.00 > Difference: +5.7% > average latency Baseline: 1315053.32 Test: 1337898.07 Difference: +1.7% > latency standard deviation Baseline: 1303983.91 Test: 1335112.23 Difference: > +2.4% > latency standard error Baseline: 101.85 Test: 105.17 Difference: +3.3% > average ops/second Baseline: 546531.56 Test: 537283.96 Difference: -1.7% > BENCHMARK FAILED: > org.apache.geode.benchmark.tests.ReplicatedFunctionExecutionBenchmark average > latency is 5% worse than baseline. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-8709) ReplicatedFunctionExecutionBenchmark failing
[ https://issues.apache.org/jira/browse/GEODE-8709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Hutchison updated GEODE-8709: -- Description: org.apache.geode.benchmark.tests.ReplicatedFunctionExecutionWithFiltersBenchmark average ops/second Baseline: 546625.03 Test: 537316.10 Difference: -1.7% ops/second standard error Baseline: 776.77 Test: 709.95 Difference: -8.6% s/second standard deviation Baseline: 13431.54 Test: 12276.10 Difference: -8.6% YS 99th percentile latency Baseline: 1700.00 Test: 1750.00 Difference: +2.9% median latency Baseline: 1213439.00 Test: 1215487.00 Difference: +0.2% 90th percentile latency Baseline: 1465343.00 Test: 1518591.00 Difference: +3.6% 99th percentile latency Baseline: 4517887.00 Test: 4636671.00 Difference: +2.6% 99.9th percentile latency Baseline: 18202623.00 Test: 19234815.00 Difference: +5.7% average latency Baseline: 1315053.32 Test: 1337898.07 Difference: +1.7% latency standard deviation Baseline: 1303983.91 Test: 1335112.23 Difference: +2.4% latency standard error Baseline: 101.85 Test: 105.17 Difference: +3.3% average ops/second Baseline: 546531.56 Test: 537283.96 Difference: -1.7% BENCHMARK FAILED: org.apache.geode.benchmark.tests.ReplicatedFunctionExecutionBenchmark average latency is 5% worse than baseline. was: org.apache.geode.benchmark.tests.ReplicatedFunctionExecutionWithFiltersBenchmark [23:46:36|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/Benchmark_base/builds/455#L5f7d595d:6985] average ops/second Baseline: 546625.03 Test: 537316.10 Difference: -1.7% [23:46:36|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/Benchmark_base/builds/455#L5f7d595d:6986] ops/second standard error Baseline: 776.77 Test: 709.95 Difference: -8.6% [23:46:36|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/Benchmark_base/builds/455#L5f7d595d:6987] ops/second standard deviation Baseline: 13431.54 Test: 12276.10 Difference: -8.6% [23:46:36|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/Benchmark_base/builds/455#L5f7d595d:6988] YS 99th percentile latency Baseline: 1700.00 Test: 1750.00 Difference: +2.9% [23:46:36|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/Benchmark_base/builds/455#L5f7d595d:6989] median latency Baseline: 1213439.00 Test: 1215487.00 Difference: +0.2% [23:46:36|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/Benchmark_base/builds/455#L5f7d595d:6990] 90th percentile latency Baseline: 1465343.00 Test: 1518591.00 Difference: +3.6% [23:46:36|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/Benchmark_base/builds/455#L5f7d595d:6991] 99th percentile latency Baseline: 4517887.00 Test: 4636671.00 Difference: +2.6% [23:46:36|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/Benchmark_base/builds/455#L5f7d595d:6992] 99.9th percentile latency Baseline: 18202623.00 Test: 19234815.00 Difference: +5.7% [23:46:36|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/Benchmark_base/builds/455#L5f7d595d:6993] average latency Baseline: 1315053.32 Test: 1337898.07 Difference: +1.7% [23:46:36|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/Benchmark_base/builds/455#L5f7d595d:6994] latency standard deviation Baseline: 1303983.91 Test: 1335112.23 Difference: +2.4% [23:46:36|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/Benchmark_base/builds/455#L5f7d595d:6995] latency standard error Baseline: 101.85 Test: 105.17 Difference: +3.3% [23:46:36|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/Benchmark_base/builds/455#L5f7d595d:6996] average ops/second Baseline: 546531.56 Test: 537283.96 Difference: -1.7% BENCHMARK FAILED: org.apache.geode.benchmark.tests.ReplicatedFunctionExecutionBenchmark average latency is 5% worse than baseline. > ReplicatedFunctionExecutionBenchmark failing > - > > Key: GEODE-8709 > URL: https://issues.apache.org/jira/browse/GEODE-8709 > Project: Geode > Issue Type: Bug >Reporter: John Hutchison >Priority: Major > > > > org.apache.geode.benchmark.tests.ReplicatedFunctionExecutionWithFiltersBenchmark > > average ops/second Baseline: 546625.03 Test: 537316.10 Difference: -1.7% > ops/second standard error Baseline: 776.77 Test: 709.95 Difference: -8.6% > s/second standard deviation Baseline: 13431.54 Test: 12276.10 Difference: > -8.6% > YS 99th percentile latency Baseline: 1700.00 Test: 1750.00 Difference: +2.9% > median latency Baseline: 1213439.00 Test: 1215487.00 Difference
[jira] [Created] (GEODE-8709) ReplicatedFunctionExecutionBenchmark failing
John Hutchison created GEODE-8709: - Summary: ReplicatedFunctionExecutionBenchmark failing Key: GEODE-8709 URL: https://issues.apache.org/jira/browse/GEODE-8709 Project: Geode Issue Type: Bug Reporter: John Hutchison org.apache.geode.benchmark.tests.ReplicatedFunctionExecutionWithFiltersBenchmark [23:46:36|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/Benchmark_base/builds/455#L5f7d595d:6985] average ops/second Baseline: 546625.03 Test: 537316.10 Difference: -1.7% [23:46:36|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/Benchmark_base/builds/455#L5f7d595d:6986] ops/second standard error Baseline: 776.77 Test: 709.95 Difference: -8.6% [23:46:36|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/Benchmark_base/builds/455#L5f7d595d:6987] ops/second standard deviation Baseline: 13431.54 Test: 12276.10 Difference: -8.6% [23:46:36|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/Benchmark_base/builds/455#L5f7d595d:6988] YS 99th percentile latency Baseline: 1700.00 Test: 1750.00 Difference: +2.9% [23:46:36|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/Benchmark_base/builds/455#L5f7d595d:6989] median latency Baseline: 1213439.00 Test: 1215487.00 Difference: +0.2% [23:46:36|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/Benchmark_base/builds/455#L5f7d595d:6990] 90th percentile latency Baseline: 1465343.00 Test: 1518591.00 Difference: +3.6% [23:46:36|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/Benchmark_base/builds/455#L5f7d595d:6991] 99th percentile latency Baseline: 4517887.00 Test: 4636671.00 Difference: +2.6% [23:46:36|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/Benchmark_base/builds/455#L5f7d595d:6992] 99.9th percentile latency Baseline: 18202623.00 Test: 19234815.00 Difference: +5.7% [23:46:36|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/Benchmark_base/builds/455#L5f7d595d:6993] average latency Baseline: 1315053.32 Test: 1337898.07 Difference: +1.7% [23:46:36|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/Benchmark_base/builds/455#L5f7d595d:6994] latency standard deviation Baseline: 1303983.91 Test: 1335112.23 Difference: +2.4% [23:46:36|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/Benchmark_base/builds/455#L5f7d595d:6995] latency standard error Baseline: 101.85 Test: 105.17 Difference: +3.3% [23:46:36|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/Benchmark_base/builds/455#L5f7d595d:6996] average ops/second Baseline: 546531.56 Test: 537283.96 Difference: -1.7% BENCHMARK FAILED: org.apache.geode.benchmark.tests.ReplicatedFunctionExecutionBenchmark average latency is 5% worse than baseline. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (GEODE-7389) CI failure: BENCHMARK FAILED: PartitionedFunctionExecutionWithFiltersBenchmark average latency is 5% worse than baseline
[
https://issues.apache.org/jira/browse/GEODE-7389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17231579#comment-17231579
]
John Hutchison edited comment on GEODE-7389 at 11/13/20, 4:07 PM:
--
occurred on 11/13
[https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/Benchmark_base/builds/455]
[http://files.apachegeode-ci.info/benchmarks/apache-develop-main/f23e01a32213245dc684b417d97a14cf5a026741/benchmarks-apache-develop-main-Benchmark_base-455-206443_base.tgz]
note: other benchmarks also failed
BENCHMARK FAILED:
org.apache.geode.benchmark.tests.PartitionedFunctionExecutionWithFiltersBenchmark
average latency is 5% worse than baseline.
[23:46:36|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/Benchmark_base/builds/455#L5f7d595d:7102]
BENCHMARK FAILED:
org.apache.geode.benchmark.tests.ReplicatedFunctionExecutionBenchmark average
latency is 5% worse than baseline.
[23:46:36|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/Benchmark_base/builds/455#L5f7d595d:7103]
was (Author: john hutch):
occurred twice on 11/13
run
[https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/Benchmark_base/builds/457]
[http://files.apachegeode-ci.info/benchmarks/apache-develop-main/f23e01a32213245dc684b417d97a14cf5a026741/benchmarks-apache-develop-main-Benchmark_base-457-206639_base.tgz]
and run
[https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/Benchmark_base/builds/455]
[http://files.apachegeode-ci.info/benchmarks/apache-develop-main/f23e01a32213245dc684b417d97a14cf5a026741/benchmarks-apache-develop-main-Benchmark_base-455-206443_base.tgz]
note: in both of the runs above , other benchmarks also failed
> CI failure: BENCHMARK FAILED:
> PartitionedFunctionExecutionWithFiltersBenchmark average latency is 5% worse
> than baseline
>
>
> Key: GEODE-7389
> URL: https://issues.apache.org/jira/browse/GEODE-7389
> Project: Geode
> Issue Type: Bug
> Components: benchmarks
>Reporter: Barrett Oglesby
>Priority: Major
>
> The PartitionedFunctionExecutionWithFiltersBenchmark in Benchmark build 643
> failed:
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/Benchmark/builds/643]
> {noformat}
> org.apache.geode.benchmark.tests.PartitionedFunctionExecutionWithFiltersBenchmark
> average ops/second Baseline:350652.64 Test:318470.59
> Difference: -9.2%
>ops/second standard error Baseline: 399.41 Test: 408.97
> Difference: +2.4%
>ops/second standard deviation Baseline: 6906.46 Test: 7071.73
> Difference: +2.4%
> YS 99th percentile latency Baseline: 3006.00 Test: 20005.00
> Difference: +565.5%
> median latency Baseline: 1202175.00 Test: 1327103.00
> Difference: +10.4%
> 90th percentile latency Baseline: 2510847.00 Test: 2826239.00
> Difference: +12.6%
> 99th percentile latency Baseline: 11788287.00 Test: 12476415.00
> Difference: +5.8%
>99.9th percentile latency Baseline: 42631167.00 Test: 46989311.00
> Difference: +10.2%
> average latency Baseline: 1640650.66 Test: 1807133.87
> Difference: +10.1%
> latency standard deviation Baseline: 2881426.77 Test: 3148034.63
> Difference: +9.3%
> latency standard error Baseline: 281.02 Test: 322.21
> Difference: +14.7%
> BENCHMARK FAILED:
> org.apache.geode.benchmark.tests.PartitionedFunctionExecutionWithFiltersBenchmark
> average latency is 5% worse than baseline.
> {noformat}
> Please drop a link to any additional CI runs that have this failure and
> restart the benchmarks.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
