Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
New distribute registrations not loaded until after service restart #276
Testing out the distribute service, ran into an error getting the node to pick up new registered connections for distribute. My guess is that you have to bounce the service, or couchdb, in order to load changes in connections - either adding new ones or removing old ones.
If you restart the LR/uwsgi/couchdb services after registering the distribute connection, it will show up in the output
This is a long outstanding problem for which the rationale for why it was this way to begin with was terrible. There was this belief that changing the replication membership meant you're changing the node, and as such you must change the node identifier, since it is no longer the same node… it makes some amount of sense if the network is intended to be made up of static/finite number of members - if membership changed you'd want some signal to be able to tell that the makeup of the data that is contained is not-what-it-was-before; however IMO it's not very well founded reason for LR (maybe a DoD reason) - which is supposed to encourage more sharing - more networking.
I thought Walt had fixed this some time ago - however we found testing this was hit/miss. Essentially the problem stems back to the fact that the node configuration loads once at boot and never goes back to check CouchDB.
To fix, if not already, the service needs to just refresh the 'static configuration' so the newly added nodes are reloaded when /distribute is run.
On Apr 7, 2014, at 4:28 PM, joe hobson email@example.com