You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@arrow.apache.org by "paolorechia (via GitHub)" <gi...@apache.org> on 2023/03/25 08:01:50 UTC
[GitHub] [arrow-ballista] paolorechia opened a new issue, #719: Starting scheduler with docker-compose on `main` throws error: Error: An unknown argument '--config-backend' was specified.
paolorechia opened a new issue, #719:
URL: https://github.com/apache/arrow-ballista/issues/719
**Describe the bug**
Starting the deployment in the `main` branch with the docker-compose option ttriggers this error:
```
arrow-ballista-ballista-scheduler-1 | Starting nginx to serve Ballista Scheduler web UI on port 80
arrow-ballista-ballista-scheduler-1 | Error: An unknown argument '--config-backend' was specified.
```
**To Reproduce**
Execute `docker-compose up --build` from main branch.
**Expected behavior**
Expected services to execute successfully.
**Additional context**
When looking at the source code, specifically `ballista/scheduler/src/bin/main.rs` I could not find the relevant `etcd` options.
Changing the `docker-compose.yml` line 29 from
```
command: "--config-backend etcd --etcd-urls etcd:2379 --bind-host 0.0.0.0"
```
To
```
command: " --bind-host 0.0.0.0"
```
Fixes the error and deploys successfully the containers. It does not seem like a proper solution here, as we're not effectively using the `etcd` service. Is there an unfinished feature in `main` branch?
--
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: github-unsubscribe@arrow.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [arrow-ballista] paolorechia commented on issue #719: Starting scheduler with docker-compose on `main` throws error: Error: An unknown argument '--config-backend' was specified.
Posted by "paolorechia (via GitHub)" <gi...@apache.org>.
paolorechia commented on issue #719:
URL: https://github.com/apache/arrow-ballista/issues/719#issuecomment-1483760411
I seem to have found the proper cause of the error. In the file `ballista/scheduler/scheduler_config_spec.toml` I found this block:
```
[[param]]
abbr = "b"
name = "cluster_backend"
type = "ballista_scheduler::cluster::ClusterStorage"
doc = "The configuration backend for the scheduler cluster state, possible values: etcd, memory, sled. Default: sled"
default = "ballista_scheduler::cluster::ClusterStorage::Sled"
```
Thus changing the config in docker-compose to:
```
command: "--cluster-backend etcd --etcd-urls etcd:2379 --bind-host 0.0.0.0"
```
Seems to work. I might create a follow-up PR 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: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [arrow-ballista] yahoNanJing closed issue #719: Starting scheduler with docker-compose on `main` throws error: Error: An unknown argument '--config-backend' was specified.
Posted by "yahoNanJing (via GitHub)" <gi...@apache.org>.
yahoNanJing closed issue #719: Starting scheduler with docker-compose on `main` throws error: Error: An unknown argument '--config-backend' was specified.
URL: https://github.com/apache/arrow-ballista/issues/719
--
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: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org