Forum: Bug Report and Feature Requests

I retired from managing a site that has very unpredictable load, and I still consult to them. I was wondering how SOL manages the Too Many Concurrent Accesses message.

I wanted to send a private note the Lazeez, but can't really figure out how, so perhaps I can ask here, and I'll be happy to get an answer either here or privately.

I need a method that will review back end services like database and offline cache, and flip a switch on the web servers to deny new sessions.

While I can probably come up with something on my own, I would be happy not to reinvent the wheel.

Lazeez? Can you reach out to me?

Thanks,
Ed Greenberg

Upper right corner of the home page "Contact"

Too Many Concurrent Accesses

SOL implementation isn't a real concurrent access detection and prevention system.
You can trigger it only by loading multiple chapter list rapidly. My guess is that it's just a last request time saved in the server session. if not enough time has elapsed, it reply with a 503 thus bypassing mysql access and saving server resources. It only make sense if the limiting factor are database reads. With mySQL replicas, it shouldn't be the case.

I need a method that will review back end services like database and offline cache, and flip a switch on the web servers to deny new sessions.

That's a bit harsh, usually in constrained system, like sales tunnel you implement a queue and let the user know (count down) when it can attempt the purchase. That prevent a lot of user refreshing 503 pages which could be even more problematic.