[jira] [Commented] (GEODE-9119) Move test file missed as part of module renaming
[ https://issues.apache.org/jira/browse/GEODE-9119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17314863#comment-17314863 ] ASF subversion and git services commented on GEODE-9119: Commit 9570f4ec2663646ea51a48d217ae9db1f423c865 in geode's branch refs/heads/develop from Jens Deppe [ https://gitbox.apache.org/repos/asf?p=geode.git;h=9570f4e ] GEODE-9119: Move file missed during module renaming (#6258) > Move test file missed as part of module renaming > > > Key: GEODE-9119 > URL: https://issues.apache.org/jira/browse/GEODE-9119 > Project: Geode > Issue Type: Test > Components: redis >Reporter: Jens Deppe >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-9119) Move test file missed as part of module renaming
[ https://issues.apache.org/jira/browse/GEODE-9119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jens Deppe resolved GEODE-9119. --- Fix Version/s: 1.15.0 Resolution: Fixed > Move test file missed as part of module renaming > > > Key: GEODE-9119 > URL: https://issues.apache.org/jira/browse/GEODE-9119 > Project: Geode > Issue Type: Test > Components: redis >Reporter: Jens Deppe >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9080) Enable resource-monitoring for Windows CI instances
[ https://issues.apache.org/jira/browse/GEODE-9080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17314939#comment-17314939 ] ASF subversion and git services commented on GEODE-9080: Commit 9b3ad21a45d8fa986b680c8268be3c5db31133a9 in geode's branch refs/heads/develop from Robert Houghton [ https://gitbox.apache.org/repos/asf?p=geode.git;h=9b3ad21 ] GEODE-9080: Add new stackdriver agent to Windows compute images (#6256) As a precursor to right-sizing our Windows instances, we need to know their resource use. The jobs are not long-lived enough for the GCP Recommendation system to tell us, so we need our own monitoring. Thus, add stackdriver, so that we can see the data for memory and details about CPU use. > Enable resource-monitoring for Windows CI instances > --- > > Key: GEODE-9080 > URL: https://issues.apache.org/jira/browse/GEODE-9080 > Project: Geode > Issue Type: Improvement > Components: ci >Reporter: Robert Houghton >Assignee: Robert Houghton >Priority: Major > Labels: pull-request-available > > Google monitoring via stackdriver is not enabled on Geode's windows CI > instances. Remedy this, to enable better utilization/sizing. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-9080) Enable resource-monitoring for Windows CI instances
[ https://issues.apache.org/jira/browse/GEODE-9080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Houghton resolved GEODE-9080. Fix Version/s: 1.15.0 Resolution: Fixed > Enable resource-monitoring for Windows CI instances > --- > > Key: GEODE-9080 > URL: https://issues.apache.org/jira/browse/GEODE-9080 > Project: Geode > Issue Type: Improvement > Components: ci >Reporter: Robert Houghton >Assignee: Robert Houghton >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > Google monitoring via stackdriver is not enabled on Geode's windows CI > instances. Remedy this, to enable better utilization/sizing. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8899) Update dockerized test plugin
[ https://issues.apache.org/jira/browse/GEODE-8899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17314945#comment-17314945 ] ASF subversion and git services commented on GEODE-8899: Commit d691567841363c28ba29cb5eb54fdbb77f4d4138 in geode's branch refs/heads/develop from Dale Emery [ https://gitbox.apache.org/repos/asf?p=geode.git;h=d691567 ] GEODE-8899: Prep CI scripts for upcoming DUnit command line changes (#6254) Change CI scripts to support running parallel DUnit tests with either Geode's current Gradle 5.5 build or the upcoming Gradle 6.8.3 build. This allows testing the upgrade to Gradle 6.8.3 in the PR precheckin pipeline. Where the current build uses a single command line option (-PdunitParallelForks) to specify the maximum number of parallel dockerized test workers, the upcoming build uses two (--max-workers and -PtestMaxParallelForks). This commit changes the CI build scripts to specify all three options on the Gradle command line for parallel DUnit tests. With this commit: - If the scripts run a Gradle 5.5 build, the old option will configure the tests, and the new options will have no effect. - If the scripts run a Gradle 6.8.3 build, the new options will configure the tests, and the old option will have no effect. Authored-by: Dale Emery > Update dockerized test plugin > - > > Key: GEODE-8899 > URL: https://issues.apache.org/jira/browse/GEODE-8899 > Project: Geode > Issue Type: Test > Components: tests >Reporter: Dale Emery >Assignee: Dale Emery >Priority: Major > Labels: GeodeOperationAPI, pull-request-available > > *Problem:* The dockerized test plugin includes modified copies of internal > Gradle code. This code depends on internal Gradle classes and method > signatures as defined in Gradle 5.8. These dependencies prevent us from > updating Gradle. > *Solution:* Update the dockerized test plugin code to be compatible with the > latest Gradle, and to take advantage of recent Gradle features (such as the > "worker lease" mechanism) that make some plugin details unnecessary. > Where possible, change the plugin code to use public Gradle APIs. > Where the plugin must depend on internal Gradle implementation details, > comment the code to indicate: > * Which internal Gradle implementation details the code depends on > * The latest version of Gradle known to satisfy these dependencies > Where the plugin must use modified copies of internal Gradle code, comment > the code to indicate: > * Which Gradle class was copied > * Which version of Gradle the class was copied from > * What modifications were made in the copy, and why > These comments will help identify implementation details in the plugin that > risk incompatibility with future versions of Gradle. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8977) Thread monitoring service should also show locked monitors and synchronizers
[
https://issues.apache.org/jira/browse/GEODE-8977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17314952#comment-17314952
]
Darrel Schneider commented on GEODE-8977:
-
Before:
{noformat}
[warn 2021/04/02 10:01:17.496 PDT tid=0xf] Thread <58> (0x3a)
that was executed at <02 Apr 2021 10:01:10 PDT> has been stuck for <7.48
seconds> and number of thread monitor iteration <1>
Thread Name state
Executor Group
Monitored metric
Thread stack:
java.lang.Thread.sleep(Native Method)
TestFunction.sleep(TestFunction.java:86)
TestFunction.execute(TestFunction.java:35)
org.apache.geode.internal.cache.execute.AbstractExecution.executeFunctionLocally(AbstractExecution.java:328)
org.apache.geode.internal.cache.execute.AbstractExecution.lambda$executeFunctionOnLocalPRNode$0(AbstractExecution.java:273)
org.apache.geode.internal.cache.execute.AbstractExecution$$Lambda$317/1611044977.run(Unknown
Source)
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
org.apache.geode.distributed.internal.ClusterOperationExecutors.runUntilShutdown(ClusterOperationExecutors.java:442)
org.apache.geode.distributed.internal.ClusterOperationExecutors.doFunctionExecutionThread(ClusterOperationExecutors.java:377)
org.apache.geode.distributed.internal.ClusterOperationExecutors$$Lambda$63/618199162.invoke(Unknown
Source)
org.apache.geode.logging.internal.executors.LoggingThreadFactory.lambda$newThread$0(LoggingThreadFactory.java:119)
org.apache.geode.logging.internal.executors.LoggingThreadFactory$$Lambda$53/873134840.run(Unknown
Source)
java.lang.Thread.run(Thread.java:745)
{noformat}
After:
{noformat}
[warn 2021/04/02 09:55:33.626 PDT tid=0xf] Thread <58> (0x3a)
that was executed at <02 Apr 2021 09:55:18 PDT> has been stuck for <14.758
seconds> and number of thread monitor iteration <2>
Thread Name state
Executor Group
Monitored metric
Thread stack for "Function Execution Processor2" (0x3a):
java.lang.ThreadState: TIMED_WAITING
at java.lang.Thread.sleep(Native Method)
at TestFunction.sleep(TestFunction.java:86)
at TestFunction.execute(TestFunction.java:35)
- locked java.lang.Object@587c50ca
at
org.apache.geode.internal.cache.execute.AbstractExecution.executeFunctionLocally(AbstractExecution.java:328)
at
org.apache.geode.internal.cache.execute.AbstractExecution.lambda$executeFunctionOnLocalPRNode$0(AbstractExecution.java:273)
at
org.apache.geode.internal.cache.execute.AbstractExecution$$Lambda$317/122802218.run(Unknown
Source)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at
org.apache.geode.distributed.internal.ClusterOperationExecutors.runUntilShutdown(ClusterOperationExecutors.java:442)
at
org.apache.geode.distributed.internal.ClusterOperationExecutors.doFunctionExecutionThread(ClusterOperationExecutors.java:377)
at
org.apache.geode.distributed.internal.ClusterOperationExecutors$$Lambda$63/618199162.invoke(Unknown
Source)
at
org.apache.geode.logging.internal.executors.LoggingThreadFactory.lambda$newThread$0(LoggingThreadFactory.java:119)
at
org.apache.geode.logging.internal.executors.LoggingThreadFactory$$Lambda$53/873134840.run(Unknown
Source)
at java.lang.Thread.run(Thread.java:745)
Locked ownable synchronizers:
- java.util.concurrent.ThreadPoolExecutor$Worker@42d21af5
{noformat}
> Thread monitoring service should also show locked monitors and synchronizers
>
>
> Key: GEODE-8977
> URL: https://issues.apache.org/jira/browse/GEODE-8977
> Project: Geode
> Issue Type: Improvement
> Components: core
>Reporter: Darrel Schneider
>Assignee: Darrel Schneider
>Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
>
> The thread monitoring service shows the call stack of a hung thread but it
> does not show the synchronizations obtained by the frames in the call stack
> like a normal stack dump does.
> It looks like this is available from the ThreadInfo class that the service is
> already using by calling getLockedMonitors and getLockedSynchronizers. The
> getLockedMonitors returns a MonitorInfo which has information in it about
> which frame of the stack obtained it. MonitorInfo subclasses LockInfo which
> is what getLockedSynchronizers returns so it is possible that
> getLockedSynchronizers does not provide any additional information to be
> logged.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (GEODE-8977) Thread monitoring service should also show locked monitors and synchronizers
[ https://issues.apache.org/jira/browse/GEODE-8977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider resolved GEODE-8977. - Fix Version/s: 1.15.0 Resolution: Fixed > Thread monitoring service should also show locked monitors and synchronizers > > > Key: GEODE-8977 > URL: https://issues.apache.org/jira/browse/GEODE-8977 > Project: Geode > Issue Type: Improvement > Components: core >Reporter: Darrel Schneider >Assignee: Darrel Schneider >Priority: Major > Labels: GeodeOperationAPI, pull-request-available > Fix For: 1.15.0 > > > The thread monitoring service shows the call stack of a hung thread but it > does not show the synchronizations obtained by the frames in the call stack > like a normal stack dump does. > It looks like this is available from the ThreadInfo class that the service is > already using by calling getLockedMonitors and getLockedSynchronizers. The > getLockedMonitors returns a MonitorInfo which has information in it about > which frame of the stack obtained it. MonitorInfo subclasses LockInfo which > is what getLockedSynchronizers returns so it is possible that > getLockedSynchronizers does not provide any additional information to be > logged. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8977) Thread monitoring service should also show locked monitors and synchronizers
[ https://issues.apache.org/jira/browse/GEODE-8977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17314953#comment-17314953 ] ASF subversion and git services commented on GEODE-8977: Commit 903afb5332b06b10e7f53a1abe9c53775a94f39e in geode's branch refs/heads/develop from Darrel Schneider [ https://gitbox.apache.org/repos/asf?p=geode.git;h=903afb5 ] GEODE-8977: include syncs in thread monitor stack (#6248) Thread monitor stack now includes syncs and locked objects. It has also been reformated to look more like a normal stack dump. > Thread monitoring service should also show locked monitors and synchronizers > > > Key: GEODE-8977 > URL: https://issues.apache.org/jira/browse/GEODE-8977 > Project: Geode > Issue Type: Improvement > Components: core >Reporter: Darrel Schneider >Assignee: Darrel Schneider >Priority: Major > Labels: GeodeOperationAPI, pull-request-available > Fix For: 1.15.0 > > > The thread monitoring service shows the call stack of a hung thread but it > does not show the synchronizations obtained by the frames in the call stack > like a normal stack dump does. > It looks like this is available from the ThreadInfo class that the service is > already using by calling getLockedMonitors and getLockedSynchronizers. The > getLockedMonitors returns a MonitorInfo which has information in it about > which frame of the stack obtained it. MonitorInfo subclasses LockInfo which > is what getLockedSynchronizers returns so it is possible that > getLockedSynchronizers does not provide any additional information to be > logged. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-7125) Simplify documentation navigation (remove left nav parent links; add in-page TOCs)
[ https://issues.apache.org/jira/browse/GEODE-7125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes reassigned GEODE-7125: -- Assignee: Dave Barnes > Simplify documentation navigation (remove left nav parent links; add in-page > TOCs) > -- > > Key: GEODE-7125 > URL: https://issues.apache.org/jira/browse/GEODE-7125 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Joey McAllister >Assignee: Dave Barnes >Priority: Major > > The Geode user guide uses Bookbinder to create HTML documentation from > markdown files. This ticket is about changing two ways in which Geode > currently uses Bookbinder sub-optimally: > # For listings in the left navigation with submenus, we give the parent > listing a link to a TOC page—e.g., [Prerequisites and Installation > Instructions|[https://geode.apache.org/docs/guide/19/prereq_and_install.html]]. > This isn't inherently bad (though it is somewhat redundant, as the left > navigation also serves this purpose), but when a user visits such a link, the > submenu on the left collapses. _Note:_ _The menu does not collapse when a > user visits a child link in the submenu of these items._ > ** Fix/Improvement: Wherever possible, remove the link from the subnav > parent item (leaving the now-unclickable parent item) and the related TOC > page. If the TOC page contains content beyond a TOC for the child pages, move > that content to an appropriate place within the existing child pages or, if > necessary, create a new page for it. For instance, the information above the > TOC in [Configuring and Running a > Cluster|[https://geode.apache.org/docs/guide/19/configuring/chapter_overview.html]] > could move to a new page at the top of that parent's submenu or, more > likely, to the Overview of the [Cluster Configuration > Service|[https://geode.apache.org/docs/guide/19/configuring/cluster_config/gfsh_persist.html]] > page. > # For left nav listings with submenus where all the pages link to anchors > within a page (instead of to topics on individual pages), Bookbinder provides > an option called "quicklinks" that automatically uses H2 (`##`) and smaller > subheads to create a small, in-page TOC at the top of the page. We currently > disable this functionality. > ** Fix/Improvement: Remove the "no-quicklinks" tags from anchors that we > want to appear in the in-page TOC. Also remove any duplicate links from the > left navigation. (In other words, the in-page TOC will now replace some > navigation functionality currently performed by the left nav, thereby > simplifying the left nav.) For example, see [Managing Heap and Off-heap > Memory|[https://geode.apache.org/docs/guide/19/managing/heap_use/heap_management.html]], > where many (but, notably, not all) of the child links in the left nav lead > to anchors within one page. These can become one new child page/link called > Managing Heap Memory, leaving only Resource Manager Example Configurations, > Managing Off-Heap Memory, and Locking Memory as child links alongside the new > one. The rest become in-page TOC anchor links in Managing Heap Memory. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9108) Remove no-ack from existing tests
[
https://issues.apache.org/jira/browse/GEODE-9108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17314975#comment-17314975
]
ASF GitHub Bot commented on GEODE-9108:
---
mmartell commented on a change in pull request #780:
URL: https://github.com/apache/geode-native/pull/780#discussion_r607208728
##
File path: cppcache/integration-test/ThinClientHelper.hpp
##
@@ -134,7 +134,7 @@ const char* vals[] = {"Value-1", "Value-2", "Value-3",
const char* nvals[] = {"New Value-1", "New Value-2", "New Value-3",
"New Value-4", "New Value-5", "New Value-6"};
-const char* regionNames[] = {"DistRegionAck", "DistRegionNoAck"};
+const char* regionNames[] = {"DistRegionAck", "not-used"};
Review comment:
Lots of tests use this header. Changing to a scalar caused lots of
compile issues (mostly in disabled tests). Suggest we leave this file
untouched, as probably too much work to fix compile issues.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Remove no-ack from existing tests
> -
>
> Key: GEODE-9108
> URL: https://issues.apache.org/jira/browse/GEODE-9108
> Project: Geode
> Issue Type: Test
> Components: native client
>Reporter: Michael Martell
>Priority: Major
> Labels: pull-request-available
>
> Many of the geode-native legacy tests use no-ack for the region scope
> attribute. This has been shown to be the source of intermittent failures of
> many of the tests, and should should be removed. As region scope is purely
> server side functionality, there should little to no need to test it from a
> client's perspective. If there is a use case for such a no-ack test from
> geode-native, it should be captured in a new test.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-8859) Redis data structures may not accurately reflect their size in Geode stats
[
https://issues.apache.org/jira/browse/GEODE-8859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17314993#comment-17314993
]
ASF subversion and git services commented on GEODE-8859:
Commit 7a85b4df1b80518e7b3d1ff405d0f76ca45fa785 in geode's branch
refs/heads/develop from Nabarun Nag
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=7a85b4d ]
Revert "GEODE-8859: Fix redis-compatability data structure bucket memory-usage
reporting (#6084)" (#6260)
This reverts commit e927bdf42b64eac96758642fcd22c8a144a3890e.
> Redis data structures may not accurately reflect their size in Geode stats
> --
>
> Key: GEODE-8859
> URL: https://issues.apache.org/jira/browse/GEODE-8859
> Project: Geode
> Issue Type: Bug
> Components: redis, statistics
>Affects Versions: 1.14.0
>Reporter: Jens Deppe
>Assignee: John Hutchison
>Priority: Major
> Labels: blocks-1.14.0, pull-request-available, release-blocker
> Fix For: 1.14.0, 1.15.0
>
>
> Here is a comment from Darrel regarding this issue. For some background, the
> Redis structures implement {{Delta}}.
>
> {quote}I was playing around with RedisInsight and was able to get most the
> the overview dashboard and the data browser working with geode redis. But I
> found a problem with how we are using geode that causes the geode stats that
> track how much data is stored in a partitioned region to be wrong and the
> bucket sizes used for rebalancing are also wrong. Basically when we do create
> ops on the region the stats track it okay. But when we do updates then geode
> always thinks that nothing (size wise) changed. So for example I created a
> string by doing a redis “set” command. I saw the size of the string accounted
> for in dataStoreBytesInUse. But then I kept doing redis “append” commands on
> that key and the dataStoreBytesInUse did not change at all. I think the
> problem is in how we are updating the data structure in place instead of
> getting a copy, modifying it, and then putting the copy into the region.
> Avoiding this copy gives us MUCH better performance but it messes up geode
> when it is trying to calculate the memory increase or decrease. It is
> possible that this is only an issue on the primary and that the secondary
> sizing may be correct. If so that could lead to other problems because for a
> given bucket our primary size would be different than the secondary. The
> bucket sizes are used when you do a rebalance but basically we can have a
> bunch of memory that is “untracked” so we might see the JVM heaps unbalanced
> but geode will think the buckets are balanced. I’m not sure what we should do
> about this.
> {quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-9037) Do not expose unsupported commands in Geode compatibility with Redis
[ https://issues.apache.org/jira/browse/GEODE-9037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nabarun Nag updated GEODE-9037: --- Fix Version/s: 1.14.0 > Do not expose unsupported commands in Geode compatibility with Redis > > > Key: GEODE-9037 > URL: https://issues.apache.org/jira/browse/GEODE-9037 > Project: Geode > Issue Type: New Feature > Components: redis >Reporter: Ray Ingles >Assignee: Ray Ingles >Priority: Major > Labels: blocks-1.14.0, pull-request-available > Fix For: 1.14.0, 1.15.0 > > > The distinction between 'supported' and 'unsupported' commands is no longer > useful and will be removed. Any commands still listed as unsupported will now > respond if they were unimplemented/unknown. > A system property will allow them to be enabled solely for tests. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9035) Enable all Hash tests in pipeline native-Redis tests
[ https://issues.apache.org/jira/browse/GEODE-9035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nabarun Nag updated GEODE-9035: --- Fix Version/s: 1.14.0 > Enable all Hash tests in pipeline native-Redis tests > > > Key: GEODE-9035 > URL: https://issues.apache.org/jira/browse/GEODE-9035 > Project: Geode > Issue Type: New Feature > Components: redis >Reporter: Ray Ingles >Assignee: Ray Ingles >Priority: Major > Labels: pull-request-available > Fix For: 1.14.0, 1.15.0 > > > All hash commands are now supported in the compatibility-with-Redis > subsystem. This will enable the native Redis integration tests (written in > TCL) to run the Hash test suite against Geode compatibility-with-Redis. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9052) rename geode-redis module
[ https://issues.apache.org/jira/browse/GEODE-9052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nabarun Nag updated GEODE-9052: --- Fix Version/s: 1.15.0 1.14.0 > rename geode-redis module > - > > Key: GEODE-9052 > URL: https://issues.apache.org/jira/browse/GEODE-9052 > Project: Geode > Issue Type: New Feature > Components: redis >Affects Versions: 1.14.0 >Reporter: Hale Bales >Assignee: Hale Bales >Priority: Major > Labels: blocks-1.14.0, pull-request-available > Fix For: 1.14.0, 1.15.0 > > > Rename the geode-redis module to geode-apis-compatible-with-redis. This will > change the name of the jar that we distribute, which will help us avoid any > potential copyright issues. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9037) Do not expose unsupported commands in Geode compatibility with Redis
[ https://issues.apache.org/jira/browse/GEODE-9037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17314995#comment-17314995 ] ASF subversion and git services commented on GEODE-9037: Commit 1c3d8f3013af20b92ab0d64382a45f77bf9c082c in geode's branch refs/heads/support/1.14 from Nabarun Nag [ https://gitbox.apache.org/repos/asf?p=geode.git;h=1c3d8f3 ] GEODE-9037: Remove unimplemented commands #6244 * Update handling of unsupported commands * This reverts commit 55ee370ca436f10f5acd383867039ccc1055fd27 in develop which implements the code change. (cherry picked from commit cf4c3395644af48bcbda81bef7a6d1e01b2c47cf) > Do not expose unsupported commands in Geode compatibility with Redis > > > Key: GEODE-9037 > URL: https://issues.apache.org/jira/browse/GEODE-9037 > Project: Geode > Issue Type: New Feature > Components: redis >Reporter: Ray Ingles >Assignee: Ray Ingles >Priority: Major > Labels: blocks-1.14.0, pull-request-available > Fix For: 1.14.0, 1.15.0 > > > The distinction between 'supported' and 'unsupported' commands is no longer > useful and will be removed. Any commands still listed as unsupported will now > respond if they were unimplemented/unknown. > A system property will allow them to be enabled solely for tests. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9035) Enable all Hash tests in pipeline native-Redis tests
[ https://issues.apache.org/jira/browse/GEODE-9035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17314997#comment-17314997 ] ASF subversion and git services commented on GEODE-9035: Commit 407b53e4679b86264b5927dabd1de7cf5efb6d1a in geode's branch refs/heads/support/1.14 from Ray Ingles [ https://gitbox.apache.org/repos/asf?p=geode.git;h=407b53e ] GEODE-9035: Enable Redis TCL tests for all Hash commands (#6243) (cherry picked from commit fa6103b444d0357e5be34650df20acebdc7e2a7a) > Enable all Hash tests in pipeline native-Redis tests > > > Key: GEODE-9035 > URL: https://issues.apache.org/jira/browse/GEODE-9035 > Project: Geode > Issue Type: New Feature > Components: redis >Reporter: Ray Ingles >Assignee: Ray Ingles >Priority: Major > Labels: pull-request-available > Fix For: 1.14.0, 1.15.0 > > > All hash commands are now supported in the compatibility-with-Redis > subsystem. This will enable the native Redis integration tests (written in > TCL) to run the Hash test suite against Geode compatibility-with-Redis. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9089) Two SerialWANStatsDUnitTest.testReplicatedSerialPropagation... Test Variants Fail
[
https://issues.apache.org/jira/browse/GEODE-9089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17315010#comment-17315010
]
Geode Integration commented on GEODE-9089:
--
Seen in [DistributedTestOpenJDK8
#131|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/131]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0116/test-results/distributedTest/1617640137/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0116/test-artifacts/1617640137/distributedtestfiles-OpenJDK8-1.15.0-build.0116.tgz].
> Two SerialWANStatsDUnitTest.testReplicatedSerialPropagation... Test Variants
> Fail
> -
>
> Key: GEODE-9089
> URL: https://issues.apache.org/jira/browse/GEODE-9089
> Project: Geode
> Issue Type: Task
> Components: wan
>Affects Versions: 1.15.0
>Reporter: Bill Burcham
>Priority: Major
>
> Two failures in this CI run:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/106:
> {code:java}
> org.apache.geode.internal.cache.wan.serial.SerialWANStatsDUnitTest >
> testReplicatedSerialPropagationHAWithGroupTransactionEvents FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.wan.serial.SerialWANStatsDUnitTest$$Lambda$151/1201663250.run
> in VM 2 running on Host d2642cb6ec08 with 8 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.internal.cache.wan.serial.SerialWANStatsDUnitTest.testReplicatedSerialPropagationHAWithGroupTransactionEvents(SerialWANStatsDUnitTest.java:757)
> Caused by:
> 00, 899000, 665100, 587000, 518100, 721000, 623100, 551000, 592000, 182100,
> 779100, 164100, 5104300, 5326300, 297000, 31100, 843000, 910100, 992000,
> 456100, 190100, 982100, 5517300, 815000, 5411200, 1093000, 657100, 870100,
> 5210300, 176100, 5065200, 294100, 5521300, 1034000, 570100, 5257200, 827000,
> 5535200, 77100, 862000, 5419300, 255100, 681000, 348100, 5423200, 5194300,
> 5416300, 5554200, 5392300, 711000, 857100, 320100, 5449200, 5348300, 5004200,
> 426100, 111, 5487200, 787000, 884000, 5216200, 5560200, 580100, 861000,
> 425000, 799100, 5553200, 972100, 5114200, 271000, 5000200, 243000, 172100,
> 5561200, 262000, 1091100, 477100, 75, 109000, 5431300, 980100, 5237300,
> 5308300, 5150200, 689000, 207000, 446100, 805100, 5111200, 9000, 00,
> 5534300, 536100, 5062300, 1082000, 5397200, 798100, 5308200, 553000, 5374300,
> 703000, 160100, 5560300, 38100, 4100, 678100, 1113100, 973000, 5558300,
> 5175200, 5188200, 212100, 1007000, 1104000, 467100, 5540200, 809000, 810100,
> 1106100, 1077100, 69100, 5143200, 776100, 5396200, 113100, 181000, 1094100,
> 883100, 542100, 5031200, 147100, 481000, 353000, 1050100, 219100, 4000,
> 576000, 393000, 248100, 5508200, 1012000, 380100, 5166300, 894100, 5398200,
> 510100, 798000, 5066200, 5189200, 39, 832000, 5377200, 5022300, 311100,
> 1017100, 383100, 5401200, 266000, 966100, 231000, 5382300, 778000, 276100,
> 5320300, 529100, 496100, 5256200, 860100, 5360300, 1055100, 5250200, 609100,
> 553100, 5259300, 5089300, 43, 5565200, 579100, 1065000, 424000, 622100,
> 157000, 847100, 80100, 5460200, 5124300, 101000, 898100, 5292300, 482100,
> 5553300, 1074100, 5499300, 554000, 5352200, 5039300, 2000, 667000, 376000,
> 5143300, 753100, 466000, 5064300, 5006200, 5174200, 744100, 937000, 5145200,
> 71100, 351100, 5289200, 206100, 805000, 5493200, 431000, 378100, 333100,
> 5118200, 103100, 462000, 5527200, 5255200, 5033200, 56100, 521100, 8100,
> 300, 42000, 331100, 5439200, 68, 801100, 65100, 5207300, 479000,
> 792100, 5004300, 5171300, 318000, 681100, 619100, 955100, 903000, 72000,
> 5292200, 1044000, 1023100, 323000, 5353300, 558000, 544100, 265000, 5018200,
> 5340300, 751100, 607000, 582000, 465100, 253100, 935100, 174100, 5043300,
> 537100, 178000, 1127100, 88100, 661100, 5402200, 3, 958100, 49000, 96100,
> 979000, 5081300, 5075300, 5206300, 84000, 5154200, 1057100, 5409300, 62000,
> 506000, 1107100, 5022200, 921000, 448100, 1004100, 427100, 829000, 1107000,
> 244000, 414000, 74100, 409000, 833100, 77, 51000, 5113300, 908100,
> 5312300, 5263300, 5148300, 138100, 336100, 1081000, 5365300, 151000, 165000,
> 759000, 752000, 19, 5460300, 685000, 298100, 566100, 877100, 46,
> 5108300, 377100, 71, 750100, 95100, 228100, 5116300, 522100, 5110200,
> 45, 64, 5086200, 683000, 348000, 305000, 797100, 18, 636000,
> 5494300, 634100, 1072000, 5323200, 7371
[jira] [Commented] (GEODE-8191) MemberMXBeanDistributedTest.testBucketCount fails intermittently
[
https://issues.apache.org/jira/browse/GEODE-8191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17315009#comment-17315009
]
Geode Integration commented on GEODE-8191:
--
Seen in [DistributedTestOpenJDK11
#135|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/135]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0116/test-results/distributedTest/1617638975/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0116/test-artifacts/1617638975/distributedtestfiles-OpenJDK11-1.15.0-build.0116.tgz].
> MemberMXBeanDistributedTest.testBucketCount fails intermittently
>
>
> Key: GEODE-8191
> URL: https://issues.apache.org/jira/browse/GEODE-8191
> Project: Geode
> Issue Type: Bug
> Components: jmx, tests
>Reporter: Kirk Lund
>Assignee: Mario Ivanac
>Priority: Major
> Labels: flaky, pull-request-available
>
> This appears to be a flaky test related to GEODE-7963 which was resolved by
> Mario Ivanac so I've assigned the ticket to him.
> {noformat}
> org.apache.geode.management.MemberMXBeanDistributedTest > testBucketCount
> FAILED
> org.awaitility.core.ConditionTimeoutException: Assertion condition
> defined as a lambda expression in
> org.apache.geode.management.MemberMXBeanDistributedTest Expected bucket count
> is 4000, and actual count is 3750 expected:<3750> but was:<4000> within 5
> minutes.
> at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
> at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:895)
> at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:679)
> at
> org.apache.geode.management.MemberMXBeanDistributedTest.testBucketCount(MemberMXBeanDistributedTest.java:102)
> Caused by:
> java.lang.AssertionError: Expected bucket count is 4000, and actual
> count is 3750 expected:<3750> but was:<4000>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:834)
> at org.junit.Assert.assertEquals(Assert.java:645)
> at
> org.apache.geode.management.MemberMXBeanDistributedTest.lambda$testBucketCount$1(MemberMXBeanDistributedTest.java:107)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-6903) CI Failure: GemFireTransactionDataSourceIntegrationTest.testExceptionHandlingGetConnection failed with Assertion
[
https://issues.apache.org/jira/browse/GEODE-6903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17315016#comment-17315016
]
Geode Integration commented on GEODE-6903:
--
Seen in [WindowsCoreIntegrationTestOpenJDK11
#126|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/WindowsCoreIntegrationTestOpenJDK11/builds/126]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0116/test-results/integrationTest/1617645658/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0116/test-artifacts/1617645658/windows-coreintegrationtestfiles-OpenJDK11-1.15.0-build.0116.tgz].
> CI Failure:
> GemFireTransactionDataSourceIntegrationTest.testExceptionHandlingGetConnection
> failed with Assertion
>
>
> Key: GEODE-6903
> URL: https://issues.apache.org/jira/browse/GEODE-6903
> Project: Geode
> Issue Type: Bug
> Components: transactions
>Affects Versions: 1.14.0
>Reporter: Eric Shu
>Assignee: Eric Shu
>Priority: Major
> Labels: flaky
>
> {noformat}
> org.apache.geode.internal.datasource.GemFireTransactionDataSourceIntegrationTest
> > testExceptionHandlingGetConnection FAILED
> org.junit.ComparisonFailure: expected:<[0]> but was:<[2]>
> at sun.reflect.GeneratedConstructorAccessor26.newInstance(Unknown
> Source)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.internal.datasource.GemFireTransactionDataSourceIntegrationTest.testExceptionHandlingGetConnection(GemFireTransactionDataSourceIntegrationTest.java:141)
> {noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0399/test-results/integrationTest/1561170841/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0399/test-artifacts/1561170841/integrationtestfiles-OpenJDK8-1.10.0-SNAPSHOT.0399.tgz
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Reopened] (GEODE-8859) Redis data structures may not accurately reflect their size in Geode stats
[
https://issues.apache.org/jira/browse/GEODE-8859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nabarun Nag reopened GEODE-8859:
> Redis data structures may not accurately reflect their size in Geode stats
> --
>
> Key: GEODE-8859
> URL: https://issues.apache.org/jira/browse/GEODE-8859
> Project: Geode
> Issue Type: Bug
> Components: redis, statistics
>Affects Versions: 1.14.0
>Reporter: Jens Deppe
>Assignee: John Hutchison
>Priority: Major
> Labels: blocks-1.14.0, pull-request-available, release-blocker
> Fix For: 1.14.0, 1.15.0
>
>
> Here is a comment from Darrel regarding this issue. For some background, the
> Redis structures implement {{Delta}}.
>
> {quote}I was playing around with RedisInsight and was able to get most the
> the overview dashboard and the data browser working with geode redis. But I
> found a problem with how we are using geode that causes the geode stats that
> track how much data is stored in a partitioned region to be wrong and the
> bucket sizes used for rebalancing are also wrong. Basically when we do create
> ops on the region the stats track it okay. But when we do updates then geode
> always thinks that nothing (size wise) changed. So for example I created a
> string by doing a redis “set” command. I saw the size of the string accounted
> for in dataStoreBytesInUse. But then I kept doing redis “append” commands on
> that key and the dataStoreBytesInUse did not change at all. I think the
> problem is in how we are updating the data structure in place instead of
> getting a copy, modifying it, and then putting the copy into the region.
> Avoiding this copy gives us MUCH better performance but it messes up geode
> when it is trying to calculate the memory increase or decrease. It is
> possible that this is only an issue on the primary and that the secondary
> sizing may be correct. If so that could lead to other problems because for a
> given bucket our primary size would be different than the secondary. The
> bucket sizes are used when you do a rebalance but basically we can have a
> bunch of memory that is “untracked” so we might see the JVM heaps unbalanced
> but geode will think the buckets are balanced. I’m not sure what we should do
> about this.
> {quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9089) Two SerialWANStatsDUnitTest.testReplicatedSerialPropagation... Test Variants Fail
[
https://issues.apache.org/jira/browse/GEODE-9089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17315063#comment-17315063
]
Geode Integration commented on GEODE-9089:
--
Seen in [DistributedTestOpenJDK11
#136|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/136]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0117/test-results/distributedTest/1617650247/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0117/test-artifacts/1617650247/distributedtestfiles-OpenJDK11-1.15.0-build.0117.tgz].
> Two SerialWANStatsDUnitTest.testReplicatedSerialPropagation... Test Variants
> Fail
> -
>
> Key: GEODE-9089
> URL: https://issues.apache.org/jira/browse/GEODE-9089
> Project: Geode
> Issue Type: Task
> Components: wan
>Affects Versions: 1.15.0
>Reporter: Bill Burcham
>Priority: Major
>
> Two failures in this CI run:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/106:
> {code:java}
> org.apache.geode.internal.cache.wan.serial.SerialWANStatsDUnitTest >
> testReplicatedSerialPropagationHAWithGroupTransactionEvents FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.wan.serial.SerialWANStatsDUnitTest$$Lambda$151/1201663250.run
> in VM 2 running on Host d2642cb6ec08 with 8 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.internal.cache.wan.serial.SerialWANStatsDUnitTest.testReplicatedSerialPropagationHAWithGroupTransactionEvents(SerialWANStatsDUnitTest.java:757)
> Caused by:
> 00, 899000, 665100, 587000, 518100, 721000, 623100, 551000, 592000, 182100,
> 779100, 164100, 5104300, 5326300, 297000, 31100, 843000, 910100, 992000,
> 456100, 190100, 982100, 5517300, 815000, 5411200, 1093000, 657100, 870100,
> 5210300, 176100, 5065200, 294100, 5521300, 1034000, 570100, 5257200, 827000,
> 5535200, 77100, 862000, 5419300, 255100, 681000, 348100, 5423200, 5194300,
> 5416300, 5554200, 5392300, 711000, 857100, 320100, 5449200, 5348300, 5004200,
> 426100, 111, 5487200, 787000, 884000, 5216200, 5560200, 580100, 861000,
> 425000, 799100, 5553200, 972100, 5114200, 271000, 5000200, 243000, 172100,
> 5561200, 262000, 1091100, 477100, 75, 109000, 5431300, 980100, 5237300,
> 5308300, 5150200, 689000, 207000, 446100, 805100, 5111200, 9000, 00,
> 5534300, 536100, 5062300, 1082000, 5397200, 798100, 5308200, 553000, 5374300,
> 703000, 160100, 5560300, 38100, 4100, 678100, 1113100, 973000, 5558300,
> 5175200, 5188200, 212100, 1007000, 1104000, 467100, 5540200, 809000, 810100,
> 1106100, 1077100, 69100, 5143200, 776100, 5396200, 113100, 181000, 1094100,
> 883100, 542100, 5031200, 147100, 481000, 353000, 1050100, 219100, 4000,
> 576000, 393000, 248100, 5508200, 1012000, 380100, 5166300, 894100, 5398200,
> 510100, 798000, 5066200, 5189200, 39, 832000, 5377200, 5022300, 311100,
> 1017100, 383100, 5401200, 266000, 966100, 231000, 5382300, 778000, 276100,
> 5320300, 529100, 496100, 5256200, 860100, 5360300, 1055100, 5250200, 609100,
> 553100, 5259300, 5089300, 43, 5565200, 579100, 1065000, 424000, 622100,
> 157000, 847100, 80100, 5460200, 5124300, 101000, 898100, 5292300, 482100,
> 5553300, 1074100, 5499300, 554000, 5352200, 5039300, 2000, 667000, 376000,
> 5143300, 753100, 466000, 5064300, 5006200, 5174200, 744100, 937000, 5145200,
> 71100, 351100, 5289200, 206100, 805000, 5493200, 431000, 378100, 333100,
> 5118200, 103100, 462000, 5527200, 5255200, 5033200, 56100, 521100, 8100,
> 300, 42000, 331100, 5439200, 68, 801100, 65100, 5207300, 479000,
> 792100, 5004300, 5171300, 318000, 681100, 619100, 955100, 903000, 72000,
> 5292200, 1044000, 1023100, 323000, 5353300, 558000, 544100, 265000, 5018200,
> 5340300, 751100, 607000, 582000, 465100, 253100, 935100, 174100, 5043300,
> 537100, 178000, 1127100, 88100, 661100, 5402200, 3, 958100, 49000, 96100,
> 979000, 5081300, 5075300, 5206300, 84000, 5154200, 1057100, 5409300, 62000,
> 506000, 1107100, 5022200, 921000, 448100, 1004100, 427100, 829000, 1107000,
> 244000, 414000, 74100, 409000, 833100, 77, 51000, 5113300, 908100,
> 5312300, 5263300, 5148300, 138100, 336100, 1081000, 5365300, 151000, 165000,
> 759000, 752000, 19, 5460300, 685000, 298100, 566100, 877100, 46,
> 5108300, 377100, 71, 750100, 95100, 228100, 5116300, 522100, 5110200,
> 45, 64, 5086200, 683000, 348000, 305000, 797100, 18, 636000,
> 5494300, 634100, 1072000, 5323200, 7
[jira] [Commented] (GEODE-8990) CI Failure: Jetty9CachingClientServerTest.shouldCacheSessionOnClient
[
https://issues.apache.org/jira/browse/GEODE-8990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17315061#comment-17315061
]
Geode Integration commented on GEODE-8990:
--
Seen in [DistributedTestOpenJDK8
#132|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/132]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0117/test-results/distributedTest/1617650019/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0117/test-artifacts/1617650019/distributedtestfiles-OpenJDK8-1.15.0-build.0117.tgz].
> CI Failure: Jetty9CachingClientServerTest.shouldCacheSessionOnClient
>
>
> Key: GEODE-8990
> URL: https://issues.apache.org/jira/browse/GEODE-8990
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Assignee: Mark Hanson
>Priority: Major
> Labels: pull-request-available
>
> {noformat}
> org.apache.geode.session.tests.Jetty9CachingClientServerTest >
> shouldCacheSessionOnClient FAILED
> org.junit.ComparisonFailure: expected:<[Foo]> but was:<[bogus]>
> at org.junit.Assert.assertEquals(Assert.java:117)
> at org.junit.Assert.assertEquals(Assert.java:146)
> at
> org.apache.geode.session.tests.Jetty9CachingClientServerTest.shouldCacheSessionOnClient(Jetty9CachingClientServerTest.java:65)
> 371 tests completed, 1 failed
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0023/test-results/distributedTest/1614646829/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0023/test-artifacts/1614646829/distributedtestfiles-OpenJDK8-1.15.0-build.0023.tgz
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-9119) Move test file missed as part of module renaming
[ https://issues.apache.org/jira/browse/GEODE-9119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen Nichols updated GEODE-9119: Labels: blocks-1.14.0 pull-request-available (was: pull-request-available) > Move test file missed as part of module renaming > > > Key: GEODE-9119 > URL: https://issues.apache.org/jira/browse/GEODE-9119 > Project: Geode > Issue Type: Test > Components: redis >Reporter: Jens Deppe >Priority: Major > Labels: blocks-1.14.0, pull-request-available > Fix For: 1.15.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-9094) Package splitting geode-gfsh
[ https://issues.apache.org/jira/browse/GEODE-9094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udo Kohlmeyer resolved GEODE-9094. -- Fix Version/s: 1.15.0 Resolution: Fixed > Package splitting geode-gfsh > > > Key: GEODE-9094 > URL: https://issues.apache.org/jira/browse/GEODE-9094 > Project: Geode > Issue Type: Sub-task >Reporter: Udo Kohlmeyer >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9115) CI failure: org.apache.geode.redis.internal.executor.pubsub.LettucePubSubIntegrationTest > quitWhileSubscribe FAILED
[ https://issues.apache.org/jira/browse/GEODE-9115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-9115: -- Labels: pull-request-available (was: ) > CI failure: > org.apache.geode.redis.internal.executor.pubsub.LettucePubSubIntegrationTest > > quitWhileSubscribe FAILED > > > Key: GEODE-9115 > URL: https://issues.apache.org/jira/browse/GEODE-9115 > Project: Geode > Issue Type: Bug > Components: redis >Affects Versions: 1.15.0 >Reporter: Ray Ingles >Priority: Major > Labels: pull-request-available > > See > https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/IntegrationTestOpenJDK8/builds/119 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-6816) Geode Native Client user guide: Broken links to API docs
[ https://issues.apache.org/jira/browse/GEODE-6816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17315103#comment-17315103 ] ASF GitHub Bot commented on GEODE-6816: --- davebarnes97 merged pull request #781: URL: https://github.com/apache/geode-native/pull/781 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Geode Native Client user guide: Broken links to API docs > > > Key: GEODE-6816 > URL: https://issues.apache.org/jira/browse/GEODE-6816 > Project: Geode > Issue Type: Bug > Components: docs, native client >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Labels: pull-request-available > > The page "Configuring the Client Cache" > ([https://geode.apache.org/docs/geode-native/19/configuring/config-client-cache.html]) > contains two links to the API docs, one for C++, one for .NET. The links > don't connect. > Fix likely involves two parts: > # Link targets in the page source need to be given a recognizable, > substitutable form, e.g. "cppdocs" should be "/cppdocs". > # The .htaccess file in the `geode-site` repo needs to pick up on this > notation and substitute the correct paths, which are: > [https://geode.apache.org/releases/latest/cppdocs/index.html], and > [https://geode.apache.org/releases/latest/dotnetdocs/index.html] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-6816) Geode Native Client user guide: Broken links to API docs
[ https://issues.apache.org/jira/browse/GEODE-6816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17315104#comment-17315104 ] ASF subversion and git services commented on GEODE-6816: Commit a04e7ed8f6a6ae197936e9cb617825ab1c65482e in geode-native's branch refs/heads/develop from Dave Barnes [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=a04e7ed ] GEODE-6816: geode-native userguide: fix broken api links (#781) > Geode Native Client user guide: Broken links to API docs > > > Key: GEODE-6816 > URL: https://issues.apache.org/jira/browse/GEODE-6816 > Project: Geode > Issue Type: Bug > Components: docs, native client >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Labels: pull-request-available > > The page "Configuring the Client Cache" > ([https://geode.apache.org/docs/geode-native/19/configuring/config-client-cache.html]) > contains two links to the API docs, one for C++, one for .NET. The links > don't connect. > Fix likely involves two parts: > # Link targets in the page source need to be given a recognizable, > substitutable form, e.g. "cppdocs" should be "/cppdocs". > # The .htaccess file in the `geode-site` repo needs to pick up on this > notation and substitute the correct paths, which are: > [https://geode.apache.org/releases/latest/cppdocs/index.html], and > [https://geode.apache.org/releases/latest/dotnetdocs/index.html] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-6816) Geode Native Client user guide: Broken links to API docs
[ https://issues.apache.org/jira/browse/GEODE-6816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-6816. Fix Version/s: 1.15.0 Resolution: Fixed > Geode Native Client user guide: Broken links to API docs > > > Key: GEODE-6816 > URL: https://issues.apache.org/jira/browse/GEODE-6816 > Project: Geode > Issue Type: Bug > Components: docs, native client >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > The page "Configuring the Client Cache" > ([https://geode.apache.org/docs/geode-native/19/configuring/config-client-cache.html]) > contains two links to the API docs, one for C++, one for .NET. The links > don't connect. > Fix likely involves two parts: > # Link targets in the page source need to be given a recognizable, > substitutable form, e.g. "cppdocs" should be "/cppdocs". > # The .htaccess file in the `geode-site` repo needs to pick up on this > notation and substitute the correct paths, which are: > [https://geode.apache.org/releases/latest/cppdocs/index.html], and > [https://geode.apache.org/releases/latest/dotnetdocs/index.html] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6816) Geode Native Client user guide: Broken links to API docs
[ https://issues.apache.org/jira/browse/GEODE-6816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes updated GEODE-6816: --- Fix Version/s: 1.14.0 > Geode Native Client user guide: Broken links to API docs > > > Key: GEODE-6816 > URL: https://issues.apache.org/jira/browse/GEODE-6816 > Project: Geode > Issue Type: Bug > Components: docs, native client >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Labels: pull-request-available > Fix For: 1.14.0, 1.15.0 > > > The page "Configuring the Client Cache" > ([https://geode.apache.org/docs/geode-native/19/configuring/config-client-cache.html]) > contains two links to the API docs, one for C++, one for .NET. The links > don't connect. > Fix likely involves two parts: > # Link targets in the page source need to be given a recognizable, > substitutable form, e.g. "cppdocs" should be "/cppdocs". > # The .htaccess file in the `geode-site` repo needs to pick up on this > notation and substitute the correct paths, which are: > [https://geode.apache.org/releases/latest/cppdocs/index.html], and > [https://geode.apache.org/releases/latest/dotnetdocs/index.html] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-6816) Geode Native Client user guide: Broken links to API docs
[ https://issues.apache.org/jira/browse/GEODE-6816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17315111#comment-17315111 ] ASF subversion and git services commented on GEODE-6816: Commit 5e0111989d3ddc9dccfacece041c69ac63959f7c in geode-native's branch refs/heads/support/1.14 from Dave Barnes [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=5e01119 ] GEODE-6816: geode-native userguide: fix broken api links (#781) > Geode Native Client user guide: Broken links to API docs > > > Key: GEODE-6816 > URL: https://issues.apache.org/jira/browse/GEODE-6816 > Project: Geode > Issue Type: Bug > Components: docs, native client >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Labels: pull-request-available > Fix For: 1.14.0, 1.15.0 > > > The page "Configuring the Client Cache" > ([https://geode.apache.org/docs/geode-native/19/configuring/config-client-cache.html]) > contains two links to the API docs, one for C++, one for .NET. The links > don't connect. > Fix likely involves two parts: > # Link targets in the page source need to be given a recognizable, > substitutable form, e.g. "cppdocs" should be "/cppdocs". > # The .htaccess file in the `geode-site` repo needs to pick up on this > notation and substitute the correct paths, which are: > [https://geode.apache.org/releases/latest/cppdocs/index.html], and > [https://geode.apache.org/releases/latest/dotnetdocs/index.html] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-9120) CI: ClientServerCacheOperationDUnitTest > largeObjectPutWithReadTimeoutThrowsException FAILED
Nabarun Nag created GEODE-9120:
--
Summary: CI: ClientServerCacheOperationDUnitTest >
largeObjectPutWithReadTimeoutThrowsException FAILED
Key: GEODE-9120
URL: https://issues.apache.org/jira/browse/GEODE-9120
Project: Geode
Issue Type: Bug
Components: membership
Reporter: Nabarun Nag
{noformat}
org.apache.geode.cache30.ClientServerCacheOperationDUnitTest >
largeObjectPutWithReadTimeoutThrowsException FAILED
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.cache30.ClientServerCacheOperationDUnitTest$$Lambda$69/1107577048.run
in VM 2 running on Host b3fa8968947d 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.cache30.ClientServerCacheOperationDUnitTest.largeObjectPutWithReadTimeoutThrowsException(ClientServerCacheOperationDUnitTest.java:118)
Caused by:
org.apache.geode.cache.client.NoAvailableLocatorsException: Unable to
connect to any locators in the list [HostAndPort[b3fa8968947d:34777],
HostAndPort[localhost:34777]]
at
org.apache.geode.cache.client.internal.AutoConnectionSourceImpl.findServer(AutoConnectionSourceImpl.java:174)
at
org.apache.geode.cache.client.internal.ConnectionFactoryImpl.createClientToServerConnection(ConnectionFactoryImpl.java:198)
at
org.apache.geode.cache.client.internal.pooling.ConnectionManagerImpl.createPooledConnection(ConnectionManagerImpl.java:196)
at
org.apache.geode.cache.client.internal.pooling.ConnectionManagerImpl.createPooledConnection(ConnectionManagerImpl.java:190)
at
org.apache.geode.cache.client.internal.pooling.ConnectionManagerImpl.borrowConnection(ConnectionManagerImpl.java:276)
at
org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:129)
at
org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:112)
at
org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:797)
at
org.apache.geode.cache.client.internal.GetOp.execute(GetOp.java:91)
at
org.apache.geode.cache.client.internal.ServerRegionProxy.get(ServerRegionProxy.java:114)
at
org.apache.geode.internal.cache.LocalRegion.findObjectInSystem(LocalRegion.java:2802)
at
org.apache.geode.internal.cache.LocalRegion.getObject(LocalRegion.java:1469)
at
org.apache.geode.internal.cache.LocalRegion.nonTxnFindObject(LocalRegion.java:1442)
at
org.apache.geode.internal.cache.LocalRegionDataView.findObject(LocalRegionDataView.java:197)
at
org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1379)
at
org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1318)
at
org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1303)
at
org.apache.geode.internal.cache.AbstractRegion.get(AbstractRegion.java:439)
at
org.apache.geode.cache30.ClientServerCacheOperationDUnitTest.lambda$largeObjectPutWithReadTimeoutThrowsException$3ab01cf6$2(ClientServerCacheOperationDUnitTest.java:121){noformat}
=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
[*http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0116/test-results/distributedTest/1617652711/*]
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Test report artifacts from this job are available at:
[*http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0116/test-artifacts/1617652711/distributedtestfiles-OpenJDK8-1.15.0-build.0116.tgz*]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-9085) Improve the compatible with redis ERB files
[ https://issues.apache.org/jira/browse/GEODE-9085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-9085: - Labels: (was: blocks-1.14.0) > Improve the compatible with redis ERB files > > > Key: GEODE-9085 > URL: https://issues.apache.org/jira/browse/GEODE-9085 > Project: Geode > Issue Type: Bug > Components: redis >Reporter: Nabarun Nag >Priority: Major > > Ensure that the erb files in the compatible with redis module are in sync > with the README files. This can be done by ensuring that they share a common > text > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-8809) Member Stops Sending Heartbeats, CPU Saturation Cannot Be Proven
[ https://issues.apache.org/jira/browse/GEODE-8809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-8809: - Labels: (was: blocks-1.14.0) > Member Stops Sending Heartbeats, CPU Saturation Cannot Be Proven > > > Key: GEODE-8809 > URL: https://issues.apache.org/jira/browse/GEODE-8809 > Project: Geode > Issue Type: Bug > Components: messaging >Reporter: Nabarun Nag >Assignee: Bill Burcham >Priority: Major > > We see this characteristic failure in a number of proprietary applications: > * member stops sending heartbeats > * The coordinator is requesting availability test from a member, > * member gets it after a delay > * the delay causes the server to be kicked out (receives > FordedDisconnectException) > * operations fail. > * server reconnects. > Usually when the failure detector/health monitor kicks a member out of the > distributed system it is for one of these reasons: > 1. Member really was malfunctioning or unreachable (i.e. something outside of > health monitoring had a problem) > a. Network problems > i. Partition: 2-way, N-way > ii. Slowdown or error rate increase > b. CPU was over-taxed in faulty member. We see gaps on the order of 10s or > more in heartbeat generation on that member. > i. Geode was running in a virtualized environment and the virtualization > system didn’t give the Geode process sufficient CPU > ii. JVM memory was over-utilized so garbage collection (pauses) took too > long > iii. There was simply too much CPU demand and the product failed to > reserve enough CPU capacity to keep the heartbeat going > This ticket captures situations where the failure detector causes a member to > be kicked out *but we cannot prove definitively that any of these as a root > cause*. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8996) Rebalance GFSH commands and restore redundancy commands were not backward compatible
[ https://issues.apache.org/jira/browse/GEODE-8996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17315133#comment-17315133 ] ASF subversion and git services commented on GEODE-8996: Commit d9e1a12c30eb551fa05ae5689441c704e64ccb3f in geode's branch refs/heads/support/1.12 from Nabarun Nag [ https://gitbox.apache.org/repos/asf?p=geode.git;h=d9e1a12 ] GEODE-8996: Fixed rebalance gfsh and REST API in mixed version mode (… (#6257) * GEODE-8996: Fixed rebalance gfsh and REST API in mixed version mode (#6080) * Moved new child RebalanceFunction and CacheRealizationFunction to pre 1.12.0 locations. * While talking to pre-1.12.0 servers, the locators send the function from the old package. * While talking to 1.12.0 server, the new package function is used. * For RebalanceFunction and CacheRealizationFunction the serialVersionUID is set to the one created by 1.11.0 for old package location and serialVersionUID created by 1.12.0 for the latter. * Update GfshCompatibilityTest.java (cherry picked from commit 3faf283c038880755a7356fe570a4f92a46826cd) > Rebalance GFSH commands and restore redundancy commands were not backward > compatible > > > Key: GEODE-8996 > URL: https://issues.apache.org/jira/browse/GEODE-8996 > Project: Geode > Issue Type: Bug > Components: gfsh, rest (admin) >Reporter: Nabarun Nag >Assignee: Nabarun Nag >Priority: Major > Labels: blocks-1.14.0, pull-request-available > Fix For: 1.13.2, 1.14.0, 1.15.0 > > > Issue: > * Rebalance command when executed with 1.12.0+ locator and older servers, > the command failed > * This was because the Rebalance function moved to a new package > * Similar problem with REST calls because of moving CacheRealizationFunction > to a new package > * There was another problem where Serializable classes with UIDs were > changed in couple of releases > * The variation of the UIDs caused deserialization issues when REST commands > were executed from new locators and old servers. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8996) Rebalance GFSH commands and restore redundancy commands were not backward compatible
[ https://issues.apache.org/jira/browse/GEODE-8996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17315132#comment-17315132 ] ASF subversion and git services commented on GEODE-8996: Commit d9e1a12c30eb551fa05ae5689441c704e64ccb3f in geode's branch refs/heads/support/1.12 from Nabarun Nag [ https://gitbox.apache.org/repos/asf?p=geode.git;h=d9e1a12 ] GEODE-8996: Fixed rebalance gfsh and REST API in mixed version mode (… (#6257) * GEODE-8996: Fixed rebalance gfsh and REST API in mixed version mode (#6080) * Moved new child RebalanceFunction and CacheRealizationFunction to pre 1.12.0 locations. * While talking to pre-1.12.0 servers, the locators send the function from the old package. * While talking to 1.12.0 server, the new package function is used. * For RebalanceFunction and CacheRealizationFunction the serialVersionUID is set to the one created by 1.11.0 for old package location and serialVersionUID created by 1.12.0 for the latter. * Update GfshCompatibilityTest.java (cherry picked from commit 3faf283c038880755a7356fe570a4f92a46826cd) > Rebalance GFSH commands and restore redundancy commands were not backward > compatible > > > Key: GEODE-8996 > URL: https://issues.apache.org/jira/browse/GEODE-8996 > Project: Geode > Issue Type: Bug > Components: gfsh, rest (admin) >Reporter: Nabarun Nag >Assignee: Nabarun Nag >Priority: Major > Labels: blocks-1.14.0, pull-request-available > Fix For: 1.13.2, 1.14.0, 1.15.0 > > > Issue: > * Rebalance command when executed with 1.12.0+ locator and older servers, > the command failed > * This was because the Rebalance function moved to a new package > * Similar problem with REST calls because of moving CacheRealizationFunction > to a new package > * There was another problem where Serializable classes with UIDs were > changed in couple of releases > * The variation of the UIDs caused deserialization issues when REST commands > were executed from new locators and old servers. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-8996) Rebalance GFSH commands and restore redundancy commands were not backward compatible
[ https://issues.apache.org/jira/browse/GEODE-8996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nabarun Nag updated GEODE-8996: --- Fix Version/s: 1.12.2 > Rebalance GFSH commands and restore redundancy commands were not backward > compatible > > > Key: GEODE-8996 > URL: https://issues.apache.org/jira/browse/GEODE-8996 > Project: Geode > Issue Type: Bug > Components: gfsh, rest (admin) >Reporter: Nabarun Nag >Assignee: Nabarun Nag >Priority: Major > Labels: blocks-1.14.0, pull-request-available > Fix For: 1.12.2, 1.13.2, 1.14.0, 1.15.0 > > > Issue: > * Rebalance command when executed with 1.12.0+ locator and older servers, > the command failed > * This was because the Rebalance function moved to a new package > * Similar problem with REST calls because of moving CacheRealizationFunction > to a new package > * There was another problem where Serializable classes with UIDs were > changed in couple of releases > * The variation of the UIDs caused deserialization issues when REST commands > were executed from new locators and old servers. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9052) rename geode-redis module
[ https://issues.apache.org/jira/browse/GEODE-9052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17315134#comment-17315134 ] ASF subversion and git services commented on GEODE-9052: Commit 2258e082d38f42b8ba5e8d6766b60ac29ae683fe in geode's branch refs/heads/support/1.14 from Hale Bales [ https://gitbox.apache.org/repos/asf?p=geode.git;h=2258e08 ] GEODE-9052: rename the geode-redis module (#6211) rename the geode-redis module to geode-apis-compatible-with-redis. this is so that this name doesn't end up in a customer-facing location that may cause us to violate Redis's copyright also adds acceptance test dependency on installDist task. Previously there was not an explicit dependency so tests would fail if they happened to start before the installDist task ran (cherry picked from commit f82304bd2a9514ad622b3a1c4b51f1fe62399e3e) > rename geode-redis module > - > > Key: GEODE-9052 > URL: https://issues.apache.org/jira/browse/GEODE-9052 > Project: Geode > Issue Type: New Feature > Components: redis >Affects Versions: 1.14.0 >Reporter: Hale Bales >Assignee: Hale Bales >Priority: Major > Labels: blocks-1.14.0, pull-request-available > Fix For: 1.14.0, 1.15.0 > > > Rename the geode-redis module to geode-apis-compatible-with-redis. This will > change the name of the jar that we distribute, which will help us avoid any > potential copyright issues. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-9052) rename geode-redis module
[ https://issues.apache.org/jira/browse/GEODE-9052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nabarun Nag resolved GEODE-9052. Resolution: Fixed > rename geode-redis module > - > > Key: GEODE-9052 > URL: https://issues.apache.org/jira/browse/GEODE-9052 > Project: Geode > Issue Type: New Feature > Components: redis >Affects Versions: 1.14.0 >Reporter: Hale Bales >Assignee: Hale Bales >Priority: Major > Labels: blocks-1.14.0, pull-request-available > Fix For: 1.14.0, 1.15.0 > > > Rename the geode-redis module to geode-apis-compatible-with-redis. This will > change the name of the jar that we distribute, which will help us avoid any > potential copyright issues. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7845) Rollingupgrade should not conflict with the new ClearPRMessage
[ https://issues.apache.org/jira/browse/GEODE-7845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17315165#comment-17315165 ] ASF subversion and git services commented on GEODE-7845: Commit c1aad2fd774e99f9b3a8507a61e718f59dfc1ba9 in geode's branch refs/heads/feature/GEODE-7665 from mhansonp [ https://gitbox.apache.org/repos/asf?p=geode.git;h=c1aad2f ] GEODE-7845: Adding a cleaner simpler test. (#5622) - Changed the test for ServerVersionMismatchException to be more readable. > Rollingupgrade should not conflict with the new ClearPRMessage > --- > > Key: GEODE-7845 > URL: https://issues.apache.org/jira/browse/GEODE-7845 > Project: Geode > Issue Type: Improvement > Components: core >Reporter: Xiaojian Zhou >Assignee: Mark Hanson >Priority: Major > Labels: GeodeCommons, pull-request-available > Fix For: 1.14.0 > > > PartitionedRegion clear introduced a new ClearPRMessage. In case of doing > rolling upgrade, the user called PR.clear. The new ClearPRMessage should not > fail. It should not be sent to the old members. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7672) Partitioned Region clear will successfully update the OQL indexes
[ https://issues.apache.org/jira/browse/GEODE-7672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17315163#comment-17315163 ] ASF subversion and git services commented on GEODE-7672: Commit 4e0be976d00df25bfdc2ff14084543a5891b6228 in geode's branch refs/heads/feature/GEODE-7665 from Jinmei Liao [ https://gitbox.apache.org/repos/asf?p=geode.git;h=4e0be97 ] GEODE-7672: add dunit test to verify OQL index after PR clear. (#5436) * require rvv lock when create index > Partitioned Region clear will successfully update the OQL indexes > - > > Key: GEODE-7672 > URL: https://issues.apache.org/jira/browse/GEODE-7672 > Project: Geode > Issue Type: Sub-task > Components: regions >Reporter: Nabarun Nag >Assignee: Jianxia Chen >Priority: Major > Labels: GeodeCommons, pull-request-available > > Clear operations are successfully updates the OQL indexes > > Acceptance : > * Passing Dunit tests where OQL queries using indexes return correct results > after the region is cleared > * clear operation and index updates are successful when clear operation is > executed when the puts are occurring which are trying to update the OQL index. > * Unit tests to ensure that index sizes are zero after the region is cleaned > * Test coverage to when a member departs in this scenario > * Test coverage to when a member restarts in this scenario > * Unit tests with complete code coverage for the newly written code. > > analyze if these tests are needed for offheap? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7858) PR.clear notify client should let the queue holder member to notify
[ https://issues.apache.org/jira/browse/GEODE-7858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17315167#comment-17315167 ] ASF subversion and git services commented on GEODE-7858: Commit dbcf865e5d005cda892bd11066ca2ea933919ee6 in geode's branch refs/heads/feature/GEODE-7665 from Jinmei Liao [ https://gitbox.apache.org/repos/asf?p=geode.git;h=dbcf865 ] GEODE-7858: PR.clear notify client should let the queue holder member to notify (#5677) > PR.clear notify client should let the queue holder member to notify > --- > > Key: GEODE-7858 > URL: https://issues.apache.org/jira/browse/GEODE-7858 > Project: Geode > Issue Type: Improvement >Reporter: Xiaojian Zhou >Priority: Major > Labels: GeodeCommons, pull-request-available > > PR.clear needs to notify client at PR level, but the coordinator member maybe > not the HARegionQueue holder. Need to find and let the queue holder member to > notify. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7679) Partitioned Region clear is successful while region is being altered
[ https://issues.apache.org/jira/browse/GEODE-7679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17315168#comment-17315168 ] ASF subversion and git services commented on GEODE-7679: Commit fdefc1a7aca1503fc6b542729f50f0268981caf0 in geode's branch refs/heads/feature/GEODE-7665 from Jianxia Chen [ https://gitbox.apache.org/repos/asf?p=geode.git;h=fdefc1a ] GEODE-7679 Partitioned Region clear is successful while region is being altered (#5516) > Partitioned Region clear is successful while region is being altered > > > Key: GEODE-7679 > URL: https://issues.apache.org/jira/browse/GEODE-7679 > Project: Geode > Issue Type: Sub-task > Components: regions >Reporter: Nabarun Nag >Assignee: Jianxia Chen >Priority: Major > Labels: GeodeCommons, pull-request-available > > Clear operations are successful and while alter region commands are being > executed. > Acceptance : > * DUnit tests validating the above behavior. > * Test coverage to when a member departs in this scenario > * Test coverage to when a member restarts in this scenario > * Unit tests with complete code coverage for the newly written code. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7675) Partitioned Region clear should be successful when clients are present with subscription enabled
[ https://issues.apache.org/jira/browse/GEODE-7675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17315169#comment-17315169 ] ASF subversion and git services commented on GEODE-7675: Commit e3a47f62d7826fc0219d66db745125074834dbb0 in geode's branch refs/heads/feature/GEODE-7665 from Jinmei Liao [ https://gitbox.apache.org/repos/asf?p=geode.git;h=e3a47f6 ] GEODE-7675: Partitioned Region clear should be successful when clients are present with subscription enabled (#5727) > Partitioned Region clear should be successful when clients are present with > subscription enabled > > > Key: GEODE-7675 > URL: https://issues.apache.org/jira/browse/GEODE-7675 > Project: Geode > Issue Type: Sub-task > Components: regions >Reporter: Nabarun Nag >Assignee: Jinmei Liao >Priority: Major > Labels: GeodeCommons, pull-request-available > > Clear operations are successful when Client Subscriptions are enabled and > clients are updated with the correct region clear event. > > Acceptance : > * DUnit tests ensuring that clear operations are successful > * Ensure that all clients are getting the correct event notifications. > * HA enabled tests > * Test coverage to when a member departs in this scenario > * Test coverage to when a member restarts in this scenario > * Unit tests with complete code coverage for the newly written code. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8771) concurrent puts and invalidates will cause PR clear to hang
[
https://issues.apache.org/jira/browse/GEODE-8771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17315170#comment-17315170
]
ASF subversion and git services commented on GEODE-8771:
Commit 4b89c3259e01849e50ed80cbc66fb0c52b48ce6c in geode's branch
refs/heads/feature/GEODE-7665 from Jinmei Liao
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=4b89c32 ]
GEODE-8771: invalidate should acquire the lock before initIndex (#5823)
> concurrent puts and invalidates will cause PR clear to hang
> ---
>
> Key: GEODE-8771
> URL: https://issues.apache.org/jira/browse/GEODE-8771
> Project: Geode
> Issue Type: Sub-task
> Components: core
>Reporter: Jinmei Liao
>Assignee: Jinmei Liao
>Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
> Fix For: 1.14.0
>
>
> On current feature/GEODE-7665 feature branch. The below test will hang:
> {quote}public class PRClearIntegrationTest {
> @Rule
> public ServerStarterRule server = new ServerStarterRule().withAutoStart();
> @Rule
> public ExecutorServiceRule executor = new ExecutorServiceRule();
> @Test
> public void test() throws Exception {
> InternalCache cache = server.getCache();
> Region region = server.createPartitionRegion("regionA",
> f->{}, f->f.setTotalNumBuckets(1));
> cache.getQueryService().createIndex("indexA", "r", "/regionA r");
> region.put(0, "value0");
> CompletableFuture put = executor.runAsync(() ->
> {
> Thread.currentThread().setName("put-Thread");
> IntStream.range(0, 1).forEach(i-> region.invalidate(i, i)); }
> );
> CompletableFuture invalidate = executor.runAsync(() ->
> {
> Thread.currentThread().setName("invalidate-Thread");
> IntStream.range(0, 1).forEach(i-> region.invalidate(0)); }
> );
> CompletableFuture clear = executor.runAsync(() ->
> {
> Thread.currentThread().setName("Clear-Thread");
> region.clear(); }
> );
> put.get();
> clear.get();
> invalidate.get();
> }
> }
> {quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-7845) Rollingupgrade should not conflict with the new ClearPRMessage
[ https://issues.apache.org/jira/browse/GEODE-7845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17315166#comment-17315166 ] ASF subversion and git services commented on GEODE-7845: Commit ab1cdda0848562ef47c015dc670643f9dd6b0aa9 in geode's branch refs/heads/feature/GEODE-7665 from mhansonp [ https://gitbox.apache.org/repos/asf?p=geode.git;h=ab1cdda ] GEODE-7845: Now behaving with clients of various versions. (#5645) - added functionality that would allow the tests to be run using various versions of the clients against and and new versions of the server. > Rollingupgrade should not conflict with the new ClearPRMessage > --- > > Key: GEODE-7845 > URL: https://issues.apache.org/jira/browse/GEODE-7845 > Project: Geode > Issue Type: Improvement > Components: core >Reporter: Xiaojian Zhou >Assignee: Mark Hanson >Priority: Major > Labels: GeodeCommons, pull-request-available > Fix For: 1.14.0 > > > PartitionedRegion clear introduced a new ClearPRMessage. In case of doing > rolling upgrade, the user called PR.clear. The new ClearPRMessage should not > fail. It should not be sent to the old members. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8878) PR clear and create index on secondary member would result in EntryDestroyedException
[ https://issues.apache.org/jira/browse/GEODE-8878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17315171#comment-17315171 ] ASF subversion and git services commented on GEODE-8878: Commit 4831647874be9e71d27e19a85a92b60dc16717fe in geode's branch refs/heads/feature/GEODE-7665 from Jinmei Liao [ https://gitbox.apache.org/repos/asf?p=geode.git;h=4831647 ] GEODE-8878: PR clear should also send a lock message to the secondary members. (#5950) > PR clear and create index on secondary member would result in > EntryDestroyedException > - > > Key: GEODE-8878 > URL: https://issues.apache.org/jira/browse/GEODE-8878 > Project: Geode > Issue Type: Sub-task > Components: regions >Reporter: Jinmei Liao >Assignee: Jinmei Liao >Priority: Major > Labels: GeodeOperationAPI, pull-request-available > > When doing a PR clear, a lock message should be sent to all the other members > to request lock to prevent "create index" operation from happening at the > same time on secondary server. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7845) Rollingupgrade should not conflict with the new ClearPRMessage
[ https://issues.apache.org/jira/browse/GEODE-7845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17315164#comment-17315164 ] ASF subversion and git services commented on GEODE-7845: Commit 7211ba44f802d94d9f5e6bccae09a0eab65bfe28 in geode's branch refs/heads/feature/GEODE-7665 from mhansonp [ https://gitbox.apache.org/repos/asf?p=geode.git;h=7211ba4 ] GEODE-7845 blocking PR region clear if one or more server versions are too old (#5577) - if a server is running an old version when a PR clear is invoked by the client, the client will receive a ServerOperationException with a cause of ServerVersionMismatchException. > Rollingupgrade should not conflict with the new ClearPRMessage > --- > > Key: GEODE-7845 > URL: https://issues.apache.org/jira/browse/GEODE-7845 > Project: Geode > Issue Type: Improvement > Components: core >Reporter: Xiaojian Zhou >Assignee: Mark Hanson >Priority: Major > Labels: GeodeCommons, pull-request-available > Fix For: 1.14.0 > > > PartitionedRegion clear introduced a new ClearPRMessage. In case of doing > rolling upgrade, the user called PR.clear. The new ClearPRMessage should not > fail. It should not be sent to the old members. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-9115) CI failure: org.apache.geode.redis.internal.executor.pubsub.LettucePubSubIntegrationTest > quitWhileSubscribe FAILED
[ https://issues.apache.org/jira/browse/GEODE-9115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jens Deppe resolved GEODE-9115. --- Fix Version/s: 1.15.0 Resolution: Fixed > CI failure: > org.apache.geode.redis.internal.executor.pubsub.LettucePubSubIntegrationTest > > quitWhileSubscribe FAILED > > > Key: GEODE-9115 > URL: https://issues.apache.org/jira/browse/GEODE-9115 > Project: Geode > Issue Type: Bug > Components: redis >Affects Versions: 1.15.0 >Reporter: Ray Ingles >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > See > https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/IntegrationTestOpenJDK8/builds/119 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9115) CI failure: org.apache.geode.redis.internal.executor.pubsub.LettucePubSubIntegrationTest > quitWhileSubscribe FAILED
[ https://issues.apache.org/jira/browse/GEODE-9115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17315177#comment-17315177 ] ASF subversion and git services commented on GEODE-9115: Commit b98079decb246e50ce39a4a0e602acc38d5c9899 in geode's branch refs/heads/develop from Jens Deppe [ https://gitbox.apache.org/repos/asf?p=geode.git;h=b98079d ] GEODE-9115: Do not have lettuce redis client autoreconnect (#6265) - Even when we explicitly quit a connection, lettuce seems to want to reconnect which causes intermittent test failures. > CI failure: > org.apache.geode.redis.internal.executor.pubsub.LettucePubSubIntegrationTest > > quitWhileSubscribe FAILED > > > Key: GEODE-9115 > URL: https://issues.apache.org/jira/browse/GEODE-9115 > Project: Geode > Issue Type: Bug > Components: redis >Affects Versions: 1.15.0 >Reporter: Ray Ingles >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > See > https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/IntegrationTestOpenJDK8/builds/119 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-8692) ArrayIndexOutOfBoundsException may be thrown in RegionAdvisor.processProfilesQueuedDuringInitialization
[
https://issues.apache.org/jira/browse/GEODE-8692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen Nichols updated GEODE-8692:
Fix Version/s: 1.13.3
1.12.2
> ArrayIndexOutOfBoundsException may be thrown in
> RegionAdvisor.processProfilesQueuedDuringInitialization
> ---
>
> Key: GEODE-8692
> URL: https://issues.apache.org/jira/browse/GEODE-8692
> Project: Geode
> Issue Type: Bug
>Reporter: Sarah Abbey
>Assignee: Sarah Abbey
>Priority: Minor
> Labels: pull-request-available
> Fix For: 1.12.2, 1.13.3, 1.14.0
>
>
> If {{RegionAdvisor.buckets == null}} at the time the value of {{serials}} is
> generated, an {{ArrayIndexOutOfBoundsException}} may be thrown in
> {{RegionAdvisor.processProfilesQueuedDuringInitialization}} if buckets have
> been initialized at that point.
> Code where {{ArrayIndexOutOfBoundsException}} might be thrown in
> {{RegionAdvisor.processProfilesQueuedDuringInitialization():}}
> {code:java}
> for (int i = 0; i < buckets.length; i++) {
> BucketAdvisor ba = buckets[i].getBucketAdvisor();
> int serial = qbp.serials[i]; <<< Exception thrown here
> if (serial != ILLEGAL_SERIAL) {
> ba.removeIdWithSerial(qbp.memberId, serial, qbp.destroyed);
> }
> }
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-8692) ArrayIndexOutOfBoundsException may be thrown in RegionAdvisor.processProfilesQueuedDuringInitialization
[
https://issues.apache.org/jira/browse/GEODE-8692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17315189#comment-17315189
]
ASF subversion and git services commented on GEODE-8692:
Commit f996d93f263d60cd3d92b5501a71fef2a4ab6c1c in geode's branch
refs/heads/support/1.13 from Sarah
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=f996d93 ]
GEODE-8692: ArrayIndexOutOfBoundsException may be thrown in
RegionAdvisor.processProfilesQueuedDuringInitialization (#5722) (#6262)
(cherry picked from commit c99087aeb19abfb5bbd57036349870a6d784df1a)
> ArrayIndexOutOfBoundsException may be thrown in
> RegionAdvisor.processProfilesQueuedDuringInitialization
> ---
>
> Key: GEODE-8692
> URL: https://issues.apache.org/jira/browse/GEODE-8692
> Project: Geode
> Issue Type: Bug
>Reporter: Sarah Abbey
>Assignee: Sarah Abbey
>Priority: Minor
> Labels: pull-request-available
> Fix For: 1.12.2, 1.13.3, 1.14.0
>
>
> If {{RegionAdvisor.buckets == null}} at the time the value of {{serials}} is
> generated, an {{ArrayIndexOutOfBoundsException}} may be thrown in
> {{RegionAdvisor.processProfilesQueuedDuringInitialization}} if buckets have
> been initialized at that point.
> Code where {{ArrayIndexOutOfBoundsException}} might be thrown in
> {{RegionAdvisor.processProfilesQueuedDuringInitialization():}}
> {code:java}
> for (int i = 0; i < buckets.length; i++) {
> BucketAdvisor ba = buckets[i].getBucketAdvisor();
> int serial = qbp.serials[i]; <<< Exception thrown here
> if (serial != ILLEGAL_SERIAL) {
> ba.removeIdWithSerial(qbp.memberId, serial, qbp.destroyed);
> }
> }
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-8692) ArrayIndexOutOfBoundsException may be thrown in RegionAdvisor.processProfilesQueuedDuringInitialization
[
https://issues.apache.org/jira/browse/GEODE-8692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17315190#comment-17315190
]
ASF subversion and git services commented on GEODE-8692:
Commit 8c69843cba5c5a72cc9f0b86affb3cb18a265621 in geode's branch
refs/heads/support/1.12 from Sarah
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=8c69843 ]
GEODE-8692: ArrayIndexOutOfBoundsException may be thrown in
RegionAdvisor.processProfilesQueuedDuringInitialization (#6263)
(cherry picked from commit c99087aeb19abfb5bbd57036349870a6d784df1a)
> ArrayIndexOutOfBoundsException may be thrown in
> RegionAdvisor.processProfilesQueuedDuringInitialization
> ---
>
> Key: GEODE-8692
> URL: https://issues.apache.org/jira/browse/GEODE-8692
> Project: Geode
> Issue Type: Bug
>Reporter: Sarah Abbey
>Assignee: Sarah Abbey
>Priority: Minor
> Labels: pull-request-available
> Fix For: 1.12.2, 1.13.3, 1.14.0
>
>
> If {{RegionAdvisor.buckets == null}} at the time the value of {{serials}} is
> generated, an {{ArrayIndexOutOfBoundsException}} may be thrown in
> {{RegionAdvisor.processProfilesQueuedDuringInitialization}} if buckets have
> been initialized at that point.
> Code where {{ArrayIndexOutOfBoundsException}} might be thrown in
> {{RegionAdvisor.processProfilesQueuedDuringInitialization():}}
> {code:java}
> for (int i = 0; i < buckets.length; i++) {
> BucketAdvisor ba = buckets[i].getBucketAdvisor();
> int serial = qbp.serials[i]; <<< Exception thrown here
> if (serial != ILLEGAL_SERIAL) {
> ba.removeIdWithSerial(qbp.memberId, serial, qbp.destroyed);
> }
> }
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-8859) Redis data structures may not accurately reflect their size in Geode stats
[
https://issues.apache.org/jira/browse/GEODE-8859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17315192#comment-17315192
]
ASF subversion and git services commented on GEODE-8859:
Commit e38d710f86f73360e36415ef5e28889be07036b2 in geode's branch
refs/heads/support/1.14 from Nabarun Nag
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=e38d710 ]
Revert "GEODE-8859: Fix redis-compatability data structure bucket memory-usage
reporting (#6084)" (#6260) (#6269)
This reverts commit e927bdf42b64eac96758642fcd22c8a144a3890e.
(cherry picked from commit 7a85b4df1b80518e7b3d1ff405d0f76ca45fa785)
> Redis data structures may not accurately reflect their size in Geode stats
> --
>
> Key: GEODE-8859
> URL: https://issues.apache.org/jira/browse/GEODE-8859
> Project: Geode
> Issue Type: Bug
> Components: redis, statistics
>Affects Versions: 1.14.0
>Reporter: Jens Deppe
>Assignee: John Hutchison
>Priority: Major
> Labels: blocks-1.14.0, pull-request-available, release-blocker
> Fix For: 1.14.0, 1.15.0
>
>
> Here is a comment from Darrel regarding this issue. For some background, the
> Redis structures implement {{Delta}}.
>
> {quote}I was playing around with RedisInsight and was able to get most the
> the overview dashboard and the data browser working with geode redis. But I
> found a problem with how we are using geode that causes the geode stats that
> track how much data is stored in a partitioned region to be wrong and the
> bucket sizes used for rebalancing are also wrong. Basically when we do create
> ops on the region the stats track it okay. But when we do updates then geode
> always thinks that nothing (size wise) changed. So for example I created a
> string by doing a redis “set” command. I saw the size of the string accounted
> for in dataStoreBytesInUse. But then I kept doing redis “append” commands on
> that key and the dataStoreBytesInUse did not change at all. I think the
> problem is in how we are updating the data structure in place instead of
> getting a copy, modifying it, and then putting the copy into the region.
> Avoiding this copy gives us MUCH better performance but it messes up geode
> when it is trying to calculate the memory increase or decrease. It is
> possible that this is only an issue on the primary and that the secondary
> sizing may be correct. If so that could lead to other problems because for a
> given bucket our primary size would be different than the secondary. The
> bucket sizes are used when you do a rebalance but basically we can have a
> bunch of memory that is “untracked” so we might see the JVM heaps unbalanced
> but geode will think the buckets are balanced. I’m not sure what we should do
> about this.
> {quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-9119) Move test file missed as part of module renaming
[ https://issues.apache.org/jira/browse/GEODE-9119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nabarun Nag updated GEODE-9119: --- Fix Version/s: 1.14.0 > Move test file missed as part of module renaming > > > Key: GEODE-9119 > URL: https://issues.apache.org/jira/browse/GEODE-9119 > Project: Geode > Issue Type: Test > Components: redis >Reporter: Jens Deppe >Priority: Major > Labels: blocks-1.14.0, pull-request-available > Fix For: 1.14.0, 1.15.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9119) Move test file missed as part of module renaming
[ https://issues.apache.org/jira/browse/GEODE-9119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17315193#comment-17315193 ] ASF subversion and git services commented on GEODE-9119: Commit 1eae94c9710e307504cb812d8a601b4e96e54309 in geode's branch refs/heads/support/1.14 from Jens Deppe [ https://gitbox.apache.org/repos/asf?p=geode.git;h=1eae94c ] GEODE-9119: Move file missed during module renaming (#6258) (cherry picked from commit 9570f4ec2663646ea51a48d217ae9db1f423c865) > Move test file missed as part of module renaming > > > Key: GEODE-9119 > URL: https://issues.apache.org/jira/browse/GEODE-9119 > Project: Geode > Issue Type: Test > Components: redis >Reporter: Jens Deppe >Priority: Major > Labels: blocks-1.14.0, pull-request-available > Fix For: 1.14.0, 1.15.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9029) Initial stub support Redis SLOWLOG command
[ https://issues.apache.org/jira/browse/GEODE-9029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nabarun Nag updated GEODE-9029: --- Fix Version/s: 1.15.0 > Initial stub support Redis SLOWLOG command > -- > > Key: GEODE-9029 > URL: https://issues.apache.org/jira/browse/GEODE-9029 > Project: Geode > Issue Type: New Feature > Components: redis >Affects Versions: 1.15.0 >Reporter: Ray Ingles >Assignee: Ray Ingles >Priority: Major > Labels: blocks-1.14.0 > Fix For: 1.14.0, 1.15.0 > > > This is used by Redis monitoring tools (e.g. Datadog). A stub implementation > is sufficient; the current implementation will be moved to the Supported > category. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9029) Initial stub support Redis SLOWLOG command
[ https://issues.apache.org/jira/browse/GEODE-9029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nabarun Nag updated GEODE-9029: --- Fix Version/s: 1.14.0 > Initial stub support Redis SLOWLOG command > -- > > Key: GEODE-9029 > URL: https://issues.apache.org/jira/browse/GEODE-9029 > Project: Geode > Issue Type: New Feature > Components: redis >Affects Versions: 1.15.0 >Reporter: Ray Ingles >Assignee: Ray Ingles >Priority: Major > Labels: blocks-1.14.0 > Fix For: 1.14.0 > > > This is used by Redis monitoring tools (e.g. Datadog). A stub implementation > is sufficient; the current implementation will be moved to the Supported > category. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9120) CI: ClientServerCacheOperationDUnitTest > largeObjectPutWithReadTimeoutThrowsException FAILED
[
https://issues.apache.org/jira/browse/GEODE-9120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17315194#comment-17315194
]
Geode Integration commented on GEODE-9120:
--
Seen in [DistributedTestOpenJDK8
#131.1|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/131.1]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0116/test-results/distributedTest/1617652711/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0116/test-artifacts/1617652711/distributedtestfiles-OpenJDK8-1.15.0-build.0116.tgz].
> CI: ClientServerCacheOperationDUnitTest >
> largeObjectPutWithReadTimeoutThrowsException FAILED
> -
>
> Key: GEODE-9120
> URL: https://issues.apache.org/jira/browse/GEODE-9120
> Project: Geode
> Issue Type: Bug
> Components: membership
>Reporter: Nabarun Nag
>Priority: Major
>
>
> {noformat}
> org.apache.geode.cache30.ClientServerCacheOperationDUnitTest >
> largeObjectPutWithReadTimeoutThrowsException FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache30.ClientServerCacheOperationDUnitTest$$Lambda$69/1107577048.run
> in VM 2 running on Host b3fa8968947d 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.cache30.ClientServerCacheOperationDUnitTest.largeObjectPutWithReadTimeoutThrowsException(ClientServerCacheOperationDUnitTest.java:118)
> Caused by:
> org.apache.geode.cache.client.NoAvailableLocatorsException: Unable to
> connect to any locators in the list [HostAndPort[b3fa8968947d:34777],
> HostAndPort[localhost:34777]]
> at
> org.apache.geode.cache.client.internal.AutoConnectionSourceImpl.findServer(AutoConnectionSourceImpl.java:174)
> at
> org.apache.geode.cache.client.internal.ConnectionFactoryImpl.createClientToServerConnection(ConnectionFactoryImpl.java:198)
> at
> org.apache.geode.cache.client.internal.pooling.ConnectionManagerImpl.createPooledConnection(ConnectionManagerImpl.java:196)
> at
> org.apache.geode.cache.client.internal.pooling.ConnectionManagerImpl.createPooledConnection(ConnectionManagerImpl.java:190)
> at
> org.apache.geode.cache.client.internal.pooling.ConnectionManagerImpl.borrowConnection(ConnectionManagerImpl.java:276)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:129)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:112)
> at
> org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:797)
> at
> org.apache.geode.cache.client.internal.GetOp.execute(GetOp.java:91)
> at
> org.apache.geode.cache.client.internal.ServerRegionProxy.get(ServerRegionProxy.java:114)
> at
> org.apache.geode.internal.cache.LocalRegion.findObjectInSystem(LocalRegion.java:2802)
> at
> org.apache.geode.internal.cache.LocalRegion.getObject(LocalRegion.java:1469)
> at
> org.apache.geode.internal.cache.LocalRegion.nonTxnFindObject(LocalRegion.java:1442)
> at
> org.apache.geode.internal.cache.LocalRegionDataView.findObject(LocalRegionDataView.java:197)
> at
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1379)
> at
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1318)
> at
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1303)
> at
> org.apache.geode.internal.cache.AbstractRegion.get(AbstractRegion.java:439)
> at
> org.apache.geode.cache30.ClientServerCacheOperationDUnitTest.lambda$largeObjectPutWithReadTimeoutThrowsException$3ab01cf6$2(ClientServerCacheOperationDUnitTest.java:121){noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> [*http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0116/test-results/distributedTest/1617652711/*]
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> [*http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0116/test-artifacts/1617652711/distributedtestfiles-OpenJDK8-1.15.0-build.0116.tgz*]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-8990) CI Failure: Jetty9CachingClientServerTest.shouldCacheSessionOnClient
[
https://issues.apache.org/jira/browse/GEODE-8990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17315195#comment-17315195
]
Geode Integration commented on GEODE-8990:
--
Seen in [DistributedTestOpenJDK8
#132.1|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/132.1]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0117/test-results/distributedTest/1617660921/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0117/test-artifacts/1617660921/distributedtestfiles-OpenJDK8-1.15.0-build.0117.tgz].
> CI Failure: Jetty9CachingClientServerTest.shouldCacheSessionOnClient
>
>
> Key: GEODE-8990
> URL: https://issues.apache.org/jira/browse/GEODE-8990
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Assignee: Mark Hanson
>Priority: Major
> Labels: pull-request-available
>
> {noformat}
> org.apache.geode.session.tests.Jetty9CachingClientServerTest >
> shouldCacheSessionOnClient FAILED
> org.junit.ComparisonFailure: expected:<[Foo]> but was:<[bogus]>
> at org.junit.Assert.assertEquals(Assert.java:117)
> at org.junit.Assert.assertEquals(Assert.java:146)
> at
> org.apache.geode.session.tests.Jetty9CachingClientServerTest.shouldCacheSessionOnClient(Jetty9CachingClientServerTest.java:65)
> 371 tests completed, 1 failed
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0023/test-results/distributedTest/1614646829/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0023/test-artifacts/1614646829/distributedtestfiles-OpenJDK8-1.15.0-build.0023.tgz
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-8859) Redis data structures may not accurately reflect their size in Geode stats
[
https://issues.apache.org/jira/browse/GEODE-8859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nabarun Nag updated GEODE-8859:
---
Fix Version/s: (was: 1.15.0)
(was: 1.14.0)
> Redis data structures may not accurately reflect their size in Geode stats
> --
>
> Key: GEODE-8859
> URL: https://issues.apache.org/jira/browse/GEODE-8859
> Project: Geode
> Issue Type: Bug
> Components: redis, statistics
>Affects Versions: 1.14.0
>Reporter: Jens Deppe
>Assignee: John Hutchison
>Priority: Major
> Labels: blocks-1.14.0, pull-request-available, release-blocker
>
> Here is a comment from Darrel regarding this issue. For some background, the
> Redis structures implement {{Delta}}.
>
> {quote}I was playing around with RedisInsight and was able to get most the
> the overview dashboard and the data browser working with geode redis. But I
> found a problem with how we are using geode that causes the geode stats that
> track how much data is stored in a partitioned region to be wrong and the
> bucket sizes used for rebalancing are also wrong. Basically when we do create
> ops on the region the stats track it okay. But when we do updates then geode
> always thinks that nothing (size wise) changed. So for example I created a
> string by doing a redis “set” command. I saw the size of the string accounted
> for in dataStoreBytesInUse. But then I kept doing redis “append” commands on
> that key and the dataStoreBytesInUse did not change at all. I think the
> problem is in how we are updating the data structure in place instead of
> getting a copy, modifying it, and then putting the copy into the region.
> Avoiding this copy gives us MUCH better performance but it messes up geode
> when it is trying to calculate the memory increase or decrease. It is
> possible that this is only an issue on the primary and that the secondary
> sizing may be correct. If so that could lead to other problems because for a
> given bucket our primary size would be different than the secondary. The
> bucket sizes are used when you do a rebalance but basically we can have a
> bunch of memory that is “untracked” so we might see the JVM heaps unbalanced
> but geode will think the buckets are balanced. I’m not sure what we should do
> about this.
> {quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-9084) Remove Redis GFSH command
[ https://issues.apache.org/jira/browse/GEODE-9084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-9084: -- Labels: blocks-1.14.0 pull-request-available (was: blocks-1.14.0) > Remove Redis GFSH command > - > > Key: GEODE-9084 > URL: https://issues.apache.org/jira/browse/GEODE-9084 > Project: Geode > Issue Type: Bug > Components: redis >Reporter: Nabarun Nag >Assignee: Nabarun Nag >Priority: Major > Labels: blocks-1.14.0, pull-request-available > > Things have changed since we first introduced the concept of Unsupported vs > Unimplemented. > _Original Idea:_ Allow users to use the unsupported commands, log which one's > were being used. Use this information to help drive future iterations. > Given: > * new direction of the product (Tanzu Cache) > * Safety for customers not to get into a bad situation > * Confusion for support, our team, the field > We should remove the ability to use the unsupported commands unless the > system property 'enable-unsupported-commands' is set. > > End result: > * The 'redis' gfsh command is no longer present > * Remove the documentation -- This message was sent by Atlassian Jira (v8.3.4#803005)
