Ted-Jiang opened a new issue #1531: URL: https://github.com/apache/arrow-datafusion/issues/1531
**Describe the bug** 1. start scheduler `RUST_LOG=INFO cargo run --bin ballista-scheduler` 2. start one executor 'RUST_LOG=INFO cargo run --release --bin ballista-executor ' 3. run load test in #1521 with `RUST_LOG=INFO cargo run --bin tpch -- loadtest ballista-load --query-list 1,3,5,6,7,10,12,13 --data-path ***/tpch-1g-oneFile/ --format parquet --host localhost --port 50050 --sql-path **` -> this run 100 sqls with 5 clients concurrency. the scheduler will hang forever after run cmd at most twice times. **Additional context** i use process sample to take the stack trace https://docs.google.com/document/d/13rTSlbE0NwCeZvw33dfJrhuVuPoc1RTWQSP42vlzoK8/edit?usp=sharing it seems all tokio-runtime-worker are at `_pthread_cond_wait` -- 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]
