matanper commented on issue #70145: URL: https://github.com/apache/doris/issues/70145#issuecomment-6615217222
Thanks for the careful read. Corrections, now reflected in the description: - **Scope of the RUNNING entries.** We observed them on 4.1.4, where every Arrow Flight query defers its coordinator. With #67504 (4.1.5) only coordinators that must outlive dispatch are deferred, so on branch-4.1 and master the lingering entries are limited to those, released by the next statement, session close or the idle reaper. The audit timing gap applies to every Arrow Flight query whose result is fetched from the BEs, deferred or not, so the fix must not be gated on deferral. - **Duration boundary.** Agreed: the last pipeline task closing is an execution boundary, not a fetch boundary. A result that fits in the result buffer can finish producing before DoGet starts, and a slow consumer keeps reading after the sink closes. The proposal is to report execution time (comparable to MySQL for results the sink has to wait on, and to FE dispatch plus BE execution otherwise), and to say so in the docs; a fetch-inclusive time would need a terminal signal from the result stream. FE time up to dispatch and the BE interval overlap by the dispatch, so their sum is an approximation. - **Participant set.** The wait is for every BE the fragments were sent to (the coordinator's backend set), not only the BEs that have reported, with the existing time cap as the fallback; on master this should build on the expected-backend barrier in `WorkloadRuntimeStatusMgr`. - **Cleanup vs audit.** Agreed that releasing a deferred coordinator must not depend on the audit queue or its caps. We will follow up with a PR against master covering ordinary internal-table queries, a deferred external scan, small buffered results with delayed DoGet, slow and multi-endpoint fetch, multi-BE delayed and missing reports, errors and cancellation, and MySQL timing unchanged. -- 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]
