feat(p2p): add layer allocation logging in heartbeat #185
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.
Summary
This PR adds layer allocation information logging to the worker heartbeat mechanism. Workers now receive and log their assigned layer ranges (start_layer, end_layer) and model name during each heartbeat.
Changes
Scheduler Side (
rpc_connection_handler.py)node_update()RPC method to return layer allocation information{node_id, model_name, start_layer, end_layer}in the responseWorker Side (
p2p/server.py)Heartbeat: Node {peer_id}... Model: {model_name}, Layers: [{start}, {end})Benefits
Testing
Related Issues