Adjust routing logic for new users to allow us to point X% of them to Spanner. #159
Assignees
Labels
3
Estimate - m - This is a small change, but there's some uncertainty.
Comments
tublitzed
added
the
3
|
This is going to Donovan once we get him access to this repo. |
|
@rfk can you give me permissions for this repo and assign this to me? |
|
Somehow I can't, I think I've lost my admin rights to this repo :-( I'll see if I can track down someone who does. |
|
The above has made its way into the correct place for actioning such requests (which for future reference, is as an issue in https://github.com/mozilla-services/github-management/) and I'll update here once it's complete. |
|
@fzzzy you should now have access to the repo; let me know if something isn't working as expect. |
|
Seems to be working, thanks! |
jrconlin
added a commit
that referenced
this issue
Dec 17, 2019
jrconlin
added a commit
that referenced
this issue
Dec 19, 2019
This adds a few entries into the .ini: ``` [tokenserver] spanner_entry = # Name of the spanner node name e.g. https://spanner.example.com spanner_node_id = # default spanner node id migrate_new_user_percentage = # percentage of users to send to spanner ``` *note* the "percentage" is a terrible hack that just sends the first _n_ of every 100 users to spanner. Closes #159
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We're planning to rollout Durable Sync for brand new users of Sync only to start with. Before we can move to phase 2, we'll need to adjust the logic here to make it easy to route users by a percentage.
Ideally, that percentage can be pulled from a config value somewhere so we can easily modify it without a deploy.
Once a user has been routed to Spanner, we'll need to continue routing them over to Spanner for subsequent sessions.
It looks like the logic for routing a new user lives here for reference.
The text was updated successfully, but these errors were encountered: