@@ -240,8 +240,8 @@ The following table maps each Scaler command to its corresponding section name i
240240| ` scaler_object_storage_server` | ` [object_storage_server]` |
241241| ` scaler_ui` | ` [webui]` |
242242| ` scaler_top` | ` [top]` |
243- | ` scaler_worker_adapter_native ` | ` [native_worker_adapter ]` |
244- | ` scaler_worker_adapter_symphony ` | ` [symphony_worker_adapter ]` |
243+ | ` scaler_worker_manager_native ` | ` [worker_manager_native ]` |
244+ | ` scaler_worker_manager_symphony ` | ` [worker_manager_symphony ]` |
245245
246246# ## Practical Scenarios & Examples
247247
@@ -376,7 +376,7 @@ might be added in the future.
376376A Scaler scheduler can interface with IBM Spectrum Symphony to provide distributed computing across Symphony clusters.
377377
378378` ` ` bash
379- $ scaler_worker_adapter_symphony tcp://127.0.0.1:2345 --service-name ScalerService --base-concurrency 4 --host 127.0.0.1 --port 8080
379+ $ scaler_worker_manager_symphony tcp://127.0.0.1:2345 --service-name ScalerService --base-concurrency 4 --host 127.0.0.1 --port 8080
380380` ` `
381381
382382This will start a Scaler worker that connects to the Scaler scheduler at ` tcp://127.0.0.1:2345` and uses the Symphony
@@ -461,31 +461,31 @@ where `deepest_nesting_level` is the deepest nesting level a task has in your wo
461461workload that has
462462a base task that calls a nested task that calls another nested task, then the deepest nesting level is 2.
463463
464- # # Worker Adapter usage
464+ # # Worker Manager usage
465465
466466> ** Note** : This feature is experimental and may change in future releases.
467467
468- Scaler provides a Worker Adapter webhook interface to integrate with other job schedulers or resource managers. The
469- Worker Adapter allows external systems to request the creation and termination of Scaler workers dynamically.
468+ Scaler provides a Worker Manager webhook interface to integrate with other job schedulers or resource managers. The
469+ Worker Manager allows external systems to request the creation and termination of Scaler workers dynamically.
470470
471- Please check the OpenGRIS standard for more details on the Worker Adapter
471+ Please check the OpenGRIS standard for more details on the Worker Manager
472472specification [here](https://github.com/finos/opengris).
473473
474- # ## Starting the Native Worker Adapter
474+ # ## Starting the Native Worker Manager
475475
476- Starting a Native Worker Adapter server at ` http://127.0.0.1:8080` :
476+ Starting a Native Worker Manager server at ` http://127.0.0.1:8080` :
477477
478478` ` ` bash
479- $ scaler_worker_adapter_native tcp://127.0.0.1:2345 --host 127.0.0.1 --port 8080
479+ $ scaler_worker_manager_native tcp://127.0.0.1:2345 --host 127.0.0.1 --port 8080
480480` ` `
481481
482- Pass the ` --adapter -webhook-url` argument to the Scaler scheduler to connect to the Worker Adapter :
482+ Pass the ` --manager -webhook-url` argument to the Scaler scheduler to connect to the Worker Manager :
483483
484484` ` ` bash
485- $ scaler_scheduler tcp://127.0.0.1:2345 --adapter -webhook-url http://127.0.0.1:8080
485+ $ scaler_scheduler tcp://127.0.0.1:2345 --manager -webhook-url http://127.0.0.1:8080
486486` ` ` `
487487
488- To check that the Worker Adapter is working, you can bring up ` scaler_top` to see workers spawning and terminating as
488+ To check that the Worker Manager is working, you can bring up ` scaler_top` to see workers spawning and terminating as
489489there is task load changes.
490490
491491# # Performance
0 commit comments