Send hearbeat along with status update between GCS and raylet #48837
Assignees
Labels
core
Issues that should be addressed in Ray Core
enhancement
Request for new feature and/or capability
P2
Important issue, but not time-critical
Comments
dentiny
added
enhancement
jjyao
removed
the
triage
This was referenced Dec 6, 2024
rynewang
pushed a commit
that referenced
this issue
Dec 21, 2024
…at NodeManager (#49235) Issue reference: #48837 This PR simply combines two existing API call: client registration and port announcement into one, with no functionality change. The plan is to - Add new APIs at callee side, so we don't have production effect; - Do no-op code refactor at caller side, so it's easier to refactor and merge API calls - Connect caller and callee with the new API calls, after (1) and (2) the code structure should be at a clean state which is friendly and easy for API merge. --------- Signed-off-by: hjiang <hjiang@anyscale.com>
anyadontfly
pushed a commit
to anyadontfly/ray
that referenced
this issue
Feb 13, 2025
…at NodeManager (ray-project#49235) Issue reference: ray-project#48837 This PR simply combines two existing API call: client registration and port announcement into one, with no functionality change. The plan is to - Add new APIs at callee side, so we don't have production effect; - Do no-op code refactor at caller side, so it's easier to refactor and merge API calls - Connect caller and callee with the new API calls, after (1) and (2) the code structure should be at a clean state which is friendly and easy for API merge. --------- Signed-off-by: hjiang <hjiang@anyscale.com> Signed-off-by: Puyuan Yao <williamyao034@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
As titled, to reduce communication between raylet and GCS.
Use case
No response
The text was updated successfully, but these errors were encountered: