[jira] [Updated] (GEODE-10056) Gateway-reciver connection load mantained only on one locator
[
https://issues.apache.org/jira/browse/GEODE-10056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jakov Varenina updated GEODE-10056:
---
Description:
The first problem is that servers send incorrect gateway-receiver connection
load to locators with CacheServerLoadMessage. The second problem is that the
locator doesn't refresh gateway-receivers load per server in the local map with
the load received in CacheServerLoadMessage. This seems to be a bug, as there
is already a mechanism to track and store gateway-receiver connection load per
server in the locator, but that load is never refreshed by a fault at the
reception of CacheServerLoadMessage. Currently, receiver load is only
refreshed/increased on the locator that is handling
ClientConnectionRequest\{group=__recv_group...} and ClientConnectionResponse
messages from a remote server that is trying to establish gateway sender
connection. All other locators in a cluster will never refresh the
gateway-receiver connection load in this case. When the locator that was
serving remote gateway-senders goes down then a new locator will take that job.
Problem is that the new locator will not have a correct load (it was never
refreshed) and that would in most situations result in new gateway-sender
connections being established in an unbalanced way.
Way to reproduce the issue:
Start 2 clusters, Let's call site1 the sending and site2 the receiving site,
The receiving site should have at least 2 locators. Both have 2 servers. No
regions are needed.
Cluster-1 gfsh>list members
Member Count : 3Name | Id
- | -
locator10 | 10.0.2.15(locator10:7332:locator):41000 [Coordinator]
server11 | 10.0.2.15(server11:8358):41003
server12 | 10.0.2.15(server12:8717):41005
Cluster-2 gfsh>list members
Member Count : 4Name | Id
- | -
locator10 | 10.0.2.15(locator10:7562:locator):41001 [Coordinator]
locator11 | 10.0.2.15(locator11:8103:locator):41002
server11 | 10.0.2.15(server11:8547):41004
server12 | 10.0.2.15(server12:8908):41006
Create GW receiver in Site2 on both servers.
Cluster-2 gfsh>list gateways
GatewayReceiver Section Member | Port | Sender Count
| Senders Connected
-- | | | -
10.0.2.15(server11:8547):41004 | 5175 | 0 |
10.0.2.15(server12:8908):41006 | 5457 | 0 |
Create GW sender in Site1 on both servers. Use 10 dispatcher threads for easier
obervation.
Cluster-1 gfsh>list gateways
GatewaySender SectionGatewaySender Id | Member |
Remote Cluster Id | Type | Status | Queued Events | Receiver
Location
| -- | - |
| - | - | -
senderTo2 | 10.0.2.15(server11:8358):41003 | 2 |
Parallel | Running and Connected | 0 | 10.0.2.15:5457
senderTo2 | 10.0.2.15(server12:8717):41005 | 2 |
Parallel | Running and Connected | 0 | 10.0.2.15:5457
Observe balance in GW receiver connections in Site2. It will be perfect.
Cluster-2 gfsh>list gateways
GatewayReceiver Section Member | Port | Sender Count
| Senders Connected
-- | | |
-
10.0.2.15(server11:8547):41004 | 5175 | 12 |
10.0.2.15(server12:8717):41005, 10.0.2.15(server12:8717):41005,
10.0.2.15(server11:8358):41003, 10.0.2.15(server11:..
10.0.2.15(server12:8908):41006 | 5457 | 12 |
10.0.2.15(server12:8717):41005, 10.0.2.15(server12:8717):41005,
10.0.2.15(server12:8717):41005, 10.0.2.15(server12:..
12 connections each - 10 payload + 2 ping connections.
Now stop GW receiver in one server of site2. In Site1 do a stop/start
gateway-sender command - all connections will go to the only receiver in site2
(as expected). Check it:
Cluster-2 gfsh>list gateways
GatewayReceiver Section Member | Port | Sender Count
| Senders Connected
-- | | |
-
10.0.2.15(server11:8547):41004 | 5175 | 22 |
10.0.2.15(server11:8358):41003, 10.0.2.15(server12:8717):41005,
10.0.2.15(server11:8358):41003, 10.0.2.15(server11:..
10.0.2.15(server12:8908):41006 | 5457 | 0 |
Now 22 in just one receiver - 20 payload + 1 ping from each sender.
Stop GW sender in one server in Site1. Connection drops in G
[jira] [Resolved] (GEODE-10099) release 1.12.9
[ https://issues.apache.org/jira/browse/GEODE-10099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dick Cavender resolved GEODE-10099. --- Resolution: Resolved > release 1.12.9 > -- > > Key: GEODE-10099 > URL: https://issues.apache.org/jira/browse/GEODE-10099 > 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-10080) Upgrade Jedis client in benchmark tests to 4.1.1
[ https://issues.apache.org/jira/browse/GEODE-10080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-10080: --- Labels: pull-request-available (was: ) > Upgrade Jedis client in benchmark tests to 4.1.1 > > > Key: GEODE-10080 > URL: https://issues.apache.org/jira/browse/GEODE-10080 > Project: Geode > Issue Type: Task > Components: benchmarks, redis >Reporter: Eric Zoerner >Assignee: Eric Zoerner >Priority: Major > Labels: pull-request-available > > Upgrade Jedis client in benchmark tests to 4.1.1. This is necessary in order > to benchmark support for Redis 6.0 in Geode for Redis. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10099) release 1.12.9
[ https://issues.apache.org/jira/browse/GEODE-10099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17504479#comment-17504479 ] ASF subversion and git services commented on GEODE-10099: - Commit 19b889e510ce4fc9b07a740981219be7f20546aa in geode's branch refs/heads/develop from Dick Cavender [ https://gitbox.apache.org/repos/asf?p=geode.git;h=19b889e ] GEODE-10099: Add 1.12.9 as old version (#7438) Adds 1.12.9 to old versions on develop > release 1.12.9 > -- > > Key: GEODE-10099 > URL: https://issues.apache.org/jira/browse/GEODE-10099 > 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-10080) Upgrade Jedis client in benchmark tests to 4.1.1
[ https://issues.apache.org/jira/browse/GEODE-10080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17504478#comment-17504478 ] ASF GitHub Bot commented on GEODE-10080: DonalEvans merged pull request #165: URL: https://github.com/apache/geode-benchmarks/pull/165 -- 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 > Upgrade Jedis client in benchmark tests to 4.1.1 > > > Key: GEODE-10080 > URL: https://issues.apache.org/jira/browse/GEODE-10080 > Project: Geode > Issue Type: Task > Components: benchmarks, redis >Reporter: Eric Zoerner >Assignee: Eric Zoerner >Priority: Major > > Upgrade Jedis client in benchmark tests to 4.1.1. This is necessary in order > to benchmark support for Redis 6.0 in Geode for Redis. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10080) Upgrade Jedis client in benchmark tests to 4.1.1
[ https://issues.apache.org/jira/browse/GEODE-10080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17504482#comment-17504482 ] ASF subversion and git services commented on GEODE-10080: - Commit 0604473ec335dd2d70ce9045bc1eceecd2a2834f in geode-benchmarks's branch refs/heads/develop from Eric Zoerner [ https://gitbox.apache.org/repos/asf?p=geode-benchmarks.git;h=0604473 ] GEODE-10080: Upgrade jedis to 4.1.1 (#165) > Upgrade Jedis client in benchmark tests to 4.1.1 > > > Key: GEODE-10080 > URL: https://issues.apache.org/jira/browse/GEODE-10080 > Project: Geode > Issue Type: Task > Components: benchmarks, redis >Reporter: Eric Zoerner >Assignee: Eric Zoerner >Priority: Major > Labels: pull-request-available > > Upgrade Jedis client in benchmark tests to 4.1.1. This is necessary in order > to benchmark support for Redis 6.0 in Geode for Redis. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (GEODE-10080) Upgrade Jedis client in benchmark tests to 4.1.1
[ https://issues.apache.org/jira/browse/GEODE-10080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Zoerner resolved GEODE-10080. -- Fix Version/s: 1.16.0 Resolution: Fixed > Upgrade Jedis client in benchmark tests to 4.1.1 > > > Key: GEODE-10080 > URL: https://issues.apache.org/jira/browse/GEODE-10080 > Project: Geode > Issue Type: Task > Components: benchmarks, redis >Reporter: Eric Zoerner >Assignee: Eric Zoerner >Priority: Major > Labels: pull-request-available > Fix For: 1.16.0 > > > Upgrade Jedis client in benchmark tests to 4.1.1. This is necessary in order > to benchmark support for Redis 6.0 in Geode for Redis. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10117) Add doc section mentioning the relationship between local-max-memory and lru eviction memory
[ https://issues.apache.org/jira/browse/GEODE-10117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-10117: -- Labels: needsTriage (was: ) > Add doc section mentioning the relationship between local-max-memory and lru > eviction memory > > > Key: GEODE-10117 > URL: https://issues.apache.org/jira/browse/GEODE-10117 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Nabarun Nag >Priority: Major > Labels: needsTriage > > Section to be added : > **Note:** For partition regions if the partition region attribute > `local-max-memory` is set then the eviction attribute `lru-memory-size > maximum` is overwritten with the value of `local-max-memory` > Both `local-max-memory` and `lru-memory-size maximum` are local > member attributes and not cluster-wide. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-10117) Add doc section mentioning the relationship between local-max-memory and lru eviction memory
[ https://issues.apache.org/jira/browse/GEODE-10117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nabarun Nag reassigned GEODE-10117: --- Assignee: Nabarun Nag > Add doc section mentioning the relationship between local-max-memory and lru > eviction memory > > > Key: GEODE-10117 > URL: https://issues.apache.org/jira/browse/GEODE-10117 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Nabarun Nag >Assignee: Nabarun Nag >Priority: Major > Labels: needsTriage > > Section to be added : > **Note:** For partition regions if the partition region attribute > `local-max-memory` is set then the eviction attribute `lru-memory-size > maximum` is overwritten with the value of `local-max-memory` > Both `local-max-memory` and `lru-memory-size maximum` are local > member attributes and not cluster-wide. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-10117) Add doc section mentioning the relationship between local-max-memory and lru eviction memory
Nabarun Nag created GEODE-10117: --- Summary: Add doc section mentioning the relationship between local-max-memory and lru eviction memory Key: GEODE-10117 URL: https://issues.apache.org/jira/browse/GEODE-10117 Project: Geode Issue Type: Bug Components: docs Reporter: Nabarun Nag Section to be added : **Note:** For partition regions if the partition region attribute `local-max-memory` is set then the eviction attribute `lru-memory-size maximum` is overwritten with the value of `local-max-memory` Both `local-max-memory` and `lru-memory-size maximum` are local member attributes and not cluster-wide. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10117) Add doc section mentioning the relationship between local-max-memory and lru eviction memory
[ https://issues.apache.org/jira/browse/GEODE-10117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-10117: --- Labels: needsTriage pull-request-available (was: needsTriage) > Add doc section mentioning the relationship between local-max-memory and lru > eviction memory > > > Key: GEODE-10117 > URL: https://issues.apache.org/jira/browse/GEODE-10117 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Nabarun Nag >Assignee: Nabarun Nag >Priority: Major > Labels: needsTriage, pull-request-available > > Section to be added : > **Note:** For partition regions if the partition region attribute > `local-max-memory` is set then the eviction attribute `lru-memory-size > maximum` is overwritten with the value of `local-max-memory` > Both `local-max-memory` and `lru-memory-size maximum` are local > member attributes and not cluster-wide. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10117) Add doc section mentioning the relationship between local-max-memory and lru eviction memory
[ https://issues.apache.org/jira/browse/GEODE-10117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17504611#comment-17504611 ] ASF subversion and git services commented on GEODE-10117: - Commit ac0c3d53f0bdbbe3105a00b40c077b3c2a6c26fd in geode's branch refs/heads/develop from Nabarun Nag [ https://gitbox.apache.org/repos/asf?p=geode.git;h=ac0c3d5 ] GEODE-10117: Added section in docs about memory (#7439) * Added section in the doc about lru max memory being over written if local max memory is set. * Also mentioned that these two settings are local and not cluster wide * Format change to preserve existing note alongside the new one. Co-authored-by: Dave Barnes > Add doc section mentioning the relationship between local-max-memory and lru > eviction memory > > > Key: GEODE-10117 > URL: https://issues.apache.org/jira/browse/GEODE-10117 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Nabarun Nag >Assignee: Nabarun Nag >Priority: Major > Labels: needsTriage, pull-request-available > > Section to be added : > **Note:** For partition regions if the partition region attribute > `local-max-memory` is set then the eviction attribute `lru-memory-size > maximum` is overwritten with the value of `local-max-memory` > Both `local-max-memory` and `lru-memory-size maximum` are local > member attributes and not cluster-wide. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10099) release 1.12.9
[ https://issues.apache.org/jira/browse/GEODE-10099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen Nichols updated GEODE-10099: - Fix Version/s: 1.12.10 1.13.9 1.14.5 1.15.0 1.16.0 > release 1.12.9 > -- > > Key: GEODE-10099 > URL: https://issues.apache.org/jira/browse/GEODE-10099 > 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, 1.16.0 > > > Release to incorporate GEODE-10093. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10103) Rebalance with no setting for include-region doesn't work for subregions
[
https://issues.apache.org/jira/browse/GEODE-10103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17504625#comment-17504625
]
ASF subversion and git services commented on GEODE-10103:
-
Commit d8f5afcecab615113c4326a32e9f56e0dfaa44f6 in geode's branch
refs/heads/support/1.15 from Barry Oglesby
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=d8f5afc ]
GEODE-10103: Retrieve full region path names (#7419)
* GEODE-10103: Retrieve full region path names
This commit modifies RebalanceOperationPerformer getMemberRegionList
to invoke listAllRegionPaths instead of listNames.
(cherry picked from commit 8610ee70d470a8b30ab067db912bd0ac345d9df0)
> Rebalance with no setting for include-region doesn't work for subregions
>
>
> Key: GEODE-10103
> URL: https://issues.apache.org/jira/browse/GEODE-10103
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Barrett Oglesby
>Assignee: Barrett Oglesby
>Priority: Major
> Labels: needsTriage, pull-request-available
>
> Executing a command like this produces no output for the rebalance command
> even though a region exists to rebalance:
> {noformat}
> gfsh -e "connect --locator=localhost[23456]" -e "rebalance"{noformat}
> Output:
> {noformat}
> ./rebalance.sh
> (1) Executing - connect --locator=localhost[23456]
> Connecting to Locator at [host=localhost, port=23456] ..
> Connecting to Manager at [host=192.168.1.5, port=1099] ..
> Successfully connected to: [host=192.168.1.5, port=1099]
> You are connected to a cluster of version: 1.16.0-build.0
> (2) Executing - rebalance{noformat}
> Running from gfsh directly does:
> {noformat}
> gfsh>rebalance
> gfsh> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-9910) Failure to auto-reconnect upon network partition
[ https://issues.apache.org/jira/browse/GEODE-9910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17504636#comment-17504636 ] ASF subversion and git services commented on GEODE-9910: Commit dd665e9699960facea5ce62215359165d175648c in geode's branch refs/heads/support/1.14 from Barry Oglesby [ https://gitbox.apache.org/repos/asf?p=geode.git;h=dd665e9 ] GEODE-9910: Stop embedded locator after failed start (#7393) The start-locator property causes a locator to be started when the InternalDistributedSystem is initialized. The initialize method creates the locator and then creates a ClusterDistributionManager. If the creation of the ClusterDistributionManager failed, the started locator was not stopped. This change addresses that by stopping the locator if an exception occurs. (cherry picked from commit 72665b1ec5c6a6b91d0d6c57e997c23033578c58) (cherry picked from commit 5a32ec00bdbd949bc473322c3643f3d96165d62d) > Failure to auto-reconnect upon network partition > > > Key: GEODE-9910 > URL: https://issues.apache.org/jira/browse/GEODE-9910 > Project: Geode > Issue Type: Bug >Affects Versions: 1.14.0 >Reporter: Surya Mudundi >Assignee: Barrett Oglesby >Priority: Major > Labels: GeodeOperationAPI, blocks-1.15.0, needsTriage, > pull-request-available > Attachments: geode-logs.zip > > > Two node cluster with embedded locators failed to auto-reconnect when node-1 > experienced network outage for couple of minutes and when node-1 recovered > from the outage, node-2 failed to auto-reconnect. > node-2 tried to re-connect to node-1 as: > [org.apache.geode.distributed.internal.InternalDistributedSystem]-[ReconnectThread] > [] Attempting to reconnect to the distributed system. This is attempt #1. > [org.apache.geode.distributed.internal.InternalDistributedSystem]-[ReconnectThread] > [] Attempting to reconnect to the distributed system. This is attempt #2. > [org.apache.geode.distributed.internal.InternalDistributedSystem]-[ReconnectThread] > [] Attempting to reconnect to the distributed system. This is attempt #3. > Finally reported below error after 3 attempts as: > INFO > [org.apache.geode.logging.internal.LoggingProviderLoader]-[ReconnectThread] > [] Using org.apache.geode.logging.internal.SimpleLoggingProvider for service > org.apache.geode.logging.internal.spi.LoggingProvider > INFO [org.apache.geode.internal.InternalDataSerializer]-[ReconnectThread] [] > initializing InternalDataSerializer with 0 services > INFO > [org.apache.geode.distributed.internal.InternalDistributedSystem]-[ReconnectThread] > [] performing a quorum check to see if location services can be started early > INFO > [org.apache.geode.distributed.internal.InternalDistributedSystem]-[ReconnectThread] > [] Quorum check passed - allowing location services to start early > WARN > [org.apache.geode.distributed.internal.InternalDistributedSystem]-[ReconnectThread] > [] Exception occurred while trying to connect the system during reconnect > java.lang.IllegalStateException: A locator can not be created because one > already exists in this JVM. > at > org.apache.geode.distributed.internal.InternalLocator.createLocator(InternalLocator.java:298) > ~[geode-core-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.InternalLocator.createLocator(InternalLocator.java:273) > ~[geode-core-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.InternalDistributedSystem.startInitLocator(InternalDistributedSystem.java:916) > ~[geode-core-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:768) > ~[geode-core-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.InternalDistributedSystem.access$200(InternalDistributedSystem.java:135) > ~[geode-core-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.InternalDistributedSystem$Builder.build(InternalDistributedSystem.java:3034) > ~[geode-core-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.InternalDistributedSystem.connectInternal(InternalDistributedSystem.java:290) > ~[geode-core-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.InternalDistributedSystem.reconnect(InternalDistributedSystem.java:2605) > ~[geode-core-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.InternalDistributedSystem.tryReconnect(InternalDistributedSystem.java:2424) > ~[geode-core-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.InternalDistributedSystem.disconnect(InternalDistributedSystem.java:1275) > ~[geode-core-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.ClusterDistributionManager$DMListener.m
[jira] [Commented] (GEODE-9910) Failure to auto-reconnect upon network partition
[ https://issues.apache.org/jira/browse/GEODE-9910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17504640#comment-17504640 ] ASF subversion and git services commented on GEODE-9910: Commit 732b735c1229ffda1e9d30f9cd23ccf6db34a999 in geode's branch refs/heads/support/1.13 from Barry Oglesby [ https://gitbox.apache.org/repos/asf?p=geode.git;h=732b735 ] GEODE-9910: Stop embedded locator after failed start (#7393) The start-locator property causes a locator to be started when the InternalDistributedSystem is initialized. The initialize method creates the locator and then creates a ClusterDistributionManager. If the creation of the ClusterDistributionManager failed, the started locator was not stopped. This change addresses that by stopping the locator if an exception occurs. (cherry picked from commit 72665b1ec5c6a6b91d0d6c57e997c23033578c58) (cherry picked from commit 5a32ec00bdbd949bc473322c3643f3d96165d62d) (cherry picked from commit 53e2b2e07a6312fa5307265d7e418e65667671cd) > Failure to auto-reconnect upon network partition > > > Key: GEODE-9910 > URL: https://issues.apache.org/jira/browse/GEODE-9910 > Project: Geode > Issue Type: Bug >Affects Versions: 1.14.0 >Reporter: Surya Mudundi >Assignee: Barrett Oglesby >Priority: Major > Labels: GeodeOperationAPI, blocks-1.15.0, needsTriage, > pull-request-available > Attachments: geode-logs.zip > > > Two node cluster with embedded locators failed to auto-reconnect when node-1 > experienced network outage for couple of minutes and when node-1 recovered > from the outage, node-2 failed to auto-reconnect. > node-2 tried to re-connect to node-1 as: > [org.apache.geode.distributed.internal.InternalDistributedSystem]-[ReconnectThread] > [] Attempting to reconnect to the distributed system. This is attempt #1. > [org.apache.geode.distributed.internal.InternalDistributedSystem]-[ReconnectThread] > [] Attempting to reconnect to the distributed system. This is attempt #2. > [org.apache.geode.distributed.internal.InternalDistributedSystem]-[ReconnectThread] > [] Attempting to reconnect to the distributed system. This is attempt #3. > Finally reported below error after 3 attempts as: > INFO > [org.apache.geode.logging.internal.LoggingProviderLoader]-[ReconnectThread] > [] Using org.apache.geode.logging.internal.SimpleLoggingProvider for service > org.apache.geode.logging.internal.spi.LoggingProvider > INFO [org.apache.geode.internal.InternalDataSerializer]-[ReconnectThread] [] > initializing InternalDataSerializer with 0 services > INFO > [org.apache.geode.distributed.internal.InternalDistributedSystem]-[ReconnectThread] > [] performing a quorum check to see if location services can be started early > INFO > [org.apache.geode.distributed.internal.InternalDistributedSystem]-[ReconnectThread] > [] Quorum check passed - allowing location services to start early > WARN > [org.apache.geode.distributed.internal.InternalDistributedSystem]-[ReconnectThread] > [] Exception occurred while trying to connect the system during reconnect > java.lang.IllegalStateException: A locator can not be created because one > already exists in this JVM. > at > org.apache.geode.distributed.internal.InternalLocator.createLocator(InternalLocator.java:298) > ~[geode-core-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.InternalLocator.createLocator(InternalLocator.java:273) > ~[geode-core-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.InternalDistributedSystem.startInitLocator(InternalDistributedSystem.java:916) > ~[geode-core-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:768) > ~[geode-core-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.InternalDistributedSystem.access$200(InternalDistributedSystem.java:135) > ~[geode-core-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.InternalDistributedSystem$Builder.build(InternalDistributedSystem.java:3034) > ~[geode-core-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.InternalDistributedSystem.connectInternal(InternalDistributedSystem.java:290) > ~[geode-core-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.InternalDistributedSystem.reconnect(InternalDistributedSystem.java:2605) > ~[geode-core-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.InternalDistributedSystem.tryReconnect(InternalDistributedSystem.java:2424) > ~[geode-core-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.InternalDistributedSystem.disconnect(InternalDistributedSystem.java:1275) > ~[geode-core-1.14.0.jar:?] > at > org.apac
[jira] [Commented] (GEODE-9910) Failure to auto-reconnect upon network partition
[ https://issues.apache.org/jira/browse/GEODE-9910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17504643#comment-17504643 ] ASF subversion and git services commented on GEODE-9910: Commit f435ec93ab3b8796bed39d3b67729449cb9a8f47 in geode's branch refs/heads/support/1.12 from Barry Oglesby [ https://gitbox.apache.org/repos/asf?p=geode.git;h=f435ec9 ] GEODE-9910: Stop embedded locator after failed start (#7393) The start-locator property causes a locator to be started when the InternalDistributedSystem is initialized. The initialize method creates the locator and then creates a ClusterDistributionManager. If the creation of the ClusterDistributionManager failed, the started locator was not stopped. This change addresses that by stopping the locator if an exception occurs. (cherry picked from commit 72665b1ec5c6a6b91d0d6c57e997c23033578c58) (cherry picked from commit 5a32ec00bdbd949bc473322c3643f3d96165d62d) (cherry picked from commit 53e2b2e07a6312fa5307265d7e418e65667671cd) (cherry picked from commit 490900535b1fc1582be63a4eed266e42cb170213) > Failure to auto-reconnect upon network partition > > > Key: GEODE-9910 > URL: https://issues.apache.org/jira/browse/GEODE-9910 > Project: Geode > Issue Type: Bug >Affects Versions: 1.14.0 >Reporter: Surya Mudundi >Assignee: Barrett Oglesby >Priority: Major > Labels: GeodeOperationAPI, blocks-1.15.0, needsTriage, > pull-request-available > Attachments: geode-logs.zip > > > Two node cluster with embedded locators failed to auto-reconnect when node-1 > experienced network outage for couple of minutes and when node-1 recovered > from the outage, node-2 failed to auto-reconnect. > node-2 tried to re-connect to node-1 as: > [org.apache.geode.distributed.internal.InternalDistributedSystem]-[ReconnectThread] > [] Attempting to reconnect to the distributed system. This is attempt #1. > [org.apache.geode.distributed.internal.InternalDistributedSystem]-[ReconnectThread] > [] Attempting to reconnect to the distributed system. This is attempt #2. > [org.apache.geode.distributed.internal.InternalDistributedSystem]-[ReconnectThread] > [] Attempting to reconnect to the distributed system. This is attempt #3. > Finally reported below error after 3 attempts as: > INFO > [org.apache.geode.logging.internal.LoggingProviderLoader]-[ReconnectThread] > [] Using org.apache.geode.logging.internal.SimpleLoggingProvider for service > org.apache.geode.logging.internal.spi.LoggingProvider > INFO [org.apache.geode.internal.InternalDataSerializer]-[ReconnectThread] [] > initializing InternalDataSerializer with 0 services > INFO > [org.apache.geode.distributed.internal.InternalDistributedSystem]-[ReconnectThread] > [] performing a quorum check to see if location services can be started early > INFO > [org.apache.geode.distributed.internal.InternalDistributedSystem]-[ReconnectThread] > [] Quorum check passed - allowing location services to start early > WARN > [org.apache.geode.distributed.internal.InternalDistributedSystem]-[ReconnectThread] > [] Exception occurred while trying to connect the system during reconnect > java.lang.IllegalStateException: A locator can not be created because one > already exists in this JVM. > at > org.apache.geode.distributed.internal.InternalLocator.createLocator(InternalLocator.java:298) > ~[geode-core-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.InternalLocator.createLocator(InternalLocator.java:273) > ~[geode-core-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.InternalDistributedSystem.startInitLocator(InternalDistributedSystem.java:916) > ~[geode-core-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:768) > ~[geode-core-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.InternalDistributedSystem.access$200(InternalDistributedSystem.java:135) > ~[geode-core-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.InternalDistributedSystem$Builder.build(InternalDistributedSystem.java:3034) > ~[geode-core-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.InternalDistributedSystem.connectInternal(InternalDistributedSystem.java:290) > ~[geode-core-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.InternalDistributedSystem.reconnect(InternalDistributedSystem.java:2605) > ~[geode-core-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.InternalDistributedSystem.tryReconnect(InternalDistributedSystem.java:2424) > ~[geode-core-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.InternalDistributedSystem.disconnect(InternalDistributedSys
[jira] [Commented] (GEODE-10103) Rebalance with no setting for include-region doesn't work for subregions
[
https://issues.apache.org/jira/browse/GEODE-10103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17504647#comment-17504647
]
ASF subversion and git services commented on GEODE-10103:
-
Commit 3b4ecd09a685b41e5b5d4df3927dd0e93ad87162 in geode's branch
refs/heads/support/1.14 from Barry Oglesby
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=3b4ecd0 ]
GEODE-10103: Retrieve full region path names (#7419)
* GEODE-10103: Retrieve full region path names
This commit modifies RebalanceOperationPerformer getMemberRegionList
to invoke listAllRegionPaths instead of listNames.
(cherry picked from commit 8610ee70d470a8b30ab067db912bd0ac345d9df0)
(cherry picked from commit d8f5afcecab615113c4326a32e9f56e0dfaa44f6)
> Rebalance with no setting for include-region doesn't work for subregions
>
>
> Key: GEODE-10103
> URL: https://issues.apache.org/jira/browse/GEODE-10103
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Barrett Oglesby
>Assignee: Barrett Oglesby
>Priority: Major
> Labels: needsTriage, pull-request-available
>
> Executing a command like this produces no output for the rebalance command
> even though a region exists to rebalance:
> {noformat}
> gfsh -e "connect --locator=localhost[23456]" -e "rebalance"{noformat}
> Output:
> {noformat}
> ./rebalance.sh
> (1) Executing - connect --locator=localhost[23456]
> Connecting to Locator at [host=localhost, port=23456] ..
> Connecting to Manager at [host=192.168.1.5, port=1099] ..
> Successfully connected to: [host=192.168.1.5, port=1099]
> You are connected to a cluster of version: 1.16.0-build.0
> (2) Executing - rebalance{noformat}
> Running from gfsh directly does:
> {noformat}
> gfsh>rebalance
> gfsh> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Resolved] (GEODE-10117) Add doc section mentioning the relationship between local-max-memory and lru eviction memory
[ https://issues.apache.org/jira/browse/GEODE-10117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nabarun Nag resolved GEODE-10117. - Fix Version/s: 1.16.0 Resolution: Fixed > Add doc section mentioning the relationship between local-max-memory and lru > eviction memory > > > Key: GEODE-10117 > URL: https://issues.apache.org/jira/browse/GEODE-10117 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Nabarun Nag >Assignee: Nabarun Nag >Priority: Major > Labels: needsTriage, pull-request-available > Fix For: 1.16.0 > > > Section to be added : > **Note:** For partition regions if the partition region attribute > `local-max-memory` is set then the eviction attribute `lru-memory-size > maximum` is overwritten with the value of `local-max-memory` > Both `local-max-memory` and `lru-memory-size maximum` are local > member attributes and not cluster-wide. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10103) Rebalance with no setting for include-region doesn't work for subregions
[
https://issues.apache.org/jira/browse/GEODE-10103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17504662#comment-17504662
]
ASF subversion and git services commented on GEODE-10103:
-
Commit ef29acb596039472a0f9a1c9b455942fe557d5b9 in geode's branch
refs/heads/support/1.13 from Barry Oglesby
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=ef29acb ]
GEODE-10103: Retrieve full region path names (#7419)
* GEODE-10103: Retrieve full region path names
This commit modifies RebalanceOperationPerformer getMemberRegionList
to invoke listAllRegionPaths instead of listNames.
(cherry picked from commit 8610ee70d470a8b30ab067db912bd0ac345d9df0)
(cherry picked from commit d8f5afcecab615113c4326a32e9f56e0dfaa44f6)
(cherry picked from commit 3b4ecd09a685b41e5b5d4df3927dd0e93ad87162)
> Rebalance with no setting for include-region doesn't work for subregions
>
>
> Key: GEODE-10103
> URL: https://issues.apache.org/jira/browse/GEODE-10103
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Barrett Oglesby
>Assignee: Barrett Oglesby
>Priority: Major
> Labels: needsTriage, pull-request-available
>
> Executing a command like this produces no output for the rebalance command
> even though a region exists to rebalance:
> {noformat}
> gfsh -e "connect --locator=localhost[23456]" -e "rebalance"{noformat}
> Output:
> {noformat}
> ./rebalance.sh
> (1) Executing - connect --locator=localhost[23456]
> Connecting to Locator at [host=localhost, port=23456] ..
> Connecting to Manager at [host=192.168.1.5, port=1099] ..
> Successfully connected to: [host=192.168.1.5, port=1099]
> You are connected to a cluster of version: 1.16.0-build.0
> (2) Executing - rebalance{noformat}
> Running from gfsh directly does:
> {noformat}
> gfsh>rebalance
> gfsh> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Resolved] (GEODE-10103) Rebalance with no setting for include-region doesn't work for subregions
[
https://issues.apache.org/jira/browse/GEODE-10103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barrett Oglesby resolved GEODE-10103.
-
Fix Version/s: 1.12.10
1.13.9
1.14.5
1.15.0
Resolution: Fixed
> Rebalance with no setting for include-region doesn't work for subregions
>
>
> Key: GEODE-10103
> URL: https://issues.apache.org/jira/browse/GEODE-10103
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Barrett Oglesby
>Assignee: Barrett Oglesby
>Priority: Major
> Labels: needsTriage, pull-request-available
> Fix For: 1.12.10, 1.13.9, 1.14.5, 1.15.0
>
>
> Executing a command like this produces no output for the rebalance command
> even though a region exists to rebalance:
> {noformat}
> gfsh -e "connect --locator=localhost[23456]" -e "rebalance"{noformat}
> Output:
> {noformat}
> ./rebalance.sh
> (1) Executing - connect --locator=localhost[23456]
> Connecting to Locator at [host=localhost, port=23456] ..
> Connecting to Manager at [host=192.168.1.5, port=1099] ..
> Successfully connected to: [host=192.168.1.5, port=1099]
> You are connected to a cluster of version: 1.16.0-build.0
> (2) Executing - rebalance{noformat}
> Running from gfsh directly does:
> {noformat}
> gfsh>rebalance
> gfsh> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Resolved] (GEODE-9910) Failure to auto-reconnect upon network partition
[ https://issues.apache.org/jira/browse/GEODE-9910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barrett Oglesby resolved GEODE-9910. Fix Version/s: 1.12.10 1.13.9 1.14.5 1.15.0 Resolution: Fixed > Failure to auto-reconnect upon network partition > > > Key: GEODE-9910 > URL: https://issues.apache.org/jira/browse/GEODE-9910 > Project: Geode > Issue Type: Bug >Affects Versions: 1.14.0 >Reporter: Surya Mudundi >Assignee: Barrett Oglesby >Priority: Major > Labels: GeodeOperationAPI, blocks-1.15.0, needsTriage, > pull-request-available > Fix For: 1.12.10, 1.13.9, 1.14.5, 1.15.0 > > Attachments: geode-logs.zip > > > Two node cluster with embedded locators failed to auto-reconnect when node-1 > experienced network outage for couple of minutes and when node-1 recovered > from the outage, node-2 failed to auto-reconnect. > node-2 tried to re-connect to node-1 as: > [org.apache.geode.distributed.internal.InternalDistributedSystem]-[ReconnectThread] > [] Attempting to reconnect to the distributed system. This is attempt #1. > [org.apache.geode.distributed.internal.InternalDistributedSystem]-[ReconnectThread] > [] Attempting to reconnect to the distributed system. This is attempt #2. > [org.apache.geode.distributed.internal.InternalDistributedSystem]-[ReconnectThread] > [] Attempting to reconnect to the distributed system. This is attempt #3. > Finally reported below error after 3 attempts as: > INFO > [org.apache.geode.logging.internal.LoggingProviderLoader]-[ReconnectThread] > [] Using org.apache.geode.logging.internal.SimpleLoggingProvider for service > org.apache.geode.logging.internal.spi.LoggingProvider > INFO [org.apache.geode.internal.InternalDataSerializer]-[ReconnectThread] [] > initializing InternalDataSerializer with 0 services > INFO > [org.apache.geode.distributed.internal.InternalDistributedSystem]-[ReconnectThread] > [] performing a quorum check to see if location services can be started early > INFO > [org.apache.geode.distributed.internal.InternalDistributedSystem]-[ReconnectThread] > [] Quorum check passed - allowing location services to start early > WARN > [org.apache.geode.distributed.internal.InternalDistributedSystem]-[ReconnectThread] > [] Exception occurred while trying to connect the system during reconnect > java.lang.IllegalStateException: A locator can not be created because one > already exists in this JVM. > at > org.apache.geode.distributed.internal.InternalLocator.createLocator(InternalLocator.java:298) > ~[geode-core-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.InternalLocator.createLocator(InternalLocator.java:273) > ~[geode-core-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.InternalDistributedSystem.startInitLocator(InternalDistributedSystem.java:916) > ~[geode-core-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:768) > ~[geode-core-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.InternalDistributedSystem.access$200(InternalDistributedSystem.java:135) > ~[geode-core-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.InternalDistributedSystem$Builder.build(InternalDistributedSystem.java:3034) > ~[geode-core-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.InternalDistributedSystem.connectInternal(InternalDistributedSystem.java:290) > ~[geode-core-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.InternalDistributedSystem.reconnect(InternalDistributedSystem.java:2605) > ~[geode-core-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.InternalDistributedSystem.tryReconnect(InternalDistributedSystem.java:2424) > ~[geode-core-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.InternalDistributedSystem.disconnect(InternalDistributedSystem.java:1275) > ~[geode-core-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.ClusterDistributionManager$DMListener.membershipFailure(ClusterDistributionManager.java:2326) > ~[geode-core-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.membership.gms.GMSMembership.uncleanShutdown(GMSMembership.java:1187) > ~[geode-membership-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.membership.gms.GMSMembership$ManagerImpl.lambda$forceDisconnect$0(GMSMembership.java:1811) > ~[geode-membership-1.14.0.jar:?] > at java.lang.Thread.run(Thread.java:829) [?:?] > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10103) Rebalance with no setting for include-region doesn't work for subregions
[
https://issues.apache.org/jira/browse/GEODE-10103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17504668#comment-17504668
]
ASF subversion and git services commented on GEODE-10103:
-
Commit 2ff0343454216171811275939032e92ae2ce63fd in geode's branch
refs/heads/support/1.12 from Barry Oglesby
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=2ff0343 ]
GEODE-10103: Retrieve full region path names (#7419)
* GEODE-10103: Retrieve full region path names
This commit modifies RebalanceOperationPerformer getMemberRegionList
to invoke listAllRegionPaths instead of listNames.
(cherry picked from commit 8610ee70d470a8b30ab067db912bd0ac345d9df0)
(cherry picked from commit d8f5afcecab615113c4326a32e9f56e0dfaa44f6)
(cherry picked from commit 3b4ecd09a685b41e5b5d4df3927dd0e93ad87162)
(cherry picked from commit ef29acb596039472a0f9a1c9b455942fe557d5b9)
> Rebalance with no setting for include-region doesn't work for subregions
>
>
> Key: GEODE-10103
> URL: https://issues.apache.org/jira/browse/GEODE-10103
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Barrett Oglesby
>Assignee: Barrett Oglesby
>Priority: Major
> Labels: needsTriage, pull-request-available
> Fix For: 1.12.10, 1.13.9, 1.14.5, 1.15.0
>
>
> Executing a command like this produces no output for the rebalance command
> even though a region exists to rebalance:
> {noformat}
> gfsh -e "connect --locator=localhost[23456]" -e "rebalance"{noformat}
> Output:
> {noformat}
> ./rebalance.sh
> (1) Executing - connect --locator=localhost[23456]
> Connecting to Locator at [host=localhost, port=23456] ..
> Connecting to Manager at [host=192.168.1.5, port=1099] ..
> Successfully connected to: [host=192.168.1.5, port=1099]
> You are connected to a cluster of version: 1.16.0-build.0
> (2) Executing - rebalance{noformat}
> Running from gfsh directly does:
> {noformat}
> gfsh>rebalance
> gfsh> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Resolved] (GEODE-10108) Duplicate Ops During GII/Delta Updates
[ https://issues.apache.org/jira/browse/GEODE-10108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jens Deppe resolved GEODE-10108. Fix Version/s: 1.16.0 Resolution: Fixed > Duplicate Ops During GII/Delta Updates > --- > > Key: GEODE-10108 > URL: https://issues.apache.org/jira/browse/GEODE-10108 > Project: Geode > Issue Type: Bug > Components: redis >Reporter: Wayne >Assignee: Jens Deppe >Priority: Major > Labels: blocks-1.15.0, pull-request-available > Fix For: 1.16.0 > > > When Redis commands are ongoing and a server that was previously not hosting > a bucket becomes the host of the primary bucket for a key, there exists a > time window where that server is performing GII but also receiving delta > updates from the previous primary bucket. This can lead to the delta being > applied to a data structure that is already in the “correct” state, resulting > in the command being applied twice. This can result in duplicated appends, > increments/decrements, and in the case of LTRIP and RPOP especially, > IndexOutOfBoundsException on the member applying the delta, as the index to > which the delta refers has already been removed. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-10118) PartitionedRegionClearWithConcurrentOperationsDUnitTest will hang in clearShouldFailWhenCoordinatorMemberIsBounced
Xiaojian Zhou created GEODE-10118: - Summary: PartitionedRegionClearWithConcurrentOperationsDUnitTest will hang in clearShouldFailWhenCoordinatorMemberIsBounced Key: GEODE-10118 URL: https://issues.apache.org/jira/browse/GEODE-10118 Project: Geode Issue Type: Bug Affects Versions: 1.16.0 Reporter: Xiaojian Zhou In PR Clear feature branch, after rebase merged in GEODE-9522, clusterDistributionManager setRootCause before TCPConduit.stop. It could cause restarting of server hang after force disconnect. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10118) PartitionedRegionClearWithConcurrentOperationsDUnitTest will hang in clearShouldFailWhenCoordinatorMemberIsBounced
[ https://issues.apache.org/jira/browse/GEODE-10118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-10118: -- Labels: needsTriage (was: ) > PartitionedRegionClearWithConcurrentOperationsDUnitTest will hang in > clearShouldFailWhenCoordinatorMemberIsBounced > --- > > Key: GEODE-10118 > URL: https://issues.apache.org/jira/browse/GEODE-10118 > Project: Geode > Issue Type: Bug >Affects Versions: 1.16.0 >Reporter: Xiaojian Zhou >Priority: Major > Labels: needsTriage > > In PR Clear feature branch, after rebase merged in GEODE-9522, > clusterDistributionManager setRootCause before TCPConduit.stop. It could > cause restarting of server hang after force disconnect. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10118) PartitionedRegionClearWithConcurrentOperationsDUnitTest will hang in clearShouldFailWhenCoordinatorMemberIsBounced
[ https://issues.apache.org/jira/browse/GEODE-10118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaojian Zhou updated GEODE-10118: -- Parent: GEODE-7665 Issue Type: Sub-task (was: Bug) > PartitionedRegionClearWithConcurrentOperationsDUnitTest will hang in > clearShouldFailWhenCoordinatorMemberIsBounced > --- > > Key: GEODE-10118 > URL: https://issues.apache.org/jira/browse/GEODE-10118 > Project: Geode > Issue Type: Sub-task >Affects Versions: 1.16.0 >Reporter: Xiaojian Zhou >Priority: Major > Labels: needsTriage > > In PR Clear feature branch, after rebase merged in GEODE-9522, > clusterDistributionManager setRootCause before TCPConduit.stop. It could > cause restarting of server hang after force disconnect. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10118) PartitionedRegionClearWithConcurrentOperationsDUnitTest will hang in clearShouldFailWhenCoordinatorMemberIsBounced
[ https://issues.apache.org/jira/browse/GEODE-10118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17504724#comment-17504724 ] Xiaojian Zhou commented on GEODE-10118: --- This is for PR clear feature branch only. Not for any releases yet. > PartitionedRegionClearWithConcurrentOperationsDUnitTest will hang in > clearShouldFailWhenCoordinatorMemberIsBounced > --- > > Key: GEODE-10118 > URL: https://issues.apache.org/jira/browse/GEODE-10118 > Project: Geode > Issue Type: Sub-task >Affects Versions: 1.16.0 >Reporter: Xiaojian Zhou >Priority: Major > Labels: needsTriage > > In PR Clear feature branch, after rebase merged in GEODE-9522, > clusterDistributionManager setRootCause before TCPConduit.stop. It could > cause restarting of server hang after force disconnect. -- This message was sent by Atlassian Jira (v8.20.1#820001)
