Justin Knoll wrote:
We plan to attempt to rewrite the snappuller (and possibly other
distribution scripts, as required) to eliminate this dependency on SSH.
I thought I ask the list in case anyone has experience with this same
situation or any insights into the reasoning behind requiring SSH access
to the master instance.
We use our database to store the master's state. Both master and
slave(s) have access to the database and can exchange "messages" using a
field in a table where we store miscellaneous information about our
system. After an update of the master's index a flag in that field
signals that a new index is available. The slaves regularly read this
field an pull the new index on demand.
Marcus
