kangkaisen opened a new issue #2282: DataStreamSender take a long time under high concurrent query URL: https://github.com/apache/incubator-doris/issues/2282 **Describe the bug** ``` I1122 09:44:58.566290 78779 plan_fragment_executor.cpp:568] Fragment 30f51ba7ecd34f3c-8faada0cd071d2a5:(Active: 19s384ms, % non-ch ild: 0.00%) - AverageThreadTokens: 1.00 - PeakReservation: 0 - PeakUsedReservation: 0 - RowsProduced: 110.59K BlockMgr: - BlockWritesOutstanding: 0 - BlocksCreated: 0 - BlocksRecycled: 0 - BufferedPins: 0 - BytesWritten: 0 - MaxBlockSize: 8.00 MB - MemoryLimit: 2.00 GB - TotalBufferWaitTime: 0.000ns - TotalEncryptionTime: 0.000ns - TotalIntegrityCheckTime: 0.000ns - TotalReadBlockTime: 0.000ns DataStreamSender (dst_id=35):(Active: 19s375ms, % non-child: 0.00%) - BytesSent: 926.40 KB - IgnoreRows: 0 - NetworkThroughput(*): 0.00 /sec - OverallThroughput: 47.81 KB/sec - SerializeBatchTime: 7.103ms - ThriftTransmitTime(*): 0.000ns - UncompressedRowBatchSize: 1.69 MB ``` **1 The scan node time is very short，and the exchange node parent node time is also very short. 2 There are a lot of timeout querys 3 The CPU, IO, Mem ,Network resource utilization is normal 4 The bprc `transmit_data` latency is very high.**  **5 DataStreamRecvr cancel_stream maybe take a lone time** ``` W1122 20:55:12.063787 6106 data_stream_mgr.cpp:252] cancel cancel_stream time 56 W1122 20:55:12.063791 6112 data_stream_mgr.cpp:159] transmit_data time 53 W1122 20:55:12.068578 6116 data_stream_mgr.cpp:252] cancel cancel_stream time 57 W1122 20:49:50.773799 6119 data_stream_mgr.cpp:252] cancel cancel_stream time 851 ```
---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
