zhengchenyu opened a new issue, #1644:
URL: https://github.com/apache/incubator-uniffle/issues/1644

   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   
   
   ### Search before asking
   
   - [X] I have searched in the 
[issues](https://github.com/apache/incubator-uniffle/issues?q=is%3Aissue) and 
found no similar issues.
   
   
   ### Describe the feature
   
   When I perform a stress test on the cluster, tasks occasionally encounter 
errors like this:
   
   ```
   Caused by: io.grpc.StatusRuntimeException: DEADLINE_EXCEEDED: ClientCall was 
cancelled at or after deadline. [closed=[CANCELLED], 
committed=[remote_addr=xxx/xxx:xxx]]
        at 
io.grpc.stub.ClientCalls.toStatusRuntimeException(ClientCalls.java:268)
        at io.grpc.stub.ClientCalls.getUnchecked(ClientCalls.java:249)
   ```
   
   In this time, I will see metrics `grpc_server_executor_blocking_queue_size` 
like this:
   <img width="1018" alt="截屏2024-04-15 上午10 40 12" 
src="https://github.com/apache/incubator-uniffle/assets/10381583/8b0d3aeb-e3b1-4dea-b351-863d2ef8d1a5";>
   
   This may mean that rpc requests are not processed in a timely manner. But 
there are no indicators that directly prove this. So we should add rpc queued 
time and rpc process time.
   
   
    
   
   ### Motivation
   
   _No response_
   
   ### Describe the solution
   
   _No response_
   
   ### Additional context
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [X] Yes I am willing to submit a PR!


-- 
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]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to