wForget opened a new issue, #2705:
URL: https://github.com/apache/uniffle/issues/2705

   ### 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 bug
   
   When the number of partitions is large, we often encounter 
`getShuffleHandleInfo` timeouts during stage startup on the spark executor.
   
   The error log:
   
   ```
   org.apache.uniffle.shaded.io.grpc.StatusRuntimeException: DEADLINE_EXCEEDED: 
CallOptions deadline exceeded after 59.999990136s. Name resolution delay 
0.000000000 seconds. [closed=[], open=[[remote_addr=xxx/xxx:xxx]]]
        at 
org.apache.uniffle.shaded.io.grpc.stub.ClientCalls.toStatusRuntimeException(ClientCalls.java:268)
        at 
org.apache.uniffle.shaded.io.grpc.stub.ClientCalls.getUnchecked(ClientCalls.java:249)
        at 
org.apache.uniffle.shaded.io.grpc.stub.ClientCalls.blockingUnaryCall(ClientCalls.java:167)
        at 
org.apache.uniffle.proto.ShuffleManagerGrpc$ShuffleManagerBlockingStub.getPartitionToShufflerServerWithBlockRetry(ShuffleManagerGrpc.java:644)
        at 
org.apache.uniffle.client.impl.grpc.ShuffleManagerGrpcClient.getPartitionToShufflerServerWithBlockRetry(ShuffleManagerGrpcClient.java:109)
        at 
org.apache.uniffle.shuffle.manager.RssShuffleManagerBase.getRemoteShuffleHandleInfoWithBlockRetry(RssShuffleManagerBase.java:955)
        at 
org.apache.uniffle.shuffle.manager.RssShuffleManagerBase.getShuffleHandleInfo(RssShuffleManagerBase.java:912)
        at 
org.apache.spark.shuffle.writer.RssShuffleWriter.(RssShuffleWriter.java:311)
        at 
org.apache.spark.shuffle.RssShuffleManager.getWriter(RssShuffleManager.java:260)
        at 
org.apache.spark.shuffle.QiyiRssShuffleManager.getWriter(QiyiRssShuffleManager.java:249)
        at 
org.apache.spark.shuffle.ShuffleWriteProcessor.write(ShuffleWriteProcessor.scala:57)
        at 
org.apache.spark.scheduler.ShuffleMapTask.runTask(ShuffleMapTask.scala:104)
        at 
org.apache.spark.scheduler.ShuffleMapTask.runTask(ShuffleMapTask.scala:54)
        at 
org.apache.spark.TaskContext.runTaskWithListeners(TaskContext.scala:161)
        at org.apache.spark.scheduler.Task.run(Task.scala:141)
        at 
org.apache.spark.executor.Executor$TaskRunner.$anonfun$run$4(Executor.scala:620)
        at 
org.apache.spark.util.SparkErrorUtils.tryWithSafeFinally(SparkErrorUtils.scala:64)
        at 
org.apache.spark.util.SparkErrorUtils.tryWithSafeFinally$(SparkErrorUtils.scala:61)
        at org.apache.spark.util.Utils$.tryWithSafeFinally(Utils.scala:94)
        at org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:623)
        at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)
   ```
   
   The gRPC threads are all blocked in `MutableShuffleHandleInfo#toProto`:
   
   <img width="1893" height="783" alt="Image" 
src="https://github.com/user-attachments/assets/b13bd97b-0080-461e-b55a-25df6e506fcd";
 />
   
   <img width="1884" height="570" alt="Image" 
src="https://github.com/user-attachments/assets/a653faf7-9818-4261-9c7a-9e74276f1c1b";
 />
   
   ### Affects Version(s)
   
   0.10
   
   ### Uniffle Server Log Output
   
   ```logtalk
   
   ```
   
   ### Uniffle Engine Log Output
   
   ```logtalk
   
   ```
   
   ### Uniffle Server Configurations
   
   ```yaml
   
   ```
   
   ### Uniffle Engine Configurations
   
   ```yaml
   
   ```
   
   ### 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