[bugfix] Update server type checks for merged PD instances #65
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.
This pull request refactors the logic for initializing server clusters in
lm_service/apis/vllm/proxy.pyto improve clarity and correctness when handling different server types based on theis_pd_mergedflag. The changes streamline which server types are initialized and adjust the conditions for skipping certain types.Cluster initialization logic improvements:
_init_cluster_with_addr_listto explicitly construct the list of active server types based on theis_pd_mergedflag, replacing the previous loop and conditional logic for skipping server types._init_cluster_with_metastoreto skip bothP_INSTANCEandD_INSTANCEwhenis_pd_mergedis true, ensuring only relevant server types are initialized.