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

[Documentation] communicate the technical merits and tradeoffs of using ZStd Compression Codec #108

Open
nknize opened this issue Aug 29, 2023 · 2 comments
Labels
documentation Improvements or additions to documentation enhancement New feature or request

Comments

@nknize
Copy link
Collaborator

nknize commented Aug 29, 2023

This issue is created out of opensearch-project/OpenSearch#9422. Technical discussions around the merits and tradeoffs of users choosing ZStd codec have been discussed. We need to make sure this doesn't get lost in the noise of how to react to the potential demotion of the ZStd module to a plugin. I'm opening this issue here to capture those merits and tradeoffs until we can get them into proper documentation.

ZStd Pros:

  1. better / faster compression
  2. cost savings

Cons:

  1. force killed nodes
  2. wildcard loadLibrary security hole
  3. no rolling upgrade
  4. libc portability issues

This is a "living" issue and the list will likely be updated as more information is learned and new protection mechanisms are injected.

@msfroh
Copy link

msfroh commented Feb 7, 2024

@opensearch-project/admin, can we please move this to the https://github.com/opensearch-project/custom-codecs repo?

@dblock dblock transferred this issue from opensearch-project/OpenSearch Feb 7, 2024
@dblock dblock removed the untriaged label Jun 6, 2024
@dblock
Copy link
Member

dblock commented Jun 6, 2024

[Triage -- attendees 1, 2, 3, 4, 5, 6, 7]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants