Skip to content

Conversation

@Feediver1
Copy link
Contributor

@Feediver1 Feediver1 commented Jun 6, 2025

Description

This pull request introduces documentation updates to include new configurable properties for message compaction in Redpanda. These changes add details about max_compaction_lag_ms and min_compaction_lag_ms at both the cluster and topic levels, enhancing clarity and usability for users configuring compaction settings.

Updates to compaction-related properties:

Cluster-level properties:

  • Added documentation for max_compaction_lag_ms in modules/reference/pages/properties/cluster-properties.adoc. This property specifies the maximum time a message remains ineligible for compaction, with details on units, accepted values, and default settings.
  • Added documentation for min_compaction_lag_ms in modules/reference/pages/properties/cluster-properties.adoc. This property defines the minimum time a message remains uncompacted in the log, including its units, accepted values, and default settings.

Topic-level properties:

  • Updated modules/reference/pages/properties/topic-properties.adoc to include cross-references for max.compaction.lag.ms and min.compaction.lag.ms, linking them to their corresponding cluster-level properties.

Updates to compaction settings documentation:

  • Enhanced modules/manage/pages/cluster-maintenance/compaction-settings.adoc with detailed descriptions of max_compaction_lag_ms and min_compaction_lag_ms for both cluster and topic levels, explaining their purpose and use cases.

Playbook configuration update:

  • Modified local-antora-playbook.yml to track the DOC-1404-Document-new-configurable-property branch in the cloud-docs repository, ensuring the documentation aligns with the latest updates.

Resolves https://redpandadata.atlassian.net/browse/DOC-1378
Review deadline:

Page previews

Topic Properties

max_compaction_lag_ms

min_compaction_lag_ms

Compaction settings - configuration options

Checks

  • [ X] New feature
  • Content gap
  • Support Follow-up
  • Small fix (typos, links, copyedits, etc)

@Feediver1 Feediver1 requested a review from a team as a code owner June 6, 2025 01:11
@netlify
Copy link

netlify bot commented Jun 6, 2025

Deploy Preview for redpanda-docs-preview ready!

Name Link
🔨 Latest commit de0b698
🔍 Latest deploy log https://app.netlify.com/projects/redpanda-docs-preview/deploys/687ab3304227ac00085fff39
😎 Deploy Preview https://deploy-preview-1153--redpanda-docs-preview.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@Feediver1 Feediver1 requested a review from mattschumpert June 6, 2025 01:18
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 3

🧹 Nitpick comments (2)
modules/reference/pages/properties/cluster-properties.adoc (1)

3698-3698: Consider linking segment.ms to its property reference
The note "Do not set this value lower than segment.ms." is helpful but could be enhanced by adding a cross-reference to the segment.ms documentation (xref:reference:properties/cluster-properties.adoc#log_segment_ms).

modules/reference/pages/properties/topic-properties.adoc (1)

45-50: Align alias IDs with existing conventions.

The new entries use dots in the alias IDs (max.compaction.lag.ms / min.compaction.lag.ms), while other properties strip dots from IDs. Consider renaming these to maxcompactionlagms and mincompactionlagms for consistency.

@@ -45,4 +45,4 @@
-| <<max.compaction.lag.ms,`max.compaction.lag.ms`>>
+| <<maxcompactionlagms,`max.compaction.lag.ms`>>

@@ -48,4 +48,4 @@
-| <<min.compaction.lag.ms,`min.compaction.lag.ms`>>
+| <<mincompactionlagms,`min.compaction.lag.ms`>>
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1a60814 and 817207c.

📒 Files selected for processing (5)
  • antora.yml (1 hunks)
  • local-antora-playbook.yml (2 hunks)
  • modules/manage/pages/cluster-maintenance/compaction-settings.adoc (1 hunks)
  • modules/reference/pages/properties/cluster-properties.adoc (2 hunks)
  • modules/reference/pages/properties/topic-properties.adoc (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: Redirect rules - redpanda-docs-preview
  • GitHub Check: Header rules - redpanda-docs-preview
  • GitHub Check: Pages changed - redpanda-docs-preview
🔇 Additional comments (4)
antora.yml (2)

3-3: Bump Antora version to 25.2
The version attribute has been correctly updated from 25.1 to 25.2 for this beta release.


4-5: Add beta display metadata
Including display_version: '25.2 Beta' and prerelease: true properly flags this as a pre-release.

local-antora-playbook.yml (2)

3-3: Verify start_page target
The start_page has been updated to 25.2@ROOT:get-started:intro-to-events.adoc. Please confirm this is the intended landing page for the 25.2 beta docs.


18-18: Prioritize main branch in sources
Moving main to the front of the branches list ensures the latest content is served first. This aligns with your version bump.

@Feediver1 Feediver1 requested a review from wdberkeley June 12, 2025 18:21
@Feediver1 Feediver1 requested a review from wdberkeley June 13, 2025 14:40
@redpanda-data redpanda-data deleted a comment from coderabbitai bot Jun 13, 2025
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jul 11, 2025

Important

Review skipped

Auto incremental reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

📝 Walkthrough

Walkthrough

The changes update documentation and configuration files to reflect the introduction of new compaction-related properties in version 25.2 Beta. Specifically, the Antora configuration is updated for the new version and prerelease status, and the playbook is adjusted to use the new version as the start page. Documentation is expanded to include two new cluster and topic-level compaction properties: max_compaction_lag_ms/max.compaction.lag.ms and min_compaction_lag_ms/min.compaction.lag.ms, with detailed descriptions and cross-references.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Docs
    participant Config

    User->>Docs: Access documentation
    Docs->>Config: Reference antora.yml and playbook for version info
    Docs->>Docs: Display new compaction properties (cluster & topic level)
    User->>Docs: View descriptions and cross-references for new properties
Loading

Assessment against linked issues

Objective Addressed Explanation
Document new compaction robustness and performance properties for 25.2 (DOC-1378)

Assessment against linked issues: Out-of-scope changes

No out-of-scope changes found.

Suggested reviewers

  • micheleRP
  • kbatuigas

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 3

♻️ Duplicate comments (2)
modules/reference/pages/properties/cluster-properties.adoc (2)

3708-3724: Cross-reference syntax & accepted-values formatting still broken

The earlier feedback hasn’t been fully applied:

  1. Antora xref syntax is wrong – the link will not render:

    (xref:reference:properties/topic-properties.adoc#max.compaction.lag.ms)[max.compaction.lag.ms]
    

    should be:

    xref:reference:properties/topic-properties.adoc#max.compaction.lag.ms[`max.compaction.lag.ms`]
    
  2. Accepted-values range is wrapped in one code span, losing the two separate literals and missing the closing back-tick after 1:

    *Accepted values:* [`1, 9223372036854`]
    

    should be:

    *Accepted values:* [`1`, `9223372036854`]
    

Apply the diff below.

-For a compacted topic, the maximum time a message remains ineligible for compaction.
-The topic property (xref:reference:properties/topic-properties.adoc#max.compaction.lag.ms)[max.compaction.lag.ms] overrides this property.
+For a compacted topic, the maximum time a message remains ineligible for compaction.
+The topic property xref:reference:properties/topic-properties.adoc#max.compaction.lag.ms[`max.compaction.lag.ms`] overrides this property.
@@
-*Accepted values:* [`1, 9223372036854`]
+*Accepted values:* [`1`, `9223372036854`]

3972-3986: Same formatting issues for min_compaction_lag_ms

The same two problems appear here:

(xref:reference:properties/topic-properties.adoc#min.compaction.lag.ms)[min.compaction.lag.ms]
*Accepted values:* [`0,9223372036854`]

Should be:

xref:reference:properties/topic-properties.adoc#min.compaction.lag.ms[`min.compaction.lag.ms`]
*Accepted values:* [`0`, `9223372036854`]

Patch:

-For a compacted topic, the minimum time a message remains uncompacted in the log. The topic property (xref:reference:properties/topic-properties.adoc#min.compaction.lag.ms)[min.compaction.lag.ms] overrides this property.
+For a compacted topic, the minimum time a message remains uncompacted in the log.
+The topic property xref:reference:properties/topic-properties.adoc#min.compaction.lag.ms[`min.compaction.lag.ms`] overrides this property.
@@
-*Accepted values:* [`0,9223372036854`]
+*Accepted values:* [`0`, `9223372036854`]
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between cf47099 and 4ca3acd.

📒 Files selected for processing (5)
  • antora.yml (1 hunks)
  • local-antora-playbook.yml (2 hunks)
  • modules/manage/pages/cluster-maintenance/compaction-settings.adoc (1 hunks)
  • modules/reference/pages/properties/cluster-properties.adoc (2 hunks)
  • modules/reference/pages/properties/topic-properties.adoc (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)
  • GitHub Check: Redirect rules - redpanda-docs-preview
  • GitHub Check: Header rules - redpanda-docs-preview
  • GitHub Check: Pages changed - redpanda-docs-preview
🔇 Additional comments (2)
local-antora-playbook.yml (2)

3-3: Confirm the 25 .2 landing page exists before merging.

start_page: 25.2@ROOT:get-started:intro-to-events.adoc will 404 in preview builds unless the 25.2 component version is generated. Double-check that the antora.yml in this branch is indeed published as 25.2 (see previous comment) and that the referenced page hasn’t moved.


18-18: Ordering sources is OK – but ensure main stays mutually exclusive with v/*.

Introducing main first is sensible for beta docs; just be aware that any cherry-picked content that lives only on maintenance branches could now be shadowed. No action required if that’s intentional.

@JakeSCahill JakeSCahill changed the base branch from main to beta July 15, 2025 13:25
@JakeSCahill JakeSCahill changed the base branch from beta to main July 15, 2025 13:26
@JakeSCahill JakeSCahill changed the base branch from main to beta July 15, 2025 13:32
@micheleRP
Copy link
Contributor

@Feediver1 Doc needs to be added for the 2 new topic properties. The other topic properties in this table have links to descriptions later in the page, but these 2 new ones link to nothing.

@micheleRP
Copy link
Contributor

After that content is added, the links in the cluster properties should go directly into those descriptions, instead of just to the Topic Properties page (e.g., this cluster property should link into the topic property description)

branches: [main, v/*, api, shared, site-search,'!v-end-of-life/*']
- url: https://github.com/redpanda-data/cloud-docs
branches: 'main'
branches: 'DOC-1404-Document-new-configurable-property'
Copy link
Collaborator

Choose a reason for hiding this comment

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

Revert this before merging

@micheleRP
Copy link
Contributor

@Feediver1: There should also be an addition for this in the What's New!

Copy link
Contributor

@micheleRP micheleRP left a comment

Choose a reason for hiding this comment

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

left some suggestions, but lgtm. Remember to change playbook back to main!

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants