Ted-Jiang opened a new pull request, #123:
URL: https://github.com/apache/arrow-ballista/pull/123
# Which issue does this PR close?
Closes #122 .
# Rationale for this change
Enable thread info and cut log file by day.
Now logs look like:
```
arrow-ballista % cat logs/scheduler_ballista_0.0.0.0_50050.2022-08-10
2022-08-10T07:28:45.457283Z INFO main ThreadId(01) ballista_scheduler:
Ballista v0.7.0 Scheduler listening on 0.0.0.0:50050
2022-08-10T07:28:45.457489Z INFO main ThreadId(01) ballista_scheduler:
Starting Scheduler grpc server with task scheduling policy of PullStaged
2022-08-10T07:28:45.458130Z INFO main ThreadId(01)
ballista_scheduler::scheduler_server::query_stage_scheduler: Starting
QueryStageScheduler
2022-08-10T07:28:45.458307Z INFO tokio-runtime-worker ThreadId(17)
ballista_core::event_loop: Starting the event loop query_stage
2022-08-10T07:29:46.156777Z INFO main ThreadId(01) ballista_scheduler:
Ballista v0.7.0 Scheduler listening on 0.0.0.0:50050
2022-08-10T07:29:46.157159Z INFO main ThreadId(01) ballista_scheduler:
Starting Scheduler grpc server with task scheduling policy of PullStaged
2022-08-10T07:29:46.157729Z INFO main ThreadId(01)
ballista_scheduler::scheduler_server::query_stage_scheduler: Starting
QueryStageScheduler
2022-08-10T07:29:46.157922Z INFO tokio-runtime-worker ThreadId(15)
ballista_core::event_loop: Starting the event loop query_stage
2022-08-10T07:30:09.766192Z INFO main ThreadId(01) ballista_scheduler:
Ballista v0.7.0 Scheduler listening on 0.0.0.0:50050
2022-08-10T07:30:09.768707Z INFO main ThreadId(01) ballista_scheduler:
Starting Scheduler grpc server with task scheduling policy of PullStaged
2022-08-10T07:30:09.769133Z INFO main ThreadId(01)
ballista_scheduler::scheduler_server::query_stage_scheduler: Starting
QueryStageScheduler
2022-08-10T07:30:09.769264Z INFO tokio-runtime-worker ThreadId(09)
ballista_core::event_loop: Starting the event loop query_stage
```
# What changes are included in this PR?
<!--
There is no need to duplicate the description in the issue here but it is
sometimes worth providing a summary of the individual changes in this PR.
-->
# Are there any user-facing changes?
<!--
If there are user-facing changes then we may require documentation to be
updated before approving the PR.
-->
<!--
If there are any breaking changes to public APIs, please add the `api
change` label.
-->
--
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]
