Locating Circuit Breaker
If an API on the server times out, a large number of concurrent requests are sent from the client, or the server returns an error (caused by a network error or an error user-defined status code), circuit breaker occurs.
If circuit breaker occurs, the API on the server is isolated from that on the client by network. Then, the client does not access the API. You can analyze client and server logs to locate faults and find the root causes.
Locating Method
- The API on the server is isolated. Check the server logs to find out what happened when the API was called.
- Check the client logs.
- View the logs related to the Call got Error to check the error information returned by the transport layer during the calling, such as the network error, timeout, and error user-defined status code.
- If max concurrency is displayed, concurrent client requests exceed the threshold.
Alternatively, check metrics in Monitoring Metrics.
Possible Causes
- A deadlock occurs on the server.
- A large number of concurrent requests are sent from the client.
- The server response times out.
- The status code returned by the server complies with the error code defined in Transport.
Parent topic: Go Chassis
Last Article: Collecting and Viewing Logs
Next Article: Mesher
Did this article solve your problem?
Thank you for your score！Your feedback would help us improve the website.