clusters off-limits for account creation
Short, concise description of the idea
Temporarily directing new accounts away from clusters that are down
Full description of the idea
The recent FiletMignon issues and the resulting flood of support requests have led me here. There were many, many requests from user who created accounts on the FiletMignon cluster while the maintenance was in progress, and who were almost completely unable to use their accounts for up to a few weeks after creating them. There was also a huge upswing in account deletion requests from FiletMignon users during that time, many of which were brand-new accounts.
If a cluster has major problems that will take a while to fix and will severely inhibit account usability, or if it is going to be unusable for a while due to maintenance, someone ought to flip a magic switch somewhere that will prevent new accounts from being placed on that cluster until it is again usable.
- prevent a slew of new users hating the site as soon as they start using it, and abandoning their accounts en masse
- reduce discontent among new users
- Creating an account only to discover that you can't use it is Not Fun.
An ordered list of problems/issues involved
- If the cluster needs to be off-limits for long enough, and enough accounts are created during that time, there could be server load balance issues that would take a while to even out once the cluster was made available again. (if you think I don't really know what I'm talking about here, you're right.)
- The main priority for developers, of course, is fixing the problems and getting the maintenance done, and taking the time to put a cluster off-limits would delay the actual maintenance. For this reason, I have this in mind only for long-term problems that seriously affect usability (as opposed to, say, a 2-hour repair or all those annoying-but-nonfatal Chef issues back in the day).
An organized list, or a few short paragraphs detailing suggestions for implementation
- Dude, you don't need to worry about me getting too technical. I really couldn't say how this would be done.
- It might be nice to set up a console command for it, so it could be taken care of quickly without delaying actual maintenance. But of course I have no idea how much work that would entail.