-
Notifications
You must be signed in to change notification settings - Fork 191
ETCD: initial heartbeat thread #1010
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
👋 Hi tstamler! Thank you for contributing to ai-dynamo/nixl. Your PR reviewers will review your contribution then trigger the CI to test your changes. 🚀 |
|
/ok to test c2065fd |
|
/build |
aranadive
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
|
/ok to test 4e8f87d |
|
/build |
|
@tstamler I added the fixes we talked about. |
@tstamler, there was an error processing your request: See the following link for more information: https://docs.gha-runners.nvidia.com/cpr/e/2/ |
|
/ok to test 5220637 |
|
/build |
5220637 to
525a807
Compare
|
/build |
|
/ok to test 525a807 |
| NIXL_DEBUG << "Using etcd namespace for agents: " << namespace_prefix; | ||
|
|
||
| etcd::Response response = etcd->leasegrant((heartbeat.count()) * 2); | ||
| lease_id = response.value().lease(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this valid if response is incorrect?
What?
Add a heartbeat mechanism to NIXL ETCD metadata to invalidate stale metadata if an agent dies.