To be Reviewed By: November 16th, 2020
Authors: Mario Ivanac
Status: Draft | Discussion | Active | Dropped | Superseded
Superseded by: N/A
Related: N/A
Currently, we can configure gateway sender, only at creation of gateway sender.
So if we want to modify any gateway sender attribute, we need to perform following steps:
Performing all these steps while traffic is ongoing, will result with data incosistency.
Due to that, we would like to introduce new command "alter gateway-sender" which would update some parameters in runtime. For now parameters of interest are:
Implement new command "alter gateway-sender" which will update gateway senders parameters in runtime. Parameters will be updated for gateway senders which have same ID as specified in command.
Current proposal will cover only changes for following parameters:
After command is executed, changes will be applied to specified gateway senders (ID), on specified (or all) members, and also in cluster configuration.
To avoid any interference, dispatch thread will be paused in moment when changes are applied for sender on each member (similar as it is done for "load-balance gateway-sender" command).
PR with proposed solution: https://github.com/apache/geode/pull/5630
New methods setAlertThreshold(), setBatchSize(), setBatchTimeInterval(), setGroupTransactionEvents(), setGatewayEventFilters() will be added to GatewaySender.
None
No upgrade or backwards compatibility issues.
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?
Answers to questions you’ve commonly been asked after requesting comments for this proposal.
What are minor adjustments that had to be made to the proposal since it was approved?
Be the first to like this