wenjin272 commented on issue #1311: URL: https://github.com/apache/flink-agents/issues/1311#issuecomment-6331758668
Thanks for reporting this and investigating the execution paths. I think we should include the fix in 0.4. The deadline for 0.4 bug fixes is October 25, so there should still be time to submit and review it. Could you address both input admission and scheduling priority in the same PR: enforce `max-in-flight-input-records` for continuation and serial execution, and prioritize queued work from earlier inputs so their follow-up calls don't end up behind many later inputs' first calls? The pre-JDK 21 parallel engine's `(recordIndex, taskIndex)` ordering and preference for resuming existing Actions should provide a useful reference. For the continuation path, the priority also needs to apply to the async executor's work queue. -- 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]
