Skip to content
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

Stateful information sync for ext-proc Instances #761

Open
Jeffwan opened this issue Feb 27, 2025 · 0 comments
Open

Stateful information sync for ext-proc Instances #761

Jeffwan opened this issue Feb 27, 2025 · 0 comments
Labels
area/gateway area/stability kind/enhancement New feature or request priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

Comments

@Jeffwan
Copy link
Collaborator

Jeffwan commented Feb 27, 2025

🚀 Feature Description and Motivation

Our external process in the Envoy Gateway tracks request routing using prefix cache awareness, making it stateful. To ensure consistency and availability across multiple instances, we need to design a state synchronization mechanism.

  • Current ext-proc builds a hash blocks/radix tree to track requests.
  • Multiple instances need to share this prefix cache state and avoid data inconsistencies between instances.
  • Ensuring minimal performance impact while syncing state.

external distributed store/election/event-driven sync etc seems a little bit heavy. We need to consider the lightweight approach for implementation.

Use Case

unblock prefix-cache awareness request scheduling in HA case

Proposed Solution

No response

@Jeffwan Jeffwan added kind/enhancement New feature or request area/gateway priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. area/stability labels Feb 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/gateway area/stability kind/enhancement New feature or request priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Development

No branches or pull requests

1 participant