Page History

...

The state parameter will be persisted within cluster configuration, but only if gfsh commands are executed successfully on at least one of the servers. The only case when state will not be updated and persisted is when commands are executed per member (using --members parameter). The reason behind this is because cluster configuration is only persisted per cluster and group, and not per member. This exception will be documented.

Currently it is possible to configure gateway-sender to always start automatically or to always require manual start (manual-start=true) at member startup. With addition of the new parameter in Cluster Configuration this behavior will be changed in a following way:

1. If manual-start="true" and state parameter is missing, then gateway sender will require manual start (same as before).
2. If manual-start is not set (or "false") and state parameter is missing, then gateway sender will be started automatically (same as before).
3. If parameter state is available incluster configuration at startup, then gateway-sender will try to reach that state regardless of manual-start parameter value.

  Any  Any failures that happen when gateway-sender try to reach desire state will be handled same as now when for example automatic startup fail. The state parameter will remain unchanged in all failure cases at startup.

The behavior of manual-start parameter must be improved in order to comply to above requirements.

Current problem with manual-start parameter:

Currently when manual-start is configured in to be true, then colocated persistent parallel gateway sender queue region and buckets are not be recovered after server is started. Due to this reason the main colocated persistent region cannot reach online status.

Solution to manual-start problem:

When manual-start parameter is true or gateway sender state is stopped, then persistent parallel gateway-sender queues should be recovered (if needed) from persistent storage during startup of the server. They should be recovered by using the existing mechanism that is used when gateway sender is automatically recovered (manual-start==false) after server is started. In this case parallel gateway sender colocated persistent region and buckets will be recovered right after the main persistent region is recovered.

Additionally, parallel gateway sender should reach the same state is has when aromatically started and then stopped by using gfsh command. In that state parallel gateway sender buckets remain on the servers, but dispatcher threads are stopped and non of the events are stored in queues.

This new behavior will be really beneficial in automated environments like Kubernetes cluster where servers could be automatically restarted.

Changes and Additions to Public Interfaces

...