[jira] [Updated] (GEODE-9952) Implement LSET
[ https://issues.apache.org/jira/browse/GEODE-9952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hale Bales updated GEODE-9952: -- Fix Version/s: 1.15.0 > Implement LSET > -- > > Key: GEODE-9952 > URL: https://issues.apache.org/jira/browse/GEODE-9952 > Project: Geode > Issue Type: New Feature > Components: redis >Reporter: Wayne >Assignee: Hale Bales >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > Implement the [LSET|https://redis.io/commands/lset] command. > > +Acceptance Criteria+ > The command has been implemented along with appropriate unit and system tests. > > The command has been tested using the redis-cli tool and verified against > native redis. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (GEODE-9948) Implement LINSERT
[ https://issues.apache.org/jira/browse/GEODE-9948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hale Bales resolved GEODE-9948. --- Fix Version/s: 1.15.0 Resolution: Fixed > Implement LINSERT > - > > Key: GEODE-9948 > URL: https://issues.apache.org/jira/browse/GEODE-9948 > Project: Geode > Issue Type: New Feature > Components: redis >Reporter: Wayne >Assignee: Hale Bales >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > Implement the [LINSERT|http://https//redis.io/commands/linsert] command. > > +Acceptance Criteria+ > The command has been implemented along with appropriate unit and system tests. > > The command has been tested using the redis-cli tool and verified against > native redis. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (GEODE-9952) Implement LSET
[ https://issues.apache.org/jira/browse/GEODE-9952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hale Bales resolved GEODE-9952. --- Resolution: Fixed > Implement LSET > -- > > Key: GEODE-9952 > URL: https://issues.apache.org/jira/browse/GEODE-9952 > Project: Geode > Issue Type: New Feature > Components: redis >Reporter: Wayne >Assignee: Hale Bales >Priority: Major > Labels: pull-request-available > > Implement the [LSET|https://redis.io/commands/lset] command. > > +Acceptance Criteria+ > The command has been implemented along with appropriate unit and system tests. > > The command has been tested using the redis-cli tool and verified against > native redis. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9948) Implement LINSERT
[ https://issues.apache.org/jira/browse/GEODE-9948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17509163#comment-17509163 ] ASF subversion and git services commented on GEODE-9948: Commit c77f262c4f80958b67961bb128476fdf0865ba88 in geode's branch refs/heads/develop from Hale Bales [ https://gitbox.apache.org/repos/asf?p=geode.git;h=c77f262 ] GEODE-9948: Implement LINSERT Command (#7392) Implements the LINSERT command as described by the Redis documentation. LINSERT key BEFORE|AFTER pivot element The command inserts an element into a list either BEFORE or AFTER the reference element, which is called the 'pivot'. It returns the new length of the list if the element is inserted, and -1 if the pivot is not an element of the list. If the key does not exist, it will not be created, and the command will return -1. > Implement LINSERT > - > > Key: GEODE-9948 > URL: https://issues.apache.org/jira/browse/GEODE-9948 > Project: Geode > Issue Type: New Feature > Components: redis >Reporter: Wayne >Assignee: Hale Bales >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > Implement the [LINSERT|http://https//redis.io/commands/linsert] command. > > +Acceptance Criteria+ > The command has been implemented along with appropriate unit and system tests. > > The command has been tested using the redis-cli tool and verified against > native redis. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10122) With TLSv1.3 and GCM-based cipher (the default), P2P Messaging Fails When Encrypted Data Limit is Reached
[
https://issues.apache.org/jira/browse/GEODE-10122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17509131#comment-17509131
]
Bill Burcham commented on GEODE-10122:
--
Made progress on the PR: the JUnit ("Integration") test fails reliably, sending
2 bytes of encoded (TLS) data.
Next step is to make the test pass!
> With TLSv1.3 and GCM-based cipher (the default), P2P Messaging Fails When
> Encrypted Data Limit is Reached
> -
>
> Key: GEODE-10122
> URL: https://issues.apache.org/jira/browse/GEODE-10122
> Project: Geode
> Issue Type: Bug
> Components: messaging
>Affects Versions: 1.13.7, 1.14.3, 1.15.0
>Reporter: Bill Burcham
>Assignee: Bill Burcham
>Priority: Major
> Labels: blocks-1.15.0, pull-request-available
> Attachments: patch-P2PMessagingConcurrencyDUnitTest.txt
>
>
> TLSv1.3 introduced [1] the ability to set per-algorithm limits on symmetric
> key usage lifetimes. Once a certain number of bytes have been encrypted, a
> KeyUpdate post-handshake message [2] is sent.
> With default settings, on Liberica JDK 11, Geode's P2P framework will
> negotiate TLSv1.3 with the TLS_AES_256_GCM_SHA384 cipher suite. Geode P2P
> messaging will eventually fail, with a "Tag mismatch!" IOException in shared
> ordered receivers, after a session has been in heavy use for days.
> We have not see this failure on TLSv1.2.
> The implementation of TLSv1.3 in the Java runtime provides a security
> property [3] to configure the encrypted data limit. The attached patch to
> P2PMessagingConcurrencyDUnitTest configures the limit large enough that the
> test makes it through the (P2P) TLS handshake but small enough so that the
> "Tag mismatch!" exception is encountered less than a minute later.
> The bug is caused by Geode’s NioSslEngine class’ ignorance of the
> “rehandshaking” phase of the TLS protocol [4]:
> Creation - ready to be configured.
> Initial handshaking - perform authentication and negotiate communication
> parameters.
> Application data - ready for application exchange.
> *Rehandshaking* - renegotiate communications parameters/authentication;
> handshaking data may be mixed with application data.
> Closure - ready to shut down connection.
> Geode's tcp.Connection and NioSslEngine classes (particularly wrap() and
> unwrap()), as they are currently implemented, fail to fully attend to the
> handshake status from javax.net.ssl.SSLEngine. As a result these Geode
> classes fail to respond to the KeyUpdate message, resulting in the "Tag
> mismatch!" IOException.
> When that exception is encountered, the Connection is destroyed and a new one
> created in its place. But users of the old Connection, waiting for
> acknowledgements, will never receive them. This can result in cluster-wide
> hangs.
> [1] [https://datatracker.ietf.org/doc/html/rfc8446#section-5.5]
> [2]
> [https://www.ibm.com/docs/en/sdk-java-technology/8?topic=handshake-post-messages]
>
> [3]
> [https://docs.oracle.com/en/java/javase/11/security/java-secure-socket-extension-jsse-reference-guide.html#GUID-B970ADD6-1E9F-4C18-A26E-0679B50CC946]
> [4] [https://www.ibm.com/docs/en/sdk-java-technology/7.1?topic=sslengine-]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Resolved] (GEODE-9951) Implement RPOP
[ https://issues.apache.org/jira/browse/GEODE-9951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bala Tripura Sundari Kaza Venkata resolved GEODE-9951. -- Fix Version/s: 1.15.0 Resolution: Fixed > Implement RPOP > -- > > Key: GEODE-9951 > URL: https://issues.apache.org/jira/browse/GEODE-9951 > Project: Geode > Issue Type: New Feature > Components: redis >Reporter: Wayne >Assignee: Bala Tripura Sundari Kaza Venkata >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > Implement the [RPOP|https://redis.io/commands/rpop] command. > > +Acceptance Criteria+ > The command has been implemented along with appropriate unit and system tests. > > The command has been tested using the redis-cli tool and verified against > native redis. > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9194) Move PR clear related statistics to the appropriate classes
[ https://issues.apache.org/jira/browse/GEODE-9194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17509125#comment-17509125 ] ASF subversion and git services commented on GEODE-9194: Commit 55d37f8b0e5ea6e467ce2d7cdb9327edee0585ef in geode's branch refs/heads/feature/GEODE-7665 from mhansonp [ https://gitbox.apache.org/repos/asf?p=geode.git;h=55d37f8 ] GEODE-9194: Missing file is causing trouble (#6574) > Move PR clear related statistics to the appropriate classes > --- > > Key: GEODE-9194 > URL: https://issues.apache.org/jira/browse/GEODE-9194 > Project: Geode > Issue Type: New Feature > Components: statistics >Reporter: Mark Hanson >Assignee: Mark Hanson >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > Currently there are PR clear statistics that are not a part of the > Partitioned Region Stats. This feature work is to track the movement of those > stats. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9195) Remove redundant local locking from PartitionedRegionClear
[
https://issues.apache.org/jira/browse/GEODE-9195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17509124#comment-17509124
]
ASF subversion and git services commented on GEODE-9195:
Commit 5fef11a8ab3eee070e1ad1ea3c8fbd3e6d23a8f9 in geode's branch
refs/heads/feature/GEODE-7665 from Kirk Lund
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=5fef11a ]
GEODE-9195: Remove PR clear local locking (#6410)
Unit test changes in BucketRegion and DistributedRegion.
Unit test most of PartitionedRegionClearMessage.
> Remove redundant local locking from PartitionedRegionClear
> --
>
> Key: GEODE-9195
> URL: https://issues.apache.org/jira/browse/GEODE-9195
> Project: Geode
> Issue Type: Improvement
> Components: regions
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
>
> Existing behavior:
> PR clear unconditionally acquires a global lock and also acquires local locks
> on all buckets before doing clear.
> Expected behavior:
> Now that PR clear acquires a global lock, it no longer needs to acquire local
> locks on all buckets before doing clear.
> Solution:
> Remove the logic taking lock in individual nodes in:
> {noformat}
> DistributedRegion.obtainWriteLocksForClear()
> {noformat}
> Remove:
> {noformat}
> if (!localLockedAlready) {
> lockLocallyForClear(getDistributionManager(), getMyId(), regionEvent);
> }
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-9194) Move PR clear related statistics to the appropriate classes
[ https://issues.apache.org/jira/browse/GEODE-9194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17509126#comment-17509126 ] ASF subversion and git services commented on GEODE-9194: Commit 0fb010443a43a6eff1e7c192bbaa0bf1ceeb5920 in geode's branch refs/heads/feature/GEODE-7665 from mhansonp [ https://gitbox.apache.org/repos/asf?p=geode.git;h=0fb0104 ] GEODE-9194: Feature/region stats update (#6430) * GEODE-9194: add PR Region Clear statistics > Move PR clear related statistics to the appropriate classes > --- > > Key: GEODE-9194 > URL: https://issues.apache.org/jira/browse/GEODE-9194 > Project: Geode > Issue Type: New Feature > Components: statistics >Reporter: Mark Hanson >Assignee: Mark Hanson >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > Currently there are PR clear statistics that are not a part of the > Partitioned Region Stats. This feature work is to track the movement of those > stats. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9132) PR clear to take locks on all buckets unconditionally.
[
https://issues.apache.org/jira/browse/GEODE-9132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17509123#comment-17509123
]
ASF subversion and git services commented on GEODE-9132:
Commit 690146bb51aed65403ac0385b64547d9139e58c5 in geode's branch
refs/heads/feature/GEODE-7665 from Kirk Lund
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=690146b ]
GEODE-9132: Fix locking in PRClearCreateIndexDUnitTest
> PR clear to take locks on all buckets unconditionally.
> --
>
> Key: GEODE-9132
> URL: https://issues.apache.org/jira/browse/GEODE-9132
> Project: Geode
> Issue Type: Sub-task
> Components: regions
>Reporter: Anilkumar Gingade
>Assignee: Blake Bender
>Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
>
> Existing behavior:
> PR clear employs two different locking behavior based on the presence of
> client subscription and cache-listeners. If there is no subscription or
> cache-listener it takes the bucket locks on local nodes else it will send a
> message to take locks on all buckets before doing the clear.
> Expected behavior:
> To keep the code/behavior simple PR clear to employ single locking behavior.
> It will take the lock on all buckets before doing clear irrespective of
> subscription or cache-listener presence.
> Solution:
> Remove the following check that drives taking lock on local nodes:
> {code}
> boolean acquireClearLockForNotification =
> (partitionedRegion.hasAnyClientsInterested() ||
> partitionedRegion.hasListener());
> {code}
> And it will call:
> {code}
> obtainLockForClear(regionEvent);
> {code}
> Also remove the logic taking lock in individual nodes in:
> DistributedRegion.obtainWriteLocksForClear()
> Remove:
> if (!localLockedAlready) {
> lockLocallyForClear(getDistributionManager(), getMyId(), regionEvent);
> }
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-9132) PR clear to take locks on all buckets unconditionally.
[
https://issues.apache.org/jira/browse/GEODE-9132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17509120#comment-17509120
]
ASF subversion and git services commented on GEODE-9132:
Commit 167b3edbe67893a3106f71d989beda0857e4bc8c in geode's branch
refs/heads/feature/GEODE-7665 from Kirk Lund
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=167b3ed ]
GEODE-9132: PartitionedRegionClearWithConcurrentOperationsDUnitTest cleanup 3
> PR clear to take locks on all buckets unconditionally.
> --
>
> Key: GEODE-9132
> URL: https://issues.apache.org/jira/browse/GEODE-9132
> Project: Geode
> Issue Type: Sub-task
> Components: regions
>Reporter: Anilkumar Gingade
>Assignee: Blake Bender
>Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
>
> Existing behavior:
> PR clear employs two different locking behavior based on the presence of
> client subscription and cache-listeners. If there is no subscription or
> cache-listener it takes the bucket locks on local nodes else it will send a
> message to take locks on all buckets before doing the clear.
> Expected behavior:
> To keep the code/behavior simple PR clear to employ single locking behavior.
> It will take the lock on all buckets before doing clear irrespective of
> subscription or cache-listener presence.
> Solution:
> Remove the following check that drives taking lock on local nodes:
> {code}
> boolean acquireClearLockForNotification =
> (partitionedRegion.hasAnyClientsInterested() ||
> partitionedRegion.hasListener());
> {code}
> And it will call:
> {code}
> obtainLockForClear(regionEvent);
> {code}
> Also remove the logic taking lock in individual nodes in:
> DistributedRegion.obtainWriteLocksForClear()
> Remove:
> if (!localLockedAlready) {
> lockLocallyForClear(getDistributionManager(), getMyId(), regionEvent);
> }
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-9132) PR clear to take locks on all buckets unconditionally.
[
https://issues.apache.org/jira/browse/GEODE-9132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17509122#comment-17509122
]
ASF subversion and git services commented on GEODE-9132:
Commit 7597335edd26706069e98886c5752b353f888287 in geode's branch
refs/heads/feature/GEODE-7665 from Kirk Lund
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=7597335 ]
GEODE-9132: Use factory method to avoid escaped reference
> PR clear to take locks on all buckets unconditionally.
> --
>
> Key: GEODE-9132
> URL: https://issues.apache.org/jira/browse/GEODE-9132
> Project: Geode
> Issue Type: Sub-task
> Components: regions
>Reporter: Anilkumar Gingade
>Assignee: Blake Bender
>Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
>
> Existing behavior:
> PR clear employs two different locking behavior based on the presence of
> client subscription and cache-listeners. If there is no subscription or
> cache-listener it takes the bucket locks on local nodes else it will send a
> message to take locks on all buckets before doing the clear.
> Expected behavior:
> To keep the code/behavior simple PR clear to employ single locking behavior.
> It will take the lock on all buckets before doing clear irrespective of
> subscription or cache-listener presence.
> Solution:
> Remove the following check that drives taking lock on local nodes:
> {code}
> boolean acquireClearLockForNotification =
> (partitionedRegion.hasAnyClientsInterested() ||
> partitionedRegion.hasListener());
> {code}
> And it will call:
> {code}
> obtainLockForClear(regionEvent);
> {code}
> Also remove the logic taking lock in individual nodes in:
> DistributedRegion.obtainWriteLocksForClear()
> Remove:
> if (!localLockedAlready) {
> lockLocallyForClear(getDistributionManager(), getMyId(), regionEvent);
> }
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-9132) PR clear to take locks on all buckets unconditionally.
[
https://issues.apache.org/jira/browse/GEODE-9132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17509119#comment-17509119
]
ASF subversion and git services commented on GEODE-9132:
Commit 195bf3481afe12b2bed43740fa8b523d04331e86 in geode's branch
refs/heads/feature/GEODE-7665 from Kirk Lund
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=195bf34 ]
GEODE-9132: PartitionedRegionClearWithConcurrentOperationsDUnitTest cleanup 2
> PR clear to take locks on all buckets unconditionally.
> --
>
> Key: GEODE-9132
> URL: https://issues.apache.org/jira/browse/GEODE-9132
> Project: Geode
> Issue Type: Sub-task
> Components: regions
>Reporter: Anilkumar Gingade
>Assignee: Blake Bender
>Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
>
> Existing behavior:
> PR clear employs two different locking behavior based on the presence of
> client subscription and cache-listeners. If there is no subscription or
> cache-listener it takes the bucket locks on local nodes else it will send a
> message to take locks on all buckets before doing the clear.
> Expected behavior:
> To keep the code/behavior simple PR clear to employ single locking behavior.
> It will take the lock on all buckets before doing clear irrespective of
> subscription or cache-listener presence.
> Solution:
> Remove the following check that drives taking lock on local nodes:
> {code}
> boolean acquireClearLockForNotification =
> (partitionedRegion.hasAnyClientsInterested() ||
> partitionedRegion.hasListener());
> {code}
> And it will call:
> {code}
> obtainLockForClear(regionEvent);
> {code}
> Also remove the logic taking lock in individual nodes in:
> DistributedRegion.obtainWriteLocksForClear()
> Remove:
> if (!localLockedAlready) {
> lockLocallyForClear(getDistributionManager(), getMyId(), regionEvent);
> }
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-9132) PR clear to take locks on all buckets unconditionally.
[
https://issues.apache.org/jira/browse/GEODE-9132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17509121#comment-17509121
]
ASF subversion and git services commented on GEODE-9132:
Commit 08a36883fd168a0c5c3a8839b739242264db2481 in geode's branch
refs/heads/feature/GEODE-7665 from Kirk Lund
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=08a3688 ]
GEODE-9132: Always acquire write lock for PR clear
> PR clear to take locks on all buckets unconditionally.
> --
>
> Key: GEODE-9132
> URL: https://issues.apache.org/jira/browse/GEODE-9132
> Project: Geode
> Issue Type: Sub-task
> Components: regions
>Reporter: Anilkumar Gingade
>Assignee: Blake Bender
>Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
>
> Existing behavior:
> PR clear employs two different locking behavior based on the presence of
> client subscription and cache-listeners. If there is no subscription or
> cache-listener it takes the bucket locks on local nodes else it will send a
> message to take locks on all buckets before doing the clear.
> Expected behavior:
> To keep the code/behavior simple PR clear to employ single locking behavior.
> It will take the lock on all buckets before doing clear irrespective of
> subscription or cache-listener presence.
> Solution:
> Remove the following check that drives taking lock on local nodes:
> {code}
> boolean acquireClearLockForNotification =
> (partitionedRegion.hasAnyClientsInterested() ||
> partitionedRegion.hasListener());
> {code}
> And it will call:
> {code}
> obtainLockForClear(regionEvent);
> {code}
> Also remove the logic taking lock in individual nodes in:
> DistributedRegion.obtainWriteLocksForClear()
> Remove:
> if (!localLockedAlready) {
> lockLocallyForClear(getDistributionManager(), getMyId(), regionEvent);
> }
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-10141) GMSJoinLeaveJUnitTest is overly specific about the expected exception message
[ https://issues.apache.org/jira/browse/GEODE-10141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale Emery updated GEODE-10141: --- Labels: Java17 (was: ) > GMSJoinLeaveJUnitTest is overly specific about the expected exception message > - > > Key: GEODE-10141 > URL: https://issues.apache.org/jira/browse/GEODE-10141 > Project: Geode > Issue Type: Improvement > Components: membership, tests >Affects Versions: 1.15.0 >Reporter: Dale Emery >Priority: Major > Labels: Java17 > > `GMSJoinLeave` throws the correct exception type, with a message correctly > describing its inability to connect to the locators at the specified > unresolved addresses. But the test's assertion is overly specific about the > description of an unresolved address, and fails on JDK 17. > In JDKs up through 13, `toString()` of an unresolved `InetSocketAddress` > returned `"hostname:port"`. Starting with JDK 14 it returns > `"hostname/:port"`. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-10141) GMSJoinLeaveJUnitTest is overly specific about the expected exception message
Dale Emery created GEODE-10141: -- Summary: GMSJoinLeaveJUnitTest is overly specific about the expected exception message Key: GEODE-10141 URL: https://issues.apache.org/jira/browse/GEODE-10141 Project: Geode Issue Type: Improvement Components: membership, tests Affects Versions: 1.15.0 Reporter: Dale Emery `GMSJoinLeave` throws the correct exception type, with a message correctly describing its inability to connect to the locators at the specified unresolved addresses. But the test's assertion is overly specific about the description of an unresolved address, and fails on JDK 17. In JDKs up through 13, `toString()` of an unresolved `InetSocketAddress` returned `"hostname:port"`. Starting with JDK 14 it returns `"hostname/:port"`. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10139) curl should always use -f
[ https://issues.apache.org/jira/browse/GEODE-10139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17509106#comment-17509106 ] ASF subversion and git services commented on GEODE-10139: - Commit a3d8ef80f0bb1f487ea0dfb7c9de1e7ea82ecf87 in geode's branch refs/heads/develop from Owen Nichols [ https://gitbox.apache.org/repos/asf?p=geode.git;h=a3d8ef8 ] GEODE-10139: add -f to curl (#7464) Without -f, curl will succeed (exitcode 0) even if the response is a 404 error, etc This is almost never the desired behavior, especially in scripts that rely on set -e to fail fast if something goes wrong > curl should always use -f > -- > > Key: GEODE-10139 > URL: https://issues.apache.org/jira/browse/GEODE-10139 > Project: Geode > Issue Type: Task > Components: ci >Reporter: Owen Nichols >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > curl commands are used throughout our CI and release scripts > without -f, curl will not fail even when a bad response code such as 404 is > returned -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-10140) QueryResultFormatterQueryIntegrationTest fails due to illegal reflective access on JDK 17
Dale Emery created GEODE-10140: -- Summary: QueryResultFormatterQueryIntegrationTest fails due to illegal reflective access on JDK 17 Key: GEODE-10140 URL: https://issues.apache.org/jira/browse/GEODE-10140 Project: Geode Issue Type: Improvement Components: tests Affects Versions: 1.15.0 Reporter: Dale Emery This test requires the following packages to be opened: - java.base/sun.reflect.generics.repository - java.base/java.time - java.base/java.time.chrono - java.base/java.time.format - java.base/java.time.temporal - java.base/sun.reflect.generics.factory - java.base/sun.reflect.generics.reflectiveObjects - java.base/sun.reflect.generics.repository - java.base/sun.reflect.generics.scope - java.base/sun.reflect.generics.tree -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-10140) QueryResultFormatterQueryIntegrationTest fails due to illegal reflective access on JDK 17
[ https://issues.apache.org/jira/browse/GEODE-10140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale Emery reassigned GEODE-10140: -- Assignee: Dale Emery > QueryResultFormatterQueryIntegrationTest fails due to illegal reflective > access on JDK 17 > - > > Key: GEODE-10140 > URL: https://issues.apache.org/jira/browse/GEODE-10140 > Project: Geode > Issue Type: Improvement > Components: tests >Affects Versions: 1.15.0 >Reporter: Dale Emery >Assignee: Dale Emery >Priority: Major > Labels: Java17 > > This test requires the following packages to be opened: > - java.base/sun.reflect.generics.repository > - java.base/java.time > - java.base/java.time.chrono > - java.base/java.time.format > - java.base/java.time.temporal > - java.base/sun.reflect.generics.factory > - java.base/sun.reflect.generics.reflectiveObjects > - java.base/sun.reflect.generics.repository > - java.base/sun.reflect.generics.scope > - java.base/sun.reflect.generics.tree -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10140) QueryResultFormatterQueryIntegrationTest fails due to illegal reflective access on JDK 17
[ https://issues.apache.org/jira/browse/GEODE-10140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale Emery updated GEODE-10140: --- Labels: Java17 (was: ) > QueryResultFormatterQueryIntegrationTest fails due to illegal reflective > access on JDK 17 > - > > Key: GEODE-10140 > URL: https://issues.apache.org/jira/browse/GEODE-10140 > Project: Geode > Issue Type: Improvement > Components: tests >Affects Versions: 1.15.0 >Reporter: Dale Emery >Priority: Major > Labels: Java17 > > This test requires the following packages to be opened: > - java.base/sun.reflect.generics.repository > - java.base/java.time > - java.base/java.time.chrono > - java.base/java.time.format > - java.base/java.time.temporal > - java.base/sun.reflect.generics.factory > - java.base/sun.reflect.generics.reflectiveObjects > - java.base/sun.reflect.generics.repository > - java.base/sun.reflect.generics.scope > - java.base/sun.reflect.generics.tree -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (GEODE-10139) curl should always use -f
[ https://issues.apache.org/jira/browse/GEODE-10139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen Nichols resolved GEODE-10139. -- Fix Version/s: 1.15.0 Resolution: Fixed > curl should always use -f > -- > > Key: GEODE-10139 > URL: https://issues.apache.org/jira/browse/GEODE-10139 > Project: Geode > Issue Type: Task > Components: ci >Reporter: Owen Nichols >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > curl commands are used throughout our CI and release scripts > without -f, curl will not fail even when a bad response code such as 404 is > returned -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10139) curl should always use -f
[ https://issues.apache.org/jira/browse/GEODE-10139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-10139: --- Labels: pull-request-available (was: ) > curl should always use -f > -- > > Key: GEODE-10139 > URL: https://issues.apache.org/jira/browse/GEODE-10139 > Project: Geode > Issue Type: Task > Components: ci >Reporter: Owen Nichols >Priority: Major > Labels: pull-request-available > > curl commands are used throughout our CI and release scripts > without -f, curl will not fail even when a bad response code such as 404 is > returned -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10131) Remove unused but set variable
[ https://issues.apache.org/jira/browse/GEODE-10131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17509080#comment-17509080 ] ASF GitHub Bot commented on GEODE-10131: moleske commented on pull request #947: URL: https://github.com/apache/geode-native/pull/947#issuecomment-1072787530 @pdxcodemonkey - I have narrowed it down. This [geode commit (hash 2554f42b925f2b9b8ca7eee14c7a887436b1d9db)](https://github.com/apache/geode/commit/2554f42b925f2b9b8ca7eee14c7a887436b1d9db) is the one that broke geode native. Don't know if @jinmeiliao has any thoughts as the author of geode commit. I haven't looked to see why it broke geode native, but feel very confident in saying this PR is not the cause of the breakage. It also looks like https://github.com/apache/geode-native/pull/948 is failing for the same reason, so CI will be broken til this is resolved -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@geode.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Remove unused but set variable > -- > > Key: GEODE-10131 > URL: https://issues.apache.org/jira/browse/GEODE-10131 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Michael Oleske >Priority: Major > Labels: pull-request-available > > When on AppleClang 13.1.6.13160021 on macOS 12.3, native client fails to > compile due to warning as error -Wunused-but-set-variable > Remove the offending lines to compile -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9951) Implement RPOP
[ https://issues.apache.org/jira/browse/GEODE-9951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17509076#comment-17509076 ] ASF subversion and git services commented on GEODE-9951: Commit e83107c87ea7fe5d5ae191b949e17efed1a7f021 in geode's branch refs/heads/develop from Bala Kaza Venkata [ https://gitbox.apache.org/repos/asf?p=geode.git;h=e83107c ] GEODE-9951: Add support for Radish RPOP command (#7418) > Implement RPOP > -- > > Key: GEODE-9951 > URL: https://issues.apache.org/jira/browse/GEODE-9951 > Project: Geode > Issue Type: New Feature > Components: redis >Reporter: Wayne >Assignee: Bala Tripura Sundari Kaza Venkata >Priority: Major > Labels: pull-request-available > > Implement the [RPOP|https://redis.io/commands/rpop] command. > > +Acceptance Criteria+ > The command has been implemented along with appropriate unit and system tests. > > The command has been tested using the redis-cli tool and verified against > native redis. > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-10139) curl should always use -f
Owen Nichols created GEODE-10139: Summary: curl should always use -f Key: GEODE-10139 URL: https://issues.apache.org/jira/browse/GEODE-10139 Project: Geode Issue Type: Task Components: ci Reporter: Owen Nichols curl commands are used throughout our CI and release scripts without -f, curl will not fail even when a bad response code such as 404 is returned -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10089) release 1.15.0
[ https://issues.apache.org/jira/browse/GEODE-10089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen Nichols updated GEODE-10089: - Description: As per [Jan 25 dev list discussion|https://lists.apache.org/thread/s9mpd207h40crcr76fpdfmohdchgdqog], support/1.15 was cut with the intention of stabilizing and releasing a new Geode minor. UPDATE: As per [Mar 16 dev list discussion|https://lists.apache.org/thread/twlwzcvmx2kqw15whpmxkh2h8bmrok21], support/1.15 was retracted. Work will continue on develop with an eye toward re-cutting support/1.15 in ~June Release status information is also updated in the Geode [Release Schedule|https://cwiki.apache.org/confluence/display/GEODE/Release+Schedule]. was: As per [Jan 25 dev list discussion|https://lists.apache.org/thread/s9mpd207h40crcr76fpdfmohdchgdqog], support/1.15 was cut with the intention of stabilizing and releasing a new Geode minor. Release status information is also updated in the Geode [Release Schedule|https://cwiki.apache.org/confluence/display/GEODE/Release+Schedule]. > release 1.15.0 > -- > > Key: GEODE-10089 > URL: https://issues.apache.org/jira/browse/GEODE-10089 > Project: Geode > Issue Type: Task > Components: release >Reporter: Owen Nichols >Assignee: Owen Nichols >Priority: Major > Labels: pull-request-available > > As per [Jan 25 dev list > discussion|https://lists.apache.org/thread/s9mpd207h40crcr76fpdfmohdchgdqog], > support/1.15 was cut with the intention of stabilizing and releasing a new > Geode minor. > UPDATE: As per [Mar 16 dev list > discussion|https://lists.apache.org/thread/twlwzcvmx2kqw15whpmxkh2h8bmrok21], > support/1.15 was retracted. Work will continue on develop with an eye toward > re-cutting support/1.15 in ~June > Release status information is also updated in the Geode [Release > Schedule|https://cwiki.apache.org/confluence/display/GEODE/Release+Schedule]. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (GEODE-10039) BucketProfiles can be stale in rare cases.
[ https://issues.apache.org/jira/browse/GEODE-10039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jianxia Chen resolved GEODE-10039. -- Resolution: Fixed > BucketProfiles can be stale in rare cases. > -- > > Key: GEODE-10039 > URL: https://issues.apache.org/jira/browse/GEODE-10039 > Project: Geode > Issue Type: Bug > Components: core >Affects Versions: 1.15.0 >Reporter: Mark Hanson >Assignee: Jianxia Chen >Priority: Major > Labels: GeodeOperationAPI, blocks-1.15.0, pull-request-available > > In the case when a server is starting as a member of a partitioned region > during a rebalance, it is possible for the the starting server to not get a > profile removal for a bucket that has been relocated. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10105) restarting of gateway sender during dispatching of events, causes duplication of events without indication of possibleduplicate
[ https://issues.apache.org/jira/browse/GEODE-10105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17509034#comment-17509034 ] ASF subversion and git services commented on GEODE-10105: - Commit d67aba9f9a94a6f7efd0e529fad1b817c23dbc6a in geode's branch refs/heads/develop from Mario Ivanac [ https://gitbox.apache.org/repos/asf?p=geode.git;h=d67aba9 ] GEODE-10105: when stopping gw sender, for pending events set possible… (#7422) * GEODE-10105: when stopping gw sender, for pending events set possibleduplicate * GEODE-10105: added test * GEODE-10105: update after comments > restarting of gateway sender during dispatching of events, causes duplication > of events without indication of possibleduplicate > --- > > Key: GEODE-10105 > URL: https://issues.apache.org/jira/browse/GEODE-10105 > Project: Geode > Issue Type: Bug > Components: wan >Affects Versions: 1.14.0 >Reporter: Mario Ivanac >Assignee: Mario Ivanac >Priority: Major > Labels: needsTriage, pull-request-available > Fix For: 1.15.0 > > > During dispatching events in parallel gateway sender, if we stop dispatching, > and after some time restart dispatching, multiple duplicate events are > observed on receiving side (without indication possible duplicate). -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (GEODE-10105) restarting of gateway sender during dispatching of events, causes duplication of events without indication of possibleduplicate
[ https://issues.apache.org/jira/browse/GEODE-10105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mario Ivanac resolved GEODE-10105. -- Fix Version/s: 1.15.0 Resolution: Fixed > restarting of gateway sender during dispatching of events, causes duplication > of events without indication of possibleduplicate > --- > > Key: GEODE-10105 > URL: https://issues.apache.org/jira/browse/GEODE-10105 > Project: Geode > Issue Type: Bug > Components: wan >Affects Versions: 1.14.0 >Reporter: Mario Ivanac >Assignee: Mario Ivanac >Priority: Major > Labels: needsTriage, pull-request-available > Fix For: 1.15.0 > > > During dispatching events in parallel gateway sender, if we stop dispatching, > and after some time restart dispatching, multiple duplicate events are > observed on receiving side (without indication possible duplicate). -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10039) BucketProfiles can be stale in rare cases.
[ https://issues.apache.org/jira/browse/GEODE-10039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17509021#comment-17509021 ] ASF subversion and git services commented on GEODE-10039: - Commit 82728074a9bc89f54af78ec57513749b84f54a45 in geode's branch refs/heads/develop from Jianxia Chen [ https://gitbox.apache.org/repos/asf?p=geode.git;h=8272807 ] GEODE-10039: Fix the issue that BucketProfile can be stale in rare cases. (#7440) When sending `DestroyRegionMessage` caused by `RemoveBucketMessage`, the recipients should include all other members. So that a member that is in the process of creating the partitioned region can receive the `DestroyRegionMessage` and remove the stale bucket profile. Co-authored-by: anilkumar gingade > BucketProfiles can be stale in rare cases. > -- > > Key: GEODE-10039 > URL: https://issues.apache.org/jira/browse/GEODE-10039 > Project: Geode > Issue Type: Bug > Components: core >Affects Versions: 1.15.0 >Reporter: Mark Hanson >Assignee: Jianxia Chen >Priority: Major > Labels: GeodeOperationAPI, blocks-1.15.0, pull-request-available > > In the case when a server is starting as a member of a partitioned region > during a rebalance, it is possible for the the starting server to not get a > profile removal for a bucket that has been relocated. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10092) IllegalArgumentException: Illegal Capacity (with a negative value) thrown from EntriesSet.toArray() in client
[ https://issues.apache.org/jira/browse/GEODE-10092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17508994#comment-17508994 ] ASF subversion and git services commented on GEODE-10092: - Commit 2ad694c58ec23a952b147e6ff1e6d531167b5475 in geode's branch refs/heads/develop from Jinmei Liao [ https://gitbox.apache.org/repos/asf?p=geode.git;h=2ad694c ] GEODE-10092: Prevent tombstone count update in the middle of size count (#7448) > IllegalArgumentException: Illegal Capacity (with a negative value) thrown > from EntriesSet.toArray() in client > - > > Key: GEODE-10092 > URL: https://issues.apache.org/jira/browse/GEODE-10092 > Project: Geode > Issue Type: Bug >Reporter: Jinmei Liao >Priority: Major > Labels: needsTriage, pull-request-available > Fix For: 1.15.0 > > > In some case, we see the following stack trace when executing > entriesSet.toArray() call: Exception java.lang.IllegalArgumentException: > Illegal Capacity: -40 > at java.util.ArrayList.(ArrayList.java:157) > at > org.apache.geode.internal.cache.EntriesSet.toArray(EntriesSet.java:251) > at > org.apache.geode.internal.cache.EntriesSet.toArray(EntriesSet.java:245) > looks like the entriesSet.size() call will sometimes returns a negative value. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (GEODE-10092) IllegalArgumentException: Illegal Capacity (with a negative value) thrown from EntriesSet.toArray() in client
[ https://issues.apache.org/jira/browse/GEODE-10092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao resolved GEODE-10092. - Fix Version/s: 1.15.0 Resolution: Fixed > IllegalArgumentException: Illegal Capacity (with a negative value) thrown > from EntriesSet.toArray() in client > - > > Key: GEODE-10092 > URL: https://issues.apache.org/jira/browse/GEODE-10092 > Project: Geode > Issue Type: Bug >Reporter: Jinmei Liao >Priority: Major > Labels: needsTriage, pull-request-available > Fix For: 1.15.0 > > > In some case, we see the following stack trace when executing > entriesSet.toArray() call: Exception java.lang.IllegalArgumentException: > Illegal Capacity: -40 > at java.util.ArrayList.(ArrayList.java:157) > at > org.apache.geode.internal.cache.EntriesSet.toArray(EntriesSet.java:251) > at > org.apache.geode.internal.cache.EntriesSet.toArray(EntriesSet.java:245) > looks like the entriesSet.size() call will sometimes returns a negative value. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10058) Remove Defunct NetCore and C-Bindings from geode-native repo and CI
[ https://issues.apache.org/jira/browse/GEODE-10058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Martell updated GEODE-10058: Summary: Remove Defunct NetCore and C-Bindings from geode-native repo and CI (was: Remove Defunct NetCore and C-Bindiings from geode-native repo and CI) > Remove Defunct NetCore and C-Bindings from geode-native repo and CI > --- > > Key: GEODE-10058 > URL: https://issues.apache.org/jira/browse/GEODE-10058 > Project: Geode > Issue Type: Task >Reporter: Michael Martell >Priority: Major > > This project is being replaced by a pure C# client for .NET Core. > Also, move the SessionState code to a new branch since it's not throw away > code. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (GEODE-9973) Documentation: socket-lease-time is not used to return sockets to a pool but to close them
[ https://issues.apache.org/jira/browse/GEODE-9973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dick Cavender closed GEODE-9973. > Documentation: socket-lease-time is not used to return sockets to a pool but > to close them > -- > > Key: GEODE-9973 > URL: https://issues.apache.org/jira/browse/GEODE-9973 > Project: Geode > Issue Type: Bug > Components: docs >Affects Versions: 1.12.9, 1.13.8, 1.14.4, 1.15.0 >Reporter: Alberto Gomez >Assignee: Donal Evans >Priority: Major > Labels: pull-request-available > Fix For: 1.12.9, 1.13.8, 1.14.4, 1.15.0 > > > The "Making sure you have enough sockets" Geode documentation section says > the following about socket-lease-time (check underlined sentence): > > Peer-to-peer. For peer-to-peer threads that do not share sockets, you can use > the socket-lease-time to make sure that no socket sits idle for too long. > +When a socket that belongs to an individual thread remains unused for this > time period, the system automatically returns it to the pool.+ The next time > the thread needs a socket, it creates a new socket. > > Actually, the system automatically closes the connection in the situation > described instead of returning it to any pool. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (GEODE-9923) User Guide: add Log Message troubleshooting section
[ https://issues.apache.org/jira/browse/GEODE-9923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dick Cavender closed GEODE-9923. > User Guide: add Log Message troubleshooting section > --- > > Key: GEODE-9923 > URL: https://issues.apache.org/jira/browse/GEODE-9923 > Project: Geode > Issue Type: Improvement > Components: docs >Affects Versions: 1.14.2 >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Labels: pull-request-available > Fix For: 1.12.9, 1.13.8, 1.14.4, 1.15.0 > > > GemFire support team (who are also Geode community members) have compiled a > troubleshooting guide that maps log messages to suggested solutions. > They have contributed this to Geode in the form of a Google doc. > Reformat the Google doc and add it to the Geode user guide. There's an > existing section under Managing Apache Geode called Troubleshooting and > System Recovery that would be a good location for this material. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (GEODE-9372) DistributionStats needs a stat for create sender time to help diagnose data replication spikes
[ https://issues.apache.org/jira/browse/GEODE-9372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dick Cavender closed GEODE-9372. > DistributionStats needs a stat for create sender time to help diagnose data > replication spikes > -- > > Key: GEODE-9372 > URL: https://issues.apache.org/jira/browse/GEODE-9372 > Project: Geode > Issue Type: Improvement > Components: statistics >Reporter: Barrett Oglesby >Assignee: Barrett Oglesby >Priority: Major > Labels: GeodeOperationAPI, pull-request-available > Fix For: 1.12.9, 1.13.8, 1.14.4, 1.15.0 > > Attachments: > PartitionedRegionStats_sendReplicationTime_DistributionStats_sendersTO.gif > > > While debugging an issue with sendReplicationTime, we realized it was all due > to sender creation time. > A statistic for that time would have been very useful. > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (GEODE-10062) Update Native Client Docs to minimize redirects
[ https://issues.apache.org/jira/browse/GEODE-10062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dick Cavender closed GEODE-10062. - > Update Native Client Docs to minimize redirects > --- > > Key: GEODE-10062 > URL: https://issues.apache.org/jira/browse/GEODE-10062 > Project: Geode > Issue Type: Improvement > Components: docs, native client >Affects Versions: 1.14.3 >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Labels: pull-request-available > Fix For: 1.14.4, 1.15.0 > > > Geode Native Client doc sources could be improved for ease of building and > use by reducing dependency on the ruby redirect feature, through measures > such as: > - Replace ruby redirects, where feasible, with template variables, e.g. links > to API docs and server guide > - Standardizing template variables, e.g. use 'serverman' consistently, > retiring other alternatives such as 'geodeman' -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (GEODE-9819) Client socket leak in CacheClientNotifier.registerClientInternal when error conditions occur for the durable client
[
https://issues.apache.org/jira/browse/GEODE-9819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dick Cavender closed GEODE-9819.
> Client socket leak in CacheClientNotifier.registerClientInternal when error
> conditions occur for the durable client
> ---
>
> Key: GEODE-9819
> URL: https://issues.apache.org/jira/browse/GEODE-9819
> Project: Geode
> Issue Type: Bug
> Components: client/server, core
>Affects Versions: 1.12.5, 1.13.4, 1.14.0, 1.15.0
>Reporter: Leon Finker
>Assignee: Darrel Schneider
>Priority: Critical
> Labels: GeodeOperationAPI, blocks-1.15.0, pull-request-available
> Fix For: 1.12.9, 1.13.8, 1.14.4, 1.15.0
>
>
> In CacheClientNotifier.registerClientInternal client socket can be left half
> open and not properly closed when error conditions occur. Such as the case of:
> {code:java}
> } else {
> // The existing proxy is already running (which means that another
> // client is already using this durable id.
> unsuccessfulMsg =
> String.format(
> "The requested durable client has the same identifier ( %s ) as an
> existing durable client ( %s ). Duplicate durable clients are not allowed.",
> clientProxyMembershipID.getDurableId(), cacheClientProxy);
> logger.warn(unsuccessfulMsg);
> // Set the unsuccessful response byte.
> responseByte = Handshake.REPLY_EXCEPTION_DUPLICATE_DURABLE_CLIENT;
> } {code}
> It considers the current client connect attempt to have failed. It writes
> this response back to client: REPLY_EXCEPTION_DUPLICATE_DURABLE_CLIENT. This
> will cause the client to throw ServerRefusedConnectionException. What seems
> wrong about this method is that even though it sets "unsuccessfulMsg" and
> correctly sends back a handshake saying the client is rejected, it does not
> throw an exception and it does not close "socket". I think right before it
> calls performPostAuthorization it should do the followiing:
> {code:java}
> if (unsuccessfulMsg != null) {
> try {
> socket.close();
> } catch (IOException ignore) {
> }
> } else {
> performPostAuthorization(...)
> }{code}
> Full discussion details can be found at
> https://markmail.org/thread/2gqmbq2m57pz7pxu
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Closed] (GEODE-9528) CI Failure: DistributionAdvisorIntegrationTest > verifyMembershipListenerIsRemovedAfterForceDisconnect
[
https://issues.apache.org/jira/browse/GEODE-9528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dick Cavender closed GEODE-9528.
> CI Failure: DistributionAdvisorIntegrationTest >
> verifyMembershipListenerIsRemovedAfterForceDisconnect
> --
>
> Key: GEODE-9528
> URL: https://issues.apache.org/jira/browse/GEODE-9528
> Project: Geode
> Issue Type: Bug
> Components: membership, tests
>Affects Versions: 1.12.5, 1.13.5, 1.14.0
>Reporter: Owen Nichols
>Assignee: Barrett Oglesby
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.12.9, 1.13.8, 1.14.4, 1.15.0
>
>
> {noformat}
> org.apache.geode.distributed.internal.DistributionAdvisorIntegrationTest >
> verifyMembershipListenerIsRemovedAfterForceDisconnect FAILED
> org.junit.ComparisonFailure: expected:<[fals]e> but was:<[tru]e>
> at
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.distributed.internal.DistributionAdvisorIntegrationTest.verifyMembershipListenerIsRemovedAfterForceDisconnect(DistributionAdvisorIntegrationTest.java:57)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Closed] (GEODE-10093) DeltaSession getAttribute method logs an NPE and returns unserialized value when called on attribute with null value
[ https://issues.apache.org/jira/browse/GEODE-10093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dick Cavender closed GEODE-10093. - > DeltaSession getAttribute method logs an NPE and returns unserialized value > when called on attribute with null value > > > Key: GEODE-10093 > URL: https://issues.apache.org/jira/browse/GEODE-10093 > Project: Geode > Issue Type: Bug > Components: http session >Affects Versions: 1.12.2, 1.13.3, 1.14.0, 1.15.0 >Reporter: Benjamin P Ross >Assignee: Benjamin P Ross >Priority: Major > Labels: needsTriage, pull-request-available > Fix For: 1.12.9, 1.13.8, 1.14.4, 1.15.0 > > > Under certain circumstances, a null value can be set for an attribute which > then throws an NPE when trying to add it to the local map during a > getAttribute call on the session. Prior to 1.12.2 we were responding to this > by removing the entry entirely from the local map which is consistent with > what the base Session class for Catalina does, but starting with 1.12.2 > onward this results in an error message being displayed and the serialized > value being returned rather than the unserialized value. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (GEODE-9817) Allow analyze serializables tests to provide custom source set paths to ClassAnalysisRule
[ https://issues.apache.org/jira/browse/GEODE-9817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dick Cavender closed GEODE-9817. > Allow analyze serializables tests to provide custom source set paths to > ClassAnalysisRule > - > > Key: GEODE-9817 > URL: https://issues.apache.org/jira/browse/GEODE-9817 > Project: Geode > Issue Type: Wish > Components: tests >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Labels: pull-request-available > Fix For: 1.14.4, 1.15.0 > > > In order to make SanctionedSerializablesService and the related tests to be > more pluggable by external modules, I need to make changes to allow analyze > serializables tests to provide custom source set paths to ClassAnalysisRule. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10089) release 1.15.0
[ https://issues.apache.org/jira/browse/GEODE-10089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17508965#comment-17508965 ] ASF subversion and git services commented on GEODE-10089: - Commit 57696a37e17d3e741659d6e7aee1c0b26aa6b7a2 in geode's branch refs/heads/develop from Owen Nichols [ https://gitbox.apache.org/repos/asf?p=geode.git;h=57696a3 ] GEODE-10089: update release scripts to handle 1.15 (#7406) * increased RC pipeline file size check limits as 1.15 is a little bigger than 1.14 * modified RC pipeline native builds to obtain a required newer cmake than what is distributed by Ubuntu * generate the full releasenotes link to add to the wiki page * move the dlcdn check to the end of the script since it only blocks sending of the announce email * generate better comment on whether the new old version was added or replaced and why * do as much as we can that doesn't depend on maven, before waiting on maven > release 1.15.0 > -- > > Key: GEODE-10089 > URL: https://issues.apache.org/jira/browse/GEODE-10089 > Project: Geode > Issue Type: Task > Components: release >Reporter: Owen Nichols >Assignee: Owen Nichols >Priority: Major > Labels: pull-request-available > > As per [Jan 25 dev list > discussion|https://lists.apache.org/thread/s9mpd207h40crcr76fpdfmohdchgdqog], > support/1.15 was cut with the intention of stabilizing and releasing a new > Geode minor. > Release status information is also updated in the Geode [Release > Schedule|https://cwiki.apache.org/confluence/display/GEODE/Release+Schedule]. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10100) release 1.13.8
[ https://issues.apache.org/jira/browse/GEODE-10100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen Nichols updated GEODE-10100: - Fix Version/s: (was: 1.12.10) > release 1.13.8 > -- > > Key: GEODE-10100 > URL: https://issues.apache.org/jira/browse/GEODE-10100 > Project: Geode > Issue Type: Task > Components: release >Reporter: Dick Cavender >Priority: Major > Labels: pull-request-available > Fix For: 1.13.9, 1.14.5, 1.15.0 > > > Release to incorporate GEODE-10093 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (GEODE-10101) release 1.14.4
[ https://issues.apache.org/jira/browse/GEODE-10101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dick Cavender resolved GEODE-10101. --- Fix Version/s: 1.14.5 1.15.0 Resolution: Fixed > release 1.14.4 > -- > > Key: GEODE-10101 > URL: https://issues.apache.org/jira/browse/GEODE-10101 > Project: Geode > Issue Type: Task > Components: release >Reporter: Dick Cavender >Priority: Major > Labels: pull-request-available > Fix For: 1.14.5, 1.15.0 > > > Release to incorporate GEODE-10093 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9952) Implement LSET
[ https://issues.apache.org/jira/browse/GEODE-9952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17508953#comment-17508953 ] ASF subversion and git services commented on GEODE-9952: Commit 669149d535b8572f305dd91c34d28338865bcbc1 in geode's branch refs/heads/develop from Hale Bales [ https://gitbox.apache.org/repos/asf?p=geode.git;h=669149d ] GEODE-9952: Support LSET Command (#7396) Implements the LSET command as described by the Redis documentation. LSET key index newValue ex. LSET key 1 "newValue" The LSET command sets the list element at the given index to the specified new value. If the value is negative, it wraps around. If the index, after being adjusted for negative values, is out of bounds, the RedisResponse will be an index out of bounds error. If the key does not exist then it will not be created and a key does not exist error will be returned. The command may return: - OK - ERR index out of bounds - ERR no such key > Implement LSET > -- > > Key: GEODE-9952 > URL: https://issues.apache.org/jira/browse/GEODE-9952 > Project: Geode > Issue Type: New Feature > Components: redis >Reporter: Wayne >Assignee: Hale Bales >Priority: Major > Labels: pull-request-available > > Implement the [LSET|https://redis.io/commands/lset] command. > > +Acceptance Criteria+ > The command has been implemented along with appropriate unit and system tests. > > The command has been tested using the redis-cli tool and verified against > native redis. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10101) release 1.14.4
[ https://issues.apache.org/jira/browse/GEODE-10101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17508952#comment-17508952 ] ASF GitHub Bot commented on GEODE-10101: dickcav opened a new pull request #948: URL: https://github.com/apache/geode-native/pull/948 Native client hardcodes Geode version to test with in several places. Update those variables to latest-and-greatest apache-geode 1.14.4 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@geode.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org > release 1.14.4 > -- > > Key: GEODE-10101 > URL: https://issues.apache.org/jira/browse/GEODE-10101 > Project: Geode > Issue Type: Task > Components: release >Reporter: Dick Cavender >Priority: Major > Labels: pull-request-available > > Release to incorporate GEODE-10093 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10101) release 1.14.4
[ https://issues.apache.org/jira/browse/GEODE-10101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-10101: --- Labels: pull-request-available (was: ) > release 1.14.4 > -- > > Key: GEODE-10101 > URL: https://issues.apache.org/jira/browse/GEODE-10101 > Project: Geode > Issue Type: Task > Components: release >Reporter: Dick Cavender >Priority: Major > Labels: pull-request-available > > Release to incorporate GEODE-10093 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10101) release 1.14.4
[ https://issues.apache.org/jira/browse/GEODE-10101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17508949#comment-17508949 ] ASF subversion and git services commented on GEODE-10101: - Commit a28c4c16d21def7167806056b97ae16cf3fbfa6c in geode-benchmarks's branch refs/heads/support/1.14 from Dick Cavender [ https://gitbox.apache.org/repos/asf?p=geode-benchmarks.git;h=a28c4c1 ] GEODE-10101: Bump version to 1.14.5 As part of the Geode Release Process, the geode-benchmarks build number must be rolled forward as work begins on the next release > release 1.14.4 > -- > > Key: GEODE-10101 > URL: https://issues.apache.org/jira/browse/GEODE-10101 > Project: Geode > Issue Type: Task > Components: release >Reporter: Dick Cavender >Priority: Major > > Release to incorporate GEODE-10093 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10062) Update Native Client Docs to minimize redirects
[ https://issues.apache.org/jira/browse/GEODE-10062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17508946#comment-17508946 ] ASF subversion and git services commented on GEODE-10062: - Commit 8a5244a84beca9b1561dff3281245b1724ab4ec4 in geode-native's branch refs/heads/master from Dave Barnes [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=8a5244a ] GEODE-10062: Update Native Client Docs to minimize redirects (#931) > Update Native Client Docs to minimize redirects > --- > > Key: GEODE-10062 > URL: https://issues.apache.org/jira/browse/GEODE-10062 > Project: Geode > Issue Type: Improvement > Components: docs, native client >Affects Versions: 1.14.3 >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Labels: pull-request-available > Fix For: 1.14.4, 1.15.0 > > > Geode Native Client doc sources could be improved for ease of building and > use by reducing dependency on the ruby redirect feature, through measures > such as: > - Replace ruby redirects, where feasible, with template variables, e.g. links > to API docs and server guide > - Standardizing template variables, e.g. use 'serverman' consistently, > retiring other alternatives such as 'geodeman' -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10101) release 1.14.4
[ https://issues.apache.org/jira/browse/GEODE-10101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17508948#comment-17508948 ] ASF subversion and git services commented on GEODE-10101: - Commit c818de15c029a0ff1ffe92b916d7508dc6ca531e in geode-benchmarks's branch refs/heads/develop from Dick Cavender [ https://gitbox.apache.org/repos/asf?p=geode-benchmarks.git;h=c818de1 ] GEODE-10101: Update benchmark baseline Updates the default benchmark baseline on develop to 1.14.4 > release 1.14.4 > -- > > Key: GEODE-10101 > URL: https://issues.apache.org/jira/browse/GEODE-10101 > Project: Geode > Issue Type: Task > Components: release >Reporter: Dick Cavender >Priority: Major > > Release to incorporate GEODE-10093 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10062) Update Native Client Docs to minimize redirects
[ https://issues.apache.org/jira/browse/GEODE-10062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17508947#comment-17508947 ] ASF subversion and git services commented on GEODE-10062: - Commit d924d995597ca05d82e7043ff8e1a942dbf0ece3 in geode-native's branch refs/heads/master from Dave Barnes [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=d924d99 ] GEODE-10062: Update Native Client Docs to minimize redirects - additions and corrections > Update Native Client Docs to minimize redirects > --- > > Key: GEODE-10062 > URL: https://issues.apache.org/jira/browse/GEODE-10062 > Project: Geode > Issue Type: Improvement > Components: docs, native client >Affects Versions: 1.14.3 >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Labels: pull-request-available > Fix For: 1.14.4, 1.15.0 > > > Geode Native Client doc sources could be improved for ease of building and > use by reducing dependency on the ruby redirect feature, through measures > such as: > - Replace ruby redirects, where feasible, with template variables, e.g. links > to API docs and server guide > - Standardizing template variables, e.g. use 'serverman' consistently, > retiring other alternatives such as 'geodeman' -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10101) release 1.14.4
[ https://issues.apache.org/jira/browse/GEODE-10101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17508944#comment-17508944 ] ASF subversion and git services commented on GEODE-10101: - Commit 8a0cf67ac346480471dc3128b3d3a23d5bb6edd5 in geode's branch refs/heads/support/1.14 from Dick Cavender [ https://gitbox.apache.org/repos/asf?p=geode.git;h=8a0cf67 ] GEODE-10101: Bump version to 1.14.5 As part of the Geode Release Process, the build number must be rolled forward so work can begin on the next release > release 1.14.4 > -- > > Key: GEODE-10101 > URL: https://issues.apache.org/jira/browse/GEODE-10101 > Project: Geode > Issue Type: Task > Components: release >Reporter: Dick Cavender >Priority: Major > > Release to incorporate GEODE-10093 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10101) release 1.14.4
[ https://issues.apache.org/jira/browse/GEODE-10101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17508918#comment-17508918 ] ASF subversion and git services commented on GEODE-10101: - Commit ff7c555f86e1d45fdf1652e682c7730b53c8aa4a in geode-examples's branch refs/heads/support/1.14 from Dick Cavender [ https://gitbox.apache.org/repos/asf?p=geode-examples.git;h=ff7c555 ] Revert "GEODE-10101: Set temporary staging repo" The staging repo no longest exists, so set this back to search the default location (mavencentral) > release 1.14.4 > -- > > Key: GEODE-10101 > URL: https://issues.apache.org/jira/browse/GEODE-10101 > Project: Geode > Issue Type: Task > Components: release >Reporter: Dick Cavender >Priority: Major > > Release to incorporate GEODE-10093 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10101) release 1.14.4
[ https://issues.apache.org/jira/browse/GEODE-10101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17508934#comment-17508934 ] ASF subversion and git services commented on GEODE-10101: - Commit eda6084109e76d7d6fbf3359dee6d8e28b9c099e in geode's branch refs/heads/support/1.14 from Dick Cavender [ https://gitbox.apache.org/repos/asf?p=geode.git;h=eda6084 ] GEODE-10101: Replace 1.14.3 with 1.14.4 as old version Replace 1.14.3 with 1.14.4 in old versions on support/1.14 to enable rolling upgrade tests from 1.14.4 The serialization version has not changed between 1.14.3 and 1.14.4, so there should be no need to keep both > release 1.14.4 > -- > > Key: GEODE-10101 > URL: https://issues.apache.org/jira/browse/GEODE-10101 > Project: Geode > Issue Type: Task > Components: release >Reporter: Dick Cavender >Priority: Major > > Release to incorporate GEODE-10093 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10093) DeltaSession getAttribute method logs an NPE and returns unserialized value when called on attribute with null value
[ https://issues.apache.org/jira/browse/GEODE-10093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17508930#comment-17508930 ] ASF subversion and git services commented on GEODE-10093: - Commit a45cbe90920c5ea9988a1674e729499abb150db1 in geode's branch refs/heads/master from BenjaminPerryRoss [ https://gitbox.apache.org/repos/asf?p=geode.git;h=a45cbe9 ] GEODE-10093 - Fixed attr issue in Delta Session (#7405) (#7413) * GEODE-10093 - Fixed attr issue in Delta Session (cherry picked from commit e040759cd1e42df377501cd423967d549ce2bfab) > DeltaSession getAttribute method logs an NPE and returns unserialized value > when called on attribute with null value > > > Key: GEODE-10093 > URL: https://issues.apache.org/jira/browse/GEODE-10093 > Project: Geode > Issue Type: Bug > Components: http session >Affects Versions: 1.12.2, 1.13.3, 1.14.0, 1.15.0 >Reporter: Benjamin P Ross >Assignee: Benjamin P Ross >Priority: Major > Labels: needsTriage, pull-request-available > Fix For: 1.12.9, 1.13.8, 1.14.4, 1.15.0 > > > Under certain circumstances, a null value can be set for an attribute which > then throws an NPE when trying to add it to the local map during a > getAttribute call on the session. Prior to 1.12.2 we were responding to this > by removing the entry entirely from the local map which is consistent with > what the base Session class for Catalina does, but starting with 1.12.2 > onward this results in an error message being displayed and the serialized > value being returned rather than the unserialized value. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10057) Redis documentation has passive and active expiration descriptions reversed
[ https://issues.apache.org/jira/browse/GEODE-10057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17508928#comment-17508928 ] ASF subversion and git services commented on GEODE-10057: - Commit 63c98d0bf76b7d8199d0fc087c2ba608227b4300 in geode's branch refs/heads/master from Dave Barnes [ https://gitbox.apache.org/repos/asf?p=geode.git;h=63c98d0 ] GEODE-10057: Correct geode-for-redis docs > Redis documentation has passive and active expiration descriptions reversed > --- > > Key: GEODE-10057 > URL: https://issues.apache.org/jira/browse/GEODE-10057 > Project: Geode > Issue Type: Bug > Components: docs, redis >Affects Versions: 1.15.0 >Reporter: Donal Evans >Assignee: Donal Evans >Priority: Major > Labels: blocks-1.15.0, pull-request-available > Fix For: 1.14.3, 1.15.0 > > > The geode-for-redis documentation describes the difference in behaviour for > active expiration and passive expiration, but the way these terms are used is > flipped from how they're typically used in documentation about open source > Redis: https://redis.io/commands/expire#how-redis-expires-keys. The docs > should be updated to match the usage in open source Redis documentation. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9758) Provide an easy to configure a process-wide serialization filter for use on Java 8
[ https://issues.apache.org/jira/browse/GEODE-9758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17508927#comment-17508927 ] ASF subversion and git services commented on GEODE-9758: Commit 8f3186cb74ccd2eb1ec8ba648c7a11b08d575962 in geode's branch refs/heads/master from Kirk Lund [ https://gitbox.apache.org/repos/asf?p=geode.git;h=8f3186c ] GEODE-9817: Enable customized source set paths for ClassAnalysisRule (#7367) Adds support for customizing source set paths of ClassAnalysisRule. PROBLEM Modules external to Geode must be structured the same as Geode source code in order to use ClassAnalysisRule and the Analyze*Serializables tests. This is necessary to better facilitate pluggability of modules that need to provide sanctioned serializable lists. SOLUTION Add source set path customization to ClassAnalysisRule, introduce a new layer of Analyze*Serializables test base classes that can be directly extended in order to customize source set paths in ClassAnalysisRule. Also includes improvements to some iterating of classes during analysis. [prereq for backport of GEODE-9980 and GEODE-9758] (cherry picked from commit 5d1e91932dff296632916a6ceccfb36039357acd) > Provide an easy to configure a process-wide serialization filter for use on > Java 8 > -- > > Key: GEODE-9758 > URL: https://issues.apache.org/jira/browse/GEODE-9758 > Project: Geode > Issue Type: Improvement > Components: configuration, serialization >Affects Versions: 1.12.7, 1.13.0, 1.14.0 >Reporter: Jianxia Chen >Assignee: Kirk Lund >Priority: Major > Labels: GeodeOperationAPI, docs, pull-request-available > > Provide an easy way to configure a process-wide serialization filter for use > on Java 8. When enabled, validate-serializable-objects should be enabled and > the process-wide serialization filter should be configured to accept only JDK > classes and Geode classes in addition to anything the user might specify with > serializable-object-filter. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9980) Startup of Locator or Server should fail fast if geode.enableGlobalSerialFilter is enabled but fails configuration
[
https://issues.apache.org/jira/browse/GEODE-9980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17508926#comment-17508926
]
ASF subversion and git services commented on GEODE-9980:
Commit 8f3186cb74ccd2eb1ec8ba648c7a11b08d575962 in geode's branch
refs/heads/master from Kirk Lund
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=8f3186c ]
GEODE-9817: Enable customized source set paths for ClassAnalysisRule (#7367)
Adds support for customizing source set paths of ClassAnalysisRule.
PROBLEM
Modules external to Geode must be structured the same as Geode
source code in order to use ClassAnalysisRule and the
Analyze*Serializables tests. This is necessary to better facilitate
pluggability of modules that need to provide sanctioned serializable
lists.
SOLUTION
Add source set path customization to ClassAnalysisRule, introduce
a new layer of Analyze*Serializables test base classes that can be
directly extended in order to customize source set paths in
ClassAnalysisRule. Also includes improvements to some iterating
of classes during analysis.
[prereq for backport of GEODE-9980 and GEODE-9758]
(cherry picked from commit 5d1e91932dff296632916a6ceccfb36039357acd)
> Startup of Locator or Server should fail fast if
> geode.enableGlobalSerialFilter is enabled but fails configuration
> --
>
> Key: GEODE-9980
> URL: https://issues.apache.org/jira/browse/GEODE-9980
> Project: Geode
> Issue Type: Bug
> Components: serialization
>Affects Versions: 1.15.0
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
> Labels: GeodeOperationAPI, blocks-1.15.0, pull-request-available
>
> The following error conditions need better handling which includes handling
> of all errors consistently and cause the startup of a Locator or Server to
> fail if it's unable to honor the setting of
> {{-Dgeode.enableGlobalSerialFilter=true}} for any reason. Currently, if
> {{-Dgeode.enableGlobalSerialFilter=true}} is specified but Geode is unable to
> create a global serial filter, then it will will log a warning and continue
> running. A user may easily miss that log statement and believe that the JVM
> is running with a properly configured serialization filter.
> 1) The user is trying to secure the JVM very thoroughly and accidentally
> specifies both {{-Djdk.serialFilter}} and
> {{-Dgeode.enableGlobalSerialFilter}}.
> 2) The user runs some non-Geode code in the same JVM that invokes
> {{ObjectInputFilter.Config.setFilter(...)}} directly.
> 3) The user is using a version of Java 8 prior to 8u121 (the release that
> first added {{sun.misc.ObjectInputFilter}}) and specifies
> {{-Dgeode.enableGlobalSerialFilter=true}}. Also, the same behavior occurs if
> they do NOT specify enabling that property.
> 4) {{LocatorLauncher}} or {{ServerLauncher}} is started in a JVM that has
> already created at least one {{ObjectInputStream}} which will cause
> {{ObjectInputFilter.Config.setFilter(...)}} to fail.
> 5) {{LocatorLauncher}} or {{ServerLauncher}} is started in a Java 8 JVM that
> is not based on OpenJDK (ie {{sun.misc.ObjectInputFilter}} does not exist).
> 6) {{LocatorLauncher}} or {{ServerLauncher}} is started in an unforeseen
> environment that causes invocation of
> {{ObjectInputFilter.Config.setFilter(...)}} via Java Reflection to throw
> {{IllegalAccessException}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-9817) Allow analyze serializables tests to provide custom source set paths to ClassAnalysisRule
[ https://issues.apache.org/jira/browse/GEODE-9817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17508925#comment-17508925 ] ASF subversion and git services commented on GEODE-9817: Commit 8f3186cb74ccd2eb1ec8ba648c7a11b08d575962 in geode's branch refs/heads/master from Kirk Lund [ https://gitbox.apache.org/repos/asf?p=geode.git;h=8f3186c ] GEODE-9817: Enable customized source set paths for ClassAnalysisRule (#7367) Adds support for customizing source set paths of ClassAnalysisRule. PROBLEM Modules external to Geode must be structured the same as Geode source code in order to use ClassAnalysisRule and the Analyze*Serializables tests. This is necessary to better facilitate pluggability of modules that need to provide sanctioned serializable lists. SOLUTION Add source set path customization to ClassAnalysisRule, introduce a new layer of Analyze*Serializables test base classes that can be directly extended in order to customize source set paths in ClassAnalysisRule. Also includes improvements to some iterating of classes during analysis. [prereq for backport of GEODE-9980 and GEODE-9758] (cherry picked from commit 5d1e91932dff296632916a6ceccfb36039357acd) > Allow analyze serializables tests to provide custom source set paths to > ClassAnalysisRule > - > > Key: GEODE-9817 > URL: https://issues.apache.org/jira/browse/GEODE-9817 > Project: Geode > Issue Type: Wish > Components: tests >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Labels: pull-request-available > Fix For: 1.14.4, 1.15.0 > > > In order to make SanctionedSerializablesService and the related tests to be > more pluggable by external modules, I need to make changes to allow analyze > serializables tests to provide custom source set paths to ClassAnalysisRule. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9923) User Guide: add Log Message troubleshooting section
[ https://issues.apache.org/jira/browse/GEODE-9923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17508923#comment-17508923 ] ASF subversion and git services commented on GEODE-9923: Commit 5a550110defaffcff2daff0becfc8740a448ca60 in geode's branch refs/heads/master from Dave Barnes [ https://gitbox.apache.org/repos/asf?p=geode.git;h=5a55011 ] GEODE-9923: Add log message troubleshooting info from support team community (#7296) > User Guide: add Log Message troubleshooting section > --- > > Key: GEODE-9923 > URL: https://issues.apache.org/jira/browse/GEODE-9923 > Project: Geode > Issue Type: Improvement > Components: docs >Affects Versions: 1.14.2 >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Labels: pull-request-available > Fix For: 1.12.9, 1.13.8, 1.14.4, 1.15.0 > > > GemFire support team (who are also Geode community members) have compiled a > troubleshooting guide that maps log messages to suggested solutions. > They have contributed this to Geode in the form of a Google doc. > Reformat the Google doc and add it to the Geode user guide. There's an > existing section under Managing Apache Geode called Troubleshooting and > System Recovery that would be a good location for this material. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9990) Geode should handle certain DiskAccessException due to CacheClosedException when creating bucket
[
https://issues.apache.org/jira/browse/GEODE-9990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17508929#comment-17508929
]
ASF subversion and git services commented on GEODE-9990:
Commit dede61d4813ecba9a51c7417214ea69092a88172 in geode's branch
refs/heads/master from Joris Melchior
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=dede61d ]
GEODE-9990: turn DiskAccessException into CacheClosedException (#7334) (#7379)
* GEODE-9990: turn DiskAccessException into CacheClosedException
- when DiskInitFile is in closed state and DiskStoreImpl is closed or
closing
- catch DiskAccessException in PRHARedundancyProvider and turn into
CacheClosedException if cache closing is in progress
- change CreateBucketMessage to handle DiskAccessException as cause of
ReplyException
(cherry picked from commit a98197b5d0a3a2547e0581e475dcabaa82e6e92f)
> Geode should handle certain DiskAccessException due to CacheClosedException
> when creating bucket
>
>
> Key: GEODE-9990
> URL: https://issues.apache.org/jira/browse/GEODE-9990
> Project: Geode
> Issue Type: Bug
> Components: persistence
>Affects Versions: 1.15.0
>Reporter: Eric Shu
>Assignee: Joris Melchior
>Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
> Fix For: 1.14.4, 1.15.0
>
>
> This exception is thrown to the node that tries to create the bucket to
> prevent it trying to create the bucket to next available server and fail the
> entry operation.
> {noformat}
> org.apache.geode.cache.DiskAccessException: For DiskStore: diskStore: The
> disk store is closed
> at Remote Member
> 'rs-FullRegression21837175a0i3large-hydra-client-49(dataStoregemfire2_host1_31566:31566):41002'
> in
> org.apache.geode.internal.cache.DiskInitFile.writeIFRecord(DiskInitFile.java:1313)
> at Remote Member
> 'rs-FullRegression21837175a0i3large-hydra-client-49(dataStoregemfire2_host1_31566:31566):41002'
> in
> org.apache.geode.internal.cache.DiskInitFile.writeIFRecord(DiskInitFile.java:916)
> at Remote Member
> 'rs-FullRegression21837175a0i3large-hydra-client-49(dataStoregemfire2_host1_31566:31566):41002'
> in
> org.apache.geode.internal.cache.DiskInitFile.markInitialized(DiskInitFile.java:2158)
> at Remote Member
> 'rs-FullRegression21837175a0i3large-hydra-client-49(dataStoregemfire2_host1_31566:31566):41002'
> in
> org.apache.geode.internal.cache.DiskStoreImpl.setInitialized(DiskStoreImpl.java:3057)
> at Remote Member
> 'rs-FullRegression21837175a0i3large-hydra-client-49(dataStoregemfire2_host1_31566:31566):41002'
> in
> org.apache.geode.internal.cache.AbstractDiskRegion.setInitialized(AbstractDiskRegion.java:606)
> at Remote Member
> 'rs-FullRegression21837175a0i3large-hydra-client-49(dataStoregemfire2_host1_31566:31566):41002'
> in
> org.apache.geode.internal.cache.persistence.PersistenceAdvisorImpl.setOnline(PersistenceAdvisorImpl.java:392)
> at Remote Member
> 'rs-FullRegression21837175a0i3large-hydra-client-49(dataStoregemfire2_host1_31566:31566):41002'
> in
> org.apache.geode.internal.cache.BucketPersistenceAdvisor.endBucketCreation(BucketPersistenceAdvisor.java:467)
> at Remote Member
> 'rs-FullRegression21837175a0i3large-hydra-client-49(dataStoregemfire2_host1_31566:31566):41002'
> in
> org.apache.geode.internal.cache.PRHARedundancyProvider.endBucketCreationLocally(PRHARedundancyProvider.java:854)
> at Remote Member
> 'rs-FullRegression21837175a0i3large-hydra-client-49(dataStoregemfire2_host1_31566:31566):41002'
> in
> org.apache.geode.internal.cache.PRHARedundancyProvider.endBucketCreation(PRHARedundancyProvider.java:813)
> at Remote Member
> 'rs-FullRegression21837175a0i3large-hydra-client-49(dataStoregemfire2_host1_31566:31566):41002'
> in
> org.apache.geode.internal.cache.PRHARedundancyProvider.createBucketAtomically(PRHARedundancyProvider.java:701)
> at Remote Member
> 'rs-FullRegression21837175a0i3large-hydra-client-49(dataStoregemfire2_host1_31566:31566):41002'
> in
> org.apache.geode.internal.cache.partitioned.CreateBucketMessage.operateOnPartitionedRegion(CreateBucketMessage.java:150)
> at Remote Member
> 'rs-FullRegression21837175a0i3large-hydra-client-49(dataStoregemfire2_host1_31566:31566):41002'
> in
> org.apache.geode.internal.cache.partitioned.PartitionMessage.process(PartitionMessage.java:333)
> at Remote Member
> 'rs-FullRegression21837175a0i3large-hydra-client-49(dataStoregemfire2_host1_31566:31566):41002'
> in
> org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:376)
> at Remote Member
>
[jira] [Commented] (GEODE-9973) Documentation: socket-lease-time is not used to return sockets to a pool but to close them
[ https://issues.apache.org/jira/browse/GEODE-9973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17508924#comment-17508924 ] ASF subversion and git services commented on GEODE-9973: Commit 0162fed255cc7708ea6e476ff3e0f9300660d4f4 in geode's branch refs/heads/master from Donal Evans [ https://gitbox.apache.org/repos/asf?p=geode.git;h=0162fed ] GEODE-9973: Correct docs regarding P2P socket timeout behaviour (#7310) > Documentation: socket-lease-time is not used to return sockets to a pool but > to close them > -- > > Key: GEODE-9973 > URL: https://issues.apache.org/jira/browse/GEODE-9973 > Project: Geode > Issue Type: Bug > Components: docs >Affects Versions: 1.12.9, 1.13.8, 1.14.4, 1.15.0 >Reporter: Alberto Gomez >Assignee: Donal Evans >Priority: Major > Labels: pull-request-available > Fix For: 1.12.9, 1.13.8, 1.14.4, 1.15.0 > > > The "Making sure you have enough sockets" Geode documentation section says > the following about socket-lease-time (check underlined sentence): > > Peer-to-peer. For peer-to-peer threads that do not share sockets, you can use > the socket-lease-time to make sure that no socket sits idle for too long. > +When a socket that belongs to an individual thread remains unused for this > time period, the system automatically returns it to the pool.+ The next time > the thread needs a socket, it creates a new socket. > > Actually, the system automatically closes the connection in the situation > described instead of returning it to any pool. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10101) release 1.14.4
[ https://issues.apache.org/jira/browse/GEODE-10101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17508920#comment-17508920 ] ASF subversion and git services commented on GEODE-10101: - Commit dbb8b398dd21121cfbfc3280f5a4083b4e38ce87 in geode-examples's branch refs/heads/master from Dick Cavender [ https://gitbox.apache.org/repos/asf?p=geode-examples.git;h=dbb8b39 ] GEODE-10101: Bump version to 1.14.5 As part of the Geode Release Process, the geode-examples build number must be rolled forward as work begins on the next release > release 1.14.4 > -- > > Key: GEODE-10101 > URL: https://issues.apache.org/jira/browse/GEODE-10101 > Project: Geode > Issue Type: Task > Components: release >Reporter: Dick Cavender >Priority: Major > > Release to incorporate GEODE-10093 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10100) release 1.13.8
[ https://issues.apache.org/jira/browse/GEODE-10100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17508919#comment-17508919 ] ASF subversion and git services commented on GEODE-10100: - Commit 56365c0c984a3bf3848281fb8b771cb1f888b3ce in geode-examples's branch refs/heads/master from Dick Cavender [ https://gitbox.apache.org/repos/asf?p=geode-examples.git;h=56365c0 ] GEODE-10100: Bump version to 1.14.4 As part of the Geode Release Process, the geode-examples build number must be rolled forward as work begins on the next release > release 1.13.8 > -- > > Key: GEODE-10100 > URL: https://issues.apache.org/jira/browse/GEODE-10100 > Project: Geode > Issue Type: Task > Components: release >Reporter: Dick Cavender >Priority: Major > Labels: pull-request-available > Fix For: 1.12.10, 1.13.9, 1.14.5, 1.15.0 > > > Release to incorporate GEODE-10093 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10101) release 1.14.4
[ https://issues.apache.org/jira/browse/GEODE-10101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17508914#comment-17508914 ] ASF subversion and git services commented on GEODE-10101: - Commit 3ff8f6f124feb6adac3ef504f99ad62062552ce8 in geode's branch refs/heads/support/1.14 from Dick Cavender [ https://gitbox.apache.org/repos/asf?p=geode.git;h=3ff8f6f ] GEODE-10101: update Dockerfile to apache-geode 1.14.4 The Dockerfile is updated _after_ the release is already tagged, because it needs to embed the sha256 of the release > release 1.14.4 > -- > > Key: GEODE-10101 > URL: https://issues.apache.org/jira/browse/GEODE-10101 > Project: Geode > Issue Type: Task > Components: release >Reporter: Dick Cavender >Priority: Major > > Release to incorporate GEODE-10093 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10101) release 1.14.4
[ https://issues.apache.org/jira/browse/GEODE-10101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17508915#comment-17508915 ] ASF subversion and git services commented on GEODE-10101: - Commit 88e780ca6f6ae07eac2420305fe53cbc82c8775a in geode-native's branch refs/heads/support/1.14 from Dick Cavender [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=88e780c ] GEODE-10101: Update Dockerfile and vars Native client hardcodes Geode version to test with in several places. Update native Dockerfile and other variables to apache-geode 1.14.4 > release 1.14.4 > -- > > Key: GEODE-10101 > URL: https://issues.apache.org/jira/browse/GEODE-10101 > Project: Geode > Issue Type: Task > Components: release >Reporter: Dick Cavender >Priority: Major > > Release to incorporate GEODE-10093 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10138) Add Versioning Support for LPUSH
[ https://issues.apache.org/jira/browse/GEODE-10138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-10138: --- Labels: pull-request-available (was: ) > Add Versioning Support for LPUSH > > > Key: GEODE-10138 > URL: https://issues.apache.org/jira/browse/GEODE-10138 > Project: Geode > Issue Type: Improvement > Components: redis >Reporter: Wayne >Assignee: Bala Tripura Sundari Kaza Venkata >Priority: Major > Labels: pull-request-available > > Add versioning support for the LPUSH command. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-10138) Add Versioning Support for LPUSH
[ https://issues.apache.org/jira/browse/GEODE-10138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wayne reassigned GEODE-10138: - Assignee: Bala Tripura Sundari Kaza Venkata > Add Versioning Support for LPUSH > > > Key: GEODE-10138 > URL: https://issues.apache.org/jira/browse/GEODE-10138 > Project: Geode > Issue Type: Improvement > Components: redis >Reporter: Wayne >Assignee: Bala Tripura Sundari Kaza Venkata >Priority: Major > > Add versioning support for the LPUSH command. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-10138) Add Versioning Support for LPUSH
Wayne created GEODE-10138: - Summary: Add Versioning Support for LPUSH Key: GEODE-10138 URL: https://issues.apache.org/jira/browse/GEODE-10138 Project: Geode Issue Type: Improvement Components: redis Reporter: Wayne Add versioning support for the LPUSH command. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10131) Remove unused but set variable
[ https://issues.apache.org/jira/browse/GEODE-10131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17508835#comment-17508835 ] ASF GitHub Bot commented on GEODE-10131: moleske commented on pull request #947: URL: https://github.com/apache/geode-native/pull/947#issuecomment-1071081612 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@geode.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Remove unused but set variable > -- > > Key: GEODE-10131 > URL: https://issues.apache.org/jira/browse/GEODE-10131 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Michael Oleske >Priority: Major > Labels: pull-request-available > > When on AppleClang 13.1.6.13160021 on macOS 12.3, native client fails to > compile due to warning as error -Wunused-but-set-variable > Remove the offending lines to compile -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10131) Remove unused but set variable
[ https://issues.apache.org/jira/browse/GEODE-10131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17508822#comment-17508822 ] ASF GitHub Bot commented on GEODE-10131: pdxcodemonkey commented on pull request #947: URL: https://github.com/apache/geode-native/pull/947#issuecomment-1071106444 Looks like `CqPlusAuthInitializeTest.reAuthenticateWithDurable` is having trouble for some reason. Give it a try on your local machine and see if it misbehaves for you. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@geode.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Remove unused but set variable > -- > > Key: GEODE-10131 > URL: https://issues.apache.org/jira/browse/GEODE-10131 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Michael Oleske >Priority: Major > Labels: pull-request-available > > When on AppleClang 13.1.6.13160021 on macOS 12.3, native client fails to > compile due to warning as error -Wunused-but-set-variable > Remove the offending lines to compile -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10067) WANCopyRegionFunctionDelegate needs to be optimized to handle large regions
[ https://issues.apache.org/jira/browse/GEODE-10067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17508632#comment-17508632 ] ASF subversion and git services commented on GEODE-10067: - Commit ffde8c788e97a09203dd1eb9385f2355f9c408e9 in geode's branch refs/heads/develop from Alberto Gomez [ https://gitbox.apache.org/repos/asf?p=geode.git;h=ffde8c7 ] GEODE-10067: Optimize wan-copy region command (#7420) When the region to copy is partitioned and the gateway sender is parallel, each gateway sender sends the primary copies of the buckets in that server. Deserialization of the entries is also avoided. > WANCopyRegionFunctionDelegate needs to be optimized to handle large regions > --- > > Key: GEODE-10067 > URL: https://issues.apache.org/jira/browse/GEODE-10067 > Project: Geode > Issue Type: Improvement > Components: wan >Affects Versions: 1.15.0 >Reporter: Udo Kohlmeyer >Assignee: Alberto Gomez >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > The current WanCopyRegionFunctionDelegate may cause significant memory issues > in with really large regions. > The > [getEntries|https://github.com/apache/geode/blob/develop/geode-wan/src/main/java/org/apache/geode/management/internal/cli/functions/WanCopyRegionFunctionDelegate.java#L102] > method returns both primary and redundant Region Entries for local server. > The invocation of getEntries from the PartitionedRegionDataStore will cause > all entries to be deserialized > https://github.com/apache/geode/blob/develop/geode-core/src/main/java/org/apache/geode/internal/cache/PartitionedRegionDataStore.java#L2501-L2515 > The > [createBatch|https://github.com/apache/geode/blob/develop/geode-wan/src/main/java/org/apache/geode/management/internal/cli/functions/WanCopyRegionFunctionDelegate.java#L107-L108] > method creates a List equally that of the local Region > size. > Essentially ... In a system with VERY large regions this might cause > significant memory issues > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (GEODE-10067) WANCopyRegionFunctionDelegate needs to be optimized to handle large regions
[ https://issues.apache.org/jira/browse/GEODE-10067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Gomez resolved GEODE-10067. --- Fix Version/s: 1.15.0 Resolution: Fixed > WANCopyRegionFunctionDelegate needs to be optimized to handle large regions > --- > > Key: GEODE-10067 > URL: https://issues.apache.org/jira/browse/GEODE-10067 > Project: Geode > Issue Type: Improvement > Components: wan >Affects Versions: 1.15.0 >Reporter: Udo Kohlmeyer >Assignee: Alberto Gomez >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > The current WanCopyRegionFunctionDelegate may cause significant memory issues > in with really large regions. > The > [getEntries|https://github.com/apache/geode/blob/develop/geode-wan/src/main/java/org/apache/geode/management/internal/cli/functions/WanCopyRegionFunctionDelegate.java#L102] > method returns both primary and redundant Region Entries for local server. > The invocation of getEntries from the PartitionedRegionDataStore will cause > all entries to be deserialized > https://github.com/apache/geode/blob/develop/geode-core/src/main/java/org/apache/geode/internal/cache/PartitionedRegionDataStore.java#L2501-L2515 > The > [createBatch|https://github.com/apache/geode/blob/develop/geode-wan/src/main/java/org/apache/geode/management/internal/cli/functions/WanCopyRegionFunctionDelegate.java#L107-L108] > method creates a List equally that of the local Region > size. > Essentially ... In a system with VERY large regions this might cause > significant memory issues > -- This message was sent by Atlassian Jira (v8.20.1#820001)
