Skip to content

Conversation

@RoeyAzran1992
Copy link

What?

Giving the user the option to define a callback for the peer's metadata removal from the ETCD.

Why?

Current implementation has a race in resource release flow: When a peer removes its metadata from the ETCD, NIXL automatically invalidates cached MD, but the upper layers are not aware of this invalidation and will try to release requests to connections that were already invalidated.

How?

Allowing the user to install a customized callback so he can decide what actions to do upon peer metadata removal from ETCD (releasing transfer requests, invalidating the cached MD, etc.).

@copy-pr-bot
Copy link

copy-pr-bot bot commented Oct 21, 2025

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

@github-actions
Copy link

👋 Hi RoeyAzran1992! Thank you for contributing to ai-dynamo/nixl.

Your PR reviewers will review your contribution then trigger the CI to test your changes.

🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant