You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

To be Reviewed By: 14 March 2022

Authors: Mario Ivanac

Status: Draft | Discussion | Active | Dropped | Superseded

Superseded by: N/A

Related: N/A

Problem

When several gateway receivers have the same value for hostname-for-senders (for example when running Geode under kubernetes and a load balancer balances the load among the remote servers), it has been observed that number of connections in gw senders pool used for sending ping message is much greater then number of dispatcher threads, although in this case only one connection could be used (since destinations have same address and port ). There are 2 reasons for this behavior:

  1. Since all Ping tasks are triggered in parallel, generally each task will request same connection at the same time, and we will create new connection for each task

Anti-Goals


Solution

Describe your solution and how it’s going to solve the problem. This is likely the largest section of your proposal and might even include some high-level diagrams if you are proposing code changes. While all important aspects need to be covered, also keep in mind that shorter documents are more likely to be read.

Changes and Additions to Public Interfaces


Performance Impact

No impacts.

Backwards Compatibility and Upgrade Path

No impacts.

Prior Art

What would be the alternatives to the proposed solution? What would happen if we don’t solve the problem? Why should this proposal be preferred?

FAQ

Answers to questions you’ve commonly been asked after requesting comments for this proposal.

Errata

What are minor adjustments that had to be made to the proposal since it was approved?

  • No labels