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

feat: add per-tenant time sharding for long out-of-order ingestion (backport release-3.3.x) #15482

Open
wants to merge 1 commit into
base: release-3.3.x
Choose a base branch
from

Conversation

xperimental
Copy link
Collaborator

What this PR does / why we need it:

This is a backport of #14711 to release-3.3.x.

Which issue(s) this PR fixes:

Special notes for your reviewer:

Checklist

  • Reviewed the CONTRIBUTING.md guide (required)
  • Documentation added
  • Tests updated
  • Title matches the required conventional commits format, see here

@xperimental xperimental requested a review from a team as a code owner December 18, 2024 16:39
@github-actions github-actions bot added the type/docs Issues related to technical documentation; the Docs Squad uses this label across many repositories label Dec 18, 2024
@@ -3723,6 +3723,18 @@ shard_streams:
# CLI flag: -shard-streams.enabled
[enabled: <boolean> | default = true]

# Automatically shard streams by adding a __time_shard__ label, with values
# calculated from the log timestamps divided by MaxChunkAge/2. This allows the
# out-of-order ingestion of very old logs. If both flags are enabled,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When this says "Both flags" I'm unclear on what the other flag is. Could you please name it to avoid confusion.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The time-sharding feature depends on the stream-sharding to be enabled (directly above in this view). While I agree that this is a bit intransparent in how it is currently worded, I don't think we should change the text in the backport. This change should be introduced into main first, to avoid reverting back to the old text in the future.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I didn't notice that this was a backport. I agree, the change should be made in main.

@xperimental xperimental changed the title feat: backport per-tenant time sharding for long out-of-order ingestion feat: add per-tenant time sharding for long out-of-order ingestion (backport release-3.3.x) Dec 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
size/L type/docs Issues related to technical documentation; the Docs Squad uses this label across many repositories
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants