Scalability and Daughterships

It is possible to run daughtership processes that read their configuration from a mothership process, and then act as that mothership would. This can provide advantages in some configurations, such as superclusters comprised of subclusters (interconnected with relatively fast networks) connected together across relatively slow networks. If each subcluster has a single dedicated daughtership process, only the daughtership need connect to the mothership to collect data; the other processes in the subcluster can get their connection information from the daughtership.

Daughterships can be arranged in something of a matriarchal hierarchy, with one grandmothership having multiple daughterships, and each of those daughterships also having daughterships of its own. This might provide startup performance advantages for very-large-scale clusters. (Note that only one grandmothership can exist in any configuration; there must be one and only one mothership at the top of the hierarchy.)

Running a Daughtership Process

To create a daughtership process, set appropriate environment variables, then run the Python script:

$ export CRMOTHERSHIP=mothermachine:port
$ export CRDAUGHTERSHIP=localhost:port
$ python

The daughtership will connect to the specified mothership, and will request and read all of the configuration information from that mothership. The mothership will, in turn, register the existence of the daughtership (so that dynamic configuration information will be shared with the daughtership).

The daughtership will then start listening for connections just as a mothership would. Other processes (say, a crserver) can be told to connect to the daughtership (by setting the CRMOTHERSHIP environment variable to point at the daughtership, rather than the mothership) and can operate (with a few limitations) just as though they were connected to the mothership.

Daughtership Limitations