You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2022/01/27 10:26:00 UTC
[jira] [Commented] (GEODE-9853) Optimize number of ParallelQueueRemovalMessage sent for dropped events in large clusters
[ https://issues.apache.org/jira/browse/GEODE-9853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17483045#comment-17483045 ]
ASF subversion and git services commented on GEODE-9853:
--------------------------------------------------------
Commit bbe9a3acf2f0812ef733dfe74f07fb9412c886e3 in geode's branch refs/heads/develop from Mario Ivanac
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=bbe9a3a ]
GEODE-9853: get all members hosting bucket (#7144)
* GEODE-9853: get all members hosting bucket
> Optimize number of ParallelQueueRemovalMessage sent for dropped events in large clusters
> ----------------------------------------------------------------------------------------
>
> Key: GEODE-9853
> URL: https://issues.apache.org/jira/browse/GEODE-9853
> Project: Geode
> Issue Type: Improvement
> Components: wan
> Reporter: Mario Ivanac
> Assignee: Mario Ivanac
> Priority: Major
> Labels: pull-request-available
>
> In multi site cluster (16 or more servers), in case we stop gw sender, and continue to put new entries in region, it is observed large number of ParallelQueueRemovalMessage sent.
> It seems that this can be optimized, since most of sent messages are ignored by most of other servers.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)