milenkovicm opened a new issue, #2105:
URL: https://github.com/apache/datafusion-ballista/issues/2105

   **Describe the bug**
   
   with current main, executor hags on `ctrl+c` event
   
   
   **To Reproduce**
   
   start scheduler and executor with release profile, then execute `ctrl+c` in 
executor terminal 
   
   
   ```
   2026-07-20T15:06:50.614607Z  INFO tokio-rt-worker ThreadId(13) 
ballista_executor::executor_process: Built-in arrow flight server listening on: 
0.0.0.0:50051 max_encoding_size: 16777216 max_decoding_size: 16777216
   2026-07-20T15:06:50.614585Z  INFO tokio-rt-worker ThreadId(03) 
ballista_executor::executor_server: Starting the task runner pool
   ^C2026-07-20T15:06:55.308860Z  INFO            main ThreadId(01) 
ballista_executor::executor_process: "executor received ctrl-c event."
   2026-07-20T15:06:55.308899Z  INFO            main ThreadId(01) 
ballista_executor::executor_process: setting executor to TERMINATING status
   ```
   
   executor process will never finish 
   
   scheduler will be informed about ctrl+c event from executor 
   
   ```
   2026-07-20T15:06:55.309902Z  INFO tokio-rt-worker ThreadId(12) 
ballista_scheduler::scheduler_server::grpc: Received executor stopped request 
from Executor 39f33b93-e43c-4bbe-b282-10b8c13c4080 with reason 'executor 
received ctrl-c event.'
   2026-07-20T15:07:25.311847Z  INFO tokio-rt-worker ThreadId(04) 
ballista_scheduler::state::executor_manager: Removing executor 
39f33b93-e43c-4bbe-b282-10b8c13c4080: Some("executor received ctrl-c event.")
   2026-07-20T15:07:50.617499Z  WARN tokio-rt-worker ThreadId(04) 
ballista_scheduler::scheduler_server::grpc: Fail to get executor metadata: 
Internal Ballista error: Not executor with ID 
39f33b93-e43c-4bbe-b282-10b8c13c4080 found
   2026-07-20T15:08:28.583909Z  WARN tokio-rt-worker ThreadId(15) 
ballista_scheduler::scheduler_server: TERMINATING executor 
39f33b93-e43c-4bbe-b282-10b8c13c4080 heartbeat timed out after 30s
   2026-07-20T15:08:28.585160Z  INFO tokio-rt-worker ThreadId(15) 
ballista_scheduler::state::executor_manager: Removing executor 
39f33b93-e43c-4bbe-b282-10b8c13c4080: Some("TERMINATING executor 
39f33b93-e43c-4bbe-b282-10b8c13c4080 heartbeat timed out after 30s")
   2026-07-20T15:08:50.620769Z  WARN tokio-rt-worker ThreadId(15) 
ballista_scheduler::scheduler_server::grpc: Fail to get executor metadata: 
Internal Ballista error: Not executor with ID 
39f33b93-e43c-4bbe-b282-10b8c13c4080 found
   ```
   
   
   **Expected behavior**
   
   executor to be shut down on `ctrl+c`
   
   **Additional context**
   Add any other context about the problem here.
   


-- 
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]

Reply via email to