milenkovicm opened a new issue, #2103: URL: https://github.com/apache/datafusion-ballista/issues/2103
there are few new logs on scheduler which i would argue could be debug: ``` 2026-07-20T14:49:38.237073Z INFO tokio-rt-worker ThreadId(14) ballista_scheduler::cluster: DIAG stage_has_input_collapse: root=ShuffleWriterExec root_partitions=32 → false 2026-07-20T14:49:38.237074Z INFO tokio-rt-worker ThreadId(14) ballista_scheduler::cluster: DIAG bind_one: job=pVyZiWX stage=6 exec=3963a325-7c89-4838-941d-4cd07e43d282 vcores=2 max=1 slice_len=1 consumed=1 partitions=[26] collapse=false 2026-07-20T14:49:38.237076Z INFO tokio-rt-worker ThreadId(14) ballista_scheduler::cluster: DIAG stage_has_input_collapse: root=ShuffleWriterExec root_partitions=32 → false 2026-07-20T14:49:38.237077Z INFO tokio-rt-worker ThreadId(14) ballista_scheduler::cluster: DIAG bind_one: job=pVyZiWX stage=6 exec=3963a325-7c89-4838-941d-4cd07e43d282 vcores=1 max=1 slice_len=1 consumed=1 partitions=[27] collapse=false ``` i believe they are introduced with #2038 if you agree @avantgardnerio they should be changed to `debug` and removed `DIAG` prefix -- 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]
