A dynamic cluster is a cluster schema where the slave servers are only known at runtime.
This situation is occurring in those situations where hosts are being added or removed at will, such as in cloud computing settings.
These are the components of a dynamic cluster configuration:
The master slave server is just the same as it was before. However, in the latest version (PDI 3.2) it gained a new trick: it can accept slave server registrations.
Once a slave server is registered, it will be monitored every 30 seconds to see if it is still available to run ETL jobs on.
The slave server gained a new trick as well: it can be configured through an XML file. This is what carte expects to find in it:
- masters: You can list the slave servers to which this slave has to report back to.
If this is a master, we will contact the other masters to get a list of all the slaves in the cluster.
- report_to_masters : send a message to the defined masters to let them know we exist (Y/N)
- slaveserver : specify the slave server details of this carte instance.
IMPORTANT : the username and password specified here are used by the master instances to connect to this slave.
In the <slaveserver> sections you can specify the <network_interface> parameter to replace the hostname with at Carte startup. It will take the primary IP address of the given network interface instead.
The carte configuration xml can be passed to carte as a command line option, for example:
Sample configuration files are located in the pwd directory.
On the transformation side, things become a bit easier: all we now need to do is check the "Dynamic" checkbox and specify a master slave server we want to talk to.
You can even specify multiple slave servers for fail-over purposes.
/kettle/getSlaves : retrieves the list of Slave Server Detections in XML. The layout of the document is this:
See also class: SlaveServerDetection
: Allows a slave server to register with a master server. This is the XML to send:
See also class: SlaveServer