[jira] [Updated] (GEODE-9339) bump json-smart to recommended version
[ https://issues.apache.org/jira/browse/GEODE-9339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-9339: -- Labels: blocks-1.14.0 pull-request-available (was: blocks-1.14.0) > bump json-smart to recommended version > -- > > Key: GEODE-9339 > URL: https://issues.apache.org/jira/browse/GEODE-9339 > Project: Geode > Issue Type: Improvement > Components: management >Affects Versions: 1.12.2, 1.13.2, 1.14.0, 1.15.0 >Reporter: Owen Nichols >Priority: Major > Labels: blocks-1.14.0, pull-request-available > > json-smart 2.3 should be updated to 2.3.1 > (fyi json-smart is used by json-path, not directly by Geode) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9289) Configuration Class cannot be deserialized in old locators
[ https://issues.apache.org/jira/browse/GEODE-9289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen Nichols updated GEODE-9289: Labels: blocks-1.14.0 pull-request-available (was: pull-request-available) > Configuration Class cannot be deserialized in old locators > -- > > Key: GEODE-9289 > URL: https://issues.apache.org/jira/browse/GEODE-9289 > Project: Geode > Issue Type: Bug > Components: serialization >Reporter: Nabarun Nag >Priority: Major > Labels: blocks-1.14.0, pull-request-available > > * Locators post version 1.12.0 when send out the Configuration to old version > locators > * Old locators are not able to interpret the null jarNames sent by the new > locators > * This causes a lot of NPEs in the old locators > * This clears out the jarNames in the configuration and if a server joins > the cluster and requests the cluster configuration from the oldest locator, > then it does not the jars deployed in the cluster. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-8609) Create a dunit suspect file per VM
[
https://issues.apache.org/jira/browse/GEODE-8609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen Nichols updated GEODE-8609:
Labels: blocks-1.14.0 pull-request-available (was: pull-request-available)
> Create a dunit suspect file per VM
> --
>
> Key: GEODE-8609
> URL: https://issues.apache.org/jira/browse/GEODE-8609
> Project: Geode
> Issue Type: Test
> Components: tests
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
> Labels: blocks-1.14.0, pull-request-available
> Fix For: 1.14.0
>
>
> In some situations, especially when restarting Dunit VMs, it appears that the
> suspect log file can be corrupted since suspect processing reports errors
> such as:
> {noformat}
> org.apache.geode.redis.internal.executor.CrashAndNoRepeatDUnitTest >
> classMethod FAILED
> java.lang.AssertionError: Suspicious strings were written to the log
> during this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in log4j at line 19594
> /home/geode/.gradle/caches/modules-2/files-2.1/antlr/antlr/2.7.7/83cd2cd674a21[warn
> 2020/10/11 15:23:24.988 GMT tid=105] Execution
> of Redis command APPEND append-key-1 -append-key-1-17484- failed:
> org.apache.geode.cache.execute.FunctionException:
> org.apache.geode.cache.execute.FunctionInvocationTargetException:
> memberDeparted event for < 172.17.0.20(server-3:2004):41003 > crashed,
> true{noformat}
> Where the suspected string is corrupted.
> The proposed fix will create a new dunit_suspect log for each VM. The logs
> will now be named {{dunit_suspect-vm.log}}. The {{locator}} vm and the
> test runner vm will have logs named {{dunit_suspect-locator.log}} and
> {{dunit_suspect-local.log}} respectively.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-9139) SSLException in starting up a Locator
[
https://issues.apache.org/jira/browse/GEODE-9139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen Nichols updated GEODE-9139:
Fix Version/s: (was: 1.14.0)
> SSLException in starting up a Locator
> -
>
> Key: GEODE-9139
> URL: https://issues.apache.org/jira/browse/GEODE-9139
> Project: Geode
> Issue Type: Bug
> Components: membership, messaging
>Reporter: Bruce J Schuchardt
>Assignee: Bruce J Schuchardt
>Priority: Major
> Labels: blocks-1.14.0, pull-request-available
> Fix For: 1.15.0
>
>
> If you start up a locator using its host name, without a domain name, as a
> bind address you may get an SSLException in the form
> {noformat}
> javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException:
> No subject alternative DNS name matching hostname.domainname found
> {noformat}
> The LocatorLauncher and InternalLocator throw away the bind address string
> and later do a reverse lookup to find the fully qualified hostname to use in
> endpoint identification matching.If the locator's own TLS certificate
> doesn't have the fully qualified name in it as a Subject Alternate Name the
> connection that the Locator makes to its own location service will fail.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-9339) bump json-smart to recommended version
[ https://issues.apache.org/jira/browse/GEODE-9339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen Nichols updated GEODE-9339: Labels: blocks-1.14.0 (was: ) > bump json-smart to recommended version > -- > > Key: GEODE-9339 > URL: https://issues.apache.org/jira/browse/GEODE-9339 > Project: Geode > Issue Type: Improvement > Components: management >Affects Versions: 1.12.2, 1.13.2, 1.14.0, 1.15.0 >Reporter: Owen Nichols >Priority: Major > Labels: blocks-1.14.0 > > json-smart 2.3 should be updated to 2.3.1 > (fyi json-smart is used by json-path, not directly by Geode) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9339) bump json-smart to recommended version
[ https://issues.apache.org/jira/browse/GEODE-9339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17355430#comment-17355430 ] ASF subversion and git services commented on GEODE-9339: Commit 4f6eff98faacec41eb52252a2697ce191a2dba2d in geode's branch refs/heads/support/1.13 from Owen Nichols [ https://gitbox.apache.org/repos/asf?p=geode.git;h=4f6eff9 ] GEODE-9339: bump json-smart from 2.3 to 2.3.1 (cherry picked from commit b3b86bb1b2919f0faadf239046883c217d3e2d80) (cherry picked from commit c6881a5a5b287d4c6cbae37e210cd02b46274f02) > bump json-smart to recommended version > -- > > Key: GEODE-9339 > URL: https://issues.apache.org/jira/browse/GEODE-9339 > Project: Geode > Issue Type: Improvement > Components: management >Affects Versions: 1.12.2, 1.13.2, 1.14.0, 1.15.0 >Reporter: Owen Nichols >Priority: Major > Labels: blocks-1.14.0 > > json-smart 2.3 should be updated to 2.3.1 > (fyi json-smart is used by json-path, not directly by Geode) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9339) bump json-smart to recommended version
[ https://issues.apache.org/jira/browse/GEODE-9339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17355427#comment-17355427 ] ASF subversion and git services commented on GEODE-9339: Commit 5f558074edfe5ce47608c5f7ffbcea663a36a574 in geode's branch refs/heads/support/1.12 from Owen Nichols [ https://gitbox.apache.org/repos/asf?p=geode.git;h=5f55807 ] GEODE-9339: bump json-smart from 2.3 to 2.3.1 > bump json-smart to recommended version > -- > > Key: GEODE-9339 > URL: https://issues.apache.org/jira/browse/GEODE-9339 > Project: Geode > Issue Type: Improvement > Components: management >Affects Versions: 1.12.2, 1.13.2, 1.14.0, 1.15.0 >Reporter: Owen Nichols >Priority: Major > > json-smart 2.3 should be updated to 2.3.1 > (fyi json-smart is used by json-path, not directly by Geode) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9336) Implement ZADD option CH
[ https://issues.apache.org/jira/browse/GEODE-9336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-9336: -- Labels: pull-request-available (was: ) > Implement ZADD option CH > > > Key: GEODE-9336 > URL: https://issues.apache.org/jira/browse/GEODE-9336 > Project: Geode > Issue Type: Improvement > Components: redis >Affects Versions: 1.15.0 >Reporter: Louis R. Jacome >Assignee: Louis R. Jacome >Priority: Major > Labels: pull-request-available > > CH option for ZADD > CH: Modify the return value from the number of new elements added, to the > total number of elements changed (CH is an abbreviation of changed). Changed > elements are new elements added and elements already existing for which the > score was updated. So elements specified in the command line having the same > score as they had in the past are not counted. Note: normally the return > value of ZADD only counts the number of new elements added. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9339) bump json-smart to recommended version
[ https://issues.apache.org/jira/browse/GEODE-9339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17355420#comment-17355420 ] ASF subversion and git services commented on GEODE-9339: Commit a7e134de3b441c89d80ab292edea6f7f026fb68b in geode's branch refs/heads/support/1.12 from Owen Nichols [ https://gitbox.apache.org/repos/asf?p=geode.git;h=a7e134d ] GEODE-9339: bump json-smart from 2.3 to 2.3.1 (cherry picked from commit b3b86bb1b2919f0faadf239046883c217d3e2d80) (cherry picked from commit c6881a5a5b287d4c6cbae37e210cd02b46274f02) > bump json-smart to recommended version > -- > > Key: GEODE-9339 > URL: https://issues.apache.org/jira/browse/GEODE-9339 > Project: Geode > Issue Type: Improvement > Components: management >Affects Versions: 1.12.2, 1.13.2, 1.14.0, 1.15.0 >Reporter: Owen Nichols >Priority: Major > > json-smart 2.3 should be updated to 2.3.1 > (fyi json-smart is used by json-path, not directly by Geode) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-9339) bump json-smart to recommended version
Owen Nichols created GEODE-9339: --- Summary: bump json-smart to recommended version Key: GEODE-9339 URL: https://issues.apache.org/jira/browse/GEODE-9339 Project: Geode Issue Type: Improvement Components: management Affects Versions: 1.13.2, 1.12.2, 1.14.0, 1.15.0 Reporter: Owen Nichols json-smart 2.3 should be updated to 2.3.1 (fyi json-smart is used by json-path, not directly by Geode) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9252) CI failure: NativeRedisClusterTestRule incorrect primary node count (expected 3 but was 2)
[
https://issues.apache.org/jira/browse/GEODE-9252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17355409#comment-17355409
]
Donal Evans commented on GEODE-9252:
Seen again in a PR pre-checkin run,
[https://concourse.apachegeode-ci.info/builds/44622#L6071513e:312]
Results archived below:
=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
http://files.apachegeode-ci.info/builds/apache-develop-pr/geode-pr-6523/test-results/acceptanceTest/1622590184/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Test report artifacts from this job are available at:
http://files.apachegeode-ci.info/builds/apache-develop-pr/geode-pr-6523/test-artifacts/1622590184/acceptancetestfiles-geode-pr-6523.tgz
> CI failure: NativeRedisClusterTestRule incorrect primary node count (expected
> 3 but was 2)
> --
>
> Key: GEODE-9252
> URL: https://issues.apache.org/jira/browse/GEODE-9252
> Project: Geode
> Issue Type: Bug
> Components: redis
>Reporter: Owen Nichols
>Assignee: Jens Deppe
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> {noformat}
> org.apache.geode.redis.internal.executor.hash.HashesNativeRedisAcceptanceTest
> > classMethod FAILED
> org.junit.ComparisonFailure: [Incorrect primary node count]
> expected:<[3]> but was:<[2]>
> at
> org.apache.geode.redis.NativeRedisClusterTestRule$1.evaluate(NativeRedisClusterTestRule.java:93)
> {noformat}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (GEODE-5304) RemoteTransactionCCEDUnitTest.testValuesIteratorOnDestroy FAILED
[
https://issues.apache.org/jira/browse/GEODE-5304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Louis R. Jacome reassigned GEODE-5304:
--
Assignee: Louis R. Jacome
> RemoteTransactionCCEDUnitTest.testValuesIteratorOnDestroy FAILED
>
>
> Key: GEODE-5304
> URL: https://issues.apache.org/jira/browse/GEODE-5304
> Project: Geode
> Issue Type: Bug
> Components: tests, transactions
>Reporter: Eric Shu
>Assignee: Louis R. Jacome
>Priority: Major
> Fix For: 1.15.0
>
>
> This failed in one of the precheckin run.
> The test assume that the accessor.invoke will use the some thread each time,
> but the assumption is wrong.
> Test could use suspend and resume the transaction to make sure the
> transaction can continue in different invoke methods.
> {noformat}
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.RemoteTransactionDUnitTest$58.call in VM 0
> running on Host 79f3f35365c7 with 4 VMs
> at org.apache.geode.test.dunit.VM.invoke(VM.java:436)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:405)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:371)
> at
> org.apache.geode.internal.cache.RemoteTransactionDUnitTest.doTestIterator(RemoteTransactionDUnitTest.java:2086)
> at
> org.apache.geode.internal.cache.RemoteTransactionDUnitTest.testValuesIteratorOnDestroy(RemoteTransactionDUnitTest.java:2013)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:114)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:57)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
[jira] [Reopened] (GEODE-9252) CI failure: NativeRedisClusterTestRule incorrect primary node count (expected 3 but was 2)
[
https://issues.apache.org/jira/browse/GEODE-9252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donal Evans reopened GEODE-9252:
> CI failure: NativeRedisClusterTestRule incorrect primary node count (expected
> 3 but was 2)
> --
>
> Key: GEODE-9252
> URL: https://issues.apache.org/jira/browse/GEODE-9252
> Project: Geode
> Issue Type: Bug
> Components: redis
>Reporter: Owen Nichols
>Assignee: Jens Deppe
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> {noformat}
> org.apache.geode.redis.internal.executor.hash.HashesNativeRedisAcceptanceTest
> > classMethod FAILED
> org.junit.ComparisonFailure: [Incorrect primary node count]
> expected:<[3]> but was:<[2]>
> at
> org.apache.geode.redis.NativeRedisClusterTestRule$1.evaluate(NativeRedisClusterTestRule.java:93)
> {noformat}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Reopened] (GEODE-5304) RemoteTransactionCCEDUnitTest.testValuesIteratorOnDestroy FAILED
[
https://issues.apache.org/jira/browse/GEODE-5304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donal Evans reopened GEODE-5304:
> RemoteTransactionCCEDUnitTest.testValuesIteratorOnDestroy FAILED
>
>
> Key: GEODE-5304
> URL: https://issues.apache.org/jira/browse/GEODE-5304
> Project: Geode
> Issue Type: Bug
> Components: tests, transactions
>Reporter: Eric Shu
>Priority: Major
> Fix For: 1.15.0
>
>
> This failed in one of the precheckin run.
> The test assume that the accessor.invoke will use the some thread each time,
> but the assumption is wrong.
> Test could use suspend and resume the transaction to make sure the
> transaction can continue in different invoke methods.
> {noformat}
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.RemoteTransactionDUnitTest$58.call in VM 0
> running on Host 79f3f35365c7 with 4 VMs
> at org.apache.geode.test.dunit.VM.invoke(VM.java:436)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:405)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:371)
> at
> org.apache.geode.internal.cache.RemoteTransactionDUnitTest.doTestIterator(RemoteTransactionDUnitTest.java:2086)
> at
> org.apache.geode.internal.cache.RemoteTransactionDUnitTest.testValuesIteratorOnDestroy(RemoteTransactionDUnitTest.java:2013)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:114)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:57)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>
[jira] [Commented] (GEODE-5304) RemoteTransactionCCEDUnitTest.testValuesIteratorOnDestroy FAILED
[
https://issues.apache.org/jira/browse/GEODE-5304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17355411#comment-17355411
]
Donal Evans commented on GEODE-5304:
Reoccurred in a [PR pre-checkin
run|https://concourse.apachegeode-ci.info/builds/44632#L60715386:678] at a
slightly different place:
{noformat}
org.apache.geode.internal.cache.RemoteTransactionDUnitTest >
testValuesIteratorOnDestroy FAILED
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.internal.cache.RemoteTransactionDUnitTest$58.call in VM 0
running on Host c2213f325f47 with 4 VMs
at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631)
at org.apache.geode.test.dunit.VM.invoke(VM.java:473)
at
org.apache.geode.internal.cache.RemoteTransactionDUnitTest.doTestIterator(RemoteTransactionDUnitTest.java:2103)
at
org.apache.geode.internal.cache.RemoteTransactionDUnitTest.testValuesIteratorOnDestroy(RemoteTransactionDUnitTest.java:2031)
Caused by:
java.lang.AssertionError
at org.junit.Assert.fail(Assert.java:87)
at org.junit.Assert.assertTrue(Assert.java:42)
at org.junit.Assert.assertNotNull(Assert.java:713)
at org.junit.Assert.assertNotNull(Assert.java:723)
at
org.apache.geode.internal.cache.RemoteTransactionDUnitTest$58.call(RemoteTransactionDUnitTest.java:2110)
{noformat}
Results are archived at (note, there is a second, unrelated failure in
ShutdownAllDUnitTest also present in these artifacts:
{noformat}
=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
http://files.apachegeode-ci.info/builds/apache-develop-pr/geode-pr-6523/test-results/distributedTest/1622589676/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Test report artifacts from this job are available at:
http://files.apachegeode-ci.info/builds/apache-develop-pr/geode-pr-6523/test-artifacts/1622589676/distributedtestfiles-geode-pr-6523.tgz
{noformat}
> RemoteTransactionCCEDUnitTest.testValuesIteratorOnDestroy FAILED
>
>
> Key: GEODE-5304
> URL: https://issues.apache.org/jira/browse/GEODE-5304
> Project: Geode
> Issue Type: Bug
> Components: tests, transactions
>Reporter: Eric Shu
>Priority: Major
> Fix For: 1.15.0
>
>
> This failed in one of the precheckin run.
> The test assume that the accessor.invoke will use the some thread each time,
> but the assumption is wrong.
> Test could use suspend and resume the transaction to make sure the
> transaction can continue in different invoke methods.
> {noformat}
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.RemoteTransactionDUnitTest$58.call in VM 0
> running on Host 79f3f35365c7 with 4 VMs
> at org.apache.geode.test.dunit.VM.invoke(VM.java:436)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:405)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:371)
> at
> org.apache.geode.internal.cache.RemoteTransactionDUnitTest.doTestIterator(RemoteTransactionDUnitTest.java:2086)
> at
> org.apache.geode.internal.cache.RemoteTransactionDUnitTest.testValuesIteratorOnDestroy(RemoteTransactionDUnitTest.java:2013)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at
[jira] [Updated] (GEODE-9338) Remove strong guarantees for redis PUBLISH command response
[
https://issues.apache.org/jira/browse/GEODE-9338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jens Deppe updated GEODE-9338:
--
Description:
Redis' {{PUBLISH}} command responds with the number of clients that have
received the published message. Our current implementation attempts to respond
with as accurate a number as possible. To that end, each publish (see
{{PubSubImpl.publishMessageToSubscribers}} and
{{AbstractSubscription.publishMessage}} are effectively synchronous operations.
The current flow is:
- PUBLISH some_message
- Issue a fn call to each server and attempt to publish to each subscribed
client
- Count how many successful publish messages were written and return those
- Respond to the redis client with the aggregated successful publishings
In redis clustering mode, the response is only the number of local publishings.
We can go even further and not attempt to first publish before subscribing, but
simply respond with the current number of subscribers, regardless whether they
are connected or not.
We should be able to perform all pubsub work on the regular netty thread and
completely remove the subscriber EventLoopGroup.
> Remove strong guarantees for redis PUBLISH command response
> ---
>
> Key: GEODE-9338
> URL: https://issues.apache.org/jira/browse/GEODE-9338
> Project: Geode
> Issue Type: Improvement
> Components: redis
>Reporter: Jens Deppe
>Priority: Major
>
> Redis' {{PUBLISH}} command responds with the number of clients that have
> received the published message. Our current implementation attempts to
> respond with as accurate a number as possible. To that end, each publish (see
> {{PubSubImpl.publishMessageToSubscribers}} and
> {{AbstractSubscription.publishMessage}} are effectively synchronous
> operations. The current flow is:
> - PUBLISH some_message
> - Issue a fn call to each server and attempt to publish to each subscribed
> client
> - Count how many successful publish messages were written and return those
> - Respond to the redis client with the aggregated successful publishings
> In redis clustering mode, the response is only the number of local
> publishings. We can go even further and not attempt to first publish before
> subscribing, but simply respond with the current number of subscribers,
> regardless whether they are connected or not.
> We should be able to perform all pubsub work on the regular netty thread and
> completely remove the subscriber EventLoopGroup.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-9338) Remove strong guarantees for redis PUBLISH command response
Jens Deppe created GEODE-9338: - Summary: Remove strong guarantees for redis PUBLISH command response Key: GEODE-9338 URL: https://issues.apache.org/jira/browse/GEODE-9338 Project: Geode Issue Type: Improvement Components: redis Reporter: Jens Deppe -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-9337) CI: session.NativeRedisSessionAcceptanceTest failed with Suspicious strings
[ https://issues.apache.org/jira/browse/GEODE-9337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaojian Zhou reassigned GEODE-9337: Assignee: Ray Ingles > CI: session.NativeRedisSessionAcceptanceTest failed with Suspicious strings > --- > > Key: GEODE-9337 > URL: https://issues.apache.org/jira/browse/GEODE-9337 > Project: Geode > Issue Type: Bug > Components: redis >Reporter: Xiaojian Zhou >Assignee: Ray Ingles >Priority: Major > > In acceptance test: > > Task :geode-apis-compatible-with-redis:acceptanceTest > session.NativeRedisSessionAcceptanceTest > classMethod 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-local.log' at line 1445 > [error 2021/06/01 17:35:16.963 UTC tid=98] Failed to > return response on inboundChannel > io.netty.channel.StacklessClosedChannelException > at io.netty.channel.AbstractChannel$AbstractUnsafe.write(Object, > ChannelPromise)(Unknown Source) > at org.junit.Assert.fail(Assert.java:89) > at > org.apache.geode.test.dunit.internal.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:409) > at > org.apache.geode.test.dunit.rules.ClusterStartupRule.after(ClusterStartupRule.java:185) > at > org.apache.geode.test.dunit.rules.ClusterStartupRule.access$100(ClusterStartupRule.java:69) > at > org.apache.geode.test.dunit.rules.ClusterStartupRule$1.evaluate(ClusterStartupRule.java:140) > at org.junit.rules.RunRules.evaluate(RunRules.java:20) > at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306) > at org.junit.runners.ParentRunner.run(ParentRunner.java:413) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:110) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38) > at > org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:62) > at > org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:36) > at > org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) > at > org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:33) > at > org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:94) > at com.sun.proxy.$Proxy2.processTestClass(Unknown Source) > at > org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:119) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:36) > at > org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) > at > org.gradle.internal.remote.internal.hub.MessageHubBackedObjectConnection$DispatchWrapper.dispatch(MessageHubBackedObjectConnection.java:182) > at > org.gradle.internal.remote.internal.hub.MessageHubBackedObjectConnection$DispatchWrapper.dispatch(MessageHubBackedObjectConnection.java:164) > at > org.gradle.internal.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:414) > at > org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64) > at > org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:48) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at >
[jira] [Commented] (GEODE-9337) CI: session.NativeRedisSessionAcceptanceTest failed with Suspicious strings
[ https://issues.apache.org/jira/browse/GEODE-9337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17355344#comment-17355344 ] Geode Integration commented on GEODE-9337: -- Seen in [acceptance-test-openjdk8 #5|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/acceptance-test-openjdk8/builds/5] ... see [test results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0281/test-results/acceptanceTest/1622576576/] or download [artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0281/test-artifacts/1622576576/acceptancetestfiles-openjdk8-1.15.0-build.0281.tgz]. > CI: session.NativeRedisSessionAcceptanceTest failed with Suspicious strings > --- > > Key: GEODE-9337 > URL: https://issues.apache.org/jira/browse/GEODE-9337 > Project: Geode > Issue Type: Bug > Components: redis >Reporter: Xiaojian Zhou >Assignee: Ray Ingles >Priority: Major > > In acceptance test: > > Task :geode-apis-compatible-with-redis:acceptanceTest > session.NativeRedisSessionAcceptanceTest > classMethod 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-local.log' at line 1445 > [error 2021/06/01 17:35:16.963 UTC tid=98] Failed to > return response on inboundChannel > io.netty.channel.StacklessClosedChannelException > at io.netty.channel.AbstractChannel$AbstractUnsafe.write(Object, > ChannelPromise)(Unknown Source) > at org.junit.Assert.fail(Assert.java:89) > at > org.apache.geode.test.dunit.internal.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:409) > at > org.apache.geode.test.dunit.rules.ClusterStartupRule.after(ClusterStartupRule.java:185) > at > org.apache.geode.test.dunit.rules.ClusterStartupRule.access$100(ClusterStartupRule.java:69) > at > org.apache.geode.test.dunit.rules.ClusterStartupRule$1.evaluate(ClusterStartupRule.java:140) > at org.junit.rules.RunRules.evaluate(RunRules.java:20) > at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306) > at org.junit.runners.ParentRunner.run(ParentRunner.java:413) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:110) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38) > at > org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:62) > at > org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:36) > at > org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) > at > org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:33) > at > org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:94) > at com.sun.proxy.$Proxy2.processTestClass(Unknown Source) > at > org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:119) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:36) > at > org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) > at > org.gradle.internal.remote.internal.hub.MessageHubBackedObjectConnection$DispatchWrapper.dispatch(MessageHubBackedObjectConnection.java:182) > at >
[jira] [Created] (GEODE-9337) CI: session.NativeRedisSessionAcceptanceTest failed with Suspicious strings
Xiaojian Zhou created GEODE-9337: Summary: CI: session.NativeRedisSessionAcceptanceTest failed with Suspicious strings Key: GEODE-9337 URL: https://issues.apache.org/jira/browse/GEODE-9337 Project: Geode Issue Type: Bug Components: redis Reporter: Xiaojian Zhou In acceptance test: > Task :geode-apis-compatible-with-redis:acceptanceTest session.NativeRedisSessionAcceptanceTest > classMethod 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-local.log' at line 1445 [error 2021/06/01 17:35:16.963 UTC tid=98] Failed to return response on inboundChannel io.netty.channel.StacklessClosedChannelException at io.netty.channel.AbstractChannel$AbstractUnsafe.write(Object, ChannelPromise)(Unknown Source) at org.junit.Assert.fail(Assert.java:89) at org.apache.geode.test.dunit.internal.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:409) at org.apache.geode.test.dunit.rules.ClusterStartupRule.after(ClusterStartupRule.java:185) at org.apache.geode.test.dunit.rules.ClusterStartupRule.access$100(ClusterStartupRule.java:69) at org.apache.geode.test.dunit.rules.ClusterStartupRule$1.evaluate(ClusterStartupRule.java:140) at org.junit.rules.RunRules.evaluate(RunRules.java:20) at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306) at org.junit.runners.ParentRunner.run(ParentRunner.java:413) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:110) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38) at org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:62) at org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:36) at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) at org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:33) at org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:94) at com.sun.proxy.$Proxy2.processTestClass(Unknown Source) at org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:119) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:36) at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) at org.gradle.internal.remote.internal.hub.MessageHubBackedObjectConnection$DispatchWrapper.dispatch(MessageHubBackedObjectConnection.java:182) at org.gradle.internal.remote.internal.hub.MessageHubBackedObjectConnection$DispatchWrapper.dispatch(MessageHubBackedObjectConnection.java:164) at org.gradle.internal.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:414) at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64) at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:48) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:56) at java.lang.Thread.run(Thread.java:748) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-9336) Implement ZADD option CH
[ https://issues.apache.org/jira/browse/GEODE-9336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Louis R. Jacome reassigned GEODE-9336: -- Assignee: Louis R. Jacome > Implement ZADD option CH > > > Key: GEODE-9336 > URL: https://issues.apache.org/jira/browse/GEODE-9336 > Project: Geode > Issue Type: Improvement > Components: redis >Affects Versions: 1.15.0 >Reporter: Louis R. Jacome >Assignee: Louis R. Jacome >Priority: Major > > CH option for ZADD > CH: Modify the return value from the number of new elements added, to the > total number of elements changed (CH is an abbreviation of changed). Changed > elements are new elements added and elements already existing for which the > score was updated. So elements specified in the command line having the same > score as they had in the past are not counted. Note: normally the return > value of ZADD only counts the number of new elements added. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-9292) Implement ZCARD
[ https://issues.apache.org/jira/browse/GEODE-9292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Louis R. Jacome resolved GEODE-9292. Fix Version/s: 1.15.0 Resolution: Fixed > Implement ZCARD > --- > > Key: GEODE-9292 > URL: https://issues.apache.org/jira/browse/GEODE-9292 > Project: Geode > Issue Type: Improvement > Components: redis >Affects Versions: 1.15.0 >Reporter: Louis R. Jacome >Assignee: Louis R. Jacome >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > Implement ZCARD redis command -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-9292) Implement ZCARD
[ https://issues.apache.org/jira/browse/GEODE-9292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Louis R. Jacome reassigned GEODE-9292: -- Assignee: Louis R. Jacome > Implement ZCARD > --- > > Key: GEODE-9292 > URL: https://issues.apache.org/jira/browse/GEODE-9292 > Project: Geode > Issue Type: Improvement > Components: redis >Affects Versions: 1.15.0 >Reporter: Louis R. Jacome >Assignee: Louis R. Jacome >Priority: Major > Labels: pull-request-available > > Implement ZCARD redis command -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9292) Implement ZCARD
[ https://issues.apache.org/jira/browse/GEODE-9292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17355338#comment-17355338 ] ASF subversion and git services commented on GEODE-9292: Commit 92e8f788e11572820998a0c541d819f28bdd4648 in geode's branch refs/heads/develop from Louis Jacome [ https://gitbox.apache.org/repos/asf?p=geode.git;h=92e8f78 ] GEODE-9292: Implement ZCARD (#6525) > Implement ZCARD > --- > > Key: GEODE-9292 > URL: https://issues.apache.org/jira/browse/GEODE-9292 > Project: Geode > Issue Type: Improvement > Components: redis >Affects Versions: 1.15.0 >Reporter: Louis R. Jacome >Priority: Major > Labels: pull-request-available > > Implement ZCARD redis command -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9316) user guide typo repairs
[ https://issues.apache.org/jira/browse/GEODE-9316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17355335#comment-17355335 ] ASF subversion and git services commented on GEODE-9316: Commit 9d7ed44ff7e068872671e278e953c94a54fd345d in geode's branch refs/heads/support/1.14 from Dave Barnes [ https://gitbox.apache.org/repos/asf?p=geode.git;h=9d7ed44 ] GEODE-9316: user guide typo repairs (#6541) > user guide typo repairs > --- > > Key: GEODE-9316 > URL: https://issues.apache.org/jira/browse/GEODE-9316 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Labels: pull-request-available > Fix For: 1.14.0, 1.15.0 > > > Some small fixes grouped together for convenience. > * > [https://geode.apache.org/docs/guide/113/managing/monitor_tune/system_member_performance_distributed_system_member.html] > Add a space in bullet-list item beginning "*statistic-sampling-enabled*." > * > [https://geode.apache.org/docs/guide/113/managing/management/management_and_monitoring_features.html] > Second bullet item, change "programs no longer require access" to "programs > do not require access". -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-9316) user guide typo repairs
[ https://issues.apache.org/jira/browse/GEODE-9316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-9316. Fix Version/s: 1.15.0 1.14.0 Resolution: Fixed > user guide typo repairs > --- > > Key: GEODE-9316 > URL: https://issues.apache.org/jira/browse/GEODE-9316 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Labels: pull-request-available > Fix For: 1.14.0, 1.15.0 > > > Some small fixes grouped together for convenience. > * > [https://geode.apache.org/docs/guide/113/managing/monitor_tune/system_member_performance_distributed_system_member.html] > Add a space in bullet-list item beginning "*statistic-sampling-enabled*." > * > [https://geode.apache.org/docs/guide/113/managing/management/management_and_monitoring_features.html] > Second bullet item, change "programs no longer require access" to "programs > do not require access". -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9316) user guide typo repairs
[ https://issues.apache.org/jira/browse/GEODE-9316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17355334#comment-17355334 ] ASF subversion and git services commented on GEODE-9316: Commit ace71807f07d25637e9669b01e3059f742359ec7 in geode's branch refs/heads/develop from Dave Barnes [ https://gitbox.apache.org/repos/asf?p=geode.git;h=ace7180 ] GEODE-9316: user guide typo repairs (#6541) > user guide typo repairs > --- > > Key: GEODE-9316 > URL: https://issues.apache.org/jira/browse/GEODE-9316 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Labels: pull-request-available > > Some small fixes grouped together for convenience. > * > [https://geode.apache.org/docs/guide/113/managing/monitor_tune/system_member_performance_distributed_system_member.html] > Add a space in bullet-list item beginning "*statistic-sampling-enabled*." > * > [https://geode.apache.org/docs/guide/113/managing/management/management_and_monitoring_features.html] > Second bullet item, change "programs no longer require access" to "programs > do not require access". -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9316) user guide typo repairs
[ https://issues.apache.org/jira/browse/GEODE-9316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-9316: -- Labels: pull-request-available (was: ) > user guide typo repairs > --- > > Key: GEODE-9316 > URL: https://issues.apache.org/jira/browse/GEODE-9316 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Labels: pull-request-available > > Some small fixes grouped together for convenience. > * > [https://geode.apache.org/docs/guide/113/managing/monitor_tune/system_member_performance_distributed_system_member.html] > Add a space in bullet-list item beginning "*statistic-sampling-enabled*." > * > [https://geode.apache.org/docs/guide/113/managing/management/management_and_monitoring_features.html] > Second bullet item, change "programs no longer require access" to "programs > do not require access". -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-9336) Implement ZADD option CH
Louis R. Jacome created GEODE-9336: -- Summary: Implement ZADD option CH Key: GEODE-9336 URL: https://issues.apache.org/jira/browse/GEODE-9336 Project: Geode Issue Type: Improvement Components: redis Affects Versions: 1.15.0 Reporter: Louis R. Jacome CH option for ZADD CH: Modify the return value from the number of new elements added, to the total number of elements changed (CH is an abbreviation of changed). Changed elements are new elements added and elements already existing for which the score was updated. So elements specified in the command line having the same score as they had in the past are not counted. Note: normally the return value of ZADD only counts the number of new elements added. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-9335) Organize HitsMissesIntegrationTest
Hale Bales created GEODE-9335: - Summary: Organize HitsMissesIntegrationTest Key: GEODE-9335 URL: https://issues.apache.org/jira/browse/GEODE-9335 Project: Geode Issue Type: Task Components: redis Affects Versions: 1.15.0 Reporter: Hale Bales the HitsMissesIntegrationTest has sections divided by comments to keep all the supported commands separate from the unsupported ones, and to keep commands of the same type together within the supported/unsupported sections. as we added more supported commands, we didn't move the tests into the right section. A.C. All the tests that test supported commands have been moved to the appropriate section. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9299) CI Failure: WANRollingUpgradeSecondaryEventsNotReprocessedAfterOldSiteMemberFailover > testSecondaryEventsNotReprocessedAfterOldSiteMemberFailover
[
https://issues.apache.org/jira/browse/GEODE-9299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17355240#comment-17355240
]
ASF subversion and git services commented on GEODE-9299:
Commit be70505db870b1501103adf18080768058803ccd in geode's branch
refs/heads/develop from Barry Oglesby
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=be70505 ]
GEODE-9299: Assert greater than or equal instead of equals (#6536)
> CI Failure:
> WANRollingUpgradeSecondaryEventsNotReprocessedAfterOldSiteMemberFailover >
> testSecondaryEventsNotReprocessedAfterOldSiteMemberFailover
> --
>
> Key: GEODE-9299
> URL: https://issues.apache.org/jira/browse/GEODE-9299
> Project: Geode
> Issue Type: Bug
> Components: wan
>Affects Versions: 1.15.0
>Reporter: Hale Bales
>Assignee: Barrett Oglesby
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> {code:java}
> org.apache.geode.cache.wan.WANRollingUpgradeSecondaryEventsNotReprocessedAfterOldSiteMemberFailover
> > testSecondaryEventsNotReprocessedAfterOldSiteMemberFailover[from_v1.12.2]
> FAILED
> java.lang.AssertionError: expected:<100> but was:<101>
> at org.junit.Assert.fail(Assert.java:89)
> at org.junit.Assert.failNotEquals(Assert.java:835)
> at org.junit.Assert.assertEquals(Assert.java:647)
> at org.junit.Assert.assertEquals(Assert.java:633)
> at
> org.apache.geode.cache.wan.WANRollingUpgradeDUnitTest.stopSenderAndVerifyEvents(WANRollingUpgradeDUnitTest.java:227)
> at
> org.apache.geode.cache.wan.WANRollingUpgradeSecondaryEventsNotReprocessedAfterOldSiteMemberFailover.testSecondaryEventsNotReprocessedAfterOldSiteMemberFailover(WANRollingUpgradeSecondaryEventsNotReprocessedAfterOldSiteMemberFailover.java:98)
> {code}
> CI Failure:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/UpgradeTestOpenJDK11/builds/229#B
> Artifacts Available here:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0253/test-results/upgradeTest/1621635640/
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (GEODE-9299) CI Failure: WANRollingUpgradeSecondaryEventsNotReprocessedAfterOldSiteMemberFailover > testSecondaryEventsNotReprocessedAfterOldSiteMemberFailover
[
https://issues.apache.org/jira/browse/GEODE-9299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barrett Oglesby resolved GEODE-9299.
Fix Version/s: 1.15.0
Resolution: Fixed
> CI Failure:
> WANRollingUpgradeSecondaryEventsNotReprocessedAfterOldSiteMemberFailover >
> testSecondaryEventsNotReprocessedAfterOldSiteMemberFailover
> --
>
> Key: GEODE-9299
> URL: https://issues.apache.org/jira/browse/GEODE-9299
> Project: Geode
> Issue Type: Bug
> Components: wan
>Affects Versions: 1.15.0
>Reporter: Hale Bales
>Assignee: Barrett Oglesby
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> {code:java}
> org.apache.geode.cache.wan.WANRollingUpgradeSecondaryEventsNotReprocessedAfterOldSiteMemberFailover
> > testSecondaryEventsNotReprocessedAfterOldSiteMemberFailover[from_v1.12.2]
> FAILED
> java.lang.AssertionError: expected:<100> but was:<101>
> at org.junit.Assert.fail(Assert.java:89)
> at org.junit.Assert.failNotEquals(Assert.java:835)
> at org.junit.Assert.assertEquals(Assert.java:647)
> at org.junit.Assert.assertEquals(Assert.java:633)
> at
> org.apache.geode.cache.wan.WANRollingUpgradeDUnitTest.stopSenderAndVerifyEvents(WANRollingUpgradeDUnitTest.java:227)
> at
> org.apache.geode.cache.wan.WANRollingUpgradeSecondaryEventsNotReprocessedAfterOldSiteMemberFailover.testSecondaryEventsNotReprocessedAfterOldSiteMemberFailover(WANRollingUpgradeSecondaryEventsNotReprocessedAfterOldSiteMemberFailover.java:98)
> {code}
> CI Failure:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/UpgradeTestOpenJDK11/builds/229#B
> Artifacts Available here:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0253/test-results/upgradeTest/1621635640/
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9334) Geode Native User Guide: update dockerfile to use newer ruby & gems
[ https://issues.apache.org/jira/browse/GEODE-9334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17355087#comment-17355087 ] ASF GitHub Bot commented on GEODE-9334: --- alb3rtobr opened a new pull request #816: URL: https://github.com/apache/geode-native/pull/816 This PR aligns the user guide generation instructions and scripts with the instructions recently added in Geode (see GEODE-9042). Uplifts Bookbinder and other gems version, and simplifies the Docker-based scripts to preview the user guides. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Geode Native User Guide: update dockerfile to use newer ruby & gems > --- > > Key: GEODE-9334 > URL: https://issues.apache.org/jira/browse/GEODE-9334 > Project: Geode > Issue Type: Improvement > Components: docs, native client >Reporter: Alberto Bustamante Reyes >Assignee: Alberto Bustamante Reyes >Priority: Major > > Update the Geode Native docker-based scripts to generate the user guides, > following the same process done for Geode User Guide (GEODE-9042) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9334) Geode Native User Guide: update dockerfile to use newer ruby & gems
[ https://issues.apache.org/jira/browse/GEODE-9334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-9334: -- Labels: pull-request-available (was: ) > Geode Native User Guide: update dockerfile to use newer ruby & gems > --- > > Key: GEODE-9334 > URL: https://issues.apache.org/jira/browse/GEODE-9334 > Project: Geode > Issue Type: Improvement > Components: docs, native client >Reporter: Alberto Bustamante Reyes >Assignee: Alberto Bustamante Reyes >Priority: Major > Labels: pull-request-available > > Update the Geode Native docker-based scripts to generate the user guides, > following the same process done for Geode User Guide (GEODE-9042) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-9334) Geode Native User Guide: update dockerfile to use newer ruby & gems
[ https://issues.apache.org/jira/browse/GEODE-9334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Bustamante Reyes reassigned GEODE-9334: --- Assignee: Alberto Bustamante Reyes > Geode Native User Guide: update dockerfile to use newer ruby & gems > --- > > Key: GEODE-9334 > URL: https://issues.apache.org/jira/browse/GEODE-9334 > Project: Geode > Issue Type: Improvement > Components: docs, native client >Reporter: Alberto Bustamante Reyes >Assignee: Alberto Bustamante Reyes >Priority: Major > > Update the Geode Native docker-based scripts to generate the user guides, > following the same process done for Geode User Guide (GEODE-9042) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-9334) Geode Native User Guide: update dockerfile to use newer ruby & gems
Alberto Bustamante Reyes created GEODE-9334: --- Summary: Geode Native User Guide: update dockerfile to use newer ruby & gems Key: GEODE-9334 URL: https://issues.apache.org/jira/browse/GEODE-9334 Project: Geode Issue Type: Improvement Components: docs, native client Reporter: Alberto Bustamante Reyes Update the Geode Native docker-based scripts to generate the user guides, following the same process done for Geode User Guide (GEODE-9042) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-9042) Geode User Guide: update dockerfile to use newer ruby & gems
[ https://issues.apache.org/jira/browse/GEODE-9042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Bustamante Reyes resolved GEODE-9042. - Fix Version/s: 1.15.0 Resolution: Fixed > Geode User Guide: update dockerfile to use newer ruby & gems > > > Key: GEODE-9042 > URL: https://issues.apache.org/jira/browse/GEODE-9042 > Project: Geode > Issue Type: Improvement > Components: docs, tools >Affects Versions: 1.13.1 >Reporter: Dave Barnes >Assignee: Alberto Bustamante Reyes >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > The scripts that build the user guide are pinned at Ruby 2.3.0 and Bookbinder > 1.10.14. > These need to be updated to Ruby 2.5.3 (or later) and Bookbinder 1.10.15 in > order to support current deployment infrastructure. > Path to the Bookbinder gem: > http://docs-wiki.cfapps.io/wiki/bookbinder/installing-bookbinder.html#v10 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9042) Geode User Guide: update dockerfile to use newer ruby & gems
[ https://issues.apache.org/jira/browse/GEODE-9042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17354913#comment-17354913 ] ASF subversion and git services commented on GEODE-9042: Commit 6a3e2cb6c302b02fceeb57e09b3c6cf41a7fbcf6 in geode's branch refs/heads/develop from Alberto Bustamante Reyes [ https://gitbox.apache.org/repos/asf?p=geode.git;h=6a3e2cb ] GEODE-9042: Update docker-based scripts to build UG (#6528) > Geode User Guide: update dockerfile to use newer ruby & gems > > > Key: GEODE-9042 > URL: https://issues.apache.org/jira/browse/GEODE-9042 > Project: Geode > Issue Type: Improvement > Components: docs, tools >Affects Versions: 1.13.1 >Reporter: Dave Barnes >Assignee: Alberto Bustamante Reyes >Priority: Major > Labels: pull-request-available > > The scripts that build the user guide are pinned at Ruby 2.3.0 and Bookbinder > 1.10.14. > These need to be updated to Ruby 2.5.3 (or later) and Bookbinder 1.10.15 in > order to support current deployment infrastructure. > Path to the Bookbinder gem: > http://docs-wiki.cfapps.io/wiki/bookbinder/installing-bookbinder.html#v10 -- This message was sent by Atlassian Jira (v8.3.4#803005)
