mrproliu opened a new issue, #13504:
URL: https://github.com/apache/skywalking/issues/13504

   ### Search before asking
   
   - [x] I had searched in the 
[issues](https://github.com/apache/skywalking/issues?q=is%3Aissue) and found no 
similar issues.
   
   
   ### Apache SkyWalking Component
   
   BanyanDB (apache/skywalking-banyandb)
   
   ### What happened
   
   When I stress test to write metrics into the liaison node, I often see this 
error log in the client. 
   ```
   {"level":"error","module":"MEASURE-CLIENT-0","error":"measure service got an 
unexpected response: message_id:77693335381003 status:\"STATUS_INTERNAL_ERROR\" 
metadata:{group:\"metricsMinute\" 
name:\"service_status_code2_minute\"}","time":"2025-09-21T11:30:00Z","message":"failed
 to receive response from measureService"}
   ```
   
   There is also have this kind of log in the liaison node: 
   ```
   {"level":"error","module":"SERVER-QUEUE-PUB-LIAISON","err_msg":"code: 
STATUS_INTERNAL_ERROR, msg: rpc error: code = DeadlineExceeded desc = context 
deadline 
exceeded","code":"STATUS_INTERNAL_ERROR","time":"2025-09-21T11:22:00Z","message":"node
 banyandb-liaison-1.banyandb-liaison-headless.banyandb:18912 returns error"}
   ```
   
   But there no any error logs in the data node. 
   
   ### What you expected to happen
   
   On the client side, there is no error received when sending metrics. 
   
   ### How to reproduce
   
   1. Start a banyanDB cluster.
   2. Write metrics with an interval(1m). 
   
   ### Anything else
   
   _No response_
   
   ### Are you willing to submit a pull request to fix on your own?
   
   - [ ] Yes I am willing to submit a pull request on my own!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: 
[email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to