-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When searching for co-workers in the origin server cluster, occasional inability to find the origin server nodes occurs. #1520
Comments
Currently, this error is being reported continuously. I have deployed 2 sets, and one of the environments in the source station cluster does not report this error.
|
This problem may only occur when there are more than 2 servers in the source station cluster, for example:
Start an edge server:
Reproduction steps:
When ServerB is in
After finding that there is no stream, it directly returns an error. However, if it is
|
Description
When compiling and installing version 3.0 alpha4 (3.0.71), there are occasional log reports of a connect error with code=3090. If this error continues to occur consecutively, it will result in the inability to stream.
Environment
Ubuntu 16.04
3.0 alpha4 (3.0.71)
Reproduction
The steps to reproduce the bug are as follows:
Expected Behavior
It is expected that the source nodes can find each other, stream normally, and the latency will not be affected by the number of source nodes in the polling process.
TRANS_BY_GPT3
The text was updated successfully, but these errors were encountered: