[jira] [Commented] (GEODE-10074) Remove ACE remains
[ https://issues.apache.org/jira/browse/GEODE-10074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17497284#comment-17497284 ] ASF GitHub Bot commented on GEODE-10074: gaussianrecurrence commented on a change in pull request #928: URL: https://github.com/apache/geode-native/pull/928#discussion_r813702430 ## File path: cppcache/integration-test/CMakeLists.txt ## @@ -69,6 +67,10 @@ add_clangformat(unit_test_callbacks) enable_testing() +if(UNIX AND NOT APPLE) Review comment: It's true that my solution for this is not the best one. Regarding root CMakeLists.txt I don't think it makes sense, as rt is only needed for the shared memory API, which is used only by integration-tests. I'll try the find_library approach for this -- 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. To unsubscribe, e-mail: notifications-unsubscr...@geode.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Remove ACE remains > -- > > Key: GEODE-10074 > URL: https://issues.apache.org/jira/browse/GEODE-10074 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Mario Salazar de Torres >Assignee: Mario Salazar de Torres >Priority: Major > Labels: obliterate-ace, pull-request-available > > *AS A* geode-native contributor > *I WANT TO* remove all the ACE remaining > *SO THAT* geode-native does not depend on ACE anymore -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10074) Remove ACE remains
[
https://issues.apache.org/jira/browse/GEODE-10074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17497285#comment-17497285
]
ASF GitHub Bot commented on GEODE-10074:
gaussianrecurrence commented on a change in pull request #928:
URL: https://github.com/apache/geode-native/pull/928#discussion_r813704606
##
File path: cppcache/src/CppCacheLibrary.cpp
##
@@ -36,18 +33,15 @@ namespace apache {
namespace geode {
namespace client {
-void CppCacheLibrary::initLib(void) { ACE::init(); }
+void CppCacheLibrary::initLib(void) {}
-void CppCacheLibrary::closeLib(void) {
- // DO NOT CALL ACE::fini() HERE!
- // Things might be using ace beyond the life of Geode.
-}
+void CppCacheLibrary::closeLib(void) {}
std::string CppCacheLibrary::initProductLibDir() {
// otherwise... get the DLL path, and work backwards from it.
- char buffer[PATH_MAX + 1];
+ char buffer[4097];
Review comment:
Ups, my bad, I did hardcode this while testing and forgot to properly
solve it. Thanks for pointing it out :)
--
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.
To unsubscribe, e-mail: notifications-unsubscr...@geode.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Remove ACE remains
> --
>
> Key: GEODE-10074
> URL: https://issues.apache.org/jira/browse/GEODE-10074
> Project: Geode
> Issue Type: Improvement
> Components: native client
>Reporter: Mario Salazar de Torres
>Assignee: Mario Salazar de Torres
>Priority: Major
> Labels: obliterate-ace, pull-request-available
>
> *AS A* geode-native contributor
> *I WANT TO* remove all the ACE remaining
> *SO THAT* geode-native does not depend on ACE anymore
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-10074) Remove ACE remains
[
https://issues.apache.org/jira/browse/GEODE-10074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17497287#comment-17497287
]
ASF GitHub Bot commented on GEODE-10074:
gaussianrecurrence commented on a change in pull request #928:
URL: https://github.com/apache/geode-native/pull/928#discussion_r813704882
##
File path: cppcache/src/CppCacheLibrary.cpp
##
@@ -36,18 +33,15 @@ namespace apache {
namespace geode {
namespace client {
-void CppCacheLibrary::initLib(void) { ACE::init(); }
+void CppCacheLibrary::initLib(void) {}
-void CppCacheLibrary::closeLib(void) {
- // DO NOT CALL ACE::fini() HERE!
- // Things might be using ace beyond the life of Geode.
-}
+void CppCacheLibrary::closeLib(void) {}
std::string CppCacheLibrary::initProductLibDir() {
// otherwise... get the DLL path, and work backwards from it.
- char buffer[PATH_MAX + 1];
+ char buffer[4097];
buffer[0] = '\0';
- DllMainGetPath(buffer, PATH_MAX);
+ DllMainGetPath(buffer, 4096);
Review comment:
See below comment
--
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.
To unsubscribe, e-mail: notifications-unsubscr...@geode.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Remove ACE remains
> --
>
> Key: GEODE-10074
> URL: https://issues.apache.org/jira/browse/GEODE-10074
> Project: Geode
> Issue Type: Improvement
> Components: native client
>Reporter: Mario Salazar de Torres
>Assignee: Mario Salazar de Torres
>Priority: Major
> Labels: obliterate-ace, pull-request-available
>
> *AS A* geode-native contributor
> *I WANT TO* remove all the ACE remaining
> *SO THAT* geode-native does not depend on ACE anymore
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-10074) Remove ACE remains
[ https://issues.apache.org/jira/browse/GEODE-10074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17497291#comment-17497291 ] ASF GitHub Bot commented on GEODE-10074: gaussianrecurrence commented on a change in pull request #928: URL: https://github.com/apache/geode-native/pull/928#discussion_r813706974 ## File path: cppcache/integration-test/fw_helper.hpp ## @@ -107,7 +105,7 @@ BEGIN_TEST. #define ASSERT_EQ(x, y) _ASSERT_EQ(x, y, __LINE__, __FILE__) #define ASSERT_STREQ(x, y)\ - ASSERT((strcmp(x, y) == 0), \ + ASSERT(x == y, \ Review comment: Well thing is this ASSERT_STREQ macro is only used in one place within integration-tests, so I'd rather remove this macro and use operator== in-place. For reference here is the only place where it's used: https://github.com/apache/geode-native/blob/a072c8f69aa59335ab0b134f435f174c97d0ac22/cppcache/integration-test/testSystemProperties.cpp#L61 As you can see it's safe to remove this macro and use operator== from std::string -- 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. To unsubscribe, e-mail: notifications-unsubscr...@geode.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Remove ACE remains > -- > > Key: GEODE-10074 > URL: https://issues.apache.org/jira/browse/GEODE-10074 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Mario Salazar de Torres >Assignee: Mario Salazar de Torres >Priority: Major > Labels: obliterate-ace, pull-request-available > > *AS A* geode-native contributor > *I WANT TO* remove all the ACE remaining > *SO THAT* geode-native does not depend on ACE anymore -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10074) Remove ACE remains
[ https://issues.apache.org/jira/browse/GEODE-10074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17497384#comment-17497384 ] ASF GitHub Bot commented on GEODE-10074: pivotal-jbarrett commented on a change in pull request #928: URL: https://github.com/apache/geode-native/pull/928#discussion_r813859028 ## File path: cppcache/integration-test/fw_helper.hpp ## @@ -107,7 +105,7 @@ BEGIN_TEST. #define ASSERT_EQ(x, y) _ASSERT_EQ(x, y, __LINE__, __FILE__) #define ASSERT_STREQ(x, y)\ - ASSERT((strcmp(x, y) == 0), \ + ASSERT(x == y, \ Review comment: Yes! So that! One less macro! -- 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. To unsubscribe, e-mail: notifications-unsubscr...@geode.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Remove ACE remains > -- > > Key: GEODE-10074 > URL: https://issues.apache.org/jira/browse/GEODE-10074 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Mario Salazar de Torres >Assignee: Mario Salazar de Torres >Priority: Major > Labels: obliterate-ace, pull-request-available > > *AS A* geode-native contributor > *I WANT TO* remove all the ACE remaining > *SO THAT* geode-native does not depend on ACE anymore -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-10081) Freeze during launch of locator
Julien Gilles created GEODE-10081: - Summary: Freeze during launch of locator Key: GEODE-10081 URL: https://issues.apache.org/jira/browse/GEODE-10081 Project: Geode Issue Type: Bug Components: gfsh Affects Versions: 1.14.2 Reporter: Julien Gilles We are using gfsh with a script to automatically launch a locator and a server. During the launch of the locator, the process gfsh just freezes randomly. The locator process is forked, but gfsh remains frozen. A jstack on the process shows that the process is stuck on an internal NativeLibrary.load call. This one happens when gfsh try to attach to the process : internally the jvm loads the libattach.so library, but the call never return. To be complete, Geode is here deployed inside a docker container, using ubi8 as base image, java is jdk11.0.11 - we have tested with 11.0.13, same issue. The stack is the following : "main" #1 prio=5 os_prio=0 cpu=2402.78ms elapsed=1924.45s allocated=236M defined_classes=10346 tid=0x7fc904024000 nid=0x16 runnable [0x7fc90a84a000] java.lang.Thread.State: RUNNABLE at java.lang.ClassLoader$NativeLibrary.load0(java.base@11.0.11/Native Method) at java.lang.ClassLoader$NativeLibrary.load(java.base@11.0.11/Unknown Source) at java.lang.ClassLoader$NativeLibrary.loadLibrary(java.base@11.0.11/Unknown Source) - locked <0x823efe60> (a java.util.HashSet) at java.lang.ClassLoader.loadLibrary0(java.base@11.0.11/Unknown Source) at java.lang.ClassLoader.loadLibrary(java.base@11.0.11/Unknown Source) at java.lang.Runtime.loadLibrary0(java.base@11.0.11/Unknown Source) - locked <0x828224b8> (a java.lang.Runtime) at java.lang.System.loadLibrary(java.base@11.0.11/Unknown Source) at sun.tools.attach.VirtualMachineImpl.(jdk.attach@11.0.11/Unknown Source) at sun.tools.attach.AttachProviderImpl.attachVirtualMachine(jdk.attach@11.0.11/Unknown Source) at com.sun.tools.attach.VirtualMachine.attach(jdk.attach@11.0.11/Unknown Source) at org.apache.geode.internal.process.MBeanProcessController.getJMXServiceURL(MBeanProcessController.java:227) at org.apache.geode.internal.process.MBeanProcessController.connect(MBeanProcessController.java:192) at org.apache.geode.internal.process.MBeanProcessController.invokeOperationOnTargetMBean(MBeanProcessController.java:159) at org.apache.geode.internal.process.MBeanProcessController.status(MBeanProcessController.java:136) at org.apache.geode.internal.process.MBeanProcessController.status(MBeanProcessController.java:81) at org.apache.geode.internal.process.MBeanOrFileProcessController.status(MBeanOrFileProcessController.java:37) at org.apache.geode.distributed.LocatorLauncher.statusWithWorkingDirectory(LocatorLauncher.java:1012) at org.apache.geode.distributed.LocatorLauncher.status(LocatorLauncher.java:940) at org.apache.geode.distributed.LocatorLauncher$LocatorState.fromDirectory(LocatorLauncher.java:2077) at org.apache.geode.management.internal.cli.commands.StartLocatorCommand.doStartLocator(StartLocatorCommand.java:267) at org.apache.geode.management.internal.cli.commands.StartLocatorCommand.startLocator(StartLocatorCommand.java:133) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(java.base@11.0.11/Native Method) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(java.base@11.0.11/Unknown Source) at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(java.base@11.0.11/Unknown Source) at java.lang.reflect.Method.invoke(java.base@11.0.11/Unknown Source) at org.springframework.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:282) at org.apache.geode.management.internal.cli.remote.CommandExecutor.callInvokeMethod(CommandExecutor.java:139) at org.apache.geode.management.internal.cli.remote.CommandExecutor.invokeCommand(CommandExecutor.java:149) -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10081) Freeze during launch of locator
[ https://issues.apache.org/jira/browse/GEODE-10081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-10081: -- Labels: needsTriage (was: ) > Freeze during launch of locator > --- > > Key: GEODE-10081 > URL: https://issues.apache.org/jira/browse/GEODE-10081 > Project: Geode > Issue Type: Bug > Components: gfsh >Affects Versions: 1.14.2 >Reporter: Julien Gilles >Priority: Major > Labels: needsTriage > > We are using gfsh with a script to automatically launch a locator and a > server. > During the launch of the locator, the process gfsh just freezes randomly. The > locator process is forked, but gfsh remains frozen. > A jstack on the process shows that the process is stuck on an internal > NativeLibrary.load call. This one happens when gfsh try to attach to the > process : internally the jvm loads the libattach.so library, but the call > never return. > To be complete, Geode is here deployed inside a docker container, using ubi8 > as base image, java is jdk11.0.11 - we have tested with 11.0.13, same issue. > > The stack is the following : > "main" #1 prio=5 os_prio=0 cpu=2402.78ms elapsed=1924.45s allocated=236M > defined_classes=10346 tid=0x7fc904024000 nid=0x16 runnable > [0x7fc90a84a000] > java.lang.Thread.State: RUNNABLE > at java.lang.ClassLoader$NativeLibrary.load0(java.base@11.0.11/Native > Method) > at java.lang.ClassLoader$NativeLibrary.load(java.base@11.0.11/Unknown > Source) > at > java.lang.ClassLoader$NativeLibrary.loadLibrary(java.base@11.0.11/Unknown > Source) > - locked <0x823efe60> (a java.util.HashSet) > at java.lang.ClassLoader.loadLibrary0(java.base@11.0.11/Unknown Source) > at java.lang.ClassLoader.loadLibrary(java.base@11.0.11/Unknown Source) > at java.lang.Runtime.loadLibrary0(java.base@11.0.11/Unknown Source) > - locked <0x828224b8> (a java.lang.Runtime) > at java.lang.System.loadLibrary(java.base@11.0.11/Unknown Source) > at > sun.tools.attach.VirtualMachineImpl.(jdk.attach@11.0.11/Unknown > Source) > at > sun.tools.attach.AttachProviderImpl.attachVirtualMachine(jdk.attach@11.0.11/Unknown > Source) > at com.sun.tools.attach.VirtualMachine.attach(jdk.attach@11.0.11/Unknown > Source) > at > org.apache.geode.internal.process.MBeanProcessController.getJMXServiceURL(MBeanProcessController.java:227) > at > org.apache.geode.internal.process.MBeanProcessController.connect(MBeanProcessController.java:192) > at > org.apache.geode.internal.process.MBeanProcessController.invokeOperationOnTargetMBean(MBeanProcessController.java:159) > at > org.apache.geode.internal.process.MBeanProcessController.status(MBeanProcessController.java:136) > at > org.apache.geode.internal.process.MBeanProcessController.status(MBeanProcessController.java:81) > at > org.apache.geode.internal.process.MBeanOrFileProcessController.status(MBeanOrFileProcessController.java:37) > at > org.apache.geode.distributed.LocatorLauncher.statusWithWorkingDirectory(LocatorLauncher.java:1012) > at > org.apache.geode.distributed.LocatorLauncher.status(LocatorLauncher.java:940) > at > org.apache.geode.distributed.LocatorLauncher$LocatorState.fromDirectory(LocatorLauncher.java:2077) > at > org.apache.geode.management.internal.cli.commands.StartLocatorCommand.doStartLocator(StartLocatorCommand.java:267) > at > org.apache.geode.management.internal.cli.commands.StartLocatorCommand.startLocator(StartLocatorCommand.java:133) > at > jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(java.base@11.0.11/Native > Method) > at > jdk.internal.reflect.NativeMethodAccessorImpl.invoke(java.base@11.0.11/Unknown > Source) > at > jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(java.base@11.0.11/Unknown > Source) > at java.lang.reflect.Method.invoke(java.base@11.0.11/Unknown Source) > at > org.springframework.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:282) > at > org.apache.geode.management.internal.cli.remote.CommandExecutor.callInvokeMethod(CommandExecutor.java:139) > at > org.apache.geode.management.internal.cli.remote.CommandExecutor.invokeCommand(CommandExecutor.java:149) -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10081) Freeze during launch of locator
[ https://issues.apache.org/jira/browse/GEODE-10081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julien Gilles updated GEODE-10081: -- Attachment: jstackout.txt Description: We are using gfsh with a script to automatically launch a locator and a server. During the launch of the locator, the process gfsh just freezes randomly. The locator process is forked, but gfsh remains frozen. A jstack on the process shows that the process is stuck on an internal NativeLibrary.load call. This one happens when gfsh try to attach to the process : internally the jvm loads the libattach.so library, but the call never return. To be complete, Geode is here deployed inside a docker container, using ubi8 as base image, java is jdk11.0.11 - we have tested with 11.0.13, same issue. The stack is the following (full jstack dump attached) "main" #1 prio=5 os_prio=0 cpu=2402.78ms elapsed=1924.45s allocated=236M defined_classes=10346 tid=0x7fc904024000 nid=0x16 runnable [0x7fc90a84a000] java.lang.Thread.State: RUNNABLE at java.lang.ClassLoader$NativeLibrary.load0(java.base@11.0.11/Native Method) at java.lang.ClassLoader$NativeLibrary.load(java.base@11.0.11/Unknown Source) at java.lang.ClassLoader$NativeLibrary.loadLibrary(java.base@11.0.11/Unknown Source) - locked <0x823efe60> (a java.util.HashSet) at java.lang.ClassLoader.loadLibrary0(java.base@11.0.11/Unknown Source) at java.lang.ClassLoader.loadLibrary(java.base@11.0.11/Unknown Source) at java.lang.Runtime.loadLibrary0(java.base@11.0.11/Unknown Source) - locked <0x828224b8> (a java.lang.Runtime) at java.lang.System.loadLibrary(java.base@11.0.11/Unknown Source) at sun.tools.attach.VirtualMachineImpl.(jdk.attach@11.0.11/Unknown Source) at sun.tools.attach.AttachProviderImpl.attachVirtualMachine(jdk.attach@11.0.11/Unknown Source) at com.sun.tools.attach.VirtualMachine.attach(jdk.attach@11.0.11/Unknown Source) at org.apache.geode.internal.process.MBeanProcessController.getJMXServiceURL(MBeanProcessController.java:227) at org.apache.geode.internal.process.MBeanProcessController.connect(MBeanProcessController.java:192) at org.apache.geode.internal.process.MBeanProcessController.invokeOperationOnTargetMBean(MBeanProcessController.java:159) at org.apache.geode.internal.process.MBeanProcessController.status(MBeanProcessController.java:136) at org.apache.geode.internal.process.MBeanProcessController.status(MBeanProcessController.java:81) at org.apache.geode.internal.process.MBeanOrFileProcessController.status(MBeanOrFileProcessController.java:37) at org.apache.geode.distributed.LocatorLauncher.statusWithWorkingDirectory(LocatorLauncher.java:1012) at org.apache.geode.distributed.LocatorLauncher.status(LocatorLauncher.java:940) at org.apache.geode.distributed.LocatorLauncher$LocatorState.fromDirectory(LocatorLauncher.java:2077) at org.apache.geode.management.internal.cli.commands.StartLocatorCommand.doStartLocator(StartLocatorCommand.java:267) at org.apache.geode.management.internal.cli.commands.StartLocatorCommand.startLocator(StartLocatorCommand.java:133) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(java.base@11.0.11/Native Method) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(java.base@11.0.11/Unknown Source) at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(java.base@11.0.11/Unknown Source) at java.lang.reflect.Method.invoke(java.base@11.0.11/Unknown Source) at org.springframework.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:282) at org.apache.geode.management.internal.cli.remote.CommandExecutor.callInvokeMethod(CommandExecutor.java:139) at org.apache.geode.management.internal.cli.remote.CommandExecutor.invokeCommand(CommandExecutor.java:149) was: We are using gfsh with a script to automatically launch a locator and a server. During the launch of the locator, the process gfsh just freezes randomly. The locator process is forked, but gfsh remains frozen. A jstack on the process shows that the process is stuck on an internal NativeLibrary.load call. This one happens when gfsh try to attach to the process : internally the jvm loads the libattach.so library, but the call never return. To be complete, Geode is here deployed inside a docker container, using ubi8 as base image, java is jdk11.0.11 - we have tested with 11.0.13, same issue. The stack is the following : "main" #1 prio=5 os_prio=0 cpu=2402.78ms elapsed=1924.45s allocated=236M defined_classes=10346 tid=0x7fc904024000 nid=0x16 runnable [0x7fc90a84a000] java.lang.Thread.State: RUNNABLE at java.lang.ClassLoader$NativeLibrary.load0(java.base@11.0.11/Native Method) at java.lang.ClassLoader$NativeLibrary.load(java.base@11.0.11/Unknown Source) at java.lang.ClassLoader$NativeLibrary.loadLibrary(
[jira] [Commented] (GEODE-10062) Update Native Client Docs to minimize redirects
[ https://issues.apache.org/jira/browse/GEODE-10062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17497561#comment-17497561 ] ASF subversion and git services commented on GEODE-10062: - Commit 87891bd2b3ab3741a98f2c2e7aa4d4785f05cc3f in geode-native's branch refs/heads/develop from Dave Barnes [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=87891bd ] GEODE-10062: Update Native Client Docs to minimize redirects (#931) > Update Native Client Docs to minimize redirects > --- > > Key: GEODE-10062 > URL: https://issues.apache.org/jira/browse/GEODE-10062 > Project: Geode > Issue Type: Improvement > Components: docs, native client >Affects Versions: 1.14.3 >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Labels: pull-request-available > > Geode Native Client doc sources could be improved for ease of building and > use by reducing dependency on the ruby redirect feature, through measures > such as: > - Replace ruby redirects, where feasible, with template variables, e.g. links > to API docs and server guide > - Standardizing template variables, e.g. use 'serverman' consistently, > retiring other alternatives such as 'geodeman' -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10062) Update Native Client Docs to minimize redirects
[ https://issues.apache.org/jira/browse/GEODE-10062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17497562#comment-17497562 ] ASF GitHub Bot commented on GEODE-10062: davebarnes97 merged pull request #931: URL: https://github.com/apache/geode-native/pull/931 -- 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. To unsubscribe, e-mail: notifications-unsubscr...@geode.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Update Native Client Docs to minimize redirects > --- > > Key: GEODE-10062 > URL: https://issues.apache.org/jira/browse/GEODE-10062 > Project: Geode > Issue Type: Improvement > Components: docs, native client >Affects Versions: 1.14.3 >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Labels: pull-request-available > > Geode Native Client doc sources could be improved for ease of building and > use by reducing dependency on the ruby redirect feature, through measures > such as: > - Replace ruby redirects, where feasible, with template variables, e.g. links > to API docs and server guide > - Standardizing template variables, e.g. use 'serverman' consistently, > retiring other alternatives such as 'geodeman' -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9998) Update jedis library to the current latest (>= 4.1.0)
[ https://issues.apache.org/jira/browse/GEODE-9998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17497608#comment-17497608 ] Eric Zoerner commented on GEODE-9998: - Just merged PR [https://github.com/gemfire/gemfire/pull/770|https://github.com/gemfire/gemfire/pull/770.] to fix the hydra tests in gemfire/gemfire. The issues caused by the upgrade in Geode in the benchmarks and the hydra tests should now be fixed. > Update jedis library to the current latest (>= 4.1.0) > - > > Key: GEODE-9998 > URL: https://issues.apache.org/jira/browse/GEODE-9998 > Project: Geode > Issue Type: Test > Components: redis >Affects Versions: 1.16.0 >Reporter: Jens Deppe >Assignee: Eric Zoerner >Priority: Major > Labels: pull-request-available > Fix For: 1.16.0 > > > The 4.x version has been out for a while and we're still on 3.6.x (3.8 is the > last in the 3.x line). > This is not a trivial change as various APIs have changed which will affect a > lot of test code. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Comment Edited] (GEODE-9998) Update jedis library to the current latest (>= 4.1.0)
[ https://issues.apache.org/jira/browse/GEODE-9998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17497608#comment-17497608 ] Eric Zoerner edited comment on GEODE-9998 at 2/24/22, 6:05 PM: --- Just merged PR [https://github.com/gemfire/gemfire/pull/770|https://github.com/gemfire/gemfire/pull/770.] to fix the hydra tests in gemfire/gemfire. The issues caused by the upgrade in Geode to the benchmarks and the hydra tests should now be fixed. was (Author: zoernere): Just merged PR [https://github.com/gemfire/gemfire/pull/770|https://github.com/gemfire/gemfire/pull/770.] to fix the hydra tests in gemfire/gemfire. The issues caused by the upgrade in Geode in the benchmarks and the hydra tests should now be fixed. > Update jedis library to the current latest (>= 4.1.0) > - > > Key: GEODE-9998 > URL: https://issues.apache.org/jira/browse/GEODE-9998 > Project: Geode > Issue Type: Test > Components: redis >Affects Versions: 1.16.0 >Reporter: Jens Deppe >Assignee: Eric Zoerner >Priority: Major > Labels: pull-request-available > Fix For: 1.16.0 > > > The 4.x version has been out for a while and we're still on 3.6.x (3.8 is the > last in the 3.x line). > This is not a trivial change as various APIs have changed which will affect a > lot of test code. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10082) Duplicate values found in DSCode enums
[ https://issues.apache.org/jira/browse/GEODE-10082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-10082: -- Labels: needsTriage (was: ) > Duplicate values found in DSCode enums > -- > > Key: GEODE-10082 > URL: https://issues.apache.org/jira/browse/GEODE-10082 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Blake Bender >Priority: Major > Labels: needsTriage > > The following snippet appears in DSCode.hpp: > ``` > CacheableEnum = 94, > ClientProxyMembershipId = 38, > CacheableUserData = 39, > CacheableUserData2 = 38, > CacheableUserData4 = 37, > PDX = 93, > PDX_ENUM = 94, > InterestResultPolicy = 37, > }; > ``` > `CacheableEnum` is the name of the class that geode-native uses for > `PDX_ENUM`, it should not exist as an enum value. `ClientProxyMembershipId`, > `InternalDistributedMember`, and `InterestResultPolicy` are > `DataSerializableFixedId` values, and belong in that enum rather than DSCode. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-10082) Duplicate values found in DSCode enums
Blake Bender created GEODE-10082: Summary: Duplicate values found in DSCode enums Key: GEODE-10082 URL: https://issues.apache.org/jira/browse/GEODE-10082 Project: Geode Issue Type: Bug Components: native client Reporter: Blake Bender The following snippet appears in DSCode.hpp: ``` CacheableEnum = 94, ClientProxyMembershipId = 38, CacheableUserData = 39, CacheableUserData2 = 38, CacheableUserData4 = 37, PDX = 93, PDX_ENUM = 94, InterestResultPolicy = 37, }; ``` `CacheableEnum` is the name of the class that geode-native uses for `PDX_ENUM`, it should not exist as an enum value. `ClientProxyMembershipId`, `InternalDistributedMember`, and `InterestResultPolicy` are `DataSerializableFixedId` values, and belong in that enum rather than DSCode. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10082) Duplicate values found in DSCode enums
[ https://issues.apache.org/jira/browse/GEODE-10082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-10082: --- Labels: needsTriage pull-request-available (was: needsTriage) > Duplicate values found in DSCode enums > -- > > Key: GEODE-10082 > URL: https://issues.apache.org/jira/browse/GEODE-10082 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Blake Bender >Priority: Major > Labels: needsTriage, pull-request-available > > The following snippet appears in DSCode.hpp: > ``` > CacheableEnum = 94, > ClientProxyMembershipId = 38, > CacheableUserData = 39, > CacheableUserData2 = 38, > CacheableUserData4 = 37, > PDX = 93, > PDX_ENUM = 94, > InterestResultPolicy = 37, > }; > ``` > `CacheableEnum` is the name of the class that geode-native uses for > `PDX_ENUM`, it should not exist as an enum value. `ClientProxyMembershipId`, > `InternalDistributedMember`, and `InterestResultPolicy` are > `DataSerializableFixedId` values, and belong in that enum rather than DSCode. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10082) Duplicate values found in DSCode enums
[ https://issues.apache.org/jira/browse/GEODE-10082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17497651#comment-17497651 ] ASF GitHub Bot commented on GEODE-10082: pivotal-jbarrett opened a new pull request #933: URL: https://github.com/apache/geode-native/pull/933 Moves InterestResultPolicy and ClientProxyMembershipId to DSFid. Replaces eroneous CacheableEnum with PDX_ENUM. -- 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. To unsubscribe, e-mail: notifications-unsubscr...@geode.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Duplicate values found in DSCode enums > -- > > Key: GEODE-10082 > URL: https://issues.apache.org/jira/browse/GEODE-10082 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Blake Bender >Priority: Major > Labels: needsTriage > > The following snippet appears in DSCode.hpp: > ``` > CacheableEnum = 94, > ClientProxyMembershipId = 38, > CacheableUserData = 39, > CacheableUserData2 = 38, > CacheableUserData4 = 37, > PDX = 93, > PDX_ENUM = 94, > InterestResultPolicy = 37, > }; > ``` > `CacheableEnum` is the name of the class that geode-native uses for > `PDX_ENUM`, it should not exist as an enum value. `ClientProxyMembershipId`, > `InternalDistributedMember`, and `InterestResultPolicy` are > `DataSerializableFixedId` values, and belong in that enum rather than DSCode. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10074) Remove ACE remains
[ https://issues.apache.org/jira/browse/GEODE-10074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17497654#comment-17497654 ] ASF GitHub Bot commented on GEODE-10074: pivotal-jbarrett commented on a change in pull request #928: URL: https://github.com/apache/geode-native/pull/928#discussion_r814181420 ## File path: cppcache/integration-test/CMakeLists.txt ## @@ -69,6 +67,10 @@ add_clangformat(unit_test_callbacks) enable_testing() +if(UNIX AND NOT APPLE) Review comment: Oh, well then if it is just these legacy tests... hack away. -- 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. To unsubscribe, e-mail: notifications-unsubscr...@geode.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Remove ACE remains > -- > > Key: GEODE-10074 > URL: https://issues.apache.org/jira/browse/GEODE-10074 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Mario Salazar de Torres >Assignee: Mario Salazar de Torres >Priority: Major > Labels: obliterate-ace, pull-request-available > > *AS A* geode-native contributor > *I WANT TO* remove all the ACE remaining > *SO THAT* geode-native does not depend on ACE anymore -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-10082) Duplicate values found in DSCode enums
[ https://issues.apache.org/jira/browse/GEODE-10082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacob Barrett reassigned GEODE-10082: - Assignee: Jacob Barrett > Duplicate values found in DSCode enums > -- > > Key: GEODE-10082 > URL: https://issues.apache.org/jira/browse/GEODE-10082 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Blake Bender >Assignee: Jacob Barrett >Priority: Major > Labels: needsTriage, pull-request-available > > The following snippet appears in DSCode.hpp: > ``` > CacheableEnum = 94, > ClientProxyMembershipId = 38, > CacheableUserData = 39, > CacheableUserData2 = 38, > CacheableUserData4 = 37, > PDX = 93, > PDX_ENUM = 94, > InterestResultPolicy = 37, > }; > ``` > `CacheableEnum` is the name of the class that geode-native uses for > `PDX_ENUM`, it should not exist as an enum value. `ClientProxyMembershipId`, > `InternalDistributedMember`, and `InterestResultPolicy` are > `DataSerializableFixedId` values, and belong in that enum rather than DSCode. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9943) ReplicatedIndexedQueryBenchmark perfomance degradation
[
https://issues.apache.org/jira/browse/GEODE-9943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Murmann reassigned GEODE-9943:
Assignee: Bala Tripura Sundari Kaza Venkata
> ReplicatedIndexedQueryBenchmark perfomance degradation
> --
>
> Key: GEODE-9943
> URL: https://issues.apache.org/jira/browse/GEODE-9943
> Project: Geode
> Issue Type: Bug
>Reporter: Bala Tripura Sundari Kaza Venkata
>Assignee: Bala Tripura Sundari Kaza Venkata
>Priority: Major
>
> There is performance degradation on the ReplicatedIndexedQuery benchmark.
> Below is the output:
> {code:java}
> org.apache.geode.benchmark.tests.ReplicatedIndexedQueryBenchmark
> average ops/second Baseline: 31678.93 Test: 28420.90
> Difference: -10.3%
>ops/second standard error Baseline:48.69 Test:50.69
> Difference: +4.1%
>ops/second standard deviation Baseline: 840.57 Test: 874.99
> Difference: +4.1%
> YS 99th percentile latency Baseline: 20095.61 Test: 20094.75
> Difference: -0.0%
> median latency Baseline: 7467007.00 Test: 7217151.00
> Difference: -3.3%
> 90th percentile latency Baseline: 54657023.00 Test: 81788927.00
> Difference: +49.6%
> 99th percentile latency Baseline: 111345663.00 Test: 134217727.00
> Difference: +20.5%
>99.9th percentile latency Baseline: 226623487.00 Test: 202899455.00
> Difference: -10.5%
> average latency Baseline: 18182876.80 Test: 20330177.60
> Difference: +11.8%
> latency standard deviation Baseline: 28044862.49 Test: 33920338.87
> Difference: +21.0%
> latency standard error Baseline: 9109.64 Test: 11652.11
> Difference: +27.9%
> average ops/second Baseline: 31594.76 Test: 28257.85
> Difference: -10.6%
> {code}
> Failure seen in this CI run:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/benchmark-base/builds/83
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (GEODE-9875) AuthenticationRequiredException: Failed to find the authenticated user.
[
https://issues.apache.org/jira/browse/GEODE-9875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Murmann reassigned GEODE-9875:
Assignee: Jinmei Liao
> AuthenticationRequiredException: Failed to find the authenticated user.
> ---
>
> Key: GEODE-9875
> URL: https://issues.apache.org/jira/browse/GEODE-9875
> Project: Geode
> Issue Type: Bug
> Components: client/server
>Reporter: Jinmei Liao
>Assignee: Jinmei Liao
>Priority: Major
> Labels: GeodeOperationAPI, pull-request-available, unreleased
> Fix For: 1.15.0
>
>
> Client connects to a server:
> One thread is doing puts using the connection with a valid uniqueId
> The ClientCacheUpdater thread failed to initialize, gets an IOException while
> trying to connect to the server:
> {quote}
> [warn 2021/12/06 17:41:16.345 PST edgegemfire1_host1_9691
> tid=0x37] Cache Client Updater Thread on
> rs-RunItNow-HQ1613a0i3large-hydra-client-30(bridgegemfire1_host1_13308:13308):41001
> port 23326 (rs-RunItNow-HQ1613a0i3large-hydra-client-30:23326): Caught
> following exception while attempting to create a server-to-client
> communication socket and will exit: java.net.SocketTimeoutException: Read
> timed out
> {quote}
> Then the ClientCacheUpdator resets the connections userId back to -1.
> The put thread uses this -1 as the uniqueId and then gets the exception back.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (GEODE-9884) update CI max_in_flight limits
[ https://issues.apache.org/jira/browse/GEODE-9884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-9884: Assignee: Owen Nichols > update CI max_in_flight limits > -- > > Key: GEODE-9884 > URL: https://issues.apache.org/jira/browse/GEODE-9884 > Project: Geode > Issue Type: Improvement > Components: ci >Reporter: Owen Nichols >Assignee: Owen Nichols >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > max_in_flight limits are set on the main CI pipeline to avoid overloading > concourse when a large number of commits are coming through at the same time > these limits were last calculated a few years ago based on avg time each jobs > takes, and many jobs now take much longer and should be recalculated -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9870) JedisMovedDataException exception in testReconnectionWithAuthAndServerRestarts
[
https://issues.apache.org/jira/browse/GEODE-9870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Murmann reassigned GEODE-9870:
Assignee: Jens Deppe
> JedisMovedDataException exception in testReconnectionWithAuthAndServerRestarts
> --
>
> Key: GEODE-9870
> URL: https://issues.apache.org/jira/browse/GEODE-9870
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Bill Burcham
>Assignee: Jens Deppe
>Priority: Major
> Labels: pull-request-available, unreleased
> Fix For: 1.15.0
>
>
> CI failure here
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/315|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/315]:
>
> {code:java}
> AuthWhileServersRestartDUnitTest > testReconnectionWithAuthAndServerRestarts
> FAILED
> redis.clients.jedis.exceptions.JedisMovedDataException: MOVED 12539
> 127.0.0.1:26259
> at redis.clients.jedis.Protocol.processError(Protocol.java:119)
> at redis.clients.jedis.Protocol.process(Protocol.java:169)
> at redis.clients.jedis.Protocol.read(Protocol.java:223)
> at
> redis.clients.jedis.Connection.readProtocolWithCheckingBroken(Connection.java:352)
> at
> redis.clients.jedis.Connection.getStatusCodeReply(Connection.java:270)
> at redis.clients.jedis.BinaryJedis.flushAll(BinaryJedis.java:826)
> at
> org.apache.geode.test.dunit.rules.RedisClusterStartupRule.flushAll(RedisClusterStartupRule.java:147)
> at
> org.apache.geode.test.dunit.rules.RedisClusterStartupRule.flushAll(RedisClusterStartupRule.java:131)
> at
> org.apache.geode.redis.internal.executor.auth.AuthWhileServersRestartDUnitTest.after(AuthWhileServersRestartDUnitTest.java:88){code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (GEODE-9851) Use strongly typed enums rather than int for enumeration like values.
[ https://issues.apache.org/jira/browse/GEODE-9851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-9851: Assignee: Jacob Barrett > Use strongly typed enums rather than int for enumeration like values. > - > > Key: GEODE-9851 > URL: https://issues.apache.org/jira/browse/GEODE-9851 > Project: Geode > Issue Type: Improvement >Reporter: Jacob Barrett >Assignee: Jacob Barrett >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > Internally register interest has both an interest policy and data storage > policy that it passes around as `int`. Since these values are finite and have > well defined values it makes sense to pass them as proper Java enums. > Strongly typing them provides compile time checks on acceptable values and > makes the code more readable. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9848) Duplicate and Unnecessary REGISTER_INTEREST Message Sent to Server
[ https://issues.apache.org/jira/browse/GEODE-9848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-9848: Assignee: Blake Bender > Duplicate and Unnecessary REGISTER_INTEREST Message Sent to Server > -- > > Key: GEODE-9848 > URL: https://issues.apache.org/jira/browse/GEODE-9848 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Michael Martell >Assignee: Blake Bender >Priority: Major > Labels: pull-request-available > > In the course of debugging a RegisterAllKeys bug (GEMNC-508), it was > discovered that a second REGISTER_INTEREST message is being sent to the same > server. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9847) Benchmark instability in PartitionedPutLongBenchmark with security manager on support/1.14
[
https://issues.apache.org/jira/browse/GEODE-9847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Murmann reassigned GEODE-9847:
Assignee: Kamilla Aslami
> Benchmark instability in PartitionedPutLongBenchmark with security manager on
> support/1.14
> --
>
> Key: GEODE-9847
> URL: https://issues.apache.org/jira/browse/GEODE-9847
> Project: Geode
> Issue Type: Bug
> Components: benchmarks
>Affects Versions: 1.14.1
>Reporter: Kamilla Aslami
>Assignee: Kamilla Aslami
>Priority: Major
>
> PartitionedPutLongBenchmark failed in
> apache-support-1-14-main/benchmark-with-security-manager. This issue could
> have the same root cause as GEODE-9340, but GEODE-9340 fails on 1.15 and in
> another CI job (apache-develop-main/benchmark-base).
> {noformat}
> org.apache.geode.benchmark.tests.PartitionedPutLongBenchmark
> 05:20:08 average ops/second Baseline:381785.31 Test:
> 351135.20 Difference: -8.0%
> 05:20:08 ops/second standard error Baseline: 2163.90 Test:
> 3115.81 Difference: +44.0%
> 05:20:08 ops/second standard deviation Baseline: 37417.40 Test:
> 53877.38 Difference: +44.0%
> 05:20:08 YS 99th percentile latency Baseline: 1606.00 Test:
> 1606.00 Difference: +0.0%
> 05:20:08 median latency Baseline: 1068031.00 Test:
> 1065983.00 Difference: -0.2%
> 05:20:08 90th percentile latency Baseline: 1364991.00 Test:
> 1356799.00 Difference: -0.6%
> 05:20:08 99th percentile latency Baseline: 7688191.00 Test:
> 8138751.00 Difference: +5.9%
> 05:20:08 99.9th percentile latency Baseline: 209584127.00 Test:
> 260964351.00 Difference: +24.5%
> 05:20:08 average latency Baseline: 1884576.09 Test:
> 2050262.70 Difference: +8.8%
> 05:20:08 latency standard deviation Baseline: 11587055.57 Test:
> 14728140.58 Difference: +27.1%
> 05:20:08 latency standard error Baseline: 1083.17 Test:
> 1435.92 Difference: +32.6%
> 05:20:08 average ops/second Baseline:381621.08 Test:
> 350789.84 Difference: -8.1%
> 05:20:08BENCHMARK FAILED:
> org.apache.geode.benchmark.tests.PartitionedPutLongBenchmark average latency
> is 5% worse than baseline.
> 05:20:08{noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (GEODE-9812) Kill multiple Radish servers expecting operations to continue
[ https://issues.apache.org/jira/browse/GEODE-9812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-9812: Assignee: Jens Deppe > Kill multiple Radish servers expecting operations to continue > - > > Key: GEODE-9812 > URL: https://issues.apache.org/jira/browse/GEODE-9812 > Project: Geode > Issue Type: Test > Components: redis >Reporter: Jens Deppe >Assignee: Jens Deppe >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > Kill more than one server and expect the distributed system to recover. Data > loss is expected. The motivation behind this test is to ensure that, in a > situation where both the primary and secondary buckets are not available, > Redis clients are able to continue doing ops without getting stuck or hitting > loops of MOVED responses etc. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9822) Split-brain Certain During Network Partition in Two-Locator Cluster
[ https://issues.apache.org/jira/browse/GEODE-9822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-9822: Assignee: Bill Burcham > Split-brain Certain During Network Partition in Two-Locator Cluster > --- > > Key: GEODE-9822 > URL: https://issues.apache.org/jira/browse/GEODE-9822 > Project: Geode > Issue Type: Bug > Components: membership >Reporter: Bill Burcham >Assignee: Bill Burcham >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > In a two-locator cluster with default member weights and default setting > (true) of enable-network-partition-detection, if a long-lived network > partition separates the two members, a split-brain will arise: there will be > two coordinators at the same time. > The reason for this can be found in the GMSJoinLeave.isNetworkPartition() > method. That method's name is misleading. A name like isMajorityLost() would > probably be more apt. It needs to return true iff the weight of "crashed" > members (in the prospective view) is greater-than-or-equal-to half (50%) of > the total weight (of all members in the current view). > What the method actually does is return true iff the weight of "crashed" > members is greater-than 51% of the total weight. As a result, if we have two > members of equal weight, and the coordinator sees that the non-coordinator is > "crashed", the coordinator will keep running. If a network partition is > happening, and the non-coordinator is still running, then it will become a > coordinator and start producing views. Now we'll have two coordinators > producing views concurrently. > For this discussion "crashed" members are members for which the coordinator > has received a RemoveMemberRequest message. These are members that the > failure detector has deemed failed. Keep in mind the failure detector is > imperfect (it's not always right), and that's kind of the whole point of this > ticket: we've lost contact with the non-coordinator member, but that doesn't > mean it can't still be running (on the other side of a partition). > This bug is not limited to the two-locator scenario. Any set of members that > can be partitioned into two equal sets is susceptible. In fact it's even a > little worse than that. Any set of members that can be partitioned (into more > than one set), where any two-or-more sets, each still have 49% or more of the > total weight, will result in a split-brain -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9783) stray jars in pulse.war
[ https://issues.apache.org/jira/browse/GEODE-9783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-9783: Assignee: Owen Nichols > stray jars in pulse.war > --- > > Key: GEODE-9783 > URL: https://issues.apache.org/jira/browse/GEODE-9783 > Project: Geode > Issue Type: Bug > Components: pulse >Affects Versions: 1.12.5 >Reporter: Owen Nichols >Assignee: Owen Nichols >Priority: Major > Fix For: 1.12.6 > > > due to an issue backporting GEODE-9486, a couple unneeded jars appeared in > the war file for pulse in 1.12.5 only. while harmless, this should be > cleaned up. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9775) CI changes in preparation for change in cloud infrastructure
[ https://issues.apache.org/jira/browse/GEODE-9775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-9775: Assignee: Sean Goller > CI changes in preparation for change in cloud infrastructure > > > Key: GEODE-9775 > URL: https://issues.apache.org/jira/browse/GEODE-9775 > Project: Geode > Issue Type: Improvement > Components: ci >Affects Versions: 1.12.5, 1.13.4, 1.14.0, 1.15.0 >Reporter: Sean Goller >Assignee: Sean Goller >Priority: Major > Labels: pull-request-available > Fix For: 1.12.6, 1.13.5, 1.14.1, 1.15.0 > > > The way CI currently obtains some cloud infrastructure information will no > longer be available when we migrate. This issue covers the necessary changes > that can be done in advance to maintain compatibility. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9771) change CI target for Java API test
[
https://issues.apache.org/jira/browse/GEODE-9771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Murmann reassigned GEODE-9771:
Assignee: Robert Houghton
> change CI target for Java API test
> --
>
> Key: GEODE-9771
> URL: https://issues.apache.org/jira/browse/GEODE-9771
> Project: Geode
> Issue Type: Test
> Components: ci
>Affects Versions: 1.15.0
>Reporter: Robert Houghton
>Assignee: Robert Houghton
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> In preparation for moving the {{japicmp}} test-target in Gradle, move to a
> more generic target in our CI definition
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (GEODE-9762) CI Failure in ZRevRangeByScoreNativeRedisAcceptanceTest.shouldReturnRange_givenMultipleMembersWithDifferentScores
[
https://issues.apache.org/jira/browse/GEODE-9762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Murmann reassigned GEODE-9762:
Assignee: Owen Nichols
> CI Failure in
> ZRevRangeByScoreNativeRedisAcceptanceTest.shouldReturnRange_givenMultipleMembersWithDifferentScores
> -
>
> Key: GEODE-9762
> URL: https://issues.apache.org/jira/browse/GEODE-9762
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Owen Nichols
>Assignee: Owen Nichols
>Priority: Major
>
> {noformat}
> ZRevRangeByScoreNativeRedisAcceptanceTest >
> shouldReturnRange_givenMultipleMembersWithDifferentScores FAILED
> redis.clients.jedis.exceptions.JedisClusterException: CLUSTERDOWN The
> cluster is down
> at redis.clients.jedis.Protocol.processError(Protocol.java:125)
> at redis.clients.jedis.Protocol.process(Protocol.java:169)
> at redis.clients.jedis.Protocol.read(Protocol.java:223)
> at
> redis.clients.jedis.Connection.readProtocolWithCheckingBroken(Connection.java:352)
> at redis.clients.jedis.Connection.getIntegerReply(Connection.java:294)
> at redis.clients.jedis.Jedis.zadd(Jedis.java:1716)
> at redis.clients.jedis.JedisCluster$83.execute(JedisCluster.java:1104)
> at redis.clients.jedis.JedisCluster$83.execute(JedisCluster.java:1101)
> at
> redis.clients.jedis.JedisClusterCommand.runWithRetries(JedisClusterCommand.java:121)
> at
> redis.clients.jedis.JedisClusterCommand.run(JedisClusterCommand.java:45)
> at redis.clients.jedis.JedisCluster.zadd(JedisCluster.java:1106)
> at
> org.apache.geode.redis.internal.executor.sortedset.AbstractZRevRangeByScoreIntegrationTest.shouldReturnRange_givenMultipleMembersWithDifferentScores(AbstractZRevRangeByScoreIntegrationTest.java:135)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (GEODE-9761) CI Failure in ZRevRangeByScoreNativeRedisAcceptanceTest.shouldReturnEmptyList_givenZeroCount
[
https://issues.apache.org/jira/browse/GEODE-9761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Murmann reassigned GEODE-9761:
Assignee: Owen Nichols
> CI Failure in
> ZRevRangeByScoreNativeRedisAcceptanceTest.shouldReturnEmptyList_givenZeroCount
>
>
> Key: GEODE-9761
> URL: https://issues.apache.org/jira/browse/GEODE-9761
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Owen Nichols
>Assignee: Owen Nichols
>Priority: Major
>
> {noformat}
> ZRevRangeByScoreNativeRedisAcceptanceTest >
> shouldReturnEmptyList_givenZeroCount FAILED
> redis.clients.jedis.exceptions.JedisClusterException: CLUSTERDOWN The
> cluster is down
> at redis.clients.jedis.Protocol.processError(Protocol.java:125)
> at redis.clients.jedis.Protocol.process(Protocol.java:169)
> at redis.clients.jedis.Protocol.read(Protocol.java:223)
> at
> redis.clients.jedis.Connection.readProtocolWithCheckingBroken(Connection.java:352)
> at redis.clients.jedis.Connection.getIntegerReply(Connection.java:294)
> at redis.clients.jedis.Jedis.zadd(Jedis.java:1716)
> at redis.clients.jedis.JedisCluster$83.execute(JedisCluster.java:1104)
> at redis.clients.jedis.JedisCluster$83.execute(JedisCluster.java:1101)
> at
> redis.clients.jedis.JedisClusterCommand.runWithRetries(JedisClusterCommand.java:121)
> at
> redis.clients.jedis.JedisClusterCommand.run(JedisClusterCommand.java:45)
> at redis.clients.jedis.JedisCluster.zadd(JedisCluster.java:1106)
> at
> org.apache.geode.redis.internal.executor.sortedset.AbstractZRevRangeByScoreIntegrationTest.createZSetRangeTestMap(AbstractZRevRangeByScoreIntegrationTest.java:362)
> at
> org.apache.geode.redis.internal.executor.sortedset.AbstractZRevRangeByScoreIntegrationTest.shouldReturnEmptyList_givenZeroCount(AbstractZRevRangeByScoreIntegrationTest.java:236)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (GEODE-9732) CI Failure: ExpireNativeRedisAcceptanceTest fails with JedisClusterException: CLUSTERDOWN The cluster is down
[
https://issues.apache.org/jira/browse/GEODE-9732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Murmann reassigned GEODE-9732:
Assignee: Donal Evans
> CI Failure: ExpireNativeRedisAcceptanceTest fails with JedisClusterException:
> CLUSTERDOWN The cluster is down
> -
>
> Key: GEODE-9732
> URL: https://issues.apache.org/jira/browse/GEODE-9732
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Kirk Lund
>Assignee: Donal Evans
>Priority: Major
>
> Looks like every test in the class fails when whatever caused this happens.
> {noformat}
> ExpireNativeRedisAcceptanceTest >
> usingHSETCommandToAlterAFieldValue_should_NOT_ClearExpirationTimeOnKey FAILED
> redis.clients.jedis.exceptions.JedisClusterException: CLUSTERDOWN The
> cluster is down
> at redis.clients.jedis.Protocol.processError(Protocol.java:125)
> at redis.clients.jedis.Protocol.process(Protocol.java:169)
> at redis.clients.jedis.Protocol.read(Protocol.java:223)
> at
> redis.clients.jedis.Connection.readProtocolWithCheckingBroken(Connection.java:352)
> at redis.clients.jedis.Connection.getIntegerReply(Connection.java:294)
> at redis.clients.jedis.Jedis.hset(Jedis.java:831)
> at redis.clients.jedis.JedisCluster$38.execute(JedisCluster.java:652)
> at redis.clients.jedis.JedisCluster$38.execute(JedisCluster.java:649)
> at
> redis.clients.jedis.JedisClusterCommand.runWithRetries(JedisClusterCommand.java:121)
> at
> redis.clients.jedis.JedisClusterCommand.run(JedisClusterCommand.java:45)
> at redis.clients.jedis.JedisCluster.hset(JedisCluster.java:654)
> at
> org.apache.geode.redis.internal.executor.key.AbstractExpireIntegrationTest.usingHSETCommandToAlterAFieldValue_should_NOT_ClearExpirationTimeOnKey(AbstractExpireIntegrationTest.java:268)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at
> org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
> at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
> at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
> at
> org.apache.geode.redis.NativeRedisClusterTestRule$1.evaluate(NativeRedisClusterTestRule.java:121)
> at
> org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:54)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:115)
> at
> org.junit.vintage.engine.execution.RunnerExecutor.execute(RunnerExecutor.java:43)
> at
> java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:183)
> at
> java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193)
> at java.util.Iterator.forEachRemaining(Iterator.java:116)
> at
> java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1801)
> at
> java.util.stream
[jira] [Assigned] (GEODE-9710) Clean up PRColocationDUnitTestHelper
[ https://issues.apache.org/jira/browse/GEODE-9710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-9710: Assignee: Nabarun Nag > Clean up PRColocationDUnitTestHelper > > > Key: GEODE-9710 > URL: https://issues.apache.org/jira/browse/GEODE-9710 > Project: Geode > Issue Type: Bug > Components: tests >Reporter: Nabarun Nag >Assignee: Nabarun Nag >Priority: Major > Labels: needsTriage, pull-request-available > Fix For: 1.16.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9709) Clean up GcCommandDUnitTest
[ https://issues.apache.org/jira/browse/GEODE-9709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-9709: Assignee: Nabarun Nag > Clean up GcCommandDUnitTest > --- > > Key: GEODE-9709 > URL: https://issues.apache.org/jira/browse/GEODE-9709 > Project: Geode > Issue Type: Bug > Components: tests >Reporter: Nabarun Nag >Assignee: Nabarun Nag >Priority: Major > Labels: pull-request-available, testing > Fix For: 1.15.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10062) Update Native Client Docs to minimize redirects
[ https://issues.apache.org/jira/browse/GEODE-10062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17497682#comment-17497682 ] ASF subversion and git services commented on GEODE-10062: - Commit 8a5244a84beca9b1561dff3281245b1724ab4ec4 in geode-native's branch refs/heads/support/1.14 from Dave Barnes [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=8a5244a ] GEODE-10062: Update Native Client Docs to minimize redirects (#931) > Update Native Client Docs to minimize redirects > --- > > Key: GEODE-10062 > URL: https://issues.apache.org/jira/browse/GEODE-10062 > Project: Geode > Issue Type: Improvement > Components: docs, native client >Affects Versions: 1.14.3 >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Labels: pull-request-available > > Geode Native Client doc sources could be improved for ease of building and > use by reducing dependency on the ruby redirect feature, through measures > such as: > - Replace ruby redirects, where feasible, with template variables, e.g. links > to API docs and server guide > - Standardizing template variables, e.g. use 'serverman' consistently, > retiring other alternatives such as 'geodeman' -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (GEODE-10062) Update Native Client Docs to minimize redirects
[ https://issues.apache.org/jira/browse/GEODE-10062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-10062. - Fix Version/s: 1.14.4 1.15.0 Resolution: Fixed > Update Native Client Docs to minimize redirects > --- > > Key: GEODE-10062 > URL: https://issues.apache.org/jira/browse/GEODE-10062 > Project: Geode > Issue Type: Improvement > Components: docs, native client >Affects Versions: 1.14.3 >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Labels: pull-request-available > Fix For: 1.14.4, 1.15.0 > > > Geode Native Client doc sources could be improved for ease of building and > use by reducing dependency on the ruby redirect feature, through measures > such as: > - Replace ruby redirects, where feasible, with template variables, e.g. links > to API docs and server guide > - Standardizing template variables, e.g. use 'serverman' consistently, > retiring other alternatives such as 'geodeman' -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9705) When create PR failed with DistributedSystemDisconnectedException, should use it as cause of PartitionedRegionException
[ https://issues.apache.org/jira/browse/GEODE-9705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-9705: Assignee: Xiaojian Zhou > When create PR failed with DistributedSystemDisconnectedException, should use > it as cause of PartitionedRegionException > --- > > Key: GEODE-9705 > URL: https://issues.apache.org/jira/browse/GEODE-9705 > Project: Geode > Issue Type: Bug >Reporter: Xiaojian Zhou >Assignee: Xiaojian Zhou >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > When PR failed with register itself, it will throw > DistributedSystemDisconnectedException in cleanupFailedInitialization(). > LockServiceDestroyedException should be the cause of > DistributedSystemDisconnectedException. > Currently, we throw PartitionedRegionException directly using > LockServiceDestroyedException, which is not expected. > The fix is to throw PartitionedRegionException using > DistributedSystemDisconnectedException (or any other RuntimeException) as > cause, then set LockServiceDestroyedException as the cause of the cause. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9693) Remove deprecated elements from ListIndexCommandDistributedTestBase
[ https://issues.apache.org/jira/browse/GEODE-9693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-9693: Assignee: Nabarun Nag > Remove deprecated elements from ListIndexCommandDistributedTestBase > --- > > Key: GEODE-9693 > URL: https://issues.apache.org/jira/browse/GEODE-9693 > Project: Geode > Issue Type: Bug > Components: tests >Reporter: Nabarun Nag >Assignee: Nabarun Nag >Priority: Major > Labels: pull-request-available, testing > Fix For: 1.15.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9688) .Net core builds should be x64
[ https://issues.apache.org/jira/browse/GEODE-9688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-9688: Assignee: Blake Bender > .Net core builds should be x64 > -- > > Key: GEODE-9688 > URL: https://issues.apache.org/jira/browse/GEODE-9688 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Ernest Burghardt >Assignee: Blake Bender >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9687) Remove deprecated elements from RegionMembershipMBeanDistributedTestBase
[ https://issues.apache.org/jira/browse/GEODE-9687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-9687: Assignee: Nabarun Nag > Remove deprecated elements from RegionMembershipMBeanDistributedTestBase > > > Key: GEODE-9687 > URL: https://issues.apache.org/jira/browse/GEODE-9687 > Project: Geode > Issue Type: Bug > Components: tests >Reporter: Nabarun Nag >Assignee: Nabarun Nag >Priority: Major > Labels: pull-request-available, testing > Fix For: 1.15.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9686) Upgrade GemfireDataCommandsDistributedTestBase to not use deprecated methods
[ https://issues.apache.org/jira/browse/GEODE-9686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-9686: Assignee: Nabarun Nag > Upgrade GemfireDataCommandsDistributedTestBase to not use deprecated methods > > > Key: GEODE-9686 > URL: https://issues.apache.org/jira/browse/GEODE-9686 > Project: Geode > Issue Type: Bug > Components: tests >Reporter: Nabarun Nag >Assignee: Nabarun Nag >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > * remove all deprecated components. > * the overriding method was lost in one of the refactorings and hence the > http version of the test was not testing the http component. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9679) Improve Test Coverage for SingleResultCollector
[ https://issues.apache.org/jira/browse/GEODE-9679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-9679: Assignee: Darrel Schneider > Improve Test Coverage for SingleResultCollector > --- > > Key: GEODE-9679 > URL: https://issues.apache.org/jira/browse/GEODE-9679 > Project: Geode > Issue Type: Test > Components: redis >Reporter: Wayne >Assignee: Darrel Schneider >Priority: Major > Fix For: 1.15.0 > > > The org.apache.geode.redis.internal.executor.SingleResultCollector has > insufficient test coverage that must be improved. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9673) CI Failure: AuthExpirationDUnitTest > newClient_registeredInterest_slowReAuth_policyNone_durableClient
[
https://issues.apache.org/jira/browse/GEODE-9673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Murmann reassigned GEODE-9673:
Assignee: Jinmei Liao
> CI Failure: AuthExpirationDUnitTest >
> newClient_registeredInterest_slowReAuth_policyNone_durableClient
> --
>
> Key: GEODE-9673
> URL: https://issues.apache.org/jira/browse/GEODE-9673
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Hale Bales
>Assignee: Jinmei Liao
>Priority: Major
>
> AuthExpirationDUnitTest >
> newClient_registeredInterest_slowReAuth_policyNone_durableClient failed with
> the following stacktrace (abridged for readability):
> {code:java}
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.security.AuthExpirationDUnitTest$$Lambda$612/337713063.run
> in VM 0 running on Host
> heavy-lifter-2a774957-60f5-572d-bfa8-d0f3496af7cb.c.apachegeode-ci.internal
> with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:448)
> at
> org.apache.geode.test.junit.rules.VMProvider.invoke(VMProvider.java:94)
> at
> org.apache.geode.security.AuthExpirationDUnitTest.newClient_registeredInterest_slowReAuth_policyNone_durableClient(AuthExpirationDUnitTest.java:629)
> Caused by:
> org.awaitility.core.ConditionTimeoutException: Assertion condition
> defined as a lambda expression in
> org.apache.geode.security.AuthExpirationDUnitTest that uses
> org.apache.geode.cache.Region
> Expected size: 100 but was: 88 in:
> ["key93",
> ...,
> "key55"] within 5 minutes.
> at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:166)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
> at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:939)
> at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:723)
> at
> org.apache.geode.security.AuthExpirationDUnitTest.lambda$newClient_registeredInterest_slowReAuth_policyNone_durableClient$bb17a952$2(AuthExpirationDUnitTest.java:631)
> Caused by:
> java.lang.AssertionError:
> Expected size: 100 but was: 88 in:
> ["key93",
> ...,
> "key55"]
> at
> org.apache.geode.security.AuthExpirationDUnitTest.lambda$null$17(AuthExpirationDUnitTest.java:632)
> {code}
> CI Failure:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/upgrade-test-openjdk8/builds/241#B
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (GEODE-9661) CI failure: SetRangeNativeRedisAcceptanceTest because native redis server went down
[ https://issues.apache.org/jira/browse/GEODE-9661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-9661: Assignee: Donal Evans > CI failure: SetRangeNativeRedisAcceptanceTest because native redis server > went down > --- > > Key: GEODE-9661 > URL: https://issues.apache.org/jira/browse/GEODE-9661 > Project: Geode > Issue Type: Bug > Components: redis >Affects Versions: 1.15.0 >Reporter: Darrel Schneider >Assignee: Donal Evans >Priority: Major > Labels: ci-failure, flaky > > Given that this is caused by a crash of the native redis server, this ticket > should not hold up a geode release. > SetRangeNativeRedisAcceptanceTest > setRange_replacesMiddle FAILED > redis.clients.jedis.exceptions.JedisClusterException: CLUSTERDOWN The > cluster is down -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9655) bump shiro to recommended version
[ https://issues.apache.org/jira/browse/GEODE-9655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-9655: Assignee: Owen Nichols > bump shiro to recommended version > - > > Key: GEODE-9655 > URL: https://issues.apache.org/jira/browse/GEODE-9655 > Project: Geode > Issue Type: Bug > Components: pulse >Affects Versions: 1.12.4, 1.13.4, 1.14.0 >Reporter: Owen Nichols >Assignee: Owen Nichols >Priority: Major > Labels: needsTriage > Fix For: 1.12.5, 1.13.5, 1.14.1 > > > 1.8.0 was just released and we should update to it -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9649) enforce use of version constraints in build and pom
[ https://issues.apache.org/jira/browse/GEODE-9649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-9649: Assignee: Robert Houghton > enforce use of version constraints in build and pom > --- > > Key: GEODE-9649 > URL: https://issues.apache.org/jira/browse/GEODE-9649 > Project: Geode > Issue Type: Improvement > Components: build >Affects Versions: 1.15.0 >Reporter: Robert Houghton >Assignee: Robert Houghton >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > Create a spotless rule that ensures all dependencies are fetched from the > constraints BOM where possible. Some exceptions are tomcat, for which we have > several different versions, all in their own sub-modules -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9639) Make native client compatible with C++20
[ https://issues.apache.org/jira/browse/GEODE-9639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-9639: Assignee: Matthew Reddington > Make native client compatible with C++20 > > > Key: GEODE-9639 > URL: https://issues.apache.org/jira/browse/GEODE-9639 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Matthew Reddington >Assignee: Matthew Reddington >Priority: Major > Labels: pull-request-available > > There are standard library components that were removed in C++20, making our > library incompatible. Luckily, our use of deleted components are minimal and > replaceable without breaking API backward compatibility, but it will disrupt > ABI compatibility. > > The outcome needs to be tested against MSVC2017/v141 and MSVC2019/v142, > including examples. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9634) Wan replication between clusters on localhost broken by change to IP lookup
[ https://issues.apache.org/jira/browse/GEODE-9634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-9634: Assignee: Jacob Barrett > Wan replication between clusters on localhost broken by change to IP lookup > --- > > Key: GEODE-9634 > URL: https://issues.apache.org/jira/browse/GEODE-9634 > Project: Geode > Issue Type: Bug > Components: wan >Affects Versions: 1.15.0 >Reporter: Blake Bender >Assignee: Jacob Barrett >Priority: Blocker > Labels: pull-request-available > Fix For: 1.15.0 > > > This was the fix for GEODE-8955 (PR #6045). Here's a description from the > start of the Slack discussion thread: > "PR 6045 made on geode-wan LocatorHelper class seems to have broken WAN > replication between two clusters on localhost. I get the ridiculous nature of > WAN over localhost. Is it intentional that localhost is replaced with a local > interface IP by the changes made in the PR? The result is a test in the > geode-native pipeline does not work anymore since one site can’t see the > other since the locators are bound to localhost but trying to connection to > each other on a non-localhost IP address. Did we run into this same issue on > any of our Java based tests?" > Need to determine if this is desired behavior or not. If not, the old > behavior should be restored. If so, geode native team needs a JIRA ticket to > fix their Wan integration test(s) in CI, where this issue was detected. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9630) Gateway sender has public setter methods that should not be exposed
[ https://issues.apache.org/jira/browse/GEODE-9630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-9630: Assignee: Owen Nichols > Gateway sender has public setter methods that should not be exposed > --- > > Key: GEODE-9630 > URL: https://issues.apache.org/jira/browse/GEODE-9630 > Project: Geode > Issue Type: Improvement > Components: wan >Affects Versions: 1.15.0 >Reporter: Udo Kohlmeyer >Assignee: Owen Nichols >Priority: Blocker > Labels: pull-request-available > Fix For: 1.15.0 > > > Looking at the GatewaySender interface I noticed there are numerous public > setter methods. Geode should not allow for the ability to directly change > GatewaySender functionality without proper process. > This is largely to avoid the introduction of side effects into the system. A > prime example of this is, the ability to call `setGroupTransactionEvents`, > which from what I understand should NEVER be allowed to be changed in just 1 > server instead of cluster-wide. This by writing a function and changing the > setting on only 1 server can run the risk of the whole system behaving > incorrectly causing failures which would be close to impossible to track down. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9629) GatewaySender.setRetriesToGetTransactionEventsFromQueue on public API
[ https://issues.apache.org/jira/browse/GEODE-9629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-9629: Assignee: Owen Nichols > GatewaySender.setRetriesToGetTransactionEventsFromQueue on public API > - > > Key: GEODE-9629 > URL: https://issues.apache.org/jira/browse/GEODE-9629 > Project: Geode > Issue Type: Improvement > Components: wan >Affects Versions: 1.15.0 >Reporter: Udo Kohlmeyer >Assignee: Owen Nichols >Priority: Blocker > Labels: pull-request-available > Fix For: 1.15.0 > > > GatewaySender.setRetriesToGetTransactionEventsFromQueue is defined on the > public API. > The problem with this is that Geode should not allow for the simple > modification of settings for a GatewaySender. Without proper process / > management around the changing of the properties it would be too simple to > introduce side-effects by changing settings on the GatewaySender. > We (Geode) should NOT allow for the direct manipulation of configuration of > ANY component without it having gone through a controlled process, to ensure > that there aren't any side effects resulting from the change. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9609) Fix Compiler Warning in NetCore SessionState Project
[ https://issues.apache.org/jira/browse/GEODE-9609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-9609: Assignee: Michael Martell > Fix Compiler Warning in NetCore SessionState Project > > > Key: GEODE-9609 > URL: https://issues.apache.org/jira/browse/GEODE-9609 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Michael Martell >Assignee: Michael Martell >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9606) CI Failure: PubSubIntegrationTest.testPatternWithoutAGlob fails with AssertionError
[ https://issues.apache.org/jira/browse/GEODE-9606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-9606: Assignee: Jens Deppe > CI Failure: PubSubIntegrationTest.testPatternWithoutAGlob fails with > AssertionError > --- > > Key: GEODE-9606 > URL: https://issues.apache.org/jira/browse/GEODE-9606 > Project: Geode > Issue Type: Bug > Components: redis, tests >Affects Versions: 1.15.0 >Reporter: Benjamin P Ross >Assignee: Jens Deppe >Priority: Major > Labels: flaky-test, pull-request-available, unreleased > Fix For: 1.15.0 > > > The following failure occurred in a CI run: > org.apache.geode.redis.internal.executor.pubsub.PubSubIntegrationTest > > testPatternWithoutAGlob FAILED > java.lang.AssertionError: > Expecting actual: > [] > to contain exactly (and in same order): > ["hello"] > but could not find the following elements: > ["hello"] > at > org.apache.geode.redis.internal.executor.pubsub.AbstractPubSubIntegrationTest.testPatternWithoutAGlob(AbstractPubSubIntegrationTest.java:774) > at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native > Method) > at > jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:566) > at > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56) > at > org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at > org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306) > at > org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63) > at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329) > at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293) > at > org.apache.geode.test.junit.rules.serializable.SerializableExternalResource$1.evaluate(SerializableExternalResource.java:38) > at > org.apache.geode.test.junit.rules.serializable.SerializableExternalResource$1.evaluate(SerializableExternalResource.java:38) > at org.junit.rules.RunRules.evaluate(RunRules.java:20) > at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306) > at org.junit.runners.ParentRunner.run(ParentRunner.java:413) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:110) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38) > at > org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:62) > at > org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51) > at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native > Method) > at > jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:566) > at > org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:36) > at > org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) > at > org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:33) > at > org.gradle.int
[jira] [Assigned] (GEODE-9608) Compile NetCore Projects with Warnings as Errors and Add RelWithDebInfo
[ https://issues.apache.org/jira/browse/GEODE-9608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-9608: Assignee: Michael Martell > Compile NetCore Projects with Warnings as Errors and Add RelWithDebInfo > --- > > Key: GEODE-9608 > URL: https://issues.apache.org/jira/browse/GEODE-9608 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Michael Martell >Assignee: Michael Martell >Priority: Major > Labels: pull-request-available > > The NetCore projects should be compiled with Warnings as Errors to be > consistent with other geode-native components. Also, some of the projects are > missing RelWithDebInfo configuration. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9578) bump spring-security to recommended version
[ https://issues.apache.org/jira/browse/GEODE-9578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-9578: Assignee: Kirk Lund > bump spring-security to recommended version > --- > > Key: GEODE-9578 > URL: https://issues.apache.org/jira/browse/GEODE-9578 > Project: Geode > Issue Type: Improvement > Components: pulse >Affects Versions: 1.12.4, 1.13.4, 1.14.0 >Reporter: Owen Nichols >Assignee: Kirk Lund >Priority: Major > Labels: pull-request-available > Fix For: 1.12.5, 1.13.5, 1.14.1 > > > 1.14 has spring-security 5.4.5, will bump to 5.4.8 > 1.13 has spring-security 5.3.9, will bump to 5.3.11 > 1.12 has spring-security 5.2.10, will bump to 5.2.12 > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9553) Review and eliminate all remaining usage of sprintf, snprintf, etc
[
https://issues.apache.org/jira/browse/GEODE-9553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Murmann reassigned GEODE-9553:
Assignee: Blake Bender
> Review and eliminate all remaining usage of sprintf, snprintf, etc
> --
>
> Key: GEODE-9553
> URL: https://issues.apache.org/jira/browse/GEODE-9553
> Project: Geode
> Issue Type: Improvement
> Components: native client
>Reporter: Blake Bender
>Assignee: Blake Bender
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> From time to time, we will pick up a new version of a compiler on one or
> another platform we build on, and get new complaints about potential buffer
> overflows or other assorted badness around persistent use of sprintf. See
> the following pull request, e.g.:
> https://github.com/apache/geode-native/pull/861
> Fixing these when they come up is good as far as it goes, but we're really
> just applying band-aids to the problem. *All* use of sprintf is bad,
> snprintf only slightly less so. Someone needs to just go through the code
> and rewrite all instances in modern C++ using std::string, std::stringstream,
> etc.
> At a glance, here is the list of remaining files containing calls to sprintf:
> {code}
> c:\Users\bblake\src\geode-native>findstr /sm sprintf *.cpp
> cppcache\integration\test\ThinClientConflation.cpp
> cppcache\integration-test\fw_dunit.cpp
> cppcache\integration-test\testCacheless.cpp
> cppcache\integration-test\testOverflowPutGetSqLite.cpp
> cppcache\integration-test\testRegionMap.cpp
> cppcache\integration-test\testSerialization.cpp
> cppcache\integration-test\testThinClientBigValue.cpp
> cppcache\integration-test\testThinClientCacheablesLimits.cpp
> cppcache\integration-test\testThinClientCacheableStringArray.cpp
> cppcache\integration-test\testThinClientConflation.cpp
> cppcache\integration-test\testThinClientCq.cpp
> cppcache\integration-test\testThinClientCqDurable.cpp
> cppcache\integration-test\testThinClientCqFailover.cpp
> cppcache\integration-test\testThinClientCqHAFailover.cpp
> cppcache\integration-test\testThinClientCqIR.cpp
> cppcache\integration-test\testThinClientDeltaWithNotification.cpp
> cppcache\integration-test\testThinClientGetInterests.cpp
> cppcache\integration-test\testThinClientHADistOps.cpp
> cppcache\integration-test\testThinClientHAEventIDMap.cpp
> cppcache\integration-test\testThinClientHAFailover.cpp
> cppcache\integration-test\testThinClientHAFailoverRegex.cpp
> cppcache\integration-test\testThinClientHAMixedRedundancy.cpp
> cppcache\integration-test\testThinClientHAPeriodicAck.cpp
> cppcache\integration-test\testThinClientHeapLRU.cpp
> cppcache\integration-test\testThinClientInterest1_Bug1001.cpp
> cppcache\integration-test\testThinClientInterestNotify.cpp
> cppcache\integration-test\testThinClientIntResPolKeysInv.cpp
> cppcache\integration-test\testThinClientListenerCallbackArgTest.cpp
> cppcache\integration-test\testThinClientLRUExpiration.cpp
> cppcache\integration-test\testThinClientMultiDS.cpp
> cppcache\integration-test\testThinClientNotificationWithDeltaWithoutcache.cpp
> cppcache\integration-test\testThinClientPdxDeltaWithNotification.cpp
> cppcache\integration-test\testThinClientPdxInstance.cpp
> cppcache\integration-test\testThinClientPoolAttrTest.cpp
> cppcache\integration-test\testThinClientPoolExecuteFunctionThrowsException.cpp
> cppcache\integration-test\testThinClientPoolExecuteHAFunction.cpp
> cppcache\integration-test\testThinClientPoolExecuteHAFunctionPrSHOP.cpp
> cppcache\integration-test\testThinClientPoolRedundancy.cpp
> cppcache\integration-test\testThinClientPRPutAllFailover.cpp
> cppcache\integration-test\testThinClientRemoteQueryRS.cpp
> cppcache\integration-test\testThinClientRemoteQuerySS.cpp
> cppcache\integration-test\testThinClientRemoteRegionQuery.cpp
> cppcache\integration-test\testThinClientRemoveOps.cpp
> cppcache\integration-test\testThinClientSecurityPostAuthorization.cpp
> cppcache\integration-test\testXmlCacheCreationWithPools.cpp
> cppcache\integration-test\testXmlCacheInitialization.cpp
> tests\cpp\security\PkcsCredentialGenerator.cpp
> tests\cpp\security\XmlAuthzCredentialGenerator.cpp
> tests\cpp\testobject\BatchObject.cpp
> tests\cpp\testobject\DeltaPSTObject.cpp
> tests\cpp\testobject\DeltaTestImpl.cpp
> tests\cpp\testobject\EqStruct.cpp
> tests\cpp\testobject\FastAssetAccount.cpp
> tests\cpp\testobject\InvalidPdxUsage.cpp
> tests\cpp\testobject\NestedPdxObject.cpp
> tests\cpp\testobject\PdxClassV1.cpp
> tests\cpp\testobject\PdxClassV2.cpp
> tests\cpp\testobject\PdxType.cpp
> tests\cpp\testobject\Portfolio.cpp
> tests\cpp\testobject\PortfolioPdx.cpp
> tests\cpp\testobject\Position.cpp
> tests\cpp\testobject\PositionPdx.cpp
> tests\cpp\testobject\PS
[jira] [Assigned] (GEODE-9560) ECHO Command Supported
[ https://issues.apache.org/jira/browse/GEODE-9560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-9560: Assignee: Donal Evans > ECHO Command Supported > -- > > Key: GEODE-9560 > URL: https://issues.apache.org/jira/browse/GEODE-9560 > Project: Geode > Issue Type: New Feature > Components: redis >Reporter: Wayne >Assignee: Donal Evans >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > Write unit/integration tests that run against both Geode Redis and native > Redis, and dunit tests which test multiple concurrent clients accessing > different servers for the following command: > ECHO > +Acceptance Criteria+ > Unit/integration tests for both Geode and native Redis passing > DUNIT tests passing > README/redis_api_for_geode.html.md.erb updated to make command "supported" > or > Stories in the backlog to fix the identified issues (with JIRA tickets) and > problem tests that are ignored should be fixed and enabled. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9559) Demacroize clicache
[ https://issues.apache.org/jira/browse/GEODE-9559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-9559: Assignee: Michael Martell > Demacroize clicache > > > Key: GEODE-9559 > URL: https://issues.apache.org/jira/browse/GEODE-9559 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Michael Martell >Assignee: Michael Martell >Priority: Major > Labels: pull-request-available > > Macros in C++ complicate debug efforts and code maintenance and are generally > considered old school ([https://stroustrup.com/icsm-2012-demacro.pdf).] This > PR is to remove all the complicated macros in the .NET Framework client, e.g. > the clicache module. > In addition to improving the maintainability of the clicache module, removing > the macros will greatly assist the creation of the .NET Core client. [dotPeek > |http://jetbrains.com/decompiler/] is proving to be a valuable tool in the > .NET Core project, but is currently limited by the extensive use of macros in > the clicache code. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9550) Native Client user guide: warn against floating point values in keys
[ https://issues.apache.org/jira/browse/GEODE-9550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-9550: Assignee: Dave Barnes > Native Client user guide: warn against floating point values in keys > > > Key: GEODE-9550 > URL: https://issues.apache.org/jira/browse/GEODE-9550 > Project: Geode > Issue Type: Improvement > Components: docs, native client >Affects Versions: 1.13.4 >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Labels: pull-request-available > Fix For: 1.12.4, 1.13.4, 1.14.0, 1.15.0 > > > Request from a community member: > You should NEVER use a floating point value as a key, or key component, but > for some reason we allow it. > Since this can't be prevented in code, warn against this practice in the docs. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9549) Enable .net core tests in CI
[ https://issues.apache.org/jira/browse/GEODE-9549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-9549: Assignee: Blake Bender > Enable .net core tests in CI > > > Key: GEODE-9549 > URL: https://issues.apache.org/jira/browse/GEODE-9549 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Blake Bender >Assignee: Blake Bender >Priority: Major > Labels: pull-request-available > > The .net core build and tests are integrated into the CI, but test running is > currently disabled due to a few issues. These need to be cleaned up, and > tests enabled in CI. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9542) Enable SSL Client Certificate Authorization for Redis
[ https://issues.apache.org/jira/browse/GEODE-9542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-9542: Assignee: Jens Deppe > Enable SSL Client Certificate Authorization for Redis > - > > Key: GEODE-9542 > URL: https://issues.apache.org/jira/browse/GEODE-9542 > Project: Geode > Issue Type: New Feature > Components: redis >Reporter: Wayne >Assignee: Jens Deppe >Priority: Major > Labels: pull-request-available, redis > Fix For: 1.15.0 > > > When the ssl-require-authentication Geode property is set to true, we should > validate the Redis client's certificate against the configured ssl-truststore > to ensure that the client certificate is issued by a trusted Certificate > Authority. > > _Acceptance Criteria_ > Client certificates issued by trusted Certificate Authorities are properly > authenticated. Client certificates issued by non-trusted Certificate > Authorities are not authenticated. When the Geode property > ssl-require-authentication is set to false, no client certificate > authentication is performed. > Appropriate tests are developed to ensure this feature works as expected and > does not regress. > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9524) Make name of directory agree with library name for C bindings
[ https://issues.apache.org/jira/browse/GEODE-9524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-9524: Assignee: Blake Bender > Make name of directory agree with library name for C bindings > - > > Key: GEODE-9524 > URL: https://issues.apache.org/jira/browse/GEODE-9524 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Blake Bender >Assignee: Blake Bender >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > Path uses c_bindings with a '_', but the library is c-bindings with a "-". > Switch to "-" everywhere for consistency. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9522) When a server is force disconnected, it should set shutdown cause for dm to prevent clients recreating server connection.
[ https://issues.apache.org/jira/browse/GEODE-9522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-9522: Assignee: Xiaojian Zhou > When a server is force disconnected, it should set shutdown cause for dm to > prevent clients recreating server connection. > - > > Key: GEODE-9522 > URL: https://issues.apache.org/jira/browse/GEODE-9522 > Project: Geode > Issue Type: Bug >Reporter: Xiaojian Zhou >Assignee: Xiaojian Zhou >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > When a client is doing puts (mainly creates) to servers with replicated > region, shutdown some servers to force switching of primary HARegionQueue, > sometimes, the event with later event id is distributed by previous primary > HARegionQueue, which caused the events with earlier event ids are rejected by > clients. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9518) Implement ZUNIONSTORE Command
[ https://issues.apache.org/jira/browse/GEODE-9518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-9518: Assignee: Jens Deppe > Implement ZUNIONSTORE Command > - > > Key: GEODE-9518 > URL: https://issues.apache.org/jira/browse/GEODE-9518 > Project: Geode > Issue Type: New Feature > Components: redis >Reporter: Wayne >Assignee: Jens Deppe >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > Implement the [ZUNIONSTORE|https://redis.io/commands/zunionstore] Command, > with all options, and associated tests. > > +Acceptance Criteria+ > > The command has been implemented along with appropriate unit tests. > > The command has been added to the AbstractHitsMissesIntegrationTest. The > command has been tested using the redis-cli tool and verified against native > redis. > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9509) CI Failure: RedisPartitionResolverDUnitTest fails with suspect strings
[
https://issues.apache.org/jira/browse/GEODE-9509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Murmann reassigned GEODE-9509:
Assignee: Dan Smith
> CI Failure: RedisPartitionResolverDUnitTest fails with suspect strings
> --
>
> Key: GEODE-9509
> URL: https://issues.apache.org/jira/browse/GEODE-9509
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Assignee: Dan Smith
>Priority: Major
> Fix For: 1.15.0
>
>
> {noformat}
> org.apache.geode.redis.internal.cluster.RedisPartitionResolverDUnitTest >
> 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-vm0.log' at line 713
> [fatal 2021/08/14 18:02:15.696 UTC tid=57]
> Exception in processing request from 10.0.0.113
> java.lang.Exception: Improperly configured client detected - use
> addPoolLocator to configure its locators instead of addPoolServer.
> at
> org.apache.geode.distributed.internal.ProtocolCheckerImpl.checkProtocol(ProtocolCheckerImpl.java:31)
> at
> org.apache.geode.distributed.internal.tcpserver.TcpServer.lambda$processRequest$0(TcpServer.java:342)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> ---
> Found suspect string in 'dunit_suspect-vm0.log' at line 777
> [fatal 2021/08/14 18:02:28.025 UTC tid=57]
> Exception in processing request from 10.0.0.113
> java.lang.Exception: Improperly configured client detected - use
> addPoolLocator to configure its locators instead of addPoolServer.
> at
> org.apache.geode.distributed.internal.ProtocolCheckerImpl.checkProtocol(ProtocolCheckerImpl.java:31)
> at
> org.apache.geode.distributed.internal.tcpserver.TcpServer.lambda$processRequest$0(TcpServer.java:342)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> ---
> Found suspect string in 'dunit_suspect-vm0.log' at line 785
> [fatal 2021/08/14 18:02:28.028 UTC tid=57]
> Exception in processing request from 10.0.0.113
> java.lang.Exception: Improperly configured client detected - use
> addPoolLocator to configure its locators instead of addPoolServer.
> at
> org.apache.geode.distributed.internal.ProtocolCheckerImpl.checkProtocol(ProtocolCheckerImpl.java:31)
> at
> org.apache.geode.distributed.internal.tcpserver.TcpServer.lambda$processRequest$0(TcpServer.java:342)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> ---
> Found suspect string in 'dunit_suspect-vm0.log' at line 793
> [fatal 2021/08/14 18:02:28.064 UTC tid=57]
> Exception in processing request from 10.0.0.113
> java.lang.Exception: Improperly configured client detected - use
> addPoolLocator to configure its locators instead of addPoolServer.
> at
> org.apache.geode.distributed.internal.ProtocolCheckerImpl.checkProtocol(ProtocolCheckerImpl.java:31)
> at
> org.apache.geode.distributed.internal.tcpserver.TcpServer.lambda$processRequest$0(TcpServer.java:342)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Hit occurrence limit of 5 for this string.
> Further reporting of this type of error will be suppressed.
> 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.internal.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:425)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.after(ClusterStartupRule.java:186)
> at
> org.apache.geode.test.dunit.rules.ClusterStar
[jira] [Assigned] (GEODE-9511) Allow Default WindowsSDK in ACE cmake build
[
https://issues.apache.org/jira/browse/GEODE-9511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Murmann reassigned GEODE-9511:
Assignee: Michael Martell
> Allow Default WindowsSDK in ACE cmake build
> ---
>
> Key: GEODE-9511
> URL: https://issues.apache.org/jira/browse/GEODE-9511
> Project: Geode
> Issue Type: Improvement
> Components: native client
>Reporter: Michael Martell
>Assignee: Michael Martell
>Priority: Major
> Labels: pull-request-available
>
> The cmake configuration file for ACE currently uses the CMAKE_SYSTEM_VERSION
> variable to set the WindowsTargetPlatformVersion for ACE's build system
> (called MPC):
> set ( _CONFIGURE_COMMAND ${MPC} -static ${MPC_FLAGS}
> -name_modifier "*_${MPC_TYPE}_static"
> -value_template MultiProcessorCompilation=true
> -value_template WindowsTargetPlatformVersion=${CMAKE_SYSTEM_VERSION} set (
> _CONFIGURE_COMMAND ${MPC} -static ${MPC_FLAGS}
> -name_modifier "*_${MPC_TYPE}_static"
> -value_template MultiProcessorCompilation=true
> -value_template WindowsTargetPlatformVersion=${CMAKE_SYSTEM_VERSION}
>
> This requires the user to pass in a proper value for CMAKE_SYSTEM_VERSION on
> the cmake config line:
> cmake -DCMAKE_SYSTEM_VERSION=10.0.19041.0
> due to an apparent error in the default value of this variable which leaves
> off the last part (i.e., .0 above).
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (GEODE-9501) Support Latest Microsoft Platform Toolset and Compilers for C++
[ https://issues.apache.org/jira/browse/GEODE-9501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-9501: Assignee: Blake Bender > Support Latest Microsoft Platform Toolset and Compilers for C++ > --- > > Key: GEODE-9501 > URL: https://issues.apache.org/jira/browse/GEODE-9501 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Michael Martell >Assignee: Blake Bender >Priority: Major > Labels: pull-request-available > > Currently, the Windows build of geode-native uses Platform Toolset v141. This > ticket is to build using the default Platform Toolset and compiler which is > v142. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9464) Add a non-Steeltoe Asp.Net Core SessionState sample app to SessionStateCore
[ https://issues.apache.org/jira/browse/GEODE-9464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-9464: Assignee: Michael Martell > Add a non-Steeltoe Asp.Net Core SessionState sample app to SessionStateCore > --- > > Key: GEODE-9464 > URL: https://issues.apache.org/jira/browse/GEODE-9464 > Project: Geode > Issue Type: Test > Components: native client >Reporter: Michael Martell >Assignee: Michael Martell >Priority: Major > Labels: pull-request-available > > The current Asp.Net sample app uses Steeltoe for discovery and registration > of our sessionstate provider. We need a non-Steeltoe sample as well, since > not everyone uses Steeltoe. > This will be a good test of our NuGet access to the SessionState Core > artifacts and its dependencies. > Note: Ensure that the web application runs on all platforms. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9472) Improve Test Stability of VerifyNoLeakedThreads
[ https://issues.apache.org/jira/browse/GEODE-9472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-9472: Assignee: Michael Martell > Improve Test Stability of VerifyNoLeakedThreads > --- > > Key: GEODE-9472 > URL: https://issues.apache.org/jira/browse/GEODE-9472 > Project: Geode > Issue Type: Test > Components: native client >Reporter: Michael Martell >Assignee: Michael Martell >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > This test fails occasionally in the CI due to the heuristic being a little > too stringent for such a dynamic environment. Just need to broaden the > acceptable range for the ratio process threads before and after a cache > operation and cache close. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9442) CI Failure: acceptance-test-openjdk8 timed out
[ https://issues.apache.org/jira/browse/GEODE-9442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-9442: Assignee: Donal Evans > CI Failure: acceptance-test-openjdk8 timed out > -- > > Key: GEODE-9442 > URL: https://issues.apache.org/jira/browse/GEODE-9442 > Project: Geode > Issue Type: Bug > Components: redis, tests >Reporter: Eric Shu >Assignee: Donal Evans >Priority: Major > Labels: pull-request-available, unreleased > Fix For: 1.15.0 > > > This acceptance-test-openjdk8 failed due to timeout. > https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/acceptance-test-openjdk8/builds/88 > It does not appear to be one particular test hang -- as all running tests are > finished showing status of SUCCESS. > There are 1153 tests shown being run in this run. > Test Summary > 1153 > tests > The previous run showed 1295 tests were run. > Test Summary > 1295 > tests > However, it shows that gradle no able to shut down one test worker: > in daemon-4088.out.log under .gradle_logs directory following exception was > seen: > Daemon is stopping immediately stop command received > Daemon vm is shutting down... The daemon has exited normally or was > terminated in response to a user interrupt. > failed to abort Gradle Test Executor 143 > org.gradle.process.internal.ExecException: A problem occurred waiting for > process 'Gradle Test Executor 143' to complete. > at > org.gradle.process.internal.DefaultExecHandle.execExceptionFor(DefaultExecHandle.java:241) > at > org.gradle.process.internal.DefaultExecHandle.setEndStateInfo(DefaultExecHandle.java:218) > at > org.gradle.process.internal.DefaultExecHandle.failed(DefaultExecHandle.java:369) > at > org.gradle.process.internal.ExecHandleRunner.run(ExecHandleRunner.java:87) > at > org.gradle.internal.operations.CurrentBuildOperationPreservingRunnable.run(CurrentBuildOperationPreservingRunnable.java:42) > at > org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64) > at > org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:48) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at > org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:56) > at java.lang.Thread.run(Thread.java:748) > Caused by: java.lang.IllegalStateException: Shutdown in progress > at > java.lang.ApplicationShutdownHooks.remove(ApplicationShutdownHooks.java:82) > at java.lang.Runtime.removeShutdownHook(Runtime.java:239) > at > org.gradle.process.internal.shutdown.ShutdownHooks.removeShutdownHook(ShutdownHooks.java:33) > at > org.gradle.process.internal.DefaultExecHandle.setEndStateInfo(DefaultExecHandle.java:208) > at > org.gradle.process.internal.DefaultExecHandle.aborted(DefaultExecHandle.java:365) > at > org.gradle.process.internal.ExecHandleRunner.completed(ExecHandleRunner.java:108) > at > org.gradle.process.internal.ExecHandleRunner.run(ExecHandleRunner.java:84) > ... 7 more > Also, in > geode-apis-compatible-with-redis/build/test-results/acceptanceTest/binary > output.bin file that Redis container was started but no further information > for its shutdown. No sure if this is normal or not. > ^A<9c>^H^@<8a>^A[info 2021/07/20 16:55:00.011 UTC tid=0xa] > Ryuk started - will monitor and terminate Testcontainers containers on JVM > exit > ^A<9c>^H^@^A > ^A<9c>^H^@Q[info 2021/07/20 16:55:00.012 UTC tid=0xa] Checking > the system... > ^A<9c>^H^@^A > ^A<9c>^H^@p[info 2021/07/20 16:55:00.013 UTC tid=0xa] > â<9c><94>ï¸<8e> Docker server version should be at least 1.6.0 > ^A<9c>^H^@^A > ^A<9c>^H^@~[info 2021/07/20 16:55:00.142 UTC tid=0xa] > â<9c><94>ï¸<8e> Docker environment should have more than 2GB free disk space > ^A<9c>^H^@^A > ^A<9c>^H^@d[info 2021/07/20 16:55:00.161 UTC tid=0xa] Creating > container for image: redis:5.0.6 > ^A<9c>^H^@^A > ^A<9c>^H^@<97>^A[info 2021/07/20 16:55:00.218 UTC tid=0xa] > Starting container with ID: > 3d1530c27f0b4f6e526bfc48b8232708abd3e0de55f188c74e007db30a19d634 > ^A<9c>^H^@^A > ^A<9c>^H^@<9e>^A[info 2021/07/20 16:55:00.658 UTC tid=0xa] > Container redis:5.0.6 is starting: > 3d1530c27f0b4f6e526bfc48b8232708abd3e0de55f188c74e007db30a19d634 > ^A<9c>^H^@^A > ^A<9c>^H^@d[info 2021/07/20 16:55:00.789 UTC tid=0xa] > Container redis:5.0.6 started in PT0.644S > ^A<9c>^H^@^A > ^A<9c>^H^@r[info 2021/07/20 16:55:00.791 UTC tid=0xa] Started > redi
[jira] [Assigned] (GEODE-9412) App crashes when translating string with certain Unicode characters (exception thrown across managed/native boundary)
[ https://issues.apache.org/jira/browse/GEODE-9412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-9412: Assignee: Blake Bender > App crashes when translating string with certain Unicode characters > (exception thrown across managed/native boundary) > - > > Key: GEODE-9412 > URL: https://issues.apache.org/jira/browse/GEODE-9412 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Blake Bender >Assignee: Blake Bender >Priority: Major > Labels: pull-request-available > > tl;dr, we're not translating unicode correctly between .net and C++. > When a unicode string comes into the CLI layer, we use > `marshal_as` to translate, then assume this yields UTF-8. In > fact, what it yields is a string encoded in a) whatever the local code page > is for the system, or b) the default code page for the app, if one exists in > the manifest. In the C++ layer, we then assume the string is UTF-8, and for > a PUT, attempt to translate into Java-modified UTF-8, which ends up throwing > an uncaught exception when it encounters a character that is not a valid > UTF-8 start code. When this exception hits the native/managed boundary, the > app crashes. > To avoid this issue, we need to `marshal_as`, then use `std` > conversion functions to arrive at UTF-8, and pass that down to the C++ layer. > We also need to use the reverse process when sending strings back up to CLI. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9431) CI Failure: SegFault in apache-geode_unittests
[
https://issues.apache.org/jira/browse/GEODE-9431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Murmann reassigned GEODE-9431:
Assignee: Matthew Reddington
> CI Failure: SegFault in apache-geode_unittests
> --
>
> Key: GEODE-9431
> URL: https://issues.apache.org/jira/browse/GEODE-9431
> Project: Geode
> Issue Type: Bug
> Components: native client
>Reporter: Kamilla Aslami
>Assignee: Matthew Reddington
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> {{Two consequent geode-native-develop/build-rhel-8-release runs failed with
> segmentation fault: }}
> {noformat}
> selected worker: 3eb01fee-0959-4e2d-8c25-44a153962eaa
> Warning: Permanently added '34.67.7.72' (ECDSA) to the list of known hosts.
> Test project /home/build/build/cppcache/test
> Start 1: apache-geode_unittests
> 1/1 Test #1: apache-geode_unittests ...***Exception: SegFault 0.43
> sec
> Running main() from
> /home/build/build/dependencies/gtest/gtest-extern-prefix/src/gtest-extern/googletest/src/gtest_main.cc
> [==] Running 374 tests from 42 test suites.
> [--] Global test environment set-up.
> [--] 6 tests from durationTest
> [ RUN ] durationTest.ceil
> [ OK ] durationTest.ceil (0 ms)
> [ RUN ] durationTest.toString
> [ OK ] durationTest.toString (0 ms)
> [ RUN ] durationTest.fromString
> [ OK ] durationTest.fromString (0 ms)
> [ RUN ] durationTest.fromStringWithCeil
> [ OK ] durationTest.fromStringWithCeil (0 ms)
> [ RUN ] durationTest.fromStringException
> [ OK ] durationTest.fromStringException (0 ms)
> [ RUN ] durationTest.assertBounds
> [ OK ] durationTest.assertBounds (1 ms)
> [--] 6 tests from durationTest (1 ms total){noformat}
> ...
> {noformat}
> 0% tests passed, 1 tests failed out of 1
> Total Test time (real) = 0.91 sec
> The following tests FAILED:
> 1 - apache-geode_unittests (SEGFAULT)
> Errors while running CTest{noformat}
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (GEODE-9413) Enable native Redis TCL tests for zset (sorted set) data type
[ https://issues.apache.org/jira/browse/GEODE-9413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-9413: Assignee: Eric Zoerner > Enable native Redis TCL tests for zset (sorted set) data type > - > > Key: GEODE-9413 > URL: https://issues.apache.org/jira/browse/GEODE-9413 > Project: Geode > Issue Type: Test > Components: redis >Affects Versions: 1.15.0 >Reporter: Ray Ingles >Assignee: Eric Zoerner >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > Enough commands are now implemented to enable running the native Redis > integration tests against Geode radish. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9403) Dockerfile uses an unreliable key server
[ https://issues.apache.org/jira/browse/GEODE-9403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-9403: Assignee: Owen Nichols > Dockerfile uses an unreliable key server > > > Key: GEODE-9403 > URL: https://issues.apache.org/jira/browse/GEODE-9403 > Project: Geode > Issue Type: Improvement > Components: release >Reporter: Owen Nichols >Assignee: Owen Nichols >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > This line in docker/Dockerfile stopped working for me: > `gpg --keyserver ha.pool.sks-keyservers.net --recv-keys "$GEODE_GPG";` > I found that changing it to this works: > `gpg --keyserver [keyserver.ubuntu.com|http://keyserver.ubuntu.com/] > --recv-keys "$GEODE_GPG";` -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9401) Fix Duplicate Defines on OSX
[ https://issues.apache.org/jira/browse/GEODE-9401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-9401: Assignee: Michael Martell > Fix Duplicate Defines on OSX > > > Key: GEODE-9401 > URL: https://issues.apache.org/jira/browse/GEODE-9401 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Michael Martell >Assignee: Michael Martell >Priority: Major > Labels: pull-request-available > > Recent changes to system headers causes compile errors on OSX due to > redefinition of: > * BYTE_SIZE > * PAGE_SIZE -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9387) gnmsg: remove version detection and switch regex based on found log entries
[ https://issues.apache.org/jira/browse/GEODE-9387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-9387: Assignee: Blake Bender > gnmsg: remove version detection and switch regex based on found log entries > --- > > Key: GEODE-9387 > URL: https://issues.apache.org/jira/browse/GEODE-9387 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Blake Bender >Assignee: Blake Bender >Priority: Major > Labels: pull-request-available > > gnmsg currently looks for the log line containing the version of native > client being used, in order to detect which regex to use to parse message > traces, among other things. This has several implications: > > i. gnmsg cannot parse messages in a "rolled" log file, because only the first > file contains the version stamp > ii. the parsing code is very brittle, and routinely breaks when coming across > a log from a point release we haven't seen logs for, or a developer build > with an uninitialized version stamp, etc. > > What should happen is, where there are possible variants for a given trace, > gnmsg should check for all variants until it finds a match, then thereafter > only check for that variant. This should still yield decent performance, but > also no longer care about the version stamp, allowing us to parse rolled log > files and be much more robust to the types of logs we can read. > > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9368) Upgrade to lettuce library that fixes reconnection issues
[ https://issues.apache.org/jira/browse/GEODE-9368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-9368: Assignee: Jens Deppe > Upgrade to lettuce library that fixes reconnection issues > - > > Key: GEODE-9368 > URL: https://issues.apache.org/jira/browse/GEODE-9368 > Project: Geode > Issue Type: Bug > Components: redis >Reporter: Jens Deppe >Assignee: Jens Deppe >Priority: Major > Labels: pull-request-available > > We found an issue with the lettuce library when doing failover testing: > https://github.com/lettuce-io/lettuce-core/discussions/1757 > Wait until this change is merged into a released version of lettuce and > update all tests disabled due to this problem. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9359) add net-core-session to geode-native
[ https://issues.apache.org/jira/browse/GEODE-9359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-9359: Assignee: Michael Martell > add net-core-session to geode-native > > > Key: GEODE-9359 > URL: https://issues.apache.org/jira/browse/GEODE-9359 > Project: Geode > Issue Type: New Feature > Components: native client >Reporter: Ernest Burghardt >Assignee: Michael Martell >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > net-core-session shall be added to the top level of geode-native repo and > will produce a separate binary that will be publishable to NuGet > https://docs.microsoft.com/en-us/nuget/create-packages/package-authoring-best-practices -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9358) Initial revision of native C bindings
[ https://issues.apache.org/jira/browse/GEODE-9358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-9358: Assignee: Blake Bender > Initial revision of native C bindings > - > > Key: GEODE-9358 > URL: https://issues.apache.org/jira/browse/GEODE-9358 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Blake Bender >Assignee: Blake Bender >Priority: Major > > We need a minimal set of C language bindings that will be the beginning of > support for .net core and other languages that can easily interface to C code. > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9366) Redis SynchronizedStripeExecutor can throw IndexOutOfBoundsException
[
https://issues.apache.org/jira/browse/GEODE-9366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Murmann reassigned GEODE-9366:
Assignee: Jens Deppe
> Redis SynchronizedStripeExecutor can throw IndexOutOfBoundsException
>
>
> Key: GEODE-9366
> URL: https://issues.apache.org/jira/browse/GEODE-9366
> Project: Geode
> Issue Type: Bug
> Components: redis
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
> Labels: pull-request-available, unreleased
> Fix For: 1.15.0
>
>
> Saw the following issue being logged:
> {noformat}
> [warn 2021/06/08 08:25:48.005 PDT redisServergemfire1_host1_9978
> tid=0x79] Execution of Redis command HMSET
> \xac\xed\x00\x05t\x00 \xac\xed\x00\x05t\x00\x10lastAccessedTime
>
> \xac\xed\x00\x05sr\x00\x0ejava.lang.Long;\x8b\xe4\x90\xcc\x8f#\xdf\x02\x00\x01J\x00\x05valuexr\x00\x10java.lang.Number\x86\xac\x95\x1d\x0b\x94\xe0\x8b\x02\x00\x00xp\x00\x00\x01y\xec:\xd0c
> \xac\xed\x00\x05t\x00\x13maxInactiveInterval \xac\xed\x00\x05sr\x00\x11ja
> va.lang.Integer\x12\xe2\xa0\xa4\xf7\x81\x878\x02\x00\x01I\x00\x05valuexr\x00\x10java.lang.Number\x86\xac\x95\x1d\x0b\x94\xe0\x8b\x02\x00\x00xp\x00\x00\x00<
> \xac\xed\x00\x05t\x00\x19sessionAttr:Object_214669
> \xac\xed\x00\x05t\x00\rObject_214669 \xac\xed\x00\x05t\
> x00\x0ccreationTime
> \xac\xed\x00\x05sr\x00\x0ejava.lang.Long;\x8b\xe4\x90\xcc\x8f#\xdf\x02\x00\x01J\x00\x05valuexr\x00\x10java.lang.Number\x86\xac\x95\x1d\x0b\x94\xe0\x8b\x02\x00\x00xp\x00\x00\x01y\xec:\xd0c
> failed: java.lang.ArrayIndexOutOfBoundsException: -11
> 52
> [error 2021/06/08 08:25:48.018 PDT redisServergemfire1_host1_9978
> tid=0x79] GeodeRedisServer-Unexpected error
> handler for [id: 0x7d55de8e, L:/10.32.109.109:21171 - R:/10.32.109.109:39854]
> java.lang.ArrayIndexOutOfBoundsException: -1152
> at
> org.apache.geode.redis.internal.executor.SynchronizedStripedExecutor.getSync(SynchronizedStripedExecutor.java:56)
> at
> org.apache.geode.redis.internal.executor.SynchronizedStripedExecutor.execute(SynchronizedStripedExecutor.java:44)
> at
> org.apache.geode.redis.internal.RegionProvider.execute(RegionProvider.java:136)
> at
> org.apache.geode.redis.internal.data.RedisDataCommandsFunctionExecutor.stripedExecute(RedisDataCommandsFunctionExecutor.java:48)
> at
> org.apache.geode.redis.internal.data.RedisHashCommandsFunctionExecutor.hset(RedisHashCommandsFunctionExecutor.java:42)
> at
> org.apache.geode.redis.internal.executor.hash.HMSetExecutor.executeCommand(HMSetExecutor.java:58)
> at
> org.apache.geode.redis.internal.RedisCommandType.executeCommand(RedisCommandType.java:353)
> at
> org.apache.geode.redis.internal.netty.Command.execute(Command.java:178)
> at
> org.apache.geode.redis.internal.netty.ExecutionHandlerContext.executeCommand(ExecutionHandlerContext.java:330)
> at
> org.apache.geode.redis.internal.netty.ExecutionHandlerContext.processCommandQueue(ExecutionHandlerContext.java:155)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (GEODE-9356) Create CI pipeline for net-core
[ https://issues.apache.org/jira/browse/GEODE-9356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-9356: Assignee: Matthew Reddington > Create CI pipeline for net-core > --- > > Key: GEODE-9356 > URL: https://issues.apache.org/jira/browse/GEODE-9356 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Ernest Burghardt >Assignee: Matthew Reddington >Priority: Major > Labels: pull-request-available > > This pipeline will be hosted on the Apache publicly available Concourse and > publish to NuGet -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9357) Create CI pipeline for net-core-session
[ https://issues.apache.org/jira/browse/GEODE-9357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-9357: Assignee: Blake Bender > Create CI pipeline for net-core-session > --- > > Key: GEODE-9357 > URL: https://issues.apache.org/jira/browse/GEODE-9357 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Ernest Burghardt >Assignee: Blake Bender >Priority: Major > Fix For: 1.15.0 > > > This pipeline will be hosted on the Apache publicly available Concourse and > publish to NuGet -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (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 ] Alexander Murmann reassigned GEODE-9339: Assignee: Owen Nichols > 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 >Assignee: Owen Nichols >Priority: Major > Labels: blocks-1.14.0, pull-request-available > Fix For: 1.12.3, 1.13.3, 1.14.0, 1.15.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.20.1#820001)
[jira] [Assigned] (GEODE-9329) Implement data structures needed for Redis leaderboard use case
[ https://issues.apache.org/jira/browse/GEODE-9329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-9329: Assignee: Ray Ingles > Implement data structures needed for Redis leaderboard use case > --- > > Key: GEODE-9329 > URL: https://issues.apache.org/jira/browse/GEODE-9329 > Project: Geode > Issue Type: New Feature > Components: redis >Affects Versions: 1.15.0 >Reporter: Ray Ingles >Assignee: Ray Ingles >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > Implement the data structures needed to fully support Sorted Sets in Radish. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9314) Redis CLUSTER NODES incorrect when primary buckets are moving
[ https://issues.apache.org/jira/browse/GEODE-9314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-9314: Assignee: Jens Deppe > Redis CLUSTER NODES incorrect when primary buckets are moving > - > > Key: GEODE-9314 > URL: https://issues.apache.org/jira/browse/GEODE-9314 > Project: Geode > Issue Type: Bug > Components: redis >Reporter: Jens Deppe >Assignee: Jens Deppe >Priority: Major > Labels: pull-request-available, unreleased > Fix For: 1.15.0 > > > When buckets are moving the CLUSTER NODES command may produce incorrect > results - specifically the node host/port information may be > duplicated/incorrect. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9315) bump spring-security to recommended version
[ https://issues.apache.org/jira/browse/GEODE-9315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-9315: Assignee: Owen Nichols > bump spring-security to recommended version > --- > > Key: GEODE-9315 > URL: https://issues.apache.org/jira/browse/GEODE-9315 > Project: Geode > Issue Type: Improvement > Components: pulse >Affects Versions: 1.13.2 >Reporter: Owen Nichols >Assignee: Owen Nichols >Priority: Major > Fix For: 1.13.3 > > > new 5.3.9 is available. Only Geode 1.13 uses this minor, so this change is > not applicable to any other Geode branches. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9298) Remove concourse deprecation warnings
[ https://issues.apache.org/jira/browse/GEODE-9298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-9298: Assignee: Robert Houghton > Remove concourse deprecation warnings > - > > Key: GEODE-9298 > URL: https://issues.apache.org/jira/browse/GEODE-9298 > Project: Geode > Issue Type: Improvement > Components: ci >Affects Versions: 1.15.0 >Reporter: Robert Houghton >Assignee: Robert Houghton >Priority: Major > Labels: pull-request-available > Fix For: 1.12.3, 1.13.3, 1.14.0, 1.15.0 > > > Concourse is warning of several deprecated functions and names. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9313) Allow AllowExecutionInLowMemory to be usable generically
[ https://issues.apache.org/jira/browse/GEODE-9313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-9313: Assignee: Jens Deppe > Allow AllowExecutionInLowMemory to be usable generically > > > Key: GEODE-9313 > URL: https://issues.apache.org/jira/browse/GEODE-9313 > Project: Geode > Issue Type: Improvement > Components: redis >Reporter: Jens Deppe >Assignee: Jens Deppe >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9265) Introduce redis SlotAdvisor to manage slot information
[ https://issues.apache.org/jira/browse/GEODE-9265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-9265: Assignee: Jens Deppe > Introduce redis SlotAdvisor to manage slot information > -- > > Key: GEODE-9265 > URL: https://issues.apache.org/jira/browse/GEODE-9265 > Project: Geode > Issue Type: Improvement > Components: redis >Reporter: Jens Deppe >Assignee: Jens Deppe >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > We're currently using a function to pull bucket/slot info from each member. > However members already contain the most current view of bucket locations so > we should use that instead. This will avoid an unnecessary fn call as well as > providing more up-to-date information. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9762) CI Failure in ZRevRangeByScoreNativeRedisAcceptanceTest.shouldReturnRange_givenMultipleMembersWithDifferentScores
[
https://issues.apache.org/jira/browse/GEODE-9762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen Nichols reassigned GEODE-9762:
---
Assignee: Jens Deppe (was: Owen Nichols)
> CI Failure in
> ZRevRangeByScoreNativeRedisAcceptanceTest.shouldReturnRange_givenMultipleMembersWithDifferentScores
> -
>
> Key: GEODE-9762
> URL: https://issues.apache.org/jira/browse/GEODE-9762
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Owen Nichols
>Assignee: Jens Deppe
>Priority: Major
>
> {noformat}
> ZRevRangeByScoreNativeRedisAcceptanceTest >
> shouldReturnRange_givenMultipleMembersWithDifferentScores FAILED
> redis.clients.jedis.exceptions.JedisClusterException: CLUSTERDOWN The
> cluster is down
> at redis.clients.jedis.Protocol.processError(Protocol.java:125)
> at redis.clients.jedis.Protocol.process(Protocol.java:169)
> at redis.clients.jedis.Protocol.read(Protocol.java:223)
> at
> redis.clients.jedis.Connection.readProtocolWithCheckingBroken(Connection.java:352)
> at redis.clients.jedis.Connection.getIntegerReply(Connection.java:294)
> at redis.clients.jedis.Jedis.zadd(Jedis.java:1716)
> at redis.clients.jedis.JedisCluster$83.execute(JedisCluster.java:1104)
> at redis.clients.jedis.JedisCluster$83.execute(JedisCluster.java:1101)
> at
> redis.clients.jedis.JedisClusterCommand.runWithRetries(JedisClusterCommand.java:121)
> at
> redis.clients.jedis.JedisClusterCommand.run(JedisClusterCommand.java:45)
> at redis.clients.jedis.JedisCluster.zadd(JedisCluster.java:1106)
> at
> org.apache.geode.redis.internal.executor.sortedset.AbstractZRevRangeByScoreIntegrationTest.shouldReturnRange_givenMultipleMembersWithDifferentScores(AbstractZRevRangeByScoreIntegrationTest.java:135)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (GEODE-9277) Constrain Redis FLUSHALL command to local member data only
[
https://issues.apache.org/jira/browse/GEODE-9277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Murmann reassigned GEODE-9277:
Assignee: Jens Deppe
> Constrain Redis FLUSHALL command to local member data only
> --
>
> Key: GEODE-9277
> URL: https://issues.apache.org/jira/browse/GEODE-9277
> Project: Geode
> Issue Type: Improvement
> Components: redis
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> Currently our {{FLUSHALL}} command will iterate and delete all keys in the
> whole region. While this is nice and convenient for now, it is not how native
> redis does it and will need to be switched once the function execution layer
> is removed.
> It would be helpful to do this work separately.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (GEODE-9276) Benchmark_with_security_manager pipeline failed with STANDARD_ERROR
[ https://issues.apache.org/jira/browse/GEODE-9276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-9276: Assignee: Owen Nichols > Benchmark_with_security_manager pipeline failed with STANDARD_ERROR > --- > > Key: GEODE-9276 > URL: https://issues.apache.org/jira/browse/GEODE-9276 > Project: Geode > Issue Type: Bug > Components: benchmarks >Reporter: Eric Shu >Assignee: Owen Nichols >Priority: Major > > Multiple tests failed with followings: > org.apache.geode.benchmark.tests.PartitionedFunctionExecutionWithFiltersBenchmark > > run() STANDARD_ERROR > org.apache.geode.benchmark.tests.PartitionedPutBenchmark > run() > STANDARD_ERROR > Test run results are in: > https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/Benchmark_with_security_manager/builds/208 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (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 ] Alexander Murmann reassigned GEODE-9289: Assignee: Nabarun Nag > 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 >Assignee: Nabarun Nag >Priority: Major > Labels: blocks-1.15.0, pull-request-available > Fix For: 1.12.3, 1.13.3, 1.14.0, 1.15.0 > > > * 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.20.1#820001)
[jira] [Assigned] (GEODE-9761) CI Failure in ZRevRangeByScoreNativeRedisAcceptanceTest.shouldReturnEmptyList_givenZeroCount
[
https://issues.apache.org/jira/browse/GEODE-9761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen Nichols reassigned GEODE-9761:
---
Assignee: Jens Deppe (was: Owen Nichols)
> CI Failure in
> ZRevRangeByScoreNativeRedisAcceptanceTest.shouldReturnEmptyList_givenZeroCount
>
>
> Key: GEODE-9761
> URL: https://issues.apache.org/jira/browse/GEODE-9761
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Owen Nichols
>Assignee: Jens Deppe
>Priority: Major
>
> {noformat}
> ZRevRangeByScoreNativeRedisAcceptanceTest >
> shouldReturnEmptyList_givenZeroCount FAILED
> redis.clients.jedis.exceptions.JedisClusterException: CLUSTERDOWN The
> cluster is down
> at redis.clients.jedis.Protocol.processError(Protocol.java:125)
> at redis.clients.jedis.Protocol.process(Protocol.java:169)
> at redis.clients.jedis.Protocol.read(Protocol.java:223)
> at
> redis.clients.jedis.Connection.readProtocolWithCheckingBroken(Connection.java:352)
> at redis.clients.jedis.Connection.getIntegerReply(Connection.java:294)
> at redis.clients.jedis.Jedis.zadd(Jedis.java:1716)
> at redis.clients.jedis.JedisCluster$83.execute(JedisCluster.java:1104)
> at redis.clients.jedis.JedisCluster$83.execute(JedisCluster.java:1101)
> at
> redis.clients.jedis.JedisClusterCommand.runWithRetries(JedisClusterCommand.java:121)
> at
> redis.clients.jedis.JedisClusterCommand.run(JedisClusterCommand.java:45)
> at redis.clients.jedis.JedisCluster.zadd(JedisCluster.java:1106)
> at
> org.apache.geode.redis.internal.executor.sortedset.AbstractZRevRangeByScoreIntegrationTest.createZSetRangeTestMap(AbstractZRevRangeByScoreIntegrationTest.java:362)
> at
> org.apache.geode.redis.internal.executor.sortedset.AbstractZRevRangeByScoreIntegrationTest.shouldReturnEmptyList_givenZeroCount(AbstractZRevRangeByScoreIntegrationTest.java:236)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (GEODE-9259) Fix testThinClientRemoveOps and Reenable
[ https://issues.apache.org/jira/browse/GEODE-9259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-9259: Assignee: Michael Martell > Fix testThinClientRemoveOps and Reenable > > > Key: GEODE-9259 > URL: https://issues.apache.org/jira/browse/GEODE-9259 > Project: Geode > Issue Type: Test > Components: native client >Reporter: Michael Martell >Assignee: Michael Martell >Priority: Major > Labels: pull-request-available > > This is an important test because of its thorough coverage of the region API. > > Note: This test hasn't worked in a long time due to a nativeclient bug > involving CACHING_PROXY, which allowed removing keys from the server where > were only invalid on the client (GEODE_9249). After fixing that bug, this > test runs. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9578) bump spring-security to recommended version
[ https://issues.apache.org/jira/browse/GEODE-9578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen Nichols reassigned GEODE-9578: --- Assignee: Owen Nichols (was: Kirk Lund) > bump spring-security to recommended version > --- > > Key: GEODE-9578 > URL: https://issues.apache.org/jira/browse/GEODE-9578 > Project: Geode > Issue Type: Improvement > Components: pulse >Affects Versions: 1.12.4, 1.13.4, 1.14.0 >Reporter: Owen Nichols >Assignee: Owen Nichols >Priority: Major > Labels: pull-request-available > Fix For: 1.12.5, 1.13.5, 1.14.1 > > > 1.14 has spring-security 5.4.5, will bump to 5.4.8 > 1.13 has spring-security 5.3.9, will bump to 5.3.11 > 1.12 has spring-security 5.2.10, will bump to 5.2.12 > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9249) Remove(key, nullptr) Not Working Properly
[ https://issues.apache.org/jira/browse/GEODE-9249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-9249: Assignee: Michael Martell > Remove(key, nullptr) Not Working Properly > - > > Key: GEODE-9249 > URL: https://issues.apache.org/jira/browse/GEODE-9249 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Michael Martell >Assignee: Michael Martell >Priority: Major > Labels: pull-request-available > > The Region API supports both local and remote operations. Local operations > apply to CACHING_PROXY regions and are supposed to affect only the local > cache. However, localInvalidate(key, value) invalidates both local and remote > entry. > > This is actually a but in remove(key, nullptr), not localInvalidate. > > Note: Invalidate operations sets the value for the given key to null. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9244) Improve rsync-code-down times
[ https://issues.apache.org/jira/browse/GEODE-9244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-9244: Assignee: Robert Houghton > Improve rsync-code-down times > - > > Key: GEODE-9244 > URL: https://issues.apache.org/jira/browse/GEODE-9244 > Project: Geode > Issue Type: Improvement > Components: ci >Reporter: Robert Houghton >Assignee: Robert Houghton >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > File copy and rsync from windows has been flaky. Trying to speed that up. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9246) Fix and Reenable PutAll Test with Callback
[ https://issues.apache.org/jira/browse/GEODE-9246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann reassigned GEODE-9246: Assignee: Michael Martell > Fix and Reenable PutAll Test with Callback > -- > > Key: GEODE-9246 > URL: https://issues.apache.org/jira/browse/GEODE-9246 > Project: Geode > Issue Type: Test > Components: native client >Reporter: Michael Martell >Assignee: Michael Martell >Priority: Major > Labels: pull-request-available > > There are no putAll tests with a callback. This ticket is to fix and reenable > the following legacy test: > testThinClientLargePutAllWithCallBackArg -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9220) Switch unit and integration tests to use JedisCluster
[
https://issues.apache.org/jira/browse/GEODE-9220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Murmann reassigned GEODE-9220:
Assignee: Jens Deppe
> Switch unit and integration tests to use JedisCluster
> -
>
> Key: GEODE-9220
> URL: https://issues.apache.org/jira/browse/GEODE-9220
> Project: Geode
> Issue Type: Test
> Components: redis
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> This won't make sense for some commands that are not 'cluster aware' - for
> example {{INFO}}. Commands that act on a key are all cluster aware.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
