GF v3 Clustering V3 Clustering is a superset of GF v2 Clustering features. In addition to the existing GFv2 feature set, v3 clustering will address RFEs with high vote counts. RFEs such as :
- Firewall friendly communication within Domain entities
This will also help make performance improvements.
-
- Domain's interprocess communication will be based off of
JMX HTTP channel instead of the present JMX RMI channel
- Removing the Single point of Failure through Admin Server(DAS)
redundancy
-
- A secondary redundant DAS process acting in a slave mode
while the master DAS is running, will help overcome the present shortcoming : A domain cannot be managed, once the DAS fails.
- Pluggable Node Agent(NA) design
- NodeAgent in v2 served mainly to manage life cycle of
server instances and watchdog the instance processes In v3, A node agent would allow plugging in of any monitorable VM (agent) and manage its create/delete/ start/stop lifecycle.
- Improved diagnostics for NA
- Node Agent in v2 also has the responsibility to synchronize
contents for server instances either in out of process or in-process mode. v3 will improve on the diagnostics and logging for both the modes.
- Public interface for NA configuration and flexible
configuration for instance lifecycle management
-
- v3 will include a java config for Node Agent configuration
such as log levels, log location, system properties etc for the NA VM.
-
- v3 will provide flexible instance configuration such as
configuration to decide on instance startup on NA startup, instance synchronization on NA startup, whether to watchdog instances and the interval to restart after detection of failure on watchdogged processes and the max count of failures before which watchdogging is disabled.
- v2 Remote instance management had some inherent drawbacks due to lack of a shared memory mechanism for DAS to NA communication that gave rise to confusion when changes were made in bootstrap parameters. A user has to manually make sure that the two decoupled processes remained in sync on the bootstrap parameters such as master password,handshaken co-ordinates etc v3 clustering design will include an option for a user to choose between a shared memory mode and a decoupled processes mode(v2 mode)
- v3 may include extension of self-management rules in the NA VM
|