many simultaneous new token requests kill peakaboo

[ppettit]

@androidwiltron said:

"if a user in peakaboo example 'galicaster' has many valid tokens then more are requested simultaneously the database becomes unresponsive and tokens cannot be requested, rooms remain 'offline' and users cannot visit the page getting timeout errors instead.
a suggestion was to use a UID per room to authenticate against peakaboo thus having a small array of tokens for each user making this step more responsive"

[paulgration]

We had this recently and the only solution we could find was to go into the mongo database and clear all the login tokens out - documenting what we did as it may be useful for others too..

If using docker then use docker ps to list container IDs then docker exec -it {CONTAINER_ID} mongo to connect to the mongodb running in the container - may need to prefix with sudo depending on your setup.
For non-docker instances use meteor mongo while meteor is running

Then..

// Use the peakaboo database
use peakaboo;

// Find the user that needs loginTokens clearing out
db.users.find();

// Clear all loginTokens for the user
db.users.update({ "_id" : "{GALICASTER_USER_ID"}, {$set: {"services.resume.loginTokens": []}});

Then restart peakaboo. I'm guessing you did something similar @androidwiltron?