@@ -233,8 +233,8 @@ The following table maps each Scaler command to its corresponding section name i
233233| ` scaler_object_storage_server` | ` [object_storage_server]` |
234234| ` scaler_ui` | ` [webui]` |
235235| ` scaler_top` | ` [top]` |
236- | ` scaler_worker_adapter_native ` | ` [native_worker_adapter ]` |
237- | ` scaler_worker_adapter_symphony ` | ` [symphony_worker_adapter ]` |
236+ | ` scaler_worker_manager_native ` | ` [worker_manager_native ]` |
237+ | ` scaler_worker_manager_symphony ` | ` [worker_manager_symphony ]` |
238238
239239# ## Practical Scenarios & Examples
240240
@@ -363,7 +363,7 @@ might be added in the future.
363363A Scaler scheduler can interface with IBM Spectrum Symphony to provide distributed computing across Symphony clusters.
364364
365365` ` ` bash
366- $ scaler_worker_adapter_symphony tcp://127.0.0.1:2345 --service-name ScalerService --base-concurrency 4 --host 127.0.0.1 --port 8080
366+ $ scaler_worker_manager_symphony tcp://127.0.0.1:2345 --service-name ScalerService --base-concurrency 4 --host 127.0.0.1 --port 8080
367367` ` `
368368
369369This will start a Scaler worker that connects to the Scaler scheduler at ` tcp://127.0.0.1:2345` and uses the Symphony
@@ -448,31 +448,31 @@ where `deepest_nesting_level` is the deepest nesting level a task has in your wo
448448workload that has
449449a base task that calls a nested task that calls another nested task, then the deepest nesting level is 2.
450450
451- # # Worker Adapter usage
451+ # # Worker Manager usage
452452
453453> ** Note** : This feature is experimental and may change in future releases.
454454
455- Scaler provides a Worker Adapter webhook interface to integrate with other job schedulers or resource managers. The
456- Worker Adapter allows external systems to request the creation and termination of Scaler workers dynamically.
455+ Scaler provides a Worker Manager webhook interface to integrate with other job schedulers or resource managers. The
456+ Worker Manager allows external systems to request the creation and termination of Scaler workers dynamically.
457457
458- Please check the OpenGRIS standard for more details on the Worker Adapter
458+ Please check the OpenGRIS standard for more details on the Worker Manager
459459specification [here](https://github.com/finos/opengris).
460460
461- # ## Starting the Native Worker Adapter
461+ # ## Starting the Native Worker Manager
462462
463- Starting a Native Worker Adapter server at ` http://127.0.0.1:8080` :
463+ Starting a Native Worker Manager server at ` http://127.0.0.1:8080` :
464464
465465` ` ` bash
466- $ scaler_worker_adapter_native tcp://127.0.0.1:2345 --host 127.0.0.1 --port 8080
466+ $ scaler_worker_manager_native tcp://127.0.0.1:2345 --host 127.0.0.1 --port 8080
467467` ` `
468468
469- Pass the ` --adapter -webhook-url` argument to the Scaler scheduler to connect to the Worker Adapter :
469+ Pass the ` --manager -webhook-url` argument to the Scaler scheduler to connect to the Worker Manager :
470470
471471` ` ` bash
472- $ scaler_scheduler tcp://127.0.0.1:2345 --adapter -webhook-url http://127.0.0.1:8080
472+ $ scaler_scheduler tcp://127.0.0.1:2345 --manager -webhook-url http://127.0.0.1:8080
473473` ` ` `
474474
475- To check that the Worker Adapter is working, you can bring up ` scaler_top` to see workers spawning and terminating as
475+ To check that the Worker Manager is working, you can bring up ` scaler_top` to see workers spawning and terminating as
476476there is task load changes.
477477
478478# # Performance
0 commit comments