Caideyipi commented on PR #18918: URL: https://github.com/apache/iotdb/pull/18918#issuecomment-6287694972
Correction after parsing the raw receiver error logs: REPORT.md counts both the outer TTransportException and its Caused by line, so distinct failures are 6,833 (node 44), 4,276 (45), and 11,478 (46). The stacks identify 6,833/4,276/11,457 as read-buffer growth failures in AutoScalingBufferReadTransport.fill -> TElasticFramedTransport.readFrame; node 46 has 21 additional failures allocating the initial 1 KiB buffer. I found no write-buffer allocation failures. The failed read-frame allocations have median sizes of about 13.2/14.0/13.8 MB, with a maximum near 31.9 MB. This shows shared RPC-budget exhaustion during concurrent reads, but does not by itself establish that this PR caused those read failures. The write-buffer shrink/grow regression remains independently reproducible and may add contention on that shared budget. For the report window 11:44:39-12:29:06, reject-status events are 170/0/210 for nodes 44/45/46. The totals 172/280/458 extend beyond that window; node 45 first r eports one at 12:29:11. Compression logs within the same window show 3/1/13 files below 1 MiB and 37/3/80 below 10 MiB. Without a same-workload old-build baseline, these counts do not quantify PR-induced small-file amplification. I recommend holding approval until the write-buffer regression is fixed and the fallback flush is compared with aligned flush/file-size metrics. This remains unresolved. -- 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]
