Describe the bug:
Actions bound to dedicated worker are executed on different threads when they are included in Graph.
Steps to reproduce the behavior:
- Checkout
git switch piotrkorkus_complex_graphs
cd component_integration_tests/rust_test_scenarioscargo run -- --name orchestration.graphs.dedicated_graph --input '{"runtime": {"task_queue_size": 256, "workers": 4, "dedicated_workers": [{"id": "dedicated_worker_0"}]}}'
Observed behavior:
All sync funtions 1-5 are reported to be executed on different threads (workers).
Expected behavior
As all tags are bound to the same dedicated worker they should be executed on the same thread.
You can compare that commented concurrency code in graph_with_dedicated in component_integration_tests/rust_test_scenarios/src/tests/orchestration/orchestration_graph.rs works correct - all actions are executed on the same thread.
Occurrence:
Always
Attachments / Logs:
Original report: https://github.com/qorix-group/inc_orchestrator_internal/issues/380
Describe the bug:
Actions bound to dedicated worker are executed on different threads when they are included in Graph.
Steps to reproduce the behavior:
git switch piotrkorkus_complex_graphscd component_integration_tests/rust_test_scenarioscargo run -- --name orchestration.graphs.dedicated_graph --input '{"runtime": {"task_queue_size": 256, "workers": 4, "dedicated_workers": [{"id": "dedicated_worker_0"}]}}'Observed behavior:
All sync funtions 1-5 are reported to be executed on different threads (workers).
Expected behavior
As all tags are bound to the same dedicated worker they should be executed on the same thread.
You can compare that commented concurrency code in
graph_with_dedicatedincomponent_integration_tests/rust_test_scenarios/src/tests/orchestration/orchestration_graph.rsworks correct - all actions are executed on the same thread.Occurrence:
Always
Attachments / Logs: