[jira] [Commented] (GEODE-8395) gfsh --help shows incorrect product name
[ https://issues.apache.org/jira/browse/GEODE-8395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170141#comment-17170141 ] ASF subversion and git services commented on GEODE-8395: Commit 7b1646ecc581165eed794a8a15ee04d16484027e in geode's branch refs/heads/support/1.13 from Owen Nichols [ https://gitbox.apache.org/repos/asf?p=geode.git;h=7b1646e ] GEODE-8395: fix product name in gfsh help banner (#5417) (cherry picked from commit 54421c4cd5ddde9e459f544fef9f27b44fa1ab6c) > gfsh --help shows incorrect product name > > > Key: GEODE-8395 > URL: https://issues.apache.org/jira/browse/GEODE-8395 > Project: Geode > Issue Type: Bug > Components: gfsh >Reporter: Owen Nichols >Priority: Major > Labels: pull-request-available > Fix For: 1.14.0 > > > Expected: > gfsh --help > Apache Geode v1.14.0 Command Line Shell > Actual: > gfsh --help > Pivotal GemFire(R) v1.14.0 Command Line Shell > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-6564) Clearing a replicated region with expiration causes a memory leak
[
https://issues.apache.org/jira/browse/GEODE-6564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170157#comment-17170157
]
ASF GitHub Bot commented on GEODE-6564:
---
dschneider-pivotal opened a new pull request #5419:
URL: https://github.com/apache/geode/pull/5419
Thank you for submitting a contribution to Apache Geode.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
### For all changes:
- [ ] Is there a JIRA ticket associated with this PR? Is it referenced in
the commit message?
- [ ] Has your PR been rebased against the latest commit within the target
branch (typically `develop`)?
- [ ] Is your initial contribution a single, squashed commit?
- [ ] Does `gradlew build` run cleanly?
- [ ] Have you written or updated unit tests to verify your changes?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
### Note:
Please ensure that once the PR is submitted, check Concourse for build
issues and
submit an update to your PR as soon as possible. If you need help, please
send an
email to d...@geode.apache.org.
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
> Clearing a replicated region with expiration causes a memory leak
> -
>
> Key: GEODE-6564
> URL: https://issues.apache.org/jira/browse/GEODE-6564
> Project: Geode
> Issue Type: Bug
> Components: regions
>Reporter: Barrett Oglesby
>Priority: Major
>
> Clearing a replicated region with expiration causes a memory leak
> Both the RegionEntries and EntryExpiryTasks are still live after loading
> entries into the region and then clearing it.
> Server Startup:
> {noformat}
> num #instances #bytes class name
> --
> 1: 29856 2797840 [C
> 4: 2038 520600 [B
> Total 187711 10089624
> {noformat}
> Load 100 entries with 600k payload (representing a session):
> {noformat}
> num #instances #bytes class name
> --
> 1: 2496 60666440 [B
> 2: 30157 2828496 [C
> 73: 100 7200
> org.apache.geode.internal.cache.entries.VersionedStatsRegionEntryHeapStringKey1
> 93: 100 4800 org.apache.geode.internal.cache.EntryExpiryTask
> Total 190737 70240472
> {noformat}
> Clear region:
> {noformat}
> num #instances #bytes class name
> --
> 1: 2398 60505944 [B
> 2: 30448 2849456 [C
> 74: 100 7200
> org.apache.geode.internal.cache.entries.VersionedStatsRegionEntryHeapStringKey1
> 100: 100 4800 org.apache.geode.internal.cache.EntryExpiryTask
> Total 192199 70373048
> {noformat}
> Load and clear another 100 entries:
> {noformat}
> num #instances #bytes class name
> --
> 1: 2503 120511688 [B
> 2: 30506 2854384 [C
> 46: 200 14400
> org.apache.geode.internal.cache.entries.VersionedStatsRegionEntryHeapStringKey1
> 61: 200 9600 org.apache.geode.internal.cache.EntryExpiryTask
> Total 193272 130421432
> {noformat}
> Load and clear another 100 entries:
> {noformat}
> num #instances #bytes class name
> --
> 1: 2600 180517240 [B
> 2: 30562 2859584 [C
> 33: 300 21600
> org.apache.geode.internal.cache.entries.VersionedStatsRegionEntryHeapStringKey1
> 47: 300 14400 org.apache.geode.internal.cache.EntryExpiryTask
> Total 194310 190468176
> {noformat}
> A heap dump shows the VersionedStatsRegionEntryHeapStringKey1 instances are
> referenced by the DistributedRegion entryExpiryTasks:
> {noformat}
> --> org.apache.geode.internal.cache.DistributedRegion@0x76adbbb88 (816 bytes)
> (field entryExpiryTasks:)
> --> java.util.concurrent.ConcurrentHashMap@0x76adbc028 (100 bytes) (field
> table:)
> --> [Ljava.util.concurrent.ConcurrentHashMap$Node;@0x76ee85358 (4112 bytes)
> (Element 276 of [Ljava.util.concurrent.ConcurrentHashMap$Node;@0x76ee85358:)
> --> java.util.concurrent.ConcurrentHashMap$Node@0x76edc4e20 (44 bytes) (field
> next:)
> --> java.util.concurrent.ConcurrentHashMap$Node@0x76edc32f0 (44 bytes) (field
> key:)
> -->
> org.apache.geode.internal.cache.entries.VersionedStatsRegionEntryHeapStringKey1@0x76edc3210
> (86 bytes)
> {noformat}
> LocalRegion.cancelAllEntryExpiryTasks is called when the region is cleared:
> {noformat}
> java.lang.Exception: Stack trace
> at
[jira] [Updated] (GEODE-6564) Clearing a replicated region with expiration causes a memory leak
[
https://issues.apache.org/jira/browse/GEODE-6564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-6564:
--
Labels: pull-request-available (was: )
> Clearing a replicated region with expiration causes a memory leak
> -
>
> Key: GEODE-6564
> URL: https://issues.apache.org/jira/browse/GEODE-6564
> Project: Geode
> Issue Type: Bug
> Components: regions
>Reporter: Barrett Oglesby
>Priority: Major
> Labels: pull-request-available
>
> Clearing a replicated region with expiration causes a memory leak
> Both the RegionEntries and EntryExpiryTasks are still live after loading
> entries into the region and then clearing it.
> Server Startup:
> {noformat}
> num #instances #bytes class name
> --
> 1: 29856 2797840 [C
> 4: 2038 520600 [B
> Total 187711 10089624
> {noformat}
> Load 100 entries with 600k payload (representing a session):
> {noformat}
> num #instances #bytes class name
> --
> 1: 2496 60666440 [B
> 2: 30157 2828496 [C
> 73: 100 7200
> org.apache.geode.internal.cache.entries.VersionedStatsRegionEntryHeapStringKey1
> 93: 100 4800 org.apache.geode.internal.cache.EntryExpiryTask
> Total 190737 70240472
> {noformat}
> Clear region:
> {noformat}
> num #instances #bytes class name
> --
> 1: 2398 60505944 [B
> 2: 30448 2849456 [C
> 74: 100 7200
> org.apache.geode.internal.cache.entries.VersionedStatsRegionEntryHeapStringKey1
> 100: 100 4800 org.apache.geode.internal.cache.EntryExpiryTask
> Total 192199 70373048
> {noformat}
> Load and clear another 100 entries:
> {noformat}
> num #instances #bytes class name
> --
> 1: 2503 120511688 [B
> 2: 30506 2854384 [C
> 46: 200 14400
> org.apache.geode.internal.cache.entries.VersionedStatsRegionEntryHeapStringKey1
> 61: 200 9600 org.apache.geode.internal.cache.EntryExpiryTask
> Total 193272 130421432
> {noformat}
> Load and clear another 100 entries:
> {noformat}
> num #instances #bytes class name
> --
> 1: 2600 180517240 [B
> 2: 30562 2859584 [C
> 33: 300 21600
> org.apache.geode.internal.cache.entries.VersionedStatsRegionEntryHeapStringKey1
> 47: 300 14400 org.apache.geode.internal.cache.EntryExpiryTask
> Total 194310 190468176
> {noformat}
> A heap dump shows the VersionedStatsRegionEntryHeapStringKey1 instances are
> referenced by the DistributedRegion entryExpiryTasks:
> {noformat}
> --> org.apache.geode.internal.cache.DistributedRegion@0x76adbbb88 (816 bytes)
> (field entryExpiryTasks:)
> --> java.util.concurrent.ConcurrentHashMap@0x76adbc028 (100 bytes) (field
> table:)
> --> [Ljava.util.concurrent.ConcurrentHashMap$Node;@0x76ee85358 (4112 bytes)
> (Element 276 of [Ljava.util.concurrent.ConcurrentHashMap$Node;@0x76ee85358:)
> --> java.util.concurrent.ConcurrentHashMap$Node@0x76edc4e20 (44 bytes) (field
> next:)
> --> java.util.concurrent.ConcurrentHashMap$Node@0x76edc32f0 (44 bytes) (field
> key:)
> -->
> org.apache.geode.internal.cache.entries.VersionedStatsRegionEntryHeapStringKey1@0x76edc3210
> (86 bytes)
> {noformat}
> LocalRegion.cancelAllEntryExpiryTasks is called when the region is cleared:
> {noformat}
> java.lang.Exception: Stack trace
> at java.lang.Thread.dumpStack(Thread.java:1333)
> at
> org.apache.geode.internal.cache.LocalRegion.cancelAllEntryExpiryTasks(LocalRegion.java:8202)
> at
> org.apache.geode.internal.cache.LocalRegion.clearRegionLocally(LocalRegion.java:9094)
> at
> org.apache.geode.internal.cache.DistributedRegion.cmnClearRegion(DistributedRegion.java:1962)
> at
> org.apache.geode.internal.cache.LocalRegion.basicClear(LocalRegion.java:8998)
> at
> org.apache.geode.internal.cache.DistributedRegion.basicClear(DistributedRegion.java:1939)
> at
> org.apache.geode.internal.cache.LocalRegion.basicBridgeClear(LocalRegion.java:8988)
> at
> org.apache.geode.internal.cache.tier.sockets.command.ClearRegion.cmdExecute(ClearRegion.java:123)
> {noformat}
> But it doesn't clear the entryExpiryTasks map:
> {noformat}
> LocalRegion.clearRegionLocally before cancelAllEntryExpiryTasks
> entryExpiryTasks=100
> LocalRegion.clearRegionLocally after cancelAllEntryExpiryTasks
> entryExpiryTasks=100
> {noformat}
> As a test, I added this call to the bottom of the cancelAllEntryExpiryTasks
> method:
> {noformat}
> this.entryExpiryTasks.clear();
> {noformat}
> This addressed the leak:
> {noformat}
> Server Startup: Total 182414 9855616
> Load/Clear 1: Total 191049 10315832
> Load/Clear 2: Total 191978 10329664
> Load/Clear 3: Total 192638 10360360
> {noformat}
> As a work-around, a Function that clears the region by using removeAll on
>
[jira] [Commented] (GEODE-8386) SRANDMEMBER with negative count should return that many members
[
https://issues.apache.org/jira/browse/GEODE-8386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170254#comment-17170254
]
ASF subversion and git services commented on GEODE-8386:
Commit 42c086b6578b6f0f768a3ff9ead627fbe70abf22 in geode's branch
refs/heads/feature/GEODE-7665 from Darrel Schneider
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=42c086b ]
GEODE-8386: fix SRANDMEMBER with negative count (#5404)
> SRANDMEMBER with negative count should return that many members
> ---
>
> Key: GEODE-8386
> URL: https://issues.apache.org/jira/browse/GEODE-8386
> Project: Geode
> Issue Type: Bug
> Components: redis
>Reporter: Darrel Schneider
>Assignee: Darrel Schneider
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.14.0
>
>
> When SRANDMEMBER is sent a negative count, it should return a number of items
> equal to the absolute value. uniqueness is not guaranteed.
>
> {{SADD abc 123 456
> SRANDMEMBER abc -1 -> 123
> SRANDMEMBER abc -2 -> 123, 123 OR 123, 456, 456, 123 OR 456, 456
> SRANDMEMBER abc -5 -> 123,123,456,123,456 OR any one of the 2^5
> combinations...}}
> see the redis unit tests and docs: unit/type/set -> SRANDMEMBER with
> - hashtable
> and documentation: [https://redis.io/commands/srandmember]
> Currently, Geode Redis returns only up to as many members as there are in the
> set.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-8333) Fix PUBSUB hang
[ https://issues.apache.org/jira/browse/GEODE-8333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170250#comment-17170250 ] ASF subversion and git services commented on GEODE-8333: Commit 95bba9a7af10e2bd02febbc7c35bb2f16bb9e414 in geode's branch refs/heads/feature/GEODE-7665 from Darrel Schneider [ https://gitbox.apache.org/repos/asf?p=geode.git;h=95bba9a ] Revert "GEODE-8333: Fix PUBSUB hang (#5349)" (#5415) This reverts commit 067194e8f82414b6103c4335beb6567947edcfbc. The fix for GEODE-8333 had a bug in which responses to the client could be out of order. > Fix PUBSUB hang > --- > > Key: GEODE-8333 > URL: https://issues.apache.org/jira/browse/GEODE-8333 > Project: Geode > Issue Type: Bug > Components: redis >Reporter: Sarah Abbey >Assignee: Darrel Schneider >Priority: Major > Labels: pull-request-available > Fix For: 1.14.0 > > > PUBSUB hangs with concurrent publishers and subscribers on multiple servers. > The initial fix is being reverted because it caused a bug in which responses > to clients could now be out of order. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8391) Skip AvailablePort test assertion if host machine does not support it
[
https://issues.apache.org/jira/browse/GEODE-8391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170252#comment-17170252
]
ASF subversion and git services commented on GEODE-8391:
Commit 76573ce5b52abfec608869750db510003765c51c in geode's branch
refs/heads/feature/GEODE-7665 from Dale Emery
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=76573ce ]
GEODE-8391: Skip assertion if unsupported by host (#5412)
An assertion in AvailablePortJUnitTest.testIsPortAvailable() assumes
that the InetAddress for the local host is not a loopback address.
Though this assumption holds in our CI containers, it fails on some
developer's Macs, and perhaps on other hosts.
This commit changes the test to skip that assertion if the local host
address is a loopback address.
Authored-by: Dale Emery
> Skip AvailablePort test assertion if host machine does not support it
> -
>
> Key: GEODE-8391
> URL: https://issues.apache.org/jira/browse/GEODE-8391
> Project: Geode
> Issue Type: Test
> Components: tests
>Reporter: Dale Emery
>Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
>
> One of the assertions in {{AvailablePortJUnitTest.testIsPortAvailable()}}
> assumes that the {{InetAddress}} for the local host is not a loopback
> address. Though this assumption holds in our CI containers, it fails on some
> developer's Macs.
> Change the test to skip this one assertion if the {{InetAddress}} for the
> local host is a loopback address.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-8331) allow GFSH to connect to newer and older locator/server.
[ https://issues.apache.org/jira/browse/GEODE-8331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170248#comment-17170248 ] ASF subversion and git services commented on GEODE-8331: Commit 4cea8621f535e48d2879317af18878998c32 in geode's branch refs/heads/feature/GEODE-7665 from Dave Barnes [ https://gitbox.apache.org/repos/asf?p=geode.git;h=4cea862 ] GEODE-8331: allow GFSH to connect to other versions of cluster (doc correction) (#5410) > allow GFSH to connect to newer and older locator/server. > > > Key: GEODE-8331 > URL: https://issues.apache.org/jira/browse/GEODE-8331 > Project: Geode > Issue Type: Bug > Components: docs, gfsh >Reporter: Jinmei Liao >Priority: Major > Labels: GeodeOperationAPI, pull-request-available > Fix For: 1.12.1, 1.13.0, 1.14.0 > > > When using an older or newer gfsh to connect to an older or newer distributed > system gfsh will throw a warning error and not connect. > Example warning message Cannot use a 9.8.5 gfsh client to connect to a 9.9.0 > cluster.. > The desired behavior is to allow gfsh connect and only if there is an issue > with an updated /unknown command parsing should the system throw an error and > provide the extra guidance of what version the servers are at and the version > of the current gfsh cli. > Initially add these capability into the newer product version > Later based on the feasibility of adding this to older version, this will be > ported into the older version. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7667) GFSH commands - uniform gfsh command to clear regions
[ https://issues.apache.org/jira/browse/GEODE-7667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170267#comment-17170267 ] ASF subversion and git services commented on GEODE-7667: Commit 7177dae836a912286fe4f9629c511a7241c33bdf in geode's branch refs/heads/feature/GEODE-7665 from Nabarun Nag [ https://gitbox.apache.org/repos/asf?p=geode.git;h=7177dae ] GEODE-7667: Fixing test to include PR clear help text. > GFSH commands - uniform gfsh command to clear regions > - > > Key: GEODE-7667 > URL: https://issues.apache.org/jira/browse/GEODE-7667 > Project: Geode > Issue Type: Sub-task > Components: regions >Reporter: Nabarun Nag >Assignee: Benjamin P Ross >Priority: Major > Labels: GeodeCommons, docs > Time Spent: 5h > Remaining Estimate: 0h > > * Currently, the gfsh command to clear replicated region is called ‘remove > —region=/regionName’. > * Replace this command with ‘clear region —region=regionName’ > * While executing this gfsh command on partitioned regions, this should call > the clear() Java API using the gfsh function execution machinery. > * Point to note is that this command should take into consideration of the > coordinator selection and how this command is distributed to the members > Acceptance : > * There should be ‘clear region —region=/regionName’ gfsh command > * The gfsh command must be documented in the Geode User Guide > * DUnit tests to verify that command can be executed successfully on > PartitionedRegion > * Deprecate the remove command, as remove does not mean clear > * Unit tests with complete code coverage for the newly written code. > * Test coverage to when a member departs in this scenario > * Test coverage to when a member restarts in this scenario -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7678) Partitioned Region clear operations must invoke cache level listeners
[ https://issues.apache.org/jira/browse/GEODE-7678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170268#comment-17170268 ] ASF subversion and git services commented on GEODE-7678: Commit 1ecd10ae09fdbd59de85b95b204c3eb2e920de0b in geode's branch refs/heads/feature/GEODE-7665 from agingade [ https://gitbox.apache.org/repos/asf?p=geode.git;h=1ecd10a ] GEODE-7678 (2nd PR) - Support for cache-listener and client-notification for Partitioned Region Clear operation (#5124) * GEODE-7678: Add support for cache listener and client notification for PR clear The changes are made to PR clear messaging and locking mechanism to preserve cache-listener and client-events ordering during concurrent cache operation while clear in progress. > Partitioned Region clear operations must invoke cache level listeners > - > > Key: GEODE-7678 > URL: https://issues.apache.org/jira/browse/GEODE-7678 > Project: Geode > Issue Type: Sub-task > Components: regions >Reporter: Nabarun Nag >Assignee: Anilkumar Gingade >Priority: Major > Labels: GeodeCommons, GeodeOperationAPI > > Clear operations are successful and CacheListener.afterRegionClear(), > CacheWriter.beforeRegionClear() are invoked. > > 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-8361) Incorrect Bucket Count Warning Message Shown
[
https://issues.apache.org/jira/browse/GEODE-8361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170274#comment-17170274
]
ASF subversion and git services commented on GEODE-8361:
Commit d2a974201e23e0f58e90ca9acfb4b7c1f5b23cfe in geode's branch
refs/heads/feature/GEODE-7665 from Donal Evans
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=d2a9742 ]
GEODE-8361: Use Set instead of List to track cleared buckets (#5379)
- Refactor PartitionRegionClear to use Set instead of List
- Some other changes to remove warnings/alerts from PartitionedRegionClear and
PartitionedRegionClearMessage
Authored-by: Donal Evans
> Incorrect Bucket Count Warning Message Shown
>
>
> Key: GEODE-8361
> URL: https://issues.apache.org/jira/browse/GEODE-8361
> Project: Geode
> Issue Type: Sub-task
> Components: logging
>Reporter: Juan Ramos
>Assignee: Donal Evans
>Priority: Trivial
> Labels: pull-request-available
> Fix For: 1.14.0
>
>
> While analysing some failures related to GEODE-7670, I've noticed that
> sometimes we report an incorrect bucket count within the warning message
> logged when the clear didn't complete successfully that could confuse our
> users.
> For this test the partition region always has 13 buckets so, as I user, I
> would never expect to see a bucket count higher than 13 in my logs (no matter
> how many redundant copies I have).
> ---
> Below are some examples:
> {noformat}
> [vm1] [warn 2020/07/15 11:56:17.739 GMT RMI TCP
> Connection(5)-172.17.0.5 tid=0x5f] Unable to clear all the buckets from
> the partitioned region PartitionedRegion, either data (buckets) moved or
> member departed. expected to clear number of buckets: 13 actual cleared: 26
> [vm1] [warn 2020/07/15 11:57:48.403 GMT RMI TCP
> Connection(6)-172.17.0.9 tid=0x10f] Unable to clear all the buckets from
> the partitioned region PartitionedRegion, either data (buckets) moved or
> member departed. expected to clear number of buckets: 13 actual cleared: 14
> [vm0] [warn 2020/07/15 12:07:36.227 GMT RMI TCP
> Connection(32)-172.17.0.25 tid=0x1fe] Unable to clear all the buckets
> from the partitioned region PartitionedRegion, either data (buckets) moved or
> member departed. expected to clear number of buckets: 13 actual cleared: 19
> [vm0] [warn 2020/07/15 12:08:56.277 GMT RMI TCP
> Connection(37)-172.17.0.24 tid=0x2a2] Unable to clear all the buckets
> from the partitioned region PartitionedRegion, either data (buckets) moved or
> member departed. expected to clear number of buckets: 13 actual cleared: 16
> {noformat}
> The full set of artefacts and results:
> {noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-pr/geode-pr-4848/test-results/repeatTest/1594816968/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-pr/geode-pr-4848/test-artifacts/1594816968/stressnewtestfiles-geode-pr-4848.tgz
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-7894) CustomSSLProviderDistributedTest hostNameIsValidatedWhenUsingDefaultContext fails with suspect uncaught DistributedSystemDisconnectedException
[
https://issues.apache.org/jira/browse/GEODE-7894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170266#comment-17170266
]
ASF subversion and git services commented on GEODE-7894:
Commit 16814730977822a903521e2bc89e19206c6d9698 in geode's branch
refs/heads/feature/GEODE-7665 from Nabarun Nag
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=1681473 ]
GEODE-7894: Moving expiry tasks to AbstractRegion.
> CustomSSLProviderDistributedTest hostNameIsValidatedWhenUsingDefaultContext
> fails with suspect uncaught DistributedSystemDisconnectedException
> --
>
> Key: GEODE-7894
> URL: https://issues.apache.org/jira/browse/GEODE-7894
> Project: Geode
> Issue Type: Bug
> Components: membership
>Reporter: Darrel Schneider
>Assignee: Dan Smith
>Priority: Minor
> Labels: flakey
> Fix For: 1.13.0
>
>
> See:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/1663
> {noformat}
> org.apache.geode.cache.client.internal.CustomSSLProviderDistributedTest >
> hostNameIsValidatedWhenUsingDefaultContext FAILED
> java.lang.AssertionError: Suspicious strings were written to the log
> during this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in log4j at line 1654
> [fatal 2020/03/19 17:26:01.806 GMT tid=215] Uncaught
> exception in thread Thread[unused p2p reader,5,RMI Runtime]
> org.apache.geode.distributed.DistributedSystemDisconnectedException:
> Distribution manager on 172.17.0.15(server-1:113):41001 started at Thu
> Mar 19 17:25:57 GMT 2020: Message distribution has terminated
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager$Stopper.generateCancelledException(ClusterDistributionManager.java:2873)
> at
> org.apache.geode.internal.tcp.TCPConduit$Stopper.generateCancelledException(TCPConduit.java:1004)
> at
> org.apache.geode.CancelCriterion.checkCancelInProgress(CancelCriterion.java:83)
> at
> org.apache.geode.internal.tcp.Connection.readMessages(Connection.java:1666)
> at org.apache.geode.internal.tcp.Connection.run(Connection.java:1446)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-8361) Incorrect Bucket Count Warning Message Shown
[
https://issues.apache.org/jira/browse/GEODE-8361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170287#comment-17170287
]
ASF subversion and git services commented on GEODE-8361:
Commit d2a974201e23e0f58e90ca9acfb4b7c1f5b23cfe in geode's branch
refs/heads/feature/GEODE-7665 from Donal Evans
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=d2a9742 ]
GEODE-8361: Use Set instead of List to track cleared buckets (#5379)
- Refactor PartitionRegionClear to use Set instead of List
- Some other changes to remove warnings/alerts from PartitionedRegionClear and
PartitionedRegionClearMessage
Authored-by: Donal Evans
> Incorrect Bucket Count Warning Message Shown
>
>
> Key: GEODE-8361
> URL: https://issues.apache.org/jira/browse/GEODE-8361
> Project: Geode
> Issue Type: Sub-task
> Components: logging
>Reporter: Juan Ramos
>Assignee: Donal Evans
>Priority: Trivial
> Labels: pull-request-available
> Fix For: 1.14.0
>
>
> While analysing some failures related to GEODE-7670, I've noticed that
> sometimes we report an incorrect bucket count within the warning message
> logged when the clear didn't complete successfully that could confuse our
> users.
> For this test the partition region always has 13 buckets so, as I user, I
> would never expect to see a bucket count higher than 13 in my logs (no matter
> how many redundant copies I have).
> ---
> Below are some examples:
> {noformat}
> [vm1] [warn 2020/07/15 11:56:17.739 GMT RMI TCP
> Connection(5)-172.17.0.5 tid=0x5f] Unable to clear all the buckets from
> the partitioned region PartitionedRegion, either data (buckets) moved or
> member departed. expected to clear number of buckets: 13 actual cleared: 26
> [vm1] [warn 2020/07/15 11:57:48.403 GMT RMI TCP
> Connection(6)-172.17.0.9 tid=0x10f] Unable to clear all the buckets from
> the partitioned region PartitionedRegion, either data (buckets) moved or
> member departed. expected to clear number of buckets: 13 actual cleared: 14
> [vm0] [warn 2020/07/15 12:07:36.227 GMT RMI TCP
> Connection(32)-172.17.0.25 tid=0x1fe] Unable to clear all the buckets
> from the partitioned region PartitionedRegion, either data (buckets) moved or
> member departed. expected to clear number of buckets: 13 actual cleared: 19
> [vm0] [warn 2020/07/15 12:08:56.277 GMT RMI TCP
> Connection(37)-172.17.0.24 tid=0x2a2] Unable to clear all the buckets
> from the partitioned region PartitionedRegion, either data (buckets) moved or
> member departed. expected to clear number of buckets: 13 actual cleared: 16
> {noformat}
> The full set of artefacts and results:
> {noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-pr/geode-pr-4848/test-results/repeatTest/1594816968/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-pr/geode-pr-4848/test-artifacts/1594816968/stressnewtestfiles-geode-pr-4848.tgz
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-7667) GFSH commands - uniform gfsh command to clear regions
[ https://issues.apache.org/jira/browse/GEODE-7667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170280#comment-17170280 ] ASF subversion and git services commented on GEODE-7667: Commit 7177dae836a912286fe4f9629c511a7241c33bdf in geode's branch refs/heads/feature/GEODE-7665 from Nabarun Nag [ https://gitbox.apache.org/repos/asf?p=geode.git;h=7177dae ] GEODE-7667: Fixing test to include PR clear help text. > GFSH commands - uniform gfsh command to clear regions > - > > Key: GEODE-7667 > URL: https://issues.apache.org/jira/browse/GEODE-7667 > Project: Geode > Issue Type: Sub-task > Components: regions >Reporter: Nabarun Nag >Assignee: Benjamin P Ross >Priority: Major > Labels: GeodeCommons, docs > Time Spent: 5h > Remaining Estimate: 0h > > * Currently, the gfsh command to clear replicated region is called ‘remove > —region=/regionName’. > * Replace this command with ‘clear region —region=regionName’ > * While executing this gfsh command on partitioned regions, this should call > the clear() Java API using the gfsh function execution machinery. > * Point to note is that this command should take into consideration of the > coordinator selection and how this command is distributed to the members > Acceptance : > * There should be ‘clear region —region=/regionName’ gfsh command > * The gfsh command must be documented in the Geode User Guide > * DUnit tests to verify that command can be executed successfully on > PartitionedRegion > * Deprecate the remove command, as remove does not mean clear > * Unit tests with complete code coverage for the newly written code. > * Test coverage to when a member departs in this scenario > * Test coverage to when a member restarts in this scenario -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7678) Partitioned Region clear operations must invoke cache level listeners
[ https://issues.apache.org/jira/browse/GEODE-7678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170281#comment-17170281 ] ASF subversion and git services commented on GEODE-7678: Commit 1ecd10ae09fdbd59de85b95b204c3eb2e920de0b in geode's branch refs/heads/feature/GEODE-7665 from agingade [ https://gitbox.apache.org/repos/asf?p=geode.git;h=1ecd10a ] GEODE-7678 (2nd PR) - Support for cache-listener and client-notification for Partitioned Region Clear operation (#5124) * GEODE-7678: Add support for cache listener and client notification for PR clear The changes are made to PR clear messaging and locking mechanism to preserve cache-listener and client-events ordering during concurrent cache operation while clear in progress. > Partitioned Region clear operations must invoke cache level listeners > - > > Key: GEODE-7678 > URL: https://issues.apache.org/jira/browse/GEODE-7678 > Project: Geode > Issue Type: Sub-task > Components: regions >Reporter: Nabarun Nag >Assignee: Anilkumar Gingade >Priority: Major > Labels: GeodeCommons, GeodeOperationAPI > > Clear operations are successful and CacheListener.afterRegionClear(), > CacheWriter.beforeRegionClear() are invoked. > > 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-7894) CustomSSLProviderDistributedTest hostNameIsValidatedWhenUsingDefaultContext fails with suspect uncaught DistributedSystemDisconnectedException
[
https://issues.apache.org/jira/browse/GEODE-7894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170279#comment-17170279
]
ASF subversion and git services commented on GEODE-7894:
Commit 16814730977822a903521e2bc89e19206c6d9698 in geode's branch
refs/heads/feature/GEODE-7665 from Nabarun Nag
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=1681473 ]
GEODE-7894: Moving expiry tasks to AbstractRegion.
> CustomSSLProviderDistributedTest hostNameIsValidatedWhenUsingDefaultContext
> fails with suspect uncaught DistributedSystemDisconnectedException
> --
>
> Key: GEODE-7894
> URL: https://issues.apache.org/jira/browse/GEODE-7894
> Project: Geode
> Issue Type: Bug
> Components: membership
>Reporter: Darrel Schneider
>Assignee: Dan Smith
>Priority: Minor
> Labels: flakey
> Fix For: 1.13.0
>
>
> See:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/1663
> {noformat}
> org.apache.geode.cache.client.internal.CustomSSLProviderDistributedTest >
> hostNameIsValidatedWhenUsingDefaultContext FAILED
> java.lang.AssertionError: Suspicious strings were written to the log
> during this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in log4j at line 1654
> [fatal 2020/03/19 17:26:01.806 GMT tid=215] Uncaught
> exception in thread Thread[unused p2p reader,5,RMI Runtime]
> org.apache.geode.distributed.DistributedSystemDisconnectedException:
> Distribution manager on 172.17.0.15(server-1:113):41001 started at Thu
> Mar 19 17:25:57 GMT 2020: Message distribution has terminated
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager$Stopper.generateCancelledException(ClusterDistributionManager.java:2873)
> at
> org.apache.geode.internal.tcp.TCPConduit$Stopper.generateCancelledException(TCPConduit.java:1004)
> at
> org.apache.geode.CancelCriterion.checkCancelInProgress(CancelCriterion.java:83)
> at
> org.apache.geode.internal.tcp.Connection.readMessages(Connection.java:1666)
> at org.apache.geode.internal.tcp.Connection.run(Connection.java:1446)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-7678) Partitioned Region clear operations must invoke cache level listeners
[ https://issues.apache.org/jira/browse/GEODE-7678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170282#comment-17170282 ] ASF subversion and git services commented on GEODE-7678: Commit 1ecd10ae09fdbd59de85b95b204c3eb2e920de0b in geode's branch refs/heads/feature/GEODE-7665 from agingade [ https://gitbox.apache.org/repos/asf?p=geode.git;h=1ecd10a ] GEODE-7678 (2nd PR) - Support for cache-listener and client-notification for Partitioned Region Clear operation (#5124) * GEODE-7678: Add support for cache listener and client notification for PR clear The changes are made to PR clear messaging and locking mechanism to preserve cache-listener and client-events ordering during concurrent cache operation while clear in progress. > Partitioned Region clear operations must invoke cache level listeners > - > > Key: GEODE-7678 > URL: https://issues.apache.org/jira/browse/GEODE-7678 > Project: Geode > Issue Type: Sub-task > Components: regions >Reporter: Nabarun Nag >Assignee: Anilkumar Gingade >Priority: Major > Labels: GeodeCommons, GeodeOperationAPI > > Clear operations are successful and CacheListener.afterRegionClear(), > CacheWriter.beforeRegionClear() are invoked. > > 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-8173) Add test coverage for PartitionedRegionClear class
[ https://issues.apache.org/jira/browse/GEODE-8173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170271#comment-17170271 ] ASF subversion and git services commented on GEODE-8173: Commit 862cad919fe6abf03d6bfa33900b7a2b7fc9ee30 in geode's branch refs/heads/feature/GEODE-7665 from agingade [ https://gitbox.apache.org/repos/asf?p=geode.git;h=862cad9 ] GEODE-8173: Add unit test (coverage) for PartitionedRegionClear class. (#5208) * GEODE-8173: Add unit test (coverage) for PartitionedRegionClear class. Co-authored-by: anilkumar gingade > Add test coverage for PartitionedRegionClear class > -- > > Key: GEODE-8173 > URL: https://issues.apache.org/jira/browse/GEODE-8173 > Project: Geode > Issue Type: Bug > Components: regions >Reporter: Anilkumar Gingade >Priority: Major > Labels: GeodeOperationAPI > Fix For: 1.14.0 > > > Add test coverage for PartitionedRegionClear class. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7669) Test coverage for Partitioned Region clear with Overflow enabled
[ https://issues.apache.org/jira/browse/GEODE-7669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170283#comment-17170283 ] ASF subversion and git services commented on GEODE-7669: Commit ddffddc6467d6ba557c5b1c799657a30d1a9c525 in geode's branch refs/heads/feature/GEODE-7665 from Jianxia Chen [ https://gitbox.apache.org/repos/asf?p=geode.git;h=ddffddc ] GEODE-7669 Test coverage for Partitioned Region clear with Overflow enabled (#5189) Authored-by: Jianxia Chen > Test coverage for Partitioned Region clear with Overflow enabled > > > Key: GEODE-7669 > URL: https://issues.apache.org/jira/browse/GEODE-7669 > Project: Geode > Issue Type: Sub-task > Components: regions >Reporter: Nabarun Nag >Assignee: Jianxia Chen >Priority: Major > Labels: GeodeCommons, GeodeOperationAPI > > Using TDD ensure that clear operations are successful when the partitioned > regions have overflow enabled. > Make the code changes required to enable this. > > Acceptance : > * Passing DUnit tests where clear operations are successful on partitioned > region with overflow enabled. > * Ensure that data has overflown when the clear operation is executed and in > the end everything is cleared. > * These tests should have redundancy of more than zero > * 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. > Note: > analyze if these tests are needed for offheap? > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7676) All expiration tasks are cleared after a Partitioned Region is cleared
[ https://issues.apache.org/jira/browse/GEODE-7676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170278#comment-17170278 ] ASF subversion and git services commented on GEODE-7676: Commit 0dcf0ef2b54ddf90e499fcbbee6426077790f07a in geode's branch refs/heads/feature/GEODE-7665 from Nabarun Nag [ https://gitbox.apache.org/repos/asf?p=geode.git;h=0dcf0ef ] GEODE-7676: Conversion of duration to seconds. > All expiration tasks are cleared after a Partitioned Region is cleared > -- > > Key: GEODE-7676 > URL: https://issues.apache.org/jira/browse/GEODE-7676 > Project: Geode > Issue Type: Sub-task > Components: regions >Reporter: Nabarun Nag >Assignee: Juan Ramos >Priority: Major > Labels: GeodeCommons, feature/GEODE-7665 > Time Spent: 1h 50m > Remaining Estimate: 0h > > Clear operations are successful and all the expiration tasks are cleared in > the bucket level > Acceptance : > * DUnit tests ensuring that clear operations are successful > * Expiration tasks are cleared. > * 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-8173) Add test coverage for PartitionedRegionClear class
[ https://issues.apache.org/jira/browse/GEODE-8173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170285#comment-17170285 ] ASF subversion and git services commented on GEODE-8173: Commit 862cad919fe6abf03d6bfa33900b7a2b7fc9ee30 in geode's branch refs/heads/feature/GEODE-7665 from agingade [ https://gitbox.apache.org/repos/asf?p=geode.git;h=862cad9 ] GEODE-8173: Add unit test (coverage) for PartitionedRegionClear class. (#5208) * GEODE-8173: Add unit test (coverage) for PartitionedRegionClear class. Co-authored-by: anilkumar gingade > Add test coverage for PartitionedRegionClear class > -- > > Key: GEODE-8173 > URL: https://issues.apache.org/jira/browse/GEODE-8173 > Project: Geode > Issue Type: Bug > Components: regions >Reporter: Anilkumar Gingade >Priority: Major > Labels: GeodeOperationAPI > Fix For: 1.14.0 > > > Add test coverage for PartitionedRegionClear class. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7680) Partitioned region clear operations must be successful while interacting with rebalance
[ https://issues.apache.org/jira/browse/GEODE-7680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170289#comment-17170289 ] ASF subversion and git services commented on GEODE-7680: Commit 0cb20cb322000661a466f9f63cb2c107ca1eb5d4 in geode's branch refs/heads/feature/GEODE-7665 from Donal Evans [ https://gitbox.apache.org/repos/asf?p=geode.git;h=0cb20cb ] GEODE-7680: PR.clear must be successful when interacting with rebalance (#5095) - Added DUnit tests to confirm that clear does not interfere with rebalance or vice versa - Test when member departs during clear/rebalance - Test when member joins during clear/rebalance - Fixed typo in PartitionedRegionClearWithExpirationDUnitTest - Fixed typo in PartitionedRegion - Call assignBucketsToPartitions() on leader colocated region during clear instead of target region Authored-by: Donal Evans > Partitioned region clear operations must be successful while interacting with > rebalance > > > Key: GEODE-7680 > URL: https://issues.apache.org/jira/browse/GEODE-7680 > Project: Geode > Issue Type: Sub-task > Components: regions >Reporter: Nabarun Nag >Assignee: Donal Evans >Priority: Major > Labels: GeodeCommons, caching-applications, > pull-request-available > Fix For: 1.14.0 > > > Clear operations are successful and while rebalance operations are ongoing. > 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] [Updated] (GEODE-8385) hang recovering from disk with cyclic dependencies
[
https://issues.apache.org/jira/browse/GEODE-8385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce J Schuchardt updated GEODE-8385:
--
Fix Version/s: (was: 1.14.0)
> hang recovering from disk with cyclic dependencies
> --
>
> Key: GEODE-8385
> URL: https://issues.apache.org/jira/browse/GEODE-8385
> Project: Geode
> Issue Type: Bug
> Components: membership, persistence
>Reporter: Bruce J Schuchardt
>Assignee: Bruce J Schuchardt
>Priority: Major
> Labels: no-release-note, pull-request-available
> Fix For: 1.13.0
>
>
> In a test cluster using replicated persistent Regions all of the servers were
> shut down and restarted. The restart hung showing a cycle in disk store
> dependencies.
> {noformat}
> [info 2020/05/29 03:02:36.635 PDT tid=0x8f] Region /Region_14 has
> potentially stale data. It is waiting for another online member to recover
> the latest data.My persistent id:
> DiskStore ID: a175354a-d27d-4575-9916-16fd7ff7ea67 Name:
> persistgemfire4_host1_4194 Location:
> /10.32.110.100:/var/vcap/data/rundir/concRecoverAllV4O41/concRecoverAll-0529-024642/vm_5_persist4_disk_1
> Members with potentially new data:[
> DiskStore ID: 2d77752e-507d-4425-a382-a5856c61938f Name:
> persistgemfire10_host1_4208 Location:
> /10.32.110.100:/var/vcap/data/rundir/concRecoverAllV4O41/concRecoverAll-0529-024642/vm_2_persist10_disk_1]
> Use the gfsh show missing-disk-stores command to see all disk stores that are
> being waited on by other members.
> {noformat}
> After looking at the logs for all members, the "members with potentially new
> data" for each member were found to be:
> {noformat}
> Member | Members with potentially new data
> +--
> 1 | all
> 2 | 4
> 3 | 4
> 4 | 10
> 5 | 2, 3, 4, 8, 10
> 6 | 2, 3, 4, 5, 7, 8, 10
> 7 | 3, 4, 10
> 8 | 3, 4, 10
> 9 | 2, 3, 4, 5, 7, 8, 10
> 10 | 3
> {noformat}
> It appears that there is a cycle in this "waiting for another online member"
> graph between 3 > 4 > 10 > 3.
> The problem seems to have cropped up after the fix for GEODE-7196 was merged.
> That changed the timing of member-departed notifications such that a server
> might close a Region's Persistence Advisor before getting notification that
> another server was shutting down. We used to do this notification upon
> receipt of a ShutdownMessage but now we only do it when the membership view
> has changed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-8397) extend PoolFactoryAPI to support SNI proxy
[ https://issues.apache.org/jira/browse/GEODE-8397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernest Burghardt updated GEODE-8397: Description: cppcache (was: clicache) > extend PoolFactoryAPI to support SNI proxy > -- > > Key: GEODE-8397 > URL: https://issues.apache.org/jira/browse/GEODE-8397 > Project: Geode > Issue Type: New Feature > Components: native client >Reporter: Ernest Burghardt >Priority: Major > > cppcache -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-8398) extend PoolFactoryAPI to support SNI proxy
[ https://issues.apache.org/jira/browse/GEODE-8398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernest Burghardt updated GEODE-8398: Summary: extend PoolFactoryAPI to support SNI proxy (was: CLONE - extend PoolFactoryAPI to support SNI proxy) > extend PoolFactoryAPI to support SNI proxy > -- > > Key: GEODE-8398 > URL: https://issues.apache.org/jira/browse/GEODE-8398 > Project: Geode > Issue Type: New Feature > Components: native client >Reporter: Ernest Burghardt >Priority: Major > > clicache -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8173) Add test coverage for PartitionedRegionClear class
[ https://issues.apache.org/jira/browse/GEODE-8173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170297#comment-17170297 ] ASF subversion and git services commented on GEODE-8173: Commit 862cad919fe6abf03d6bfa33900b7a2b7fc9ee30 in geode's branch refs/heads/feature/GEODE-7665 from agingade [ https://gitbox.apache.org/repos/asf?p=geode.git;h=862cad9 ] GEODE-8173: Add unit test (coverage) for PartitionedRegionClear class. (#5208) * GEODE-8173: Add unit test (coverage) for PartitionedRegionClear class. Co-authored-by: anilkumar gingade > Add test coverage for PartitionedRegionClear class > -- > > Key: GEODE-8173 > URL: https://issues.apache.org/jira/browse/GEODE-8173 > Project: Geode > Issue Type: Bug > Components: regions >Reporter: Anilkumar Gingade >Priority: Major > Labels: GeodeOperationAPI > Fix For: 1.14.0 > > > Add test coverage for PartitionedRegionClear class. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7667) GFSH commands - uniform gfsh command to clear regions
[ https://issues.apache.org/jira/browse/GEODE-7667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170293#comment-17170293 ] ASF subversion and git services commented on GEODE-7667: Commit 7177dae836a912286fe4f9629c511a7241c33bdf in geode's branch refs/heads/feature/GEODE-7665 from Nabarun Nag [ https://gitbox.apache.org/repos/asf?p=geode.git;h=7177dae ] GEODE-7667: Fixing test to include PR clear help text. > GFSH commands - uniform gfsh command to clear regions > - > > Key: GEODE-7667 > URL: https://issues.apache.org/jira/browse/GEODE-7667 > Project: Geode > Issue Type: Sub-task > Components: regions >Reporter: Nabarun Nag >Assignee: Benjamin P Ross >Priority: Major > Labels: GeodeCommons, docs > Time Spent: 5h > Remaining Estimate: 0h > > * Currently, the gfsh command to clear replicated region is called ‘remove > —region=/regionName’. > * Replace this command with ‘clear region —region=regionName’ > * While executing this gfsh command on partitioned regions, this should call > the clear() Java API using the gfsh function execution machinery. > * Point to note is that this command should take into consideration of the > coordinator selection and how this command is distributed to the members > Acceptance : > * There should be ‘clear region —region=/regionName’ gfsh command > * The gfsh command must be documented in the Geode User Guide > * DUnit tests to verify that command can be executed successfully on > PartitionedRegion > * Deprecate the remove command, as remove does not mean clear > * Unit tests with complete code coverage for the newly written code. > * Test coverage to when a member departs in this scenario > * Test coverage to when a member restarts in this scenario -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8173) Add test coverage for PartitionedRegionClear class
[ https://issues.apache.org/jira/browse/GEODE-8173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170298#comment-17170298 ] ASF subversion and git services commented on GEODE-8173: Commit 862cad919fe6abf03d6bfa33900b7a2b7fc9ee30 in geode's branch refs/heads/feature/GEODE-7665 from agingade [ https://gitbox.apache.org/repos/asf?p=geode.git;h=862cad9 ] GEODE-8173: Add unit test (coverage) for PartitionedRegionClear class. (#5208) * GEODE-8173: Add unit test (coverage) for PartitionedRegionClear class. Co-authored-by: anilkumar gingade > Add test coverage for PartitionedRegionClear class > -- > > Key: GEODE-8173 > URL: https://issues.apache.org/jira/browse/GEODE-8173 > Project: Geode > Issue Type: Bug > Components: regions >Reporter: Anilkumar Gingade >Priority: Major > Labels: GeodeOperationAPI > Fix For: 1.14.0 > > > Add test coverage for PartitionedRegionClear class. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8361) Incorrect Bucket Count Warning Message Shown
[
https://issues.apache.org/jira/browse/GEODE-8361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170300#comment-17170300
]
ASF subversion and git services commented on GEODE-8361:
Commit d2a974201e23e0f58e90ca9acfb4b7c1f5b23cfe in geode's branch
refs/heads/feature/GEODE-7665 from Donal Evans
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=d2a9742 ]
GEODE-8361: Use Set instead of List to track cleared buckets (#5379)
- Refactor PartitionRegionClear to use Set instead of List
- Some other changes to remove warnings/alerts from PartitionedRegionClear and
PartitionedRegionClearMessage
Authored-by: Donal Evans
> Incorrect Bucket Count Warning Message Shown
>
>
> Key: GEODE-8361
> URL: https://issues.apache.org/jira/browse/GEODE-8361
> Project: Geode
> Issue Type: Sub-task
> Components: logging
>Reporter: Juan Ramos
>Assignee: Donal Evans
>Priority: Trivial
> Labels: pull-request-available
> Fix For: 1.14.0
>
>
> While analysing some failures related to GEODE-7670, I've noticed that
> sometimes we report an incorrect bucket count within the warning message
> logged when the clear didn't complete successfully that could confuse our
> users.
> For this test the partition region always has 13 buckets so, as I user, I
> would never expect to see a bucket count higher than 13 in my logs (no matter
> how many redundant copies I have).
> ---
> Below are some examples:
> {noformat}
> [vm1] [warn 2020/07/15 11:56:17.739 GMT RMI TCP
> Connection(5)-172.17.0.5 tid=0x5f] Unable to clear all the buckets from
> the partitioned region PartitionedRegion, either data (buckets) moved or
> member departed. expected to clear number of buckets: 13 actual cleared: 26
> [vm1] [warn 2020/07/15 11:57:48.403 GMT RMI TCP
> Connection(6)-172.17.0.9 tid=0x10f] Unable to clear all the buckets from
> the partitioned region PartitionedRegion, either data (buckets) moved or
> member departed. expected to clear number of buckets: 13 actual cleared: 14
> [vm0] [warn 2020/07/15 12:07:36.227 GMT RMI TCP
> Connection(32)-172.17.0.25 tid=0x1fe] Unable to clear all the buckets
> from the partitioned region PartitionedRegion, either data (buckets) moved or
> member departed. expected to clear number of buckets: 13 actual cleared: 19
> [vm0] [warn 2020/07/15 12:08:56.277 GMT RMI TCP
> Connection(37)-172.17.0.24 tid=0x2a2] Unable to clear all the buckets
> from the partitioned region PartitionedRegion, either data (buckets) moved or
> member departed. expected to clear number of buckets: 13 actual cleared: 16
> {noformat}
> The full set of artefacts and results:
> {noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-pr/geode-pr-4848/test-results/repeatTest/1594816968/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-pr/geode-pr-4848/test-artifacts/1594816968/stressnewtestfiles-geode-pr-4848.tgz
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-7678) Partitioned Region clear operations must invoke cache level listeners
[ https://issues.apache.org/jira/browse/GEODE-7678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170294#comment-17170294 ] ASF subversion and git services commented on GEODE-7678: Commit 1ecd10ae09fdbd59de85b95b204c3eb2e920de0b in geode's branch refs/heads/feature/GEODE-7665 from agingade [ https://gitbox.apache.org/repos/asf?p=geode.git;h=1ecd10a ] GEODE-7678 (2nd PR) - Support for cache-listener and client-notification for Partitioned Region Clear operation (#5124) * GEODE-7678: Add support for cache listener and client notification for PR clear The changes are made to PR clear messaging and locking mechanism to preserve cache-listener and client-events ordering during concurrent cache operation while clear in progress. > Partitioned Region clear operations must invoke cache level listeners > - > > Key: GEODE-7678 > URL: https://issues.apache.org/jira/browse/GEODE-7678 > Project: Geode > Issue Type: Sub-task > Components: regions >Reporter: Nabarun Nag >Assignee: Anilkumar Gingade >Priority: Major > Labels: GeodeCommons, GeodeOperationAPI > > Clear operations are successful and CacheListener.afterRegionClear(), > CacheWriter.beforeRegionClear() are invoked. > > 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-7670) Partitioned Region clear operations can occur during concurrent data operations
[ https://issues.apache.org/jira/browse/GEODE-7670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170301#comment-17170301 ] ASF subversion and git services commented on GEODE-7670: Commit 45b36413bff34878d295544fe682341640207599 in geode's branch refs/heads/feature/GEODE-7665 from Juan José Ramos [ https://gitbox.apache.org/repos/asf?p=geode.git;h=45b3641 ] GEODE-7670: PR Clear with Concurrent Ops DUnitTests (#4848) Added distributed tests to verify that the clear operation on Partitioned Regions works as expected when there are other concurrent operations happening on the cache (put, putAll, get, remove, removeAll, members added and members removed). > Partitioned Region clear operations can occur during concurrent data > operations > --- > > Key: GEODE-7670 > URL: https://issues.apache.org/jira/browse/GEODE-7670 > Project: Geode > Issue Type: Sub-task > Components: regions >Reporter: Nabarun Nag >Assignee: Juan Ramos >Priority: Major > Labels: GeodeCommons, pull-request-available > Time Spent: 5.5h > Remaining Estimate: 0h > > Clear operations are successful when concurrent read/write operations occur. > Ensure there are test coverage for this use case and modify the code needed > to enable this. > Acceptance : > * Passing DUnit tests where clear operations are successful on partitioned > region with > * concurrent puts (writes) and clear op > * concurrent gets (reads) and clear op > * 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-7676) All expiration tasks are cleared after a Partitioned Region is cleared
[ https://issues.apache.org/jira/browse/GEODE-7676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170291#comment-17170291 ] ASF subversion and git services commented on GEODE-7676: Commit 0dcf0ef2b54ddf90e499fcbbee6426077790f07a in geode's branch refs/heads/feature/GEODE-7665 from Nabarun Nag [ https://gitbox.apache.org/repos/asf?p=geode.git;h=0dcf0ef ] GEODE-7676: Conversion of duration to seconds. > All expiration tasks are cleared after a Partitioned Region is cleared > -- > > Key: GEODE-7676 > URL: https://issues.apache.org/jira/browse/GEODE-7676 > Project: Geode > Issue Type: Sub-task > Components: regions >Reporter: Nabarun Nag >Assignee: Juan Ramos >Priority: Major > Labels: GeodeCommons, feature/GEODE-7665 > Time Spent: 1h 50m > Remaining Estimate: 0h > > Clear operations are successful and all the expiration tasks are cleared in > the bucket level > Acceptance : > * DUnit tests ensuring that clear operations are successful > * Expiration tasks are cleared. > * 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-7680) Partitioned region clear operations must be successful while interacting with rebalance
[ https://issues.apache.org/jira/browse/GEODE-7680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170314#comment-17170314 ] ASF subversion and git services commented on GEODE-7680: Commit 0cb20cb322000661a466f9f63cb2c107ca1eb5d4 in geode's branch refs/heads/feature/GEODE-7665 from Donal Evans [ https://gitbox.apache.org/repos/asf?p=geode.git;h=0cb20cb ] GEODE-7680: PR.clear must be successful when interacting with rebalance (#5095) - Added DUnit tests to confirm that clear does not interfere with rebalance or vice versa - Test when member departs during clear/rebalance - Test when member joins during clear/rebalance - Fixed typo in PartitionedRegionClearWithExpirationDUnitTest - Fixed typo in PartitionedRegion - Call assignBucketsToPartitions() on leader colocated region during clear instead of target region Authored-by: Donal Evans > Partitioned region clear operations must be successful while interacting with > rebalance > > > Key: GEODE-7680 > URL: https://issues.apache.org/jira/browse/GEODE-7680 > Project: Geode > Issue Type: Sub-task > Components: regions >Reporter: Nabarun Nag >Assignee: Donal Evans >Priority: Major > Labels: GeodeCommons, caching-applications, > pull-request-available > Fix For: 1.14.0 > > > Clear operations are successful and while rebalance operations are ongoing. > 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-8361) Incorrect Bucket Count Warning Message Shown
[
https://issues.apache.org/jira/browse/GEODE-8361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170312#comment-17170312
]
ASF subversion and git services commented on GEODE-8361:
Commit d2a974201e23e0f58e90ca9acfb4b7c1f5b23cfe in geode's branch
refs/heads/feature/GEODE-7665 from Donal Evans
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=d2a9742 ]
GEODE-8361: Use Set instead of List to track cleared buckets (#5379)
- Refactor PartitionRegionClear to use Set instead of List
- Some other changes to remove warnings/alerts from PartitionedRegionClear and
PartitionedRegionClearMessage
Authored-by: Donal Evans
> Incorrect Bucket Count Warning Message Shown
>
>
> Key: GEODE-8361
> URL: https://issues.apache.org/jira/browse/GEODE-8361
> Project: Geode
> Issue Type: Sub-task
> Components: logging
>Reporter: Juan Ramos
>Assignee: Donal Evans
>Priority: Trivial
> Labels: pull-request-available
> Fix For: 1.14.0
>
>
> While analysing some failures related to GEODE-7670, I've noticed that
> sometimes we report an incorrect bucket count within the warning message
> logged when the clear didn't complete successfully that could confuse our
> users.
> For this test the partition region always has 13 buckets so, as I user, I
> would never expect to see a bucket count higher than 13 in my logs (no matter
> how many redundant copies I have).
> ---
> Below are some examples:
> {noformat}
> [vm1] [warn 2020/07/15 11:56:17.739 GMT RMI TCP
> Connection(5)-172.17.0.5 tid=0x5f] Unable to clear all the buckets from
> the partitioned region PartitionedRegion, either data (buckets) moved or
> member departed. expected to clear number of buckets: 13 actual cleared: 26
> [vm1] [warn 2020/07/15 11:57:48.403 GMT RMI TCP
> Connection(6)-172.17.0.9 tid=0x10f] Unable to clear all the buckets from
> the partitioned region PartitionedRegion, either data (buckets) moved or
> member departed. expected to clear number of buckets: 13 actual cleared: 14
> [vm0] [warn 2020/07/15 12:07:36.227 GMT RMI TCP
> Connection(32)-172.17.0.25 tid=0x1fe] Unable to clear all the buckets
> from the partitioned region PartitionedRegion, either data (buckets) moved or
> member departed. expected to clear number of buckets: 13 actual cleared: 19
> [vm0] [warn 2020/07/15 12:08:56.277 GMT RMI TCP
> Connection(37)-172.17.0.24 tid=0x2a2] Unable to clear all the buckets
> from the partitioned region PartitionedRegion, either data (buckets) moved or
> member departed. expected to clear number of buckets: 13 actual cleared: 16
> {noformat}
> The full set of artefacts and results:
> {noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-pr/geode-pr-4848/test-results/repeatTest/1594816968/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-pr/geode-pr-4848/test-artifacts/1594816968/stressnewtestfiles-geode-pr-4848.tgz
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-7678) Partitioned Region clear operations must invoke cache level listeners
[ https://issues.apache.org/jira/browse/GEODE-7678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170307#comment-17170307 ] ASF subversion and git services commented on GEODE-7678: Commit 1ecd10ae09fdbd59de85b95b204c3eb2e920de0b in geode's branch refs/heads/feature/GEODE-7665 from agingade [ https://gitbox.apache.org/repos/asf?p=geode.git;h=1ecd10a ] GEODE-7678 (2nd PR) - Support for cache-listener and client-notification for Partitioned Region Clear operation (#5124) * GEODE-7678: Add support for cache listener and client notification for PR clear The changes are made to PR clear messaging and locking mechanism to preserve cache-listener and client-events ordering during concurrent cache operation while clear in progress. > Partitioned Region clear operations must invoke cache level listeners > - > > Key: GEODE-7678 > URL: https://issues.apache.org/jira/browse/GEODE-7678 > Project: Geode > Issue Type: Sub-task > Components: regions >Reporter: Nabarun Nag >Assignee: Anilkumar Gingade >Priority: Major > Labels: GeodeCommons, GeodeOperationAPI > > Clear operations are successful and CacheListener.afterRegionClear(), > CacheWriter.beforeRegionClear() are invoked. > > 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-7670) Partitioned Region clear operations can occur during concurrent data operations
[ https://issues.apache.org/jira/browse/GEODE-7670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170313#comment-17170313 ] ASF subversion and git services commented on GEODE-7670: Commit 45b36413bff34878d295544fe682341640207599 in geode's branch refs/heads/feature/GEODE-7665 from Juan José Ramos [ https://gitbox.apache.org/repos/asf?p=geode.git;h=45b3641 ] GEODE-7670: PR Clear with Concurrent Ops DUnitTests (#4848) Added distributed tests to verify that the clear operation on Partitioned Regions works as expected when there are other concurrent operations happening on the cache (put, putAll, get, remove, removeAll, members added and members removed). > Partitioned Region clear operations can occur during concurrent data > operations > --- > > Key: GEODE-7670 > URL: https://issues.apache.org/jira/browse/GEODE-7670 > Project: Geode > Issue Type: Sub-task > Components: regions >Reporter: Nabarun Nag >Assignee: Juan Ramos >Priority: Major > Labels: GeodeCommons, pull-request-available > Time Spent: 5.5h > Remaining Estimate: 0h > > Clear operations are successful when concurrent read/write operations occur. > Ensure there are test coverage for this use case and modify the code needed > to enable this. > Acceptance : > * Passing DUnit tests where clear operations are successful on partitioned > region with > * concurrent puts (writes) and clear op > * concurrent gets (reads) and clear op > * 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-8334) Primary and secondary bucket data mismatch with concurrent putAll/removeAll and PR.clear
[ https://issues.apache.org/jira/browse/GEODE-8334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170311#comment-17170311 ] ASF subversion and git services commented on GEODE-8334: Commit 9a67231f5a107cf019af551f5a94d1ce49614d94 in geode's branch refs/heads/feature/GEODE-7665 from Xiaojian Zhou [ https://gitbox.apache.org/repos/asf?p=geode.git;h=9a67231 ] GEODE-8334: PR.clear should sync with putAll or removeAll on rvvLock (#5365) Co-authored-by: Xiaojian Zhou Co-authored-by: Anil Gingade > Primary and secondary bucket data mismatch with concurrent putAll/removeAll > and PR.clear > - > > Key: GEODE-8334 > URL: https://issues.apache.org/jira/browse/GEODE-8334 > Project: Geode > Issue Type: Sub-task > Components: regions >Affects Versions: 1.14.0 >Reporter: Xiaojian Zhou >Assignee: Xiaojian Zhou >Priority: Major > Labels: GeodeOperationAPI > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7894) CustomSSLProviderDistributedTest hostNameIsValidatedWhenUsingDefaultContext fails with suspect uncaught DistributedSystemDisconnectedException
[
https://issues.apache.org/jira/browse/GEODE-7894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170292#comment-17170292
]
ASF subversion and git services commented on GEODE-7894:
Commit 16814730977822a903521e2bc89e19206c6d9698 in geode's branch
refs/heads/feature/GEODE-7665 from Nabarun Nag
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=1681473 ]
GEODE-7894: Moving expiry tasks to AbstractRegion.
> CustomSSLProviderDistributedTest hostNameIsValidatedWhenUsingDefaultContext
> fails with suspect uncaught DistributedSystemDisconnectedException
> --
>
> Key: GEODE-7894
> URL: https://issues.apache.org/jira/browse/GEODE-7894
> Project: Geode
> Issue Type: Bug
> Components: membership
>Reporter: Darrel Schneider
>Assignee: Dan Smith
>Priority: Minor
> Labels: flakey
> Fix For: 1.13.0
>
>
> See:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/1663
> {noformat}
> org.apache.geode.cache.client.internal.CustomSSLProviderDistributedTest >
> hostNameIsValidatedWhenUsingDefaultContext FAILED
> java.lang.AssertionError: Suspicious strings were written to the log
> during this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in log4j at line 1654
> [fatal 2020/03/19 17:26:01.806 GMT tid=215] Uncaught
> exception in thread Thread[unused p2p reader,5,RMI Runtime]
> org.apache.geode.distributed.DistributedSystemDisconnectedException:
> Distribution manager on 172.17.0.15(server-1:113):41001 started at Thu
> Mar 19 17:25:57 GMT 2020: Message distribution has terminated
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager$Stopper.generateCancelledException(ClusterDistributionManager.java:2873)
> at
> org.apache.geode.internal.tcp.TCPConduit$Stopper.generateCancelledException(TCPConduit.java:1004)
> at
> org.apache.geode.CancelCriterion.checkCancelInProgress(CancelCriterion.java:83)
> at
> org.apache.geode.internal.tcp.Connection.readMessages(Connection.java:1666)
> at org.apache.geode.internal.tcp.Connection.run(Connection.java:1446)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-7670) Partitioned Region clear operations can occur during concurrent data operations
[ https://issues.apache.org/jira/browse/GEODE-7670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170288#comment-17170288 ] ASF subversion and git services commented on GEODE-7670: Commit 45b36413bff34878d295544fe682341640207599 in geode's branch refs/heads/feature/GEODE-7665 from Juan José Ramos [ https://gitbox.apache.org/repos/asf?p=geode.git;h=45b3641 ] GEODE-7670: PR Clear with Concurrent Ops DUnitTests (#4848) Added distributed tests to verify that the clear operation on Partitioned Regions works as expected when there are other concurrent operations happening on the cache (put, putAll, get, remove, removeAll, members added and members removed). > Partitioned Region clear operations can occur during concurrent data > operations > --- > > Key: GEODE-7670 > URL: https://issues.apache.org/jira/browse/GEODE-7670 > Project: Geode > Issue Type: Sub-task > Components: regions >Reporter: Nabarun Nag >Assignee: Juan Ramos >Priority: Major > Labels: GeodeCommons, pull-request-available > Time Spent: 5.5h > Remaining Estimate: 0h > > Clear operations are successful when concurrent read/write operations occur. > Ensure there are test coverage for this use case and modify the code needed > to enable this. > Acceptance : > * Passing DUnit tests where clear operations are successful on partitioned > region with > * concurrent puts (writes) and clear op > * concurrent gets (reads) and clear op > * 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-8334) Primary and secondary bucket data mismatch with concurrent putAll/removeAll and PR.clear
[ https://issues.apache.org/jira/browse/GEODE-8334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170286#comment-17170286 ] ASF subversion and git services commented on GEODE-8334: Commit 9a67231f5a107cf019af551f5a94d1ce49614d94 in geode's branch refs/heads/feature/GEODE-7665 from Xiaojian Zhou [ https://gitbox.apache.org/repos/asf?p=geode.git;h=9a67231 ] GEODE-8334: PR.clear should sync with putAll or removeAll on rvvLock (#5365) Co-authored-by: Xiaojian Zhou Co-authored-by: Anil Gingade > Primary and secondary bucket data mismatch with concurrent putAll/removeAll > and PR.clear > - > > Key: GEODE-8334 > URL: https://issues.apache.org/jira/browse/GEODE-8334 > Project: Geode > Issue Type: Sub-task > Components: regions >Affects Versions: 1.14.0 >Reporter: Xiaojian Zhou >Assignee: Xiaojian Zhou >Priority: Major > Labels: GeodeOperationAPI > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8334) Primary and secondary bucket data mismatch with concurrent putAll/removeAll and PR.clear
[ https://issues.apache.org/jira/browse/GEODE-8334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170299#comment-17170299 ] ASF subversion and git services commented on GEODE-8334: Commit 9a67231f5a107cf019af551f5a94d1ce49614d94 in geode's branch refs/heads/feature/GEODE-7665 from Xiaojian Zhou [ https://gitbox.apache.org/repos/asf?p=geode.git;h=9a67231 ] GEODE-8334: PR.clear should sync with putAll or removeAll on rvvLock (#5365) Co-authored-by: Xiaojian Zhou Co-authored-by: Anil Gingade > Primary and secondary bucket data mismatch with concurrent putAll/removeAll > and PR.clear > - > > Key: GEODE-8334 > URL: https://issues.apache.org/jira/browse/GEODE-8334 > Project: Geode > Issue Type: Sub-task > Components: regions >Affects Versions: 1.14.0 >Reporter: Xiaojian Zhou >Assignee: Xiaojian Zhou >Priority: Major > Labels: GeodeOperationAPI > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8173) Add test coverage for PartitionedRegionClear class
[ https://issues.apache.org/jira/browse/GEODE-8173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170284#comment-17170284 ] ASF subversion and git services commented on GEODE-8173: Commit 862cad919fe6abf03d6bfa33900b7a2b7fc9ee30 in geode's branch refs/heads/feature/GEODE-7665 from agingade [ https://gitbox.apache.org/repos/asf?p=geode.git;h=862cad9 ] GEODE-8173: Add unit test (coverage) for PartitionedRegionClear class. (#5208) * GEODE-8173: Add unit test (coverage) for PartitionedRegionClear class. Co-authored-by: anilkumar gingade > Add test coverage for PartitionedRegionClear class > -- > > Key: GEODE-8173 > URL: https://issues.apache.org/jira/browse/GEODE-8173 > Project: Geode > Issue Type: Bug > Components: regions >Reporter: Anilkumar Gingade >Priority: Major > Labels: GeodeOperationAPI > Fix For: 1.14.0 > > > Add test coverage for PartitionedRegionClear class. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8173) Add test coverage for PartitionedRegionClear class
[ https://issues.apache.org/jira/browse/GEODE-8173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170309#comment-17170309 ] ASF subversion and git services commented on GEODE-8173: Commit 862cad919fe6abf03d6bfa33900b7a2b7fc9ee30 in geode's branch refs/heads/feature/GEODE-7665 from agingade [ https://gitbox.apache.org/repos/asf?p=geode.git;h=862cad9 ] GEODE-8173: Add unit test (coverage) for PartitionedRegionClear class. (#5208) * GEODE-8173: Add unit test (coverage) for PartitionedRegionClear class. Co-authored-by: anilkumar gingade > Add test coverage for PartitionedRegionClear class > -- > > Key: GEODE-8173 > URL: https://issues.apache.org/jira/browse/GEODE-8173 > Project: Geode > Issue Type: Bug > Components: regions >Reporter: Anilkumar Gingade >Priority: Major > Labels: GeodeOperationAPI > Fix For: 1.14.0 > > > Add test coverage for PartitionedRegionClear class. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7669) Test coverage for Partitioned Region clear with Overflow enabled
[ https://issues.apache.org/jira/browse/GEODE-7669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170308#comment-17170308 ] ASF subversion and git services commented on GEODE-7669: Commit ddffddc6467d6ba557c5b1c799657a30d1a9c525 in geode's branch refs/heads/feature/GEODE-7665 from Jianxia Chen [ https://gitbox.apache.org/repos/asf?p=geode.git;h=ddffddc ] GEODE-7669 Test coverage for Partitioned Region clear with Overflow enabled (#5189) Authored-by: Jianxia Chen > Test coverage for Partitioned Region clear with Overflow enabled > > > Key: GEODE-7669 > URL: https://issues.apache.org/jira/browse/GEODE-7669 > Project: Geode > Issue Type: Sub-task > Components: regions >Reporter: Nabarun Nag >Assignee: Jianxia Chen >Priority: Major > Labels: GeodeCommons, GeodeOperationAPI > > Using TDD ensure that clear operations are successful when the partitioned > regions have overflow enabled. > Make the code changes required to enable this. > > Acceptance : > * Passing DUnit tests where clear operations are successful on partitioned > region with overflow enabled. > * Ensure that data has overflown when the clear operation is executed and in > the end everything is cleared. > * These tests should have redundancy of more than zero > * 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. > Note: > analyze if these tests are needed for offheap? > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7667) GFSH commands - uniform gfsh command to clear regions
[ https://issues.apache.org/jira/browse/GEODE-7667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170305#comment-17170305 ] ASF subversion and git services commented on GEODE-7667: Commit 7177dae836a912286fe4f9629c511a7241c33bdf in geode's branch refs/heads/feature/GEODE-7665 from Nabarun Nag [ https://gitbox.apache.org/repos/asf?p=geode.git;h=7177dae ] GEODE-7667: Fixing test to include PR clear help text. > GFSH commands - uniform gfsh command to clear regions > - > > Key: GEODE-7667 > URL: https://issues.apache.org/jira/browse/GEODE-7667 > Project: Geode > Issue Type: Sub-task > Components: regions >Reporter: Nabarun Nag >Assignee: Benjamin P Ross >Priority: Major > Labels: GeodeCommons, docs > Time Spent: 5h > Remaining Estimate: 0h > > * Currently, the gfsh command to clear replicated region is called ‘remove > —region=/regionName’. > * Replace this command with ‘clear region —region=regionName’ > * While executing this gfsh command on partitioned regions, this should call > the clear() Java API using the gfsh function execution machinery. > * Point to note is that this command should take into consideration of the > coordinator selection and how this command is distributed to the members > Acceptance : > * There should be ‘clear region —region=/regionName’ gfsh command > * The gfsh command must be documented in the Geode User Guide > * DUnit tests to verify that command can be executed successfully on > PartitionedRegion > * Deprecate the remove command, as remove does not mean clear > * Unit tests with complete code coverage for the newly written code. > * Test coverage to when a member departs in this scenario > * Test coverage to when a member restarts in this scenario -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7678) Partitioned Region clear operations must invoke cache level listeners
[ https://issues.apache.org/jira/browse/GEODE-7678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170295#comment-17170295 ] ASF subversion and git services commented on GEODE-7678: Commit 1ecd10ae09fdbd59de85b95b204c3eb2e920de0b in geode's branch refs/heads/feature/GEODE-7665 from agingade [ https://gitbox.apache.org/repos/asf?p=geode.git;h=1ecd10a ] GEODE-7678 (2nd PR) - Support for cache-listener and client-notification for Partitioned Region Clear operation (#5124) * GEODE-7678: Add support for cache listener and client notification for PR clear The changes are made to PR clear messaging and locking mechanism to preserve cache-listener and client-events ordering during concurrent cache operation while clear in progress. > Partitioned Region clear operations must invoke cache level listeners > - > > Key: GEODE-7678 > URL: https://issues.apache.org/jira/browse/GEODE-7678 > Project: Geode > Issue Type: Sub-task > Components: regions >Reporter: Nabarun Nag >Assignee: Anilkumar Gingade >Priority: Major > Labels: GeodeCommons, GeodeOperationAPI > > Clear operations are successful and CacheListener.afterRegionClear(), > CacheWriter.beforeRegionClear() are invoked. > > 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-7669) Test coverage for Partitioned Region clear with Overflow enabled
[ https://issues.apache.org/jira/browse/GEODE-7669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170296#comment-17170296 ] ASF subversion and git services commented on GEODE-7669: Commit ddffddc6467d6ba557c5b1c799657a30d1a9c525 in geode's branch refs/heads/feature/GEODE-7665 from Jianxia Chen [ https://gitbox.apache.org/repos/asf?p=geode.git;h=ddffddc ] GEODE-7669 Test coverage for Partitioned Region clear with Overflow enabled (#5189) Authored-by: Jianxia Chen > Test coverage for Partitioned Region clear with Overflow enabled > > > Key: GEODE-7669 > URL: https://issues.apache.org/jira/browse/GEODE-7669 > Project: Geode > Issue Type: Sub-task > Components: regions >Reporter: Nabarun Nag >Assignee: Jianxia Chen >Priority: Major > Labels: GeodeCommons, GeodeOperationAPI > > Using TDD ensure that clear operations are successful when the partitioned > regions have overflow enabled. > Make the code changes required to enable this. > > Acceptance : > * Passing DUnit tests where clear operations are successful on partitioned > region with overflow enabled. > * Ensure that data has overflown when the clear operation is executed and in > the end everything is cleared. > * These tests should have redundancy of more than zero > * 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. > Note: > analyze if these tests are needed for offheap? > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7680) Partitioned region clear operations must be successful while interacting with rebalance
[ https://issues.apache.org/jira/browse/GEODE-7680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170302#comment-17170302 ] ASF subversion and git services commented on GEODE-7680: Commit 0cb20cb322000661a466f9f63cb2c107ca1eb5d4 in geode's branch refs/heads/feature/GEODE-7665 from Donal Evans [ https://gitbox.apache.org/repos/asf?p=geode.git;h=0cb20cb ] GEODE-7680: PR.clear must be successful when interacting with rebalance (#5095) - Added DUnit tests to confirm that clear does not interfere with rebalance or vice versa - Test when member departs during clear/rebalance - Test when member joins during clear/rebalance - Fixed typo in PartitionedRegionClearWithExpirationDUnitTest - Fixed typo in PartitionedRegion - Call assignBucketsToPartitions() on leader colocated region during clear instead of target region Authored-by: Donal Evans > Partitioned region clear operations must be successful while interacting with > rebalance > > > Key: GEODE-7680 > URL: https://issues.apache.org/jira/browse/GEODE-7680 > Project: Geode > Issue Type: Sub-task > Components: regions >Reporter: Nabarun Nag >Assignee: Donal Evans >Priority: Major > Labels: GeodeCommons, caching-applications, > pull-request-available > Fix For: 1.14.0 > > > Clear operations are successful and while rebalance operations are ongoing. > 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-8387) SUNIONSTORE, SINTERSTORE, and SDIFFSTORE should delete the target key if the computed set is empty
[ https://issues.apache.org/jira/browse/GEODE-8387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170255#comment-17170255 ] ASF subversion and git services commented on GEODE-8387: Commit dec583b9411664c4db55c4ee4651a80cfe8a51a7 in geode's branch refs/heads/feature/GEODE-7665 from Darrel Schneider [ https://gitbox.apache.org/repos/asf?p=geode.git;h=dec583b ] GEODE-8387: fix SET*STORE commands handling of empty results (#5405) > SUNIONSTORE, SINTERSTORE, and SDIFFSTORE should delete the target key if the > computed set is empty > -- > > Key: GEODE-8387 > URL: https://issues.apache.org/jira/browse/GEODE-8387 > Project: Geode > Issue Type: Bug > Components: redis >Reporter: Darrel Schneider >Priority: Major > Labels: pull-request-available > Fix For: 1.14.0 > > > The current impl of SUNIONSTORE, SINTERSTORE, and SDIFFSTORE set the > destination to an empty set if the computed set is empty. But they should > instead in that case delete the destination. This is true if the read keys do > not exist. > If the read keys exist but are not sets then the commands should fail with a > WRONGTYPE error. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8391) Skip AvailablePort test assertion if host machine does not support it
[
https://issues.apache.org/jira/browse/GEODE-8391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170241#comment-17170241
]
ASF subversion and git services commented on GEODE-8391:
Commit 76573ce5b52abfec608869750db510003765c51c in geode's branch
refs/heads/feature/GEODE-7665 from Dale Emery
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=76573ce ]
GEODE-8391: Skip assertion if unsupported by host (#5412)
An assertion in AvailablePortJUnitTest.testIsPortAvailable() assumes
that the InetAddress for the local host is not a loopback address.
Though this assumption holds in our CI containers, it fails on some
developer's Macs, and perhaps on other hosts.
This commit changes the test to skip that assertion if the local host
address is a loopback address.
Authored-by: Dale Emery
> Skip AvailablePort test assertion if host machine does not support it
> -
>
> Key: GEODE-8391
> URL: https://issues.apache.org/jira/browse/GEODE-8391
> Project: Geode
> Issue Type: Test
> Components: tests
>Reporter: Dale Emery
>Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
>
> One of the assertions in {{AvailablePortJUnitTest.testIsPortAvailable()}}
> assumes that the {{InetAddress}} for the local host is not a loopback
> address. Though this assumption holds in our CI containers, it fails on some
> developer's Macs.
> Change the test to skip this one assertion if the {{InetAddress}} for the
> local host is a loopback address.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-8333) Fix PUBSUB hang
[ https://issues.apache.org/jira/browse/GEODE-8333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170238#comment-17170238 ] ASF subversion and git services commented on GEODE-8333: Commit 95bba9a7af10e2bd02febbc7c35bb2f16bb9e414 in geode's branch refs/heads/feature/GEODE-7665 from Darrel Schneider [ https://gitbox.apache.org/repos/asf?p=geode.git;h=95bba9a ] Revert "GEODE-8333: Fix PUBSUB hang (#5349)" (#5415) This reverts commit 067194e8f82414b6103c4335beb6567947edcfbc. The fix for GEODE-8333 had a bug in which responses to the client could be out of order. > Fix PUBSUB hang > --- > > Key: GEODE-8333 > URL: https://issues.apache.org/jira/browse/GEODE-8333 > Project: Geode > Issue Type: Bug > Components: redis >Reporter: Sarah Abbey >Assignee: Darrel Schneider >Priority: Major > Labels: pull-request-available > Fix For: 1.14.0 > > > PUBSUB hangs with concurrent publishers and subscribers on multiple servers. > The initial fix is being reverted because it caused a bug in which responses > to clients could now be out of order. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8372) Configure CMS to send UTF-8 regardless of JVM default
[
https://issues.apache.org/jira/browse/GEODE-8372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170251#comment-17170251
]
ASF subversion and git services commented on GEODE-8372:
Commit 1f1bd1adb2b40e69b112900d04350b4cdbcc0d66 in geode's branch
refs/heads/feature/GEODE-7665 from Jinmei Liao
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=1f1bd1a ]
GEODE-8372: Configure CMS to send UTF-8 regardless of JVM default (#5411)
> Configure CMS to send UTF-8 regardless of JVM default
> -
>
> Key: GEODE-8372
> URL: https://issues.apache.org/jira/browse/GEODE-8372
> Project: Geode
> Issue Type: Bug
> Components: management
>Reporter: Dale Emery
>Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
>
> In a client, CMS accepts only UTF-8 messages from the locator. But the
> locator can send non-UTF-8 messages depending on how the JVM and OS are
> configured.
> It looks as if the locator CMS uses the JVM's default character encoding, and
> the JVM sets its default character encoding based on the operating system's
> default locale.
> If a client CMS accepts only UTF-8, the locator CMS should send only UTF-8,
> regardless of the JVM's default character encoding.
> Example: I have a test client that uses a {{ClientClusterManagementService}}
> to create a region. The locator, runs on a machine where the default locale
> is us_EN.US-ASCII, sends US-ASCII responses. The client throws an
> {{UnknownContentTypeException}}:
> {noformat}
> org.springframework.web.client.UnknownContentTypeException: Could not extract
> response: no suitable HttpMessageConverter found for response type [class
> org.apache.geode.management.api.ClusterManagementRealizationResult] and
> content type [application/json;charset=US-ASCII]
> at
> org.springframework.web.client.HttpMessageConverterExtractor.extractData(HttpMessageConverterExtractor.java:126)
> ~[spring-web-5.2.7.RELEASE.jar:5.2.7.RELEASE]
> at
> org.springframework.web.client.RestTemplate$ResponseEntityResponseExtractor.extractData(RestTemplate.java:998)
> ~[spring-web-5.2.7.RELEASE.jar:5.2.7.RELEASE]
> at
> org.springframework.web.client.RestTemplate$ResponseEntityResponseExtractor.extractData(RestTemplate.java:981)
> ~[spring-web-5.2.7.RELEASE.jar:5.2.7.RELEASE]
> at
> org.springframework.web.client.RestTemplate.doExecute(RestTemplate.java:741)
> ~[spring-web-5.2.7.RELEASE.jar:5.2.7.RELEASE]
> at
> org.springframework.web.client.RestTemplate.execute(RestTemplate.java:674)
> ~[spring-web-5.2.7.RELEASE.jar:5.2.7.RELEASE]
> at
> org.springframework.web.client.RestTemplate.exchange(RestTemplate.java:583)
> ~[spring-web-5.2.7.RELEASE.jar:5.2.7.RELEASE]
> at
> org.apache.geode.management.api.RestTemplateClusterManagementServiceTransport.create(RestTemplateClusterManagementServiceTransport.java:248)
> ~[geode-management-1.12.0.jar:na]
> at
> org.apache.geode.management.api.RestTemplateClusterManagementServiceTransport.submitMessage(RestTemplateClusterManagementServiceTransport.java:153)
> ~[geode-management-1.12.0.jar:na]
> at
> org.apache.geode.management.internal.ClientClusterManagementService.create(ClientClusterManagementService.java:64)
> ~[geode-management-1.12.0.jar:na]
> at
> org.apache.geode.kubernetes.client.service.AsyncOperationService.createRegion(AsyncOperationService.java:46)
> ~[main/:na]
> at
> org.apache.geode.kubernetes.client.api.Controller.createRegion(Controller.java:27)
> ~[main/:na]
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method) ~[na:na]
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> ~[na:na]
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> ~[na:na]
> at java.base/java.lang.reflect.Method.invoke(Method.java:566) ~[na:na]
> at
> org.springframework.web.method.support.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:190)
> ~[spring-web-5.2.7.RELEASE.jar:5.2.7.RELEASE]
> at
> org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:138)
> ~[spring-web-5.2.7.RELEASE.jar:5.2.7.RELEASE]
> at
> org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:105)
> ~[spring-webmvc-5.2.7.RELEASE.jar:5.2.7.RELEASE]
> at
> org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:879)
> ~[spring-webmvc-5.2.7.RELEASE.jar:5.2.7.RELEASE]
> at
>
[jira] [Commented] (GEODE-8384) SETEX error message should be consistent with native redis
[
https://issues.apache.org/jira/browse/GEODE-8384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170242#comment-17170242
]
ASF subversion and git services commented on GEODE-8384:
Commit 0a31dd5de4bfe4402e86505f5a65fbe46c48c72b in geode's branch
refs/heads/feature/GEODE-7665 from Darrel Schneider
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=0a31dd5 ]
GEODE-8384: fix SETEX error message (#5402)
> SETEX error message should be consistent with native redis
> --
>
> Key: GEODE-8384
> URL: https://issues.apache.org/jira/browse/GEODE-8384
> Project: Geode
> Issue Type: Bug
> Components: redis
>Reporter: Darrel Schneider
>Assignee: Darrel Schneider
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.14.0
>
>
> When we pass a negative expiration to SETEX on native redis we get the
> following error message:
>
> {{ERR invalid expire time in setex}}
> When we pass a negative expiration to SETEX on geode redis we get the
> following error message:
>
> {{ERR The expiration argument must be greater than 0}}
> These error messages should match.
> Revert the following native Redis test back to its original form:
>
> {{test \{SETEX - Wrong time parameter}}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-8395) gfsh --help shows incorrect product name
[ https://issues.apache.org/jira/browse/GEODE-8395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170245#comment-17170245 ] ASF subversion and git services commented on GEODE-8395: Commit 54421c4cd5ddde9e459f544fef9f27b44fa1ab6c in geode's branch refs/heads/feature/GEODE-7665 from Owen Nichols [ https://gitbox.apache.org/repos/asf?p=geode.git;h=54421c4 ] GEODE-8395: fix product name in gfsh help banner (#5417) > gfsh --help shows incorrect product name > > > Key: GEODE-8395 > URL: https://issues.apache.org/jira/browse/GEODE-8395 > Project: Geode > Issue Type: Bug > Components: gfsh >Reporter: Owen Nichols >Priority: Major > Labels: pull-request-available > Fix For: 1.12.1, 1.13.0, 1.14.0 > > > Expected: > gfsh --help > Apache Geode v1.14.0 Command Line Shell > Actual: > gfsh --help > Pivotal GemFire(R) v1.14.0 Command Line Shell > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8372) Configure CMS to send UTF-8 regardless of JVM default
[
https://issues.apache.org/jira/browse/GEODE-8372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170240#comment-17170240
]
ASF subversion and git services commented on GEODE-8372:
Commit 1f1bd1adb2b40e69b112900d04350b4cdbcc0d66 in geode's branch
refs/heads/feature/GEODE-7665 from Jinmei Liao
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=1f1bd1a ]
GEODE-8372: Configure CMS to send UTF-8 regardless of JVM default (#5411)
> Configure CMS to send UTF-8 regardless of JVM default
> -
>
> Key: GEODE-8372
> URL: https://issues.apache.org/jira/browse/GEODE-8372
> Project: Geode
> Issue Type: Bug
> Components: management
>Reporter: Dale Emery
>Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
>
> In a client, CMS accepts only UTF-8 messages from the locator. But the
> locator can send non-UTF-8 messages depending on how the JVM and OS are
> configured.
> It looks as if the locator CMS uses the JVM's default character encoding, and
> the JVM sets its default character encoding based on the operating system's
> default locale.
> If a client CMS accepts only UTF-8, the locator CMS should send only UTF-8,
> regardless of the JVM's default character encoding.
> Example: I have a test client that uses a {{ClientClusterManagementService}}
> to create a region. The locator, runs on a machine where the default locale
> is us_EN.US-ASCII, sends US-ASCII responses. The client throws an
> {{UnknownContentTypeException}}:
> {noformat}
> org.springframework.web.client.UnknownContentTypeException: Could not extract
> response: no suitable HttpMessageConverter found for response type [class
> org.apache.geode.management.api.ClusterManagementRealizationResult] and
> content type [application/json;charset=US-ASCII]
> at
> org.springframework.web.client.HttpMessageConverterExtractor.extractData(HttpMessageConverterExtractor.java:126)
> ~[spring-web-5.2.7.RELEASE.jar:5.2.7.RELEASE]
> at
> org.springframework.web.client.RestTemplate$ResponseEntityResponseExtractor.extractData(RestTemplate.java:998)
> ~[spring-web-5.2.7.RELEASE.jar:5.2.7.RELEASE]
> at
> org.springframework.web.client.RestTemplate$ResponseEntityResponseExtractor.extractData(RestTemplate.java:981)
> ~[spring-web-5.2.7.RELEASE.jar:5.2.7.RELEASE]
> at
> org.springframework.web.client.RestTemplate.doExecute(RestTemplate.java:741)
> ~[spring-web-5.2.7.RELEASE.jar:5.2.7.RELEASE]
> at
> org.springframework.web.client.RestTemplate.execute(RestTemplate.java:674)
> ~[spring-web-5.2.7.RELEASE.jar:5.2.7.RELEASE]
> at
> org.springframework.web.client.RestTemplate.exchange(RestTemplate.java:583)
> ~[spring-web-5.2.7.RELEASE.jar:5.2.7.RELEASE]
> at
> org.apache.geode.management.api.RestTemplateClusterManagementServiceTransport.create(RestTemplateClusterManagementServiceTransport.java:248)
> ~[geode-management-1.12.0.jar:na]
> at
> org.apache.geode.management.api.RestTemplateClusterManagementServiceTransport.submitMessage(RestTemplateClusterManagementServiceTransport.java:153)
> ~[geode-management-1.12.0.jar:na]
> at
> org.apache.geode.management.internal.ClientClusterManagementService.create(ClientClusterManagementService.java:64)
> ~[geode-management-1.12.0.jar:na]
> at
> org.apache.geode.kubernetes.client.service.AsyncOperationService.createRegion(AsyncOperationService.java:46)
> ~[main/:na]
> at
> org.apache.geode.kubernetes.client.api.Controller.createRegion(Controller.java:27)
> ~[main/:na]
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method) ~[na:na]
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> ~[na:na]
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> ~[na:na]
> at java.base/java.lang.reflect.Method.invoke(Method.java:566) ~[na:na]
> at
> org.springframework.web.method.support.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:190)
> ~[spring-web-5.2.7.RELEASE.jar:5.2.7.RELEASE]
> at
> org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:138)
> ~[spring-web-5.2.7.RELEASE.jar:5.2.7.RELEASE]
> at
> org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:105)
> ~[spring-webmvc-5.2.7.RELEASE.jar:5.2.7.RELEASE]
> at
> org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:879)
> ~[spring-webmvc-5.2.7.RELEASE.jar:5.2.7.RELEASE]
> at
>
[jira] [Commented] (GEODE-8333) Fix PUBSUB hang
[ https://issues.apache.org/jira/browse/GEODE-8333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170239#comment-17170239 ] ASF subversion and git services commented on GEODE-8333: Commit 95bba9a7af10e2bd02febbc7c35bb2f16bb9e414 in geode's branch refs/heads/feature/GEODE-7665 from Darrel Schneider [ https://gitbox.apache.org/repos/asf?p=geode.git;h=95bba9a ] Revert "GEODE-8333: Fix PUBSUB hang (#5349)" (#5415) This reverts commit 067194e8f82414b6103c4335beb6567947edcfbc. The fix for GEODE-8333 had a bug in which responses to the client could be out of order. > Fix PUBSUB hang > --- > > Key: GEODE-8333 > URL: https://issues.apache.org/jira/browse/GEODE-8333 > Project: Geode > Issue Type: Bug > Components: redis >Reporter: Sarah Abbey >Assignee: Darrel Schneider >Priority: Major > Labels: pull-request-available > Fix For: 1.14.0 > > > PUBSUB hangs with concurrent publishers and subscribers on multiple servers. > The initial fix is being reverted because it caused a bug in which responses > to clients could now be out of order. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8386) SRANDMEMBER with negative count should return that many members
[
https://issues.apache.org/jira/browse/GEODE-8386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170243#comment-17170243
]
ASF subversion and git services commented on GEODE-8386:
Commit 42c086b6578b6f0f768a3ff9ead627fbe70abf22 in geode's branch
refs/heads/feature/GEODE-7665 from Darrel Schneider
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=42c086b ]
GEODE-8386: fix SRANDMEMBER with negative count (#5404)
> SRANDMEMBER with negative count should return that many members
> ---
>
> Key: GEODE-8386
> URL: https://issues.apache.org/jira/browse/GEODE-8386
> Project: Geode
> Issue Type: Bug
> Components: redis
>Reporter: Darrel Schneider
>Assignee: Darrel Schneider
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.14.0
>
>
> When SRANDMEMBER is sent a negative count, it should return a number of items
> equal to the absolute value. uniqueness is not guaranteed.
>
> {{SADD abc 123 456
> SRANDMEMBER abc -1 -> 123
> SRANDMEMBER abc -2 -> 123, 123 OR 123, 456, 456, 123 OR 456, 456
> SRANDMEMBER abc -5 -> 123,123,456,123,456 OR any one of the 2^5
> combinations...}}
> see the redis unit tests and docs: unit/type/set -> SRANDMEMBER with
> - hashtable
> and documentation: [https://redis.io/commands/srandmember]
> Currently, Geode Redis returns only up to as many members as there are in the
> set.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-8333) Fix PUBSUB hang
[ https://issues.apache.org/jira/browse/GEODE-8333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170249#comment-17170249 ] ASF subversion and git services commented on GEODE-8333: Commit 95bba9a7af10e2bd02febbc7c35bb2f16bb9e414 in geode's branch refs/heads/feature/GEODE-7665 from Darrel Schneider [ https://gitbox.apache.org/repos/asf?p=geode.git;h=95bba9a ] Revert "GEODE-8333: Fix PUBSUB hang (#5349)" (#5415) This reverts commit 067194e8f82414b6103c4335beb6567947edcfbc. The fix for GEODE-8333 had a bug in which responses to the client could be out of order. > Fix PUBSUB hang > --- > > Key: GEODE-8333 > URL: https://issues.apache.org/jira/browse/GEODE-8333 > Project: Geode > Issue Type: Bug > Components: redis >Reporter: Sarah Abbey >Assignee: Darrel Schneider >Priority: Major > Labels: pull-request-available > Fix For: 1.14.0 > > > PUBSUB hangs with concurrent publishers and subscribers on multiple servers. > The initial fix is being reverted because it caused a bug in which responses > to clients could now be out of order. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8387) SUNIONSTORE, SINTERSTORE, and SDIFFSTORE should delete the target key if the computed set is empty
[ https://issues.apache.org/jira/browse/GEODE-8387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170244#comment-17170244 ] ASF subversion and git services commented on GEODE-8387: Commit dec583b9411664c4db55c4ee4651a80cfe8a51a7 in geode's branch refs/heads/feature/GEODE-7665 from Darrel Schneider [ https://gitbox.apache.org/repos/asf?p=geode.git;h=dec583b ] GEODE-8387: fix SET*STORE commands handling of empty results (#5405) > SUNIONSTORE, SINTERSTORE, and SDIFFSTORE should delete the target key if the > computed set is empty > -- > > Key: GEODE-8387 > URL: https://issues.apache.org/jira/browse/GEODE-8387 > Project: Geode > Issue Type: Bug > Components: redis >Reporter: Darrel Schneider >Priority: Major > Labels: pull-request-available > Fix For: 1.14.0 > > > The current impl of SUNIONSTORE, SINTERSTORE, and SDIFFSTORE set the > destination to an empty set if the computed set is empty. But they should > instead in that case delete the destination. This is true if the read keys do > not exist. > If the read keys exist but are not sets then the commands should fail with a > WRONGTYPE error. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8331) allow GFSH to connect to newer and older locator/server.
[ https://issues.apache.org/jira/browse/GEODE-8331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170237#comment-17170237 ] ASF subversion and git services commented on GEODE-8331: Commit 4cea8621f535e48d2879317af18878998c32 in geode's branch refs/heads/feature/GEODE-7665 from Dave Barnes [ https://gitbox.apache.org/repos/asf?p=geode.git;h=4cea862 ] GEODE-8331: allow GFSH to connect to other versions of cluster (doc correction) (#5410) > allow GFSH to connect to newer and older locator/server. > > > Key: GEODE-8331 > URL: https://issues.apache.org/jira/browse/GEODE-8331 > Project: Geode > Issue Type: Bug > Components: docs, gfsh >Reporter: Jinmei Liao >Priority: Major > Labels: GeodeOperationAPI, pull-request-available > Fix For: 1.12.1, 1.13.0, 1.14.0 > > > When using an older or newer gfsh to connect to an older or newer distributed > system gfsh will throw a warning error and not connect. > Example warning message Cannot use a 9.8.5 gfsh client to connect to a 9.9.0 > cluster.. > The desired behavior is to allow gfsh connect and only if there is an issue > with an updated /unknown command parsing should the system throw an error and > provide the extra guidance of what version the servers are at and the version > of the current gfsh cli. > Initially add these capability into the newer product version > Later based on the feasibility of adding this to older version, this will be > ported into the older version. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8395) gfsh --help shows incorrect product name
[ https://issues.apache.org/jira/browse/GEODE-8395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170256#comment-17170256 ] ASF subversion and git services commented on GEODE-8395: Commit 54421c4cd5ddde9e459f544fef9f27b44fa1ab6c in geode's branch refs/heads/feature/GEODE-7665 from Owen Nichols [ https://gitbox.apache.org/repos/asf?p=geode.git;h=54421c4 ] GEODE-8395: fix product name in gfsh help banner (#5417) > gfsh --help shows incorrect product name > > > Key: GEODE-8395 > URL: https://issues.apache.org/jira/browse/GEODE-8395 > Project: Geode > Issue Type: Bug > Components: gfsh >Reporter: Owen Nichols >Priority: Major > Labels: pull-request-available > Fix For: 1.12.1, 1.13.0, 1.14.0 > > > Expected: > gfsh --help > Apache Geode v1.14.0 Command Line Shell > Actual: > gfsh --help > Pivotal GemFire(R) v1.14.0 Command Line Shell > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8331) allow GFSH to connect to newer and older locator/server.
[ https://issues.apache.org/jira/browse/GEODE-8331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170246#comment-17170246 ] ASF subversion and git services commented on GEODE-8331: Commit de6ab7aa433af0384b9f48ff76b734a901df2a09 in geode's branch refs/heads/feature/GEODE-7665 from Jinmei Liao [ https://gitbox.apache.org/repos/asf?p=geode.git;h=de6ab7a ] GEODE-8331: allow GFSH to connect to other versions of cluster (#5408) * GEODE-8331: allow GFSH to connect to other versions of cluster * doc change * Update connect.html.md.erb Co-authored-by: Dave Barnes > allow GFSH to connect to newer and older locator/server. > > > Key: GEODE-8331 > URL: https://issues.apache.org/jira/browse/GEODE-8331 > Project: Geode > Issue Type: Bug > Components: docs, gfsh >Reporter: Jinmei Liao >Priority: Major > Labels: GeodeOperationAPI, pull-request-available > Fix For: 1.12.1, 1.13.0, 1.14.0 > > > When using an older or newer gfsh to connect to an older or newer distributed > system gfsh will throw a warning error and not connect. > Example warning message Cannot use a 9.8.5 gfsh client to connect to a 9.9.0 > cluster.. > The desired behavior is to allow gfsh connect and only if there is an issue > with an updated /unknown command parsing should the system throw an error and > provide the extra guidance of what version the servers are at and the version > of the current gfsh cli. > Initially add these capability into the newer product version > Later based on the feasibility of adding this to older version, this will be > ported into the older version. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8384) SETEX error message should be consistent with native redis
[
https://issues.apache.org/jira/browse/GEODE-8384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170253#comment-17170253
]
ASF subversion and git services commented on GEODE-8384:
Commit 0a31dd5de4bfe4402e86505f5a65fbe46c48c72b in geode's branch
refs/heads/feature/GEODE-7665 from Darrel Schneider
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=0a31dd5 ]
GEODE-8384: fix SETEX error message (#5402)
> SETEX error message should be consistent with native redis
> --
>
> Key: GEODE-8384
> URL: https://issues.apache.org/jira/browse/GEODE-8384
> Project: Geode
> Issue Type: Bug
> Components: redis
>Reporter: Darrel Schneider
>Assignee: Darrel Schneider
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.14.0
>
>
> When we pass a negative expiration to SETEX on native redis we get the
> following error message:
>
> {{ERR invalid expire time in setex}}
> When we pass a negative expiration to SETEX on geode redis we get the
> following error message:
>
> {{ERR The expiration argument must be greater than 0}}
> These error messages should match.
> Revert the following native Redis test back to its original form:
>
> {{test \{SETEX - Wrong time parameter}}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-8331) allow GFSH to connect to newer and older locator/server.
[ https://issues.apache.org/jira/browse/GEODE-8331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170247#comment-17170247 ] ASF subversion and git services commented on GEODE-8331: Commit de6ab7aa433af0384b9f48ff76b734a901df2a09 in geode's branch refs/heads/feature/GEODE-7665 from Jinmei Liao [ https://gitbox.apache.org/repos/asf?p=geode.git;h=de6ab7a ] GEODE-8331: allow GFSH to connect to other versions of cluster (#5408) * GEODE-8331: allow GFSH to connect to other versions of cluster * doc change * Update connect.html.md.erb Co-authored-by: Dave Barnes > allow GFSH to connect to newer and older locator/server. > > > Key: GEODE-8331 > URL: https://issues.apache.org/jira/browse/GEODE-8331 > Project: Geode > Issue Type: Bug > Components: docs, gfsh >Reporter: Jinmei Liao >Priority: Major > Labels: GeodeOperationAPI, pull-request-available > Fix For: 1.12.1, 1.13.0, 1.14.0 > > > When using an older or newer gfsh to connect to an older or newer distributed > system gfsh will throw a warning error and not connect. > Example warning message Cannot use a 9.8.5 gfsh client to connect to a 9.9.0 > cluster.. > The desired behavior is to allow gfsh connect and only if there is an issue > with an updated /unknown command parsing should the system throw an error and > provide the extra guidance of what version the servers are at and the version > of the current gfsh cli. > Initially add these capability into the newer product version > Later based on the feasibility of adding this to older version, this will be > ported into the older version. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8331) allow GFSH to connect to newer and older locator/server.
[ https://issues.apache.org/jira/browse/GEODE-8331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170235#comment-17170235 ] ASF subversion and git services commented on GEODE-8331: Commit de6ab7aa433af0384b9f48ff76b734a901df2a09 in geode's branch refs/heads/feature/GEODE-7665 from Jinmei Liao [ https://gitbox.apache.org/repos/asf?p=geode.git;h=de6ab7a ] GEODE-8331: allow GFSH to connect to other versions of cluster (#5408) * GEODE-8331: allow GFSH to connect to other versions of cluster * doc change * Update connect.html.md.erb Co-authored-by: Dave Barnes > allow GFSH to connect to newer and older locator/server. > > > Key: GEODE-8331 > URL: https://issues.apache.org/jira/browse/GEODE-8331 > Project: Geode > Issue Type: Bug > Components: docs, gfsh >Reporter: Jinmei Liao >Priority: Major > Labels: GeodeOperationAPI, pull-request-available > Fix For: 1.12.1, 1.13.0, 1.14.0 > > > When using an older or newer gfsh to connect to an older or newer distributed > system gfsh will throw a warning error and not connect. > Example warning message Cannot use a 9.8.5 gfsh client to connect to a 9.9.0 > cluster.. > The desired behavior is to allow gfsh connect and only if there is an issue > with an updated /unknown command parsing should the system throw an error and > provide the extra guidance of what version the servers are at and the version > of the current gfsh cli. > Initially add these capability into the newer product version > Later based on the feasibility of adding this to older version, this will be > ported into the older version. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8331) allow GFSH to connect to newer and older locator/server.
[ https://issues.apache.org/jira/browse/GEODE-8331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170236#comment-17170236 ] ASF subversion and git services commented on GEODE-8331: Commit de6ab7aa433af0384b9f48ff76b734a901df2a09 in geode's branch refs/heads/feature/GEODE-7665 from Jinmei Liao [ https://gitbox.apache.org/repos/asf?p=geode.git;h=de6ab7a ] GEODE-8331: allow GFSH to connect to other versions of cluster (#5408) * GEODE-8331: allow GFSH to connect to other versions of cluster * doc change * Update connect.html.md.erb Co-authored-by: Dave Barnes > allow GFSH to connect to newer and older locator/server. > > > Key: GEODE-8331 > URL: https://issues.apache.org/jira/browse/GEODE-8331 > Project: Geode > Issue Type: Bug > Components: docs, gfsh >Reporter: Jinmei Liao >Priority: Major > Labels: GeodeOperationAPI, pull-request-available > Fix For: 1.12.1, 1.13.0, 1.14.0 > > > When using an older or newer gfsh to connect to an older or newer distributed > system gfsh will throw a warning error and not connect. > Example warning message Cannot use a 9.8.5 gfsh client to connect to a 9.9.0 > cluster.. > The desired behavior is to allow gfsh connect and only if there is an issue > with an updated /unknown command parsing should the system throw an error and > provide the extra guidance of what version the servers are at and the version > of the current gfsh cli. > Initially add these capability into the newer product version > Later based on the feasibility of adding this to older version, this will be > ported into the older version. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8400) NullPointerException in AbstractCommitSessionValve.commitSession
[
https://issues.apache.org/jira/browse/GEODE-8400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170335#comment-17170335
]
Eric Shu commented on GEODE-8400:
-
Please also see GEODE-8221, which Jake mentioned it should be addressed.
{code:java}
protected static > void
commitSession(
final Request request) {
final Context context = request.getContext();
-->final Manager manager = context.getManager();
{code}
NPE thrown is because context is returned null.
Artifacts can be found in
http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0255/test-results/distributedTest/1596348822/
http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0255/test-artifacts/1596348822/distributedtestfiles-OpenJDK8-1.14.0-build.0255.tgz
> NullPointerException in AbstractCommitSessionValve.commitSession
>
>
> Key: GEODE-8400
> URL: https://issues.apache.org/jira/browse/GEODE-8400
> Project: Geode
> Issue Type: Bug
> Components: http session
>Reporter: Eric Shu
>Priority: Major
>
> {noformat}
> java.lang.RuntimeException:
> /home/geode/geode/geode-assembly/build/distributedTest329/cargo_logs/TOMCAT8_client-server_attributesCanBeReplaced_0_d46a2c34-8a55-4c2f-9789-01bd35afb728/container.log
> contains java.lang.NullPointerException
> at
> org.apache.geode.session.tests.LogChecker.checkLogs(LogChecker.java:87)
> at
> org.apache.geode.session.tests.LogChecker.checkLogs(LogChecker.java:44)
> at
> org.apache.geode.session.tests.CargoTestBase.checkLogs(CargoTestBase.java:412)
> at
> org.apache.geode.session.tests.CargoTestBase.attributesCanBeReplaced(CargoTestBase.java:406)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at
> org.apache.geode.test.junit.rules.DescribedExternalResource$1.evaluate(DescribedExternalResource.java:40)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule$1.evaluate(ClusterStartupRule.java:138)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> {noformat}
> The NPE occurs here:
> {noformat}
> Aug 02, 2020 4:45:10 AM org.apache.coyote.http11.Http11Processor service
> SEVERE: Error processing request
> java.lang.NullPointerException
> at
> org.apache.geode.modules.session.catalina.AbstractCommitSessionValve.commitSession(AbstractCommitSessionValve.java:61)
> at
> org.apache.geode.modules.session.catalina.Tomcat8CommitSessionValve.lambda$wrapResponse$0(Tomcat8CommitSessionValve.java:45)
> at
> org.apache.geode.modules.session.catalina.Tomcat8CommitSessionOutputBuffer.doWrite(Tomcat8CommitSessionOutputBuffer.java:48)
> at org.apache.coyote.Response.doWrite(Response.java:600)
> at
> org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:360)
> at
> org.apache.catalina.connector.OutputBuffer.flushByteBuffer(OutputBuffer.java:841)
> at
> org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:319)
> at
> org.apache.catalina.connector.OutputBuffer.close(OutputBuffer.java:272)
> at
>
[jira] [Commented] (GEODE-8293) activeCQCount has negative value
[
https://issues.apache.org/jira/browse/GEODE-8293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17169848#comment-17169848
]
ASF GitHub Bot commented on GEODE-8293:
---
mkevo commented on a change in pull request #5397:
URL: https://github.com/apache/geode/pull/5397#discussion_r464297701
##
File path:
geode-cq/src/main/java/org/apache/geode/cache/query/cq/internal/ServerCQImpl.java
##
@@ -367,10 +367,12 @@ public void close(boolean sendRequestToServer) throws
CqClosedException, CqExcep
this.removeFromCqMap();
// Stat update.
- if (stateBeforeClosing == CqStateImpl.RUNNING) {
-cqService.stats().decCqsActive();
- } else if (stateBeforeClosing == CqStateImpl.STOPPED) {
-cqService.stats().decCqsStopped();
+ if (!cqName.equals(serverCqName)) {
Review comment:
I need somehow to makes difference between servers, one on which cq is
register and others on which it will process registerCq. The server on which cq
is registered doing also incrementing active activeCqCount, but while closing
or stopping it decrements on all, but with this check it will decrement just on
the one server where it is incremented. I'm not sure if this is a good check
but it works, and I asked on dev list for a help to differentiate on which
decrement is needed, but It is concluded that this is a bug but without any
idea how to differentiate it.
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
> activeCQCount has negative value
>
>
> Key: GEODE-8293
> URL: https://issues.apache.org/jira/browse/GEODE-8293
> Project: Geode
> Issue Type: Bug
> Components: statistics
>Reporter: Mario Kevo
>Assignee: Mario Kevo
>Priority: Major
> Labels: pull-request-available
>
> In case you have more than one server in the system and you close CQ there
> will be negative value of active cqs.
> The problem is when you started more than one server and execute cq on it. In
> that case we got incCqsActive on one server, but when it is closed we have
> decCqsActive on both servers.
> {code:java}
> gfsh>show metrics --categories=query
> Cluster-wide MetricsCategory | Metric | Value
> | | -
> query| activeCQCount| 1
> | queryRequestRate | 0.0
> {code}
> After cq is closed or stopped:
> {code:java}
> gfsh>show metrics --categories=query
> Cluster-wide Metrics
> Category | Metric | Value
> | | -
> query| activeCQCount| -1
> | queryRequestRate | 0.0
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-8395) gfsh --help shows incorrect product name
[ https://issues.apache.org/jira/browse/GEODE-8395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen Nichols updated GEODE-8395: Fix Version/s: 1.13.0 1.12.1 > gfsh --help shows incorrect product name > > > Key: GEODE-8395 > URL: https://issues.apache.org/jira/browse/GEODE-8395 > Project: Geode > Issue Type: Bug > Components: gfsh >Reporter: Owen Nichols >Priority: Major > Labels: pull-request-available > Fix For: 1.12.1, 1.13.0, 1.14.0 > > > Expected: > gfsh --help > Apache Geode v1.14.0 Command Line Shell > Actual: > gfsh --help > Pivotal GemFire(R) v1.14.0 Command Line Shell > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7846) Clear in Partitioned Region should have its own stats
[
https://issues.apache.org/jira/browse/GEODE-7846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170215#comment-17170215
]
ASF GitHub Bot commented on GEODE-7846:
---
gesterzhou commented on a change in pull request #5391:
URL: https://github.com/apache/geode/pull/5391#discussion_r464551192
##
File path:
geode-core/src/main/java/org/apache/geode/internal/cache/AbstractRegionMap.java
##
@@ -344,7 +344,12 @@ void incClearCount(LocalRegion lr) {
if (lr != null && !(lr instanceof HARegion)) {
CachePerfStats stats = lr.getCachePerfStats();
if (stats != null) {
-stats.incClearCount();
+if (lr instanceof BucketRegion) {
Review comment:
Usually we use: if (owner.isUsedForPartitionedRegionBucket()) {
instead.
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
> Clear in Partitioned Region should have its own stats
> -
>
> Key: GEODE-7846
> URL: https://issues.apache.org/jira/browse/GEODE-7846
> Project: Geode
> Issue Type: Improvement
> Components: core
>Reporter: Xiaojian Zhou
>Priority: Major
> Labels: GeodeCommons, GeodeOperationAPI, pull-request-available
>
> Clear operation in PR should have its own stats:
> 1) clear operation executed.
> 2) clear operation failed
> 3) clear messages sends to buckets
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-8397) extend PoolFactoryAPI to support SNI proxy
Ernest Burghardt created GEODE-8397: --- Summary: extend PoolFactoryAPI to support SNI proxy Key: GEODE-8397 URL: https://issues.apache.org/jira/browse/GEODE-8397 Project: Geode Issue Type: New Feature Components: native client Reporter: Ernest Burghardt clicache -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-8398) CLONE - extend PoolFactoryAPI to support SNI proxy
Ernest Burghardt created GEODE-8398: --- Summary: CLONE - extend PoolFactoryAPI to support SNI proxy Key: GEODE-8398 URL: https://issues.apache.org/jira/browse/GEODE-8398 Project: Geode Issue Type: New Feature Components: native client Reporter: Ernest Burghardt clicache -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7669) Test coverage for Partitioned Region clear with Overflow enabled
[ https://issues.apache.org/jira/browse/GEODE-7669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170270#comment-17170270 ] ASF subversion and git services commented on GEODE-7669: Commit ddffddc6467d6ba557c5b1c799657a30d1a9c525 in geode's branch refs/heads/feature/GEODE-7665 from Jianxia Chen [ https://gitbox.apache.org/repos/asf?p=geode.git;h=ddffddc ] GEODE-7669 Test coverage for Partitioned Region clear with Overflow enabled (#5189) Authored-by: Jianxia Chen > Test coverage for Partitioned Region clear with Overflow enabled > > > Key: GEODE-7669 > URL: https://issues.apache.org/jira/browse/GEODE-7669 > Project: Geode > Issue Type: Sub-task > Components: regions >Reporter: Nabarun Nag >Assignee: Jianxia Chen >Priority: Major > Labels: GeodeCommons, GeodeOperationAPI > > Using TDD ensure that clear operations are successful when the partitioned > regions have overflow enabled. > Make the code changes required to enable this. > > Acceptance : > * Passing DUnit tests where clear operations are successful on partitioned > region with overflow enabled. > * Ensure that data has overflown when the clear operation is executed and in > the end everything is cleared. > * These tests should have redundancy of more than zero > * 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. > Note: > analyze if these tests are needed for offheap? > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8334) Primary and secondary bucket data mismatch with concurrent putAll/removeAll and PR.clear
[ https://issues.apache.org/jira/browse/GEODE-8334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170273#comment-17170273 ] ASF subversion and git services commented on GEODE-8334: Commit 9a67231f5a107cf019af551f5a94d1ce49614d94 in geode's branch refs/heads/feature/GEODE-7665 from Xiaojian Zhou [ https://gitbox.apache.org/repos/asf?p=geode.git;h=9a67231 ] GEODE-8334: PR.clear should sync with putAll or removeAll on rvvLock (#5365) Co-authored-by: Xiaojian Zhou Co-authored-by: Anil Gingade > Primary and secondary bucket data mismatch with concurrent putAll/removeAll > and PR.clear > - > > Key: GEODE-8334 > URL: https://issues.apache.org/jira/browse/GEODE-8334 > Project: Geode > Issue Type: Sub-task > Components: regions >Affects Versions: 1.14.0 >Reporter: Xiaojian Zhou >Assignee: Xiaojian Zhou >Priority: Major > Labels: GeodeOperationAPI > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7676) All expiration tasks are cleared after a Partitioned Region is cleared
[ https://issues.apache.org/jira/browse/GEODE-7676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170265#comment-17170265 ] ASF subversion and git services commented on GEODE-7676: Commit 0dcf0ef2b54ddf90e499fcbbee6426077790f07a in geode's branch refs/heads/feature/GEODE-7665 from Nabarun Nag [ https://gitbox.apache.org/repos/asf?p=geode.git;h=0dcf0ef ] GEODE-7676: Conversion of duration to seconds. > All expiration tasks are cleared after a Partitioned Region is cleared > -- > > Key: GEODE-7676 > URL: https://issues.apache.org/jira/browse/GEODE-7676 > Project: Geode > Issue Type: Sub-task > Components: regions >Reporter: Nabarun Nag >Assignee: Juan Ramos >Priority: Major > Labels: GeodeCommons, feature/GEODE-7665 > Time Spent: 1h 50m > Remaining Estimate: 0h > > Clear operations are successful and all the expiration tasks are cleared in > the bucket level > Acceptance : > * DUnit tests ensuring that clear operations are successful > * Expiration tasks are cleared. > * 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-7680) Partitioned region clear operations must be successful while interacting with rebalance
[ https://issues.apache.org/jira/browse/GEODE-7680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170276#comment-17170276 ] ASF subversion and git services commented on GEODE-7680: Commit 0cb20cb322000661a466f9f63cb2c107ca1eb5d4 in geode's branch refs/heads/feature/GEODE-7665 from Donal Evans [ https://gitbox.apache.org/repos/asf?p=geode.git;h=0cb20cb ] GEODE-7680: PR.clear must be successful when interacting with rebalance (#5095) - Added DUnit tests to confirm that clear does not interfere with rebalance or vice versa - Test when member departs during clear/rebalance - Test when member joins during clear/rebalance - Fixed typo in PartitionedRegionClearWithExpirationDUnitTest - Fixed typo in PartitionedRegion - Call assignBucketsToPartitions() on leader colocated region during clear instead of target region Authored-by: Donal Evans > Partitioned region clear operations must be successful while interacting with > rebalance > > > Key: GEODE-7680 > URL: https://issues.apache.org/jira/browse/GEODE-7680 > Project: Geode > Issue Type: Sub-task > Components: regions >Reporter: Nabarun Nag >Assignee: Donal Evans >Priority: Major > Labels: GeodeCommons, caching-applications, > pull-request-available > Fix For: 1.14.0 > > > Clear operations are successful and while rebalance operations are ongoing. > 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-8173) Add test coverage for PartitionedRegionClear class
[ https://issues.apache.org/jira/browse/GEODE-8173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170272#comment-17170272 ] ASF subversion and git services commented on GEODE-8173: Commit 862cad919fe6abf03d6bfa33900b7a2b7fc9ee30 in geode's branch refs/heads/feature/GEODE-7665 from agingade [ https://gitbox.apache.org/repos/asf?p=geode.git;h=862cad9 ] GEODE-8173: Add unit test (coverage) for PartitionedRegionClear class. (#5208) * GEODE-8173: Add unit test (coverage) for PartitionedRegionClear class. Co-authored-by: anilkumar gingade > Add test coverage for PartitionedRegionClear class > -- > > Key: GEODE-8173 > URL: https://issues.apache.org/jira/browse/GEODE-8173 > Project: Geode > Issue Type: Bug > Components: regions >Reporter: Anilkumar Gingade >Priority: Major > Labels: GeodeOperationAPI > Fix For: 1.14.0 > > > Add test coverage for PartitionedRegionClear class. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7678) Partitioned Region clear operations must invoke cache level listeners
[ https://issues.apache.org/jira/browse/GEODE-7678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170269#comment-17170269 ] ASF subversion and git services commented on GEODE-7678: Commit 1ecd10ae09fdbd59de85b95b204c3eb2e920de0b in geode's branch refs/heads/feature/GEODE-7665 from agingade [ https://gitbox.apache.org/repos/asf?p=geode.git;h=1ecd10a ] GEODE-7678 (2nd PR) - Support for cache-listener and client-notification for Partitioned Region Clear operation (#5124) * GEODE-7678: Add support for cache listener and client notification for PR clear The changes are made to PR clear messaging and locking mechanism to preserve cache-listener and client-events ordering during concurrent cache operation while clear in progress. > Partitioned Region clear operations must invoke cache level listeners > - > > Key: GEODE-7678 > URL: https://issues.apache.org/jira/browse/GEODE-7678 > Project: Geode > Issue Type: Sub-task > Components: regions >Reporter: Nabarun Nag >Assignee: Anilkumar Gingade >Priority: Major > Labels: GeodeCommons, GeodeOperationAPI > > Clear operations are successful and CacheListener.afterRegionClear(), > CacheWriter.beforeRegionClear() are invoked. > > 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-7670) Partitioned Region clear operations can occur during concurrent data operations
[ https://issues.apache.org/jira/browse/GEODE-7670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170275#comment-17170275 ] ASF subversion and git services commented on GEODE-7670: Commit 45b36413bff34878d295544fe682341640207599 in geode's branch refs/heads/feature/GEODE-7665 from Juan José Ramos [ https://gitbox.apache.org/repos/asf?p=geode.git;h=45b3641 ] GEODE-7670: PR Clear with Concurrent Ops DUnitTests (#4848) Added distributed tests to verify that the clear operation on Partitioned Regions works as expected when there are other concurrent operations happening on the cache (put, putAll, get, remove, removeAll, members added and members removed). > Partitioned Region clear operations can occur during concurrent data > operations > --- > > Key: GEODE-7670 > URL: https://issues.apache.org/jira/browse/GEODE-7670 > Project: Geode > Issue Type: Sub-task > Components: regions >Reporter: Nabarun Nag >Assignee: Juan Ramos >Priority: Major > Labels: GeodeCommons, pull-request-available > Time Spent: 5.5h > Remaining Estimate: 0h > > Clear operations are successful when concurrent read/write operations occur. > Ensure there are test coverage for this use case and modify the code needed > to enable this. > Acceptance : > * Passing DUnit tests where clear operations are successful on partitioned > region with > * concurrent puts (writes) and clear op > * concurrent gets (reads) and clear op > * 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-6564) Clearing a replicated region with expiration causes a memory leak
[
https://issues.apache.org/jira/browse/GEODE-6564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170148#comment-17170148
]
Darrel Schneider commented on GEODE-6564:
-
I think the fix for this is pretty simple. In
LocalRegion.cancelAllEntryExpiryTasks as the values of the entryExpiryTasks map
are iterated, the method needs to also remove each value from the map.
Currently it just cancels the task and purges the scheduler but all this does
is remove the task from the scheduler. It needs to also remove the task from
the entryExpiryTasks map.
> Clearing a replicated region with expiration causes a memory leak
> -
>
> Key: GEODE-6564
> URL: https://issues.apache.org/jira/browse/GEODE-6564
> Project: Geode
> Issue Type: Bug
> Components: regions
>Reporter: Barrett Oglesby
>Priority: Major
>
> Clearing a replicated region with expiration causes a memory leak
> Both the RegionEntries and EntryExpiryTasks are still live after loading
> entries into the region and then clearing it.
> Server Startup:
> {noformat}
> num #instances #bytes class name
> --
> 1: 29856 2797840 [C
> 4: 2038 520600 [B
> Total 187711 10089624
> {noformat}
> Load 100 entries with 600k payload (representing a session):
> {noformat}
> num #instances #bytes class name
> --
> 1: 2496 60666440 [B
> 2: 30157 2828496 [C
> 73: 100 7200
> org.apache.geode.internal.cache.entries.VersionedStatsRegionEntryHeapStringKey1
> 93: 100 4800 org.apache.geode.internal.cache.EntryExpiryTask
> Total 190737 70240472
> {noformat}
> Clear region:
> {noformat}
> num #instances #bytes class name
> --
> 1: 2398 60505944 [B
> 2: 30448 2849456 [C
> 74: 100 7200
> org.apache.geode.internal.cache.entries.VersionedStatsRegionEntryHeapStringKey1
> 100: 100 4800 org.apache.geode.internal.cache.EntryExpiryTask
> Total 192199 70373048
> {noformat}
> Load and clear another 100 entries:
> {noformat}
> num #instances #bytes class name
> --
> 1: 2503 120511688 [B
> 2: 30506 2854384 [C
> 46: 200 14400
> org.apache.geode.internal.cache.entries.VersionedStatsRegionEntryHeapStringKey1
> 61: 200 9600 org.apache.geode.internal.cache.EntryExpiryTask
> Total 193272 130421432
> {noformat}
> Load and clear another 100 entries:
> {noformat}
> num #instances #bytes class name
> --
> 1: 2600 180517240 [B
> 2: 30562 2859584 [C
> 33: 300 21600
> org.apache.geode.internal.cache.entries.VersionedStatsRegionEntryHeapStringKey1
> 47: 300 14400 org.apache.geode.internal.cache.EntryExpiryTask
> Total 194310 190468176
> {noformat}
> A heap dump shows the VersionedStatsRegionEntryHeapStringKey1 instances are
> referenced by the DistributedRegion entryExpiryTasks:
> {noformat}
> --> org.apache.geode.internal.cache.DistributedRegion@0x76adbbb88 (816 bytes)
> (field entryExpiryTasks:)
> --> java.util.concurrent.ConcurrentHashMap@0x76adbc028 (100 bytes) (field
> table:)
> --> [Ljava.util.concurrent.ConcurrentHashMap$Node;@0x76ee85358 (4112 bytes)
> (Element 276 of [Ljava.util.concurrent.ConcurrentHashMap$Node;@0x76ee85358:)
> --> java.util.concurrent.ConcurrentHashMap$Node@0x76edc4e20 (44 bytes) (field
> next:)
> --> java.util.concurrent.ConcurrentHashMap$Node@0x76edc32f0 (44 bytes) (field
> key:)
> -->
> org.apache.geode.internal.cache.entries.VersionedStatsRegionEntryHeapStringKey1@0x76edc3210
> (86 bytes)
> {noformat}
> LocalRegion.cancelAllEntryExpiryTasks is called when the region is cleared:
> {noformat}
> java.lang.Exception: Stack trace
> at java.lang.Thread.dumpStack(Thread.java:1333)
> at
> org.apache.geode.internal.cache.LocalRegion.cancelAllEntryExpiryTasks(LocalRegion.java:8202)
> at
> org.apache.geode.internal.cache.LocalRegion.clearRegionLocally(LocalRegion.java:9094)
> at
> org.apache.geode.internal.cache.DistributedRegion.cmnClearRegion(DistributedRegion.java:1962)
> at
> org.apache.geode.internal.cache.LocalRegion.basicClear(LocalRegion.java:8998)
> at
> org.apache.geode.internal.cache.DistributedRegion.basicClear(DistributedRegion.java:1939)
> at
> org.apache.geode.internal.cache.LocalRegion.basicBridgeClear(LocalRegion.java:8988)
> at
> org.apache.geode.internal.cache.tier.sockets.command.ClearRegion.cmdExecute(ClearRegion.java:123)
> {noformat}
> But it doesn't clear the entryExpiryTasks map:
> {noformat}
> LocalRegion.clearRegionLocally before cancelAllEntryExpiryTasks
> entryExpiryTasks=100
> LocalRegion.clearRegionLocally after cancelAllEntryExpiryTasks
> entryExpiryTasks=100
> {noformat}
> As a test, I added this call to the bottom of the cancelAllEntryExpiryTasks
> method:
> {noformat}
[jira] [Updated] (GEODE-8399) extend PoolFactoryAPI to support SNI proxy
[ https://issues.apache.org/jira/browse/GEODE-8399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernest Burghardt updated GEODE-8399: Summary: extend PoolFactoryAPI to support SNI proxy (was: CLONE - extend PoolFactoryAPI to support SNI proxy) > extend PoolFactoryAPI to support SNI proxy > -- > > Key: GEODE-8399 > URL: https://issues.apache.org/jira/browse/GEODE-8399 > Project: Geode > Issue Type: New Feature > Components: native client >Reporter: Ernest Burghardt >Priority: Major > > cppcache — on boost::asio -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-8399) CLONE - extend PoolFactoryAPI to support SNI proxy
[ https://issues.apache.org/jira/browse/GEODE-8399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernest Burghardt updated GEODE-8399: Description: cppcache — on boost::asio (was: cppcache) > CLONE - extend PoolFactoryAPI to support SNI proxy > -- > > Key: GEODE-8399 > URL: https://issues.apache.org/jira/browse/GEODE-8399 > Project: Geode > Issue Type: New Feature > Components: native client >Reporter: Ernest Burghardt >Priority: Major > > cppcache — on boost::asio -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8382) Run Redis tests against Redis API for Geode
[ https://issues.apache.org/jira/browse/GEODE-8382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170331#comment-17170331 ] ASF GitHub Bot commented on GEODE-8382: --- sabbeyPivotal commented on pull request #5416: URL: https://github.com/apache/geode/pull/5416#issuecomment-668168119 @smgoller @rhoughton-pivot @onichols-pivotal @dickcav 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 > Run Redis tests against Redis API for Geode > --- > > Key: GEODE-8382 > URL: https://issues.apache.org/jira/browse/GEODE-8382 > Project: Geode > Issue Type: New Feature > Components: ci, redis >Reporter: Sarah Abbey >Priority: Major > Labels: pull-request-available > > We would like to run Redis's tests against Redis API for Geode. Tests will > run a separate job in the PR and main pipelines. It has been included in the > 'tests' jinja variables. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-8391) Skip AvailablePort test assertion if host machine does not support it
[
https://issues.apache.org/jira/browse/GEODE-8391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dale Emery resolved GEODE-8391.
---
Fix Version/s: 1.14.0
Resolution: Fixed
> Skip AvailablePort test assertion if host machine does not support it
> -
>
> Key: GEODE-8391
> URL: https://issues.apache.org/jira/browse/GEODE-8391
> Project: Geode
> Issue Type: Test
> Components: tests
>Reporter: Dale Emery
>Assignee: Dale Emery
>Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
> Fix For: 1.14.0
>
>
> One of the assertions in {{AvailablePortJUnitTest.testIsPortAvailable()}}
> assumes that the {{InetAddress}} for the local host is not a loopback
> address. Though this assumption holds in our CI containers, it fails on some
> developer's Macs.
> Change the test to skip this one assertion if the {{InetAddress}} for the
> local host is a loopback address.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (GEODE-8391) Skip AvailablePort test assertion if host machine does not support it
[
https://issues.apache.org/jira/browse/GEODE-8391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dale Emery closed GEODE-8391.
-
> Skip AvailablePort test assertion if host machine does not support it
> -
>
> Key: GEODE-8391
> URL: https://issues.apache.org/jira/browse/GEODE-8391
> Project: Geode
> Issue Type: Test
> Components: tests
>Reporter: Dale Emery
>Assignee: Dale Emery
>Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
> Fix For: 1.14.0
>
>
> One of the assertions in {{AvailablePortJUnitTest.testIsPortAvailable()}}
> assumes that the {{InetAddress}} for the local host is not a loopback
> address. Though this assumption holds in our CI containers, it fails on some
> developer's Macs.
> Change the test to skip this one assertion if the {{InetAddress}} for the
> local host is a loopback address.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (GEODE-8391) Skip AvailablePort test assertion if host machine does not support it
[
https://issues.apache.org/jira/browse/GEODE-8391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dale Emery reassigned GEODE-8391:
-
Assignee: Dale Emery
> Skip AvailablePort test assertion if host machine does not support it
> -
>
> Key: GEODE-8391
> URL: https://issues.apache.org/jira/browse/GEODE-8391
> Project: Geode
> Issue Type: Test
> Components: tests
>Reporter: Dale Emery
>Assignee: Dale Emery
>Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
>
> One of the assertions in {{AvailablePortJUnitTest.testIsPortAvailable()}}
> assumes that the {{InetAddress}} for the local host is not a loopback
> address. Though this assumption holds in our CI containers, it fails on some
> developer's Macs.
> Change the test to skip this one assertion if the {{InetAddress}} for the
> local host is a loopback address.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-8395) gfsh --help shows incorrect product name
[ https://issues.apache.org/jira/browse/GEODE-8395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170145#comment-17170145 ] ASF subversion and git services commented on GEODE-8395: Commit b765c9e56031ee15c7b34b5ac0b6667d6ef003bc in geode's branch refs/heads/support/1.12 from Owen Nichols [ https://gitbox.apache.org/repos/asf?p=geode.git;h=b765c9e ] GEODE-8395: fix product name in gfsh help banner (#5417) (cherry picked from commit 54421c4cd5ddde9e459f544fef9f27b44fa1ab6c) > gfsh --help shows incorrect product name > > > Key: GEODE-8395 > URL: https://issues.apache.org/jira/browse/GEODE-8395 > Project: Geode > Issue Type: Bug > Components: gfsh >Reporter: Owen Nichols >Priority: Major > Labels: pull-request-available > Fix For: 1.14.0 > > > Expected: > gfsh --help > Apache Geode v1.14.0 Command Line Shell > Actual: > gfsh --help > Pivotal GemFire(R) v1.14.0 Command Line Shell > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-6222) CI Failure: GemFireDeadlockDetectorDUnitTest
[
https://issues.apache.org/jira/browse/GEODE-6222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce J Schuchardt reassigned GEODE-6222:
-
Assignee: Bruce J Schuchardt
> CI Failure: GemFireDeadlockDetectorDUnitTest
>
>
> Key: GEODE-6222
> URL: https://issues.apache.org/jira/browse/GEODE-6222
> Project: Geode
> Issue Type: Bug
> Components: distributed lock service
>Affects Versions: 1.9.0
>Reporter: Ken Howe
>Assignee: Bruce J Schuchardt
>Priority: Major
> Labels: flaky
>
> Flaky test failure in
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/247]
> {code:java}
> org.apache.geode.distributed.internal.deadlock.GemFireDeadlockDetectorDUnitTest
> > testDistributedDeadlockWithDLock FAILED
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertTrue(Assert.java:52)
> at
> org.apache.geode.distributed.internal.deadlock.GemFireDeadlockDetectorDUnitTest.testDistributedDeadlockWithDLock(GemFireDeadlockDetectorDUnitTest.java:199)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-8399) CLONE - extend PoolFactoryAPI to support SNI proxy
Ernest Burghardt created GEODE-8399: --- Summary: CLONE - extend PoolFactoryAPI to support SNI proxy Key: GEODE-8399 URL: https://issues.apache.org/jira/browse/GEODE-8399 Project: Geode Issue Type: New Feature Components: native client Reporter: Ernest Burghardt cppcache -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7894) CustomSSLProviderDistributedTest hostNameIsValidatedWhenUsingDefaultContext fails with suspect uncaught DistributedSystemDisconnectedException
[
https://issues.apache.org/jira/browse/GEODE-7894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170304#comment-17170304
]
ASF subversion and git services commented on GEODE-7894:
Commit 16814730977822a903521e2bc89e19206c6d9698 in geode's branch
refs/heads/feature/GEODE-7665 from Nabarun Nag
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=1681473 ]
GEODE-7894: Moving expiry tasks to AbstractRegion.
> CustomSSLProviderDistributedTest hostNameIsValidatedWhenUsingDefaultContext
> fails with suspect uncaught DistributedSystemDisconnectedException
> --
>
> Key: GEODE-7894
> URL: https://issues.apache.org/jira/browse/GEODE-7894
> Project: Geode
> Issue Type: Bug
> Components: membership
>Reporter: Darrel Schneider
>Assignee: Dan Smith
>Priority: Minor
> Labels: flakey
> Fix For: 1.13.0
>
>
> See:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/1663
> {noformat}
> org.apache.geode.cache.client.internal.CustomSSLProviderDistributedTest >
> hostNameIsValidatedWhenUsingDefaultContext FAILED
> java.lang.AssertionError: Suspicious strings were written to the log
> during this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in log4j at line 1654
> [fatal 2020/03/19 17:26:01.806 GMT tid=215] Uncaught
> exception in thread Thread[unused p2p reader,5,RMI Runtime]
> org.apache.geode.distributed.DistributedSystemDisconnectedException:
> Distribution manager on 172.17.0.15(server-1:113):41001 started at Thu
> Mar 19 17:25:57 GMT 2020: Message distribution has terminated
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager$Stopper.generateCancelledException(ClusterDistributionManager.java:2873)
> at
> org.apache.geode.internal.tcp.TCPConduit$Stopper.generateCancelledException(TCPConduit.java:1004)
> at
> org.apache.geode.CancelCriterion.checkCancelInProgress(CancelCriterion.java:83)
> at
> org.apache.geode.internal.tcp.Connection.readMessages(Connection.java:1666)
> at org.apache.geode.internal.tcp.Connection.run(Connection.java:1446)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-7676) All expiration tasks are cleared after a Partitioned Region is cleared
[ https://issues.apache.org/jira/browse/GEODE-7676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170303#comment-17170303 ] ASF subversion and git services commented on GEODE-7676: Commit 0dcf0ef2b54ddf90e499fcbbee6426077790f07a in geode's branch refs/heads/feature/GEODE-7665 from Nabarun Nag [ https://gitbox.apache.org/repos/asf?p=geode.git;h=0dcf0ef ] GEODE-7676: Conversion of duration to seconds. > All expiration tasks are cleared after a Partitioned Region is cleared > -- > > Key: GEODE-7676 > URL: https://issues.apache.org/jira/browse/GEODE-7676 > Project: Geode > Issue Type: Sub-task > Components: regions >Reporter: Nabarun Nag >Assignee: Juan Ramos >Priority: Major > Labels: GeodeCommons, feature/GEODE-7665 > Time Spent: 1h 50m > Remaining Estimate: 0h > > Clear operations are successful and all the expiration tasks are cleared in > the bucket level > Acceptance : > * DUnit tests ensuring that clear operations are successful > * Expiration tasks are cleared. > * 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-8334) Primary and secondary bucket data mismatch with concurrent putAll/removeAll and PR.clear
[ https://issues.apache.org/jira/browse/GEODE-8334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170323#comment-17170323 ] ASF subversion and git services commented on GEODE-8334: Commit 9a67231f5a107cf019af551f5a94d1ce49614d94 in geode's branch refs/heads/feature/GEODE-7665 from Xiaojian Zhou [ https://gitbox.apache.org/repos/asf?p=geode.git;h=9a67231 ] GEODE-8334: PR.clear should sync with putAll or removeAll on rvvLock (#5365) Co-authored-by: Xiaojian Zhou Co-authored-by: Anil Gingade > Primary and secondary bucket data mismatch with concurrent putAll/removeAll > and PR.clear > - > > Key: GEODE-8334 > URL: https://issues.apache.org/jira/browse/GEODE-8334 > Project: Geode > Issue Type: Sub-task > Components: regions >Affects Versions: 1.14.0 >Reporter: Xiaojian Zhou >Assignee: Xiaojian Zhou >Priority: Major > Labels: GeodeOperationAPI > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7680) Partitioned region clear operations must be successful while interacting with rebalance
[ https://issues.apache.org/jira/browse/GEODE-7680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170326#comment-17170326 ] ASF subversion and git services commented on GEODE-7680: Commit 0cb20cb322000661a466f9f63cb2c107ca1eb5d4 in geode's branch refs/heads/feature/GEODE-7665 from Donal Evans [ https://gitbox.apache.org/repos/asf?p=geode.git;h=0cb20cb ] GEODE-7680: PR.clear must be successful when interacting with rebalance (#5095) - Added DUnit tests to confirm that clear does not interfere with rebalance or vice versa - Test when member departs during clear/rebalance - Test when member joins during clear/rebalance - Fixed typo in PartitionedRegionClearWithExpirationDUnitTest - Fixed typo in PartitionedRegion - Call assignBucketsToPartitions() on leader colocated region during clear instead of target region Authored-by: Donal Evans > Partitioned region clear operations must be successful while interacting with > rebalance > > > Key: GEODE-7680 > URL: https://issues.apache.org/jira/browse/GEODE-7680 > Project: Geode > Issue Type: Sub-task > Components: regions >Reporter: Nabarun Nag >Assignee: Donal Evans >Priority: Major > Labels: GeodeCommons, caching-applications, > pull-request-available > Fix For: 1.14.0 > > > Clear operations are successful and while rebalance operations are ongoing. > 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-8361) Incorrect Bucket Count Warning Message Shown
[
https://issues.apache.org/jira/browse/GEODE-8361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170324#comment-17170324
]
ASF subversion and git services commented on GEODE-8361:
Commit d2a974201e23e0f58e90ca9acfb4b7c1f5b23cfe in geode's branch
refs/heads/feature/GEODE-7665 from Donal Evans
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=d2a9742 ]
GEODE-8361: Use Set instead of List to track cleared buckets (#5379)
- Refactor PartitionRegionClear to use Set instead of List
- Some other changes to remove warnings/alerts from PartitionedRegionClear and
PartitionedRegionClearMessage
Authored-by: Donal Evans
> Incorrect Bucket Count Warning Message Shown
>
>
> Key: GEODE-8361
> URL: https://issues.apache.org/jira/browse/GEODE-8361
> Project: Geode
> Issue Type: Sub-task
> Components: logging
>Reporter: Juan Ramos
>Assignee: Donal Evans
>Priority: Trivial
> Labels: pull-request-available
> Fix For: 1.14.0
>
>
> While analysing some failures related to GEODE-7670, I've noticed that
> sometimes we report an incorrect bucket count within the warning message
> logged when the clear didn't complete successfully that could confuse our
> users.
> For this test the partition region always has 13 buckets so, as I user, I
> would never expect to see a bucket count higher than 13 in my logs (no matter
> how many redundant copies I have).
> ---
> Below are some examples:
> {noformat}
> [vm1] [warn 2020/07/15 11:56:17.739 GMT RMI TCP
> Connection(5)-172.17.0.5 tid=0x5f] Unable to clear all the buckets from
> the partitioned region PartitionedRegion, either data (buckets) moved or
> member departed. expected to clear number of buckets: 13 actual cleared: 26
> [vm1] [warn 2020/07/15 11:57:48.403 GMT RMI TCP
> Connection(6)-172.17.0.9 tid=0x10f] Unable to clear all the buckets from
> the partitioned region PartitionedRegion, either data (buckets) moved or
> member departed. expected to clear number of buckets: 13 actual cleared: 14
> [vm0] [warn 2020/07/15 12:07:36.227 GMT RMI TCP
> Connection(32)-172.17.0.25 tid=0x1fe] Unable to clear all the buckets
> from the partitioned region PartitionedRegion, either data (buckets) moved or
> member departed. expected to clear number of buckets: 13 actual cleared: 19
> [vm0] [warn 2020/07/15 12:08:56.277 GMT RMI TCP
> Connection(37)-172.17.0.24 tid=0x2a2] Unable to clear all the buckets
> from the partitioned region PartitionedRegion, either data (buckets) moved or
> member departed. expected to clear number of buckets: 13 actual cleared: 16
> {noformat}
> The full set of artefacts and results:
> {noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-pr/geode-pr-4848/test-results/repeatTest/1594816968/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-pr/geode-pr-4848/test-artifacts/1594816968/stressnewtestfiles-geode-pr-4848.tgz
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-7667) GFSH commands - uniform gfsh command to clear regions
[ https://issues.apache.org/jira/browse/GEODE-7667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170317#comment-17170317 ] ASF subversion and git services commented on GEODE-7667: Commit 7177dae836a912286fe4f9629c511a7241c33bdf in geode's branch refs/heads/feature/GEODE-7665 from Nabarun Nag [ https://gitbox.apache.org/repos/asf?p=geode.git;h=7177dae ] GEODE-7667: Fixing test to include PR clear help text. > GFSH commands - uniform gfsh command to clear regions > - > > Key: GEODE-7667 > URL: https://issues.apache.org/jira/browse/GEODE-7667 > Project: Geode > Issue Type: Sub-task > Components: regions >Reporter: Nabarun Nag >Assignee: Benjamin P Ross >Priority: Major > Labels: GeodeCommons, docs > Time Spent: 5h > Remaining Estimate: 0h > > * Currently, the gfsh command to clear replicated region is called ‘remove > —region=/regionName’. > * Replace this command with ‘clear region —region=regionName’ > * While executing this gfsh command on partitioned regions, this should call > the clear() Java API using the gfsh function execution machinery. > * Point to note is that this command should take into consideration of the > coordinator selection and how this command is distributed to the members > Acceptance : > * There should be ‘clear region —region=/regionName’ gfsh command > * The gfsh command must be documented in the Geode User Guide > * DUnit tests to verify that command can be executed successfully on > PartitionedRegion > * Deprecate the remove command, as remove does not mean clear > * Unit tests with complete code coverage for the newly written code. > * Test coverage to when a member departs in this scenario > * Test coverage to when a member restarts in this scenario -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7670) Partitioned Region clear operations can occur during concurrent data operations
[ https://issues.apache.org/jira/browse/GEODE-7670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170325#comment-17170325 ] ASF subversion and git services commented on GEODE-7670: Commit 45b36413bff34878d295544fe682341640207599 in geode's branch refs/heads/feature/GEODE-7665 from Juan José Ramos [ https://gitbox.apache.org/repos/asf?p=geode.git;h=45b3641 ] GEODE-7670: PR Clear with Concurrent Ops DUnitTests (#4848) Added distributed tests to verify that the clear operation on Partitioned Regions works as expected when there are other concurrent operations happening on the cache (put, putAll, get, remove, removeAll, members added and members removed). > Partitioned Region clear operations can occur during concurrent data > operations > --- > > Key: GEODE-7670 > URL: https://issues.apache.org/jira/browse/GEODE-7670 > Project: Geode > Issue Type: Sub-task > Components: regions >Reporter: Nabarun Nag >Assignee: Juan Ramos >Priority: Major > Labels: GeodeCommons, pull-request-available > Time Spent: 5.5h > Remaining Estimate: 0h > > Clear operations are successful when concurrent read/write operations occur. > Ensure there are test coverage for this use case and modify the code needed > to enable this. > Acceptance : > * Passing DUnit tests where clear operations are successful on partitioned > region with > * concurrent puts (writes) and clear op > * concurrent gets (reads) and clear op > * 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-8173) Add test coverage for PartitionedRegionClear class
[ https://issues.apache.org/jira/browse/GEODE-8173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170310#comment-17170310 ] ASF subversion and git services commented on GEODE-8173: Commit 862cad919fe6abf03d6bfa33900b7a2b7fc9ee30 in geode's branch refs/heads/feature/GEODE-7665 from agingade [ https://gitbox.apache.org/repos/asf?p=geode.git;h=862cad9 ] GEODE-8173: Add unit test (coverage) for PartitionedRegionClear class. (#5208) * GEODE-8173: Add unit test (coverage) for PartitionedRegionClear class. Co-authored-by: anilkumar gingade > Add test coverage for PartitionedRegionClear class > -- > > Key: GEODE-8173 > URL: https://issues.apache.org/jira/browse/GEODE-8173 > Project: Geode > Issue Type: Bug > Components: regions >Reporter: Anilkumar Gingade >Priority: Major > Labels: GeodeOperationAPI > Fix For: 1.14.0 > > > Add test coverage for PartitionedRegionClear class. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7678) Partitioned Region clear operations must invoke cache level listeners
[ https://issues.apache.org/jira/browse/GEODE-7678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170306#comment-17170306 ] ASF subversion and git services commented on GEODE-7678: Commit 1ecd10ae09fdbd59de85b95b204c3eb2e920de0b in geode's branch refs/heads/feature/GEODE-7665 from agingade [ https://gitbox.apache.org/repos/asf?p=geode.git;h=1ecd10a ] GEODE-7678 (2nd PR) - Support for cache-listener and client-notification for Partitioned Region Clear operation (#5124) * GEODE-7678: Add support for cache listener and client notification for PR clear The changes are made to PR clear messaging and locking mechanism to preserve cache-listener and client-events ordering during concurrent cache operation while clear in progress. > Partitioned Region clear operations must invoke cache level listeners > - > > Key: GEODE-7678 > URL: https://issues.apache.org/jira/browse/GEODE-7678 > Project: Geode > Issue Type: Sub-task > Components: regions >Reporter: Nabarun Nag >Assignee: Anilkumar Gingade >Priority: Major > Labels: GeodeCommons, GeodeOperationAPI > > Clear operations are successful and CacheListener.afterRegionClear(), > CacheWriter.beforeRegionClear() are invoked. > > 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-7676) All expiration tasks are cleared after a Partitioned Region is cleared
[ https://issues.apache.org/jira/browse/GEODE-7676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170315#comment-17170315 ] ASF subversion and git services commented on GEODE-7676: Commit 0dcf0ef2b54ddf90e499fcbbee6426077790f07a in geode's branch refs/heads/feature/GEODE-7665 from Nabarun Nag [ https://gitbox.apache.org/repos/asf?p=geode.git;h=0dcf0ef ] GEODE-7676: Conversion of duration to seconds. > All expiration tasks are cleared after a Partitioned Region is cleared > -- > > Key: GEODE-7676 > URL: https://issues.apache.org/jira/browse/GEODE-7676 > Project: Geode > Issue Type: Sub-task > Components: regions >Reporter: Nabarun Nag >Assignee: Juan Ramos >Priority: Major > Labels: GeodeCommons, feature/GEODE-7665 > Time Spent: 1h 50m > Remaining Estimate: 0h > > Clear operations are successful and all the expiration tasks are cleared in > the bucket level > Acceptance : > * DUnit tests ensuring that clear operations are successful > * Expiration tasks are cleared. > * 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-8173) Add test coverage for PartitionedRegionClear class
[ https://issues.apache.org/jira/browse/GEODE-8173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170321#comment-17170321 ] ASF subversion and git services commented on GEODE-8173: Commit 862cad919fe6abf03d6bfa33900b7a2b7fc9ee30 in geode's branch refs/heads/feature/GEODE-7665 from agingade [ https://gitbox.apache.org/repos/asf?p=geode.git;h=862cad9 ] GEODE-8173: Add unit test (coverage) for PartitionedRegionClear class. (#5208) * GEODE-8173: Add unit test (coverage) for PartitionedRegionClear class. Co-authored-by: anilkumar gingade > Add test coverage for PartitionedRegionClear class > -- > > Key: GEODE-8173 > URL: https://issues.apache.org/jira/browse/GEODE-8173 > Project: Geode > Issue Type: Bug > Components: regions >Reporter: Anilkumar Gingade >Priority: Major > Labels: GeodeOperationAPI > Fix For: 1.14.0 > > > Add test coverage for PartitionedRegionClear class. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7894) CustomSSLProviderDistributedTest hostNameIsValidatedWhenUsingDefaultContext fails with suspect uncaught DistributedSystemDisconnectedException
[
https://issues.apache.org/jira/browse/GEODE-7894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170316#comment-17170316
]
ASF subversion and git services commented on GEODE-7894:
Commit 16814730977822a903521e2bc89e19206c6d9698 in geode's branch
refs/heads/feature/GEODE-7665 from Nabarun Nag
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=1681473 ]
GEODE-7894: Moving expiry tasks to AbstractRegion.
> CustomSSLProviderDistributedTest hostNameIsValidatedWhenUsingDefaultContext
> fails with suspect uncaught DistributedSystemDisconnectedException
> --
>
> Key: GEODE-7894
> URL: https://issues.apache.org/jira/browse/GEODE-7894
> Project: Geode
> Issue Type: Bug
> Components: membership
>Reporter: Darrel Schneider
>Assignee: Dan Smith
>Priority: Minor
> Labels: flakey
> Fix For: 1.13.0
>
>
> See:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/1663
> {noformat}
> org.apache.geode.cache.client.internal.CustomSSLProviderDistributedTest >
> hostNameIsValidatedWhenUsingDefaultContext FAILED
> java.lang.AssertionError: Suspicious strings were written to the log
> during this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in log4j at line 1654
> [fatal 2020/03/19 17:26:01.806 GMT tid=215] Uncaught
> exception in thread Thread[unused p2p reader,5,RMI Runtime]
> org.apache.geode.distributed.DistributedSystemDisconnectedException:
> Distribution manager on 172.17.0.15(server-1:113):41001 started at Thu
> Mar 19 17:25:57 GMT 2020: Message distribution has terminated
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager$Stopper.generateCancelledException(ClusterDistributionManager.java:2873)
> at
> org.apache.geode.internal.tcp.TCPConduit$Stopper.generateCancelledException(TCPConduit.java:1004)
> at
> org.apache.geode.CancelCriterion.checkCancelInProgress(CancelCriterion.java:83)
> at
> org.apache.geode.internal.tcp.Connection.readMessages(Connection.java:1666)
> at org.apache.geode.internal.tcp.Connection.run(Connection.java:1446)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
