[Feature] EngineWorkerQueue anonymous port #4597
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
Currently, EngineWorkerQueue requires explicit port configuration. This PR adds support for anonymous port allocation (port=0), allowing the system to automatically assign available ports. This enhancement improves flexibility in deployment scenarios where predefined ports might be unavailable or when running multiple instances on the same host.
isn’t compatible with the multi_api_server interface
Modifications
EngineWorkerQueueto handle anonymous port configuration (port=0)Usage or Command
--cache-queue-port and --engine-worker-queue-port args default 0
python -m fastdeploy.entrypoints.openai.api_server
Accuracy Tests
This change does not affect model outputs or inference accuracy as it only modifies the networking infrastructure. All existing functionality remains unchanged.
Checklist
[FDConfig],[APIServer],[Engine],[Scheduler],[PD Disaggregation],[Executor],[Graph Optimization],[Speculative Decoding],[RL],[Models],[Quantization],[Loader],[OP],[KVCache],[DataProcessor],[BugFix],[Docs],[CI],[Optimization],[Feature],[Benchmark],[Others],[XPU],[HPU],[GCU],[DCU],[Iluvatar],[Metax]]pre-commitbefore commit.releasebranch, make sure the PR has been submitted to thedevelopbranch, then cherry-pick it to thereleasebranch with the[Cherry-Pick]PR tag.