518271 - make node assignment smarter and support delayed assignment to a node

Status: RESOLVED FIXED

(Cloud Services Graveyard :: Server: Sync, defect, P1)

Description

[Mike Connor [:mconnor]]

Instead of sticking everyone onto whatever the currently-specified node, we should distribute evenly up to a per-node cap.  We should also cap new node assignments to better avoid spikes from new user setups.  I'll leave it to Toby/zandr to figure out what the user/signup caps should be, but if we can't assign a node to a user, we should just return an empty string and the client will deal.

Ideally, chknode should attempt to find the user a home on subsequent queries, since that'll give us complete control over new user spikes...

I'll file a bug on the client side of this (and implement it, since it doesn't depend on the server side at all).

Comment 1

[Mike Connor [:mconnor]]

This is fixed on weave-dev, will push to production in Tuesday's push.

Comment 2

[Mike Connor [:mconnor]]

Toby, what's left here?

Comment 3

[Toby Elliott [:telliott]]

The stuff I emailed about last week re the dashboard. Since nobody had any objections to the plan, I'll file the bugs.

Comment 4

[Toby Elliott [:telliott]]

Once the blockers are done, this is enabled by setting WEAVE_REGISTRATION_THROTTLE_DB to any value, and defining WEAVE_REGISTRATION_THROTTLE_HOST, WEAVE_REGISTRATION_THROTTLE_DB, WEAVE_REGISTRATION_THROTTLE_USER and WEAVE_REGISTRATION_THROTTLE_PASS

Let's not do that while we're not all around to test and watch for problems...

Comment 5

[Toby Elliott [:telliott]]

Whoops, ignore the dupe constant above