-
Notifications
You must be signed in to change notification settings - Fork 14.3k
KAFKA-19151: docs: clarify that flush.ms requires log.flush.scheduler.interval.ms config #19479
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
base: trunk
Are you sure you want to change the base?
KAFKA-19151: docs: clarify that flush.ms requires log.flush.scheduler.interval.ms config #19479
Conversation
…iggered by log.flush.scheduler.interval.ms
"this and use replication for durability and allow the operating system's background " + | ||
"we would fsync after 1000 ms had passed. Note that this setting depends on the broker-level " + | ||
"configuration \"log.flush.scheduler.interval.ms\", which controls how frequently the flush check occurs. " + | ||
"If \"log.flush.scheduler.interval.ms\" is not configured, the topic config \"flush.ms\" will not be triggered. " + |
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.
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.
+1
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 "log.flush.scheduler.interval.ms" is not configured, the topic config "flush.ms" will not be triggered. "
Maybe we can remove this as the remaining docs is good enough
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.
We can also use the LOG_FLUSH_SCHEDULER_INTERVAL_MS_CONFIG
and FLUSH_MS_CONFIG
constants instead of hardcoding the strings.
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.
@m1a2st The LOG_FLUSH_SCHEDULER_INTERVAL_MS_CONFIG
is in org.apache.kafka.server.config.ServerLogConfigs
. It already imported TopicConfig
. I don't think we can import the ServerLogConfigs
configuration in TopicConfig
.
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
LOG_FLUSH_SCHEDULER_INTERVAL_MS_CONFIG
is inorg.apache.kafka.server.config.ServerLogConfigs
Thanks, but FLUSH_MS_CONFIG
can update.
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.
@yunchipang: Thanks for the patch.
Please provide a screenshot of your patch if it is related to documentation.
You can find the instructions in the readme of https://github.com/apache/kafka-site
"this and use replication for durability and allow the operating system's background " + | ||
"we would fsync after 1000 ms had passed. Note that this setting depends on the broker-level " + | ||
"configuration \"log.flush.scheduler.interval.ms\", which controls how frequently the flush check occurs. " + | ||
"If \"log.flush.scheduler.interval.ms\" is not configured, the topic config \"flush.ms\" will not be triggered. " + |
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.
+1
@chia7712 @FrankYang0529 @frankvicky @m1a2st thanks y'all for reviewing. i have pushed the changes, please find the screenshot of the patch below. one newbie question, do i raise a PR in kafka-site repo after this patch is merged? |
Enhanced docs of
flush.ms
to remind users the flush is triggered bylog.flush.scheduler.interval.ms
.Reviewers: @chia7712