albertogpz opened a new pull request #5452: URL: https://github.com/apache/geode/pull/5452
…ifference This is a draft PR to see if it fixes, without any undesired effect, the difference in behavior in Geode between creating a region with a gateway sender or creating a region without it and then altering the region to add the gateway sender. In the second case, when executing transactions on partitioned regions, all members in the region are notified and not only those that host the entries corresponding to the transaction. The notification in the members who do not host entries for the transaction provokes that they try to queue the event in the gateway sender queue but as they do not host a bucket for the entry in the event, they are queued in ParallelGatewaySenderQueue.tempQueue. These events are removed from there when the event is sent by the primary gateway sender but if the remote site is stopped, these events stored in tempQueue could end up filling up the heap of the member. Thank you for submitting a contribution to Apache Geode. In order to streamline the review of the contribution we ask you to ensure the following steps have been taken: ### For all changes: - [ ] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message? - [ ] Has your PR been rebased against the latest commit within the target branch (typically `develop`)? - [ ] Is your initial contribution a single, squashed commit? - [ ] Does `gradlew build` run cleanly? - [ ] Have you written or updated unit tests to verify your changes? - [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)? ### Note: Please ensure that once the PR is submitted, check Concourse for build issues and submit an update to your PR as soon as possible. If you need help, please send an email to [email protected]. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
