Closed seansan closed 6 years ago
The "concurrency" is with respect to a single session and is affected by the "max_concurrency" setting. So with "6" this means a single session (user) cannot have more than 6 processes requesting the lock before the requests will be aborted. Typically a page load should have one request that hits Magento and then all assets loaded without Magento so to hit a limit of 6 the user would have to do something like hold Ctrl while clicking links on the page as fast as they can. Or, there can be something causing very slow page loads or PHP fatal errors could be causing the lock to not be released. So AFAIK there is no bug and you are seeing this message for one of the other reasons, but it is not very easy to determine, just need to do some profiling and inspecting logs to figure it out. If you have any fatal errors those definitely have to be fixed first.
thanks updated to 10. And supplied local xml for other users per info
Hi, since last update we are seeing ConcurrentConnectionsExceededException (something we have not seen before). It this something new? or maybe in redis core?
I dont think we have any limiting setting. Also I dont understand the word "concurrent" because it is not like there are millions of users on our site. Maybe some kind of process is not releasing itself?
I attached my conf file
Maybe some has seen this before
LOCAL.XML
REDIS.CONF