Skip to content

[Feature]: Use deterministic hashing for KV events always #25210

@PeaBrane

Description

@PeaBrane

🚀 The feature, motivation and pitch

Motivation

My understanding is that the KV events are mainly used to interface with the NVIDIA Dynamo framework, whose KvIndexer would always expect the external sequence hashes emitted by the engines to be consistent across backend engine processes. Therefore, it would probably make sense to always use SHA-256 hashing (or default to it) if the overhead is acceptable

Pitch

Always use SHA-256 hashing so the user does not need to set a fixed seed in the env var or set the --prefix-caching-algo sha256 flag, as done here, which would mean the flag would be deprecated as well.

Alternatives

No response

Additional context

No response

Before submitting a new issue...

  • Make sure you already searched for relevant issues, and asked the chatbot living at the bottom right corner of the documentation page, which can answer lots of frequently asked questions.

Metadata

Metadata

Assignees

No one assigned

    Labels

    feature requestNew feature or requeststaleOver 90 days of inactivity

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions