killzoner opened a new pull request, #1698:
URL: https://github.com/apache/datafusion-ballista/pull/1698
# Which issue does this PR close?
I was looking at testing some stuff locally in distributed mode.
I made :
```bash
cargo run --bin ballista-scheduler --features prometheus-metrics # first
shell
cargo run --bin ballista-cli -- --host localhost --port 50050 # second shell
```
then submit `SELECT 1;` in the cli.
This hangs forever (cannot even close the cli) and nothing appears.
# Rationale for this change
This avoids silent job submission without user feedback. I can also imagine
a cluster with all executor not reachable, the task would be submitted but zero
warning, and 0 visibility in metrics.
# What changes are included in this PR?
- promote `debug` message to `warn` when no executor (I guess this should
never happen and makes the issue visible even running with no extra config)
- fix a typo in the (great!) TUI on prometheus metrics feature name to enable
- expose pending task in metrics (metric existed but what never filled)
- did *not* address the cli hang while waiting for scheduler response (might
be a follow up if deemed useful)
# Are there any user-facing changes?
Existing `pending_tasks_queue_size` is now filled
<!--
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
