You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the case of high concurrency, many errors are reported, mainly performance related
「invokewithcallback」 is for: check connection failed for address: origin URL [x.x.x.x:43314], unique key [x.x.x.x:43314], maybe write overflow!
「exception」 is for: represents timeout
「retrytimes」 is for: it means to retry 10 times or fail, and finally give up
How to solve
Use multiple connections between sessionServer and dataServer
Resolve the low efficiency of processing in SessionServer
e.g. trace com.alipay.sofa.registry.server.session.remoting.handler.DataChangeRequestHandler reply -n 100 #cost>2000
The text was updated successfully, but these errors were encountered:
In the case of high concurrency, many errors are reported, mainly performance related
「invokewithcallback」 is for: check connection failed for address: origin URL [x.x.x.x:43314], unique key [x.x.x.x:43314], maybe write overflow!
「exception」 is for: represents timeout
「retrytimes」 is for: it means to retry 10 times or fail, and finally give up
How to solve
e.g. trace com.alipay.sofa.registry.server.session.remoting.handler.DataChangeRequestHandler reply -n 100 #cost>2000
The text was updated successfully, but these errors were encountered: