-
Notifications
You must be signed in to change notification settings - Fork 34
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
add Tombstone property #847
Merged
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
820e238
add tombstone cluster property
Deflaimun e4b1482
Update modules/reference/pages/properties/cluster-properties.adoc
Deflaimun 326cfd3
Update modules/reference/pages/properties/cluster-properties.adoc
Deflaimun 6cb3e60
add related topic
Deflaimun File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -4856,6 +4856,26 @@ Transaction manager's synchronization timeout. Maximum time to wait for internal | |
|
||
--- | ||
|
||
=== tombstone_retention_ms | ||
|
||
The retention time for tombstone records in a compacted topic. Cannot be enabled at the same time as any of `cloud_storage_enabled`, `cloud_storage_enable_remote_read`, or `cloud_storage_enable_remote_write`. A typical default setting is `86400000`, or 24 hours. | ||
|
||
*Unit:* milliseconds | ||
|
||
*Requires restart:* No | ||
|
||
*Visibility:* `user` | ||
|
||
*Type:* integer | ||
|
||
*Accepted values:* [`1`, `17592186044415`] | ||
|
||
*Default:* `null` | ||
|
||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We could also add the main doc as a related topic? The xref will be |
||
*Related topics:* xref:manage:cluster-maintenance/compaction-settings.adoc#tombstone-record-removal[Tombstone record removal] | ||
|
||
--- | ||
|
||
=== topic_fds_per_partition | ||
|
||
Required file handles per partition when creating topics. | ||
|
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure if we usually add recommended values for properties that default to
null
in the docs, but up to your discretion as to whether we want to mention a typical default of24 hours
/86400000 ms
(see kafka docs here).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we have recommended values we can add them in the description cc @kbatuigas
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@WillemKauf per the code, look like this accepts negative values. Should this be a bounded_property to avoid this? I can add 0 as starting point too.
Asking because someties allowing negative numbers in time-based properties is intended
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The valid range is actually defined here:
[1ms, 17592186044415]
is correct.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I notice some other time-based properties that might need fixing:
https://docs.redpanda.com/current/reference/properties/cluster-properties/#raft_replica_max_flush_delay_ms is also bounded by
[1ms, 17592186044415]
but is negative in the docs.https://docs.redpanda.com/current/reference/properties/cluster-properties/#raft_heartbeat_interval_ms is also bounded by
[1ms, 17592186044415]
but is negative in the docs.There are a lot more properties in core that should have these bounds enforced, but don't... hm.