Skip to content

KAFKA-20901: Enforce cordoned log directories configured with relative paths - #23241

Open
majialoong wants to merge 1 commit into
apache:trunkfrom
majialoong:KAFKA-20901
Open

KAFKA-20901: Enforce cordoned log directories configured with relative paths#23241
majialoong wants to merge 1 commit into
apache:trunkfrom
majialoong:KAFKA-20901

Conversation

@majialoong

Copy link
Copy Markdown
Contributor

Kafka allows log.dirs to be configured with relative paths, but cordoned.log.dirs was validated and applied using the original configuration strings, whereas LogManager converts log directories to absolute paths and uses those paths for directory ID lookups.

As a result, configuring cordoned.log.dirs with the absolute path reported by DescribeLogDirs was rejected when log.dirs contained the equivalent relative path. Using the relative path passed validation, but it did not match the absolute path used internally, so the directory was not reported as cordoned to the controller.

This change consistently uses absolute paths when validating and applying cordoned.log.dirs, including during dynamic reconfiguration and broker heartbeat propagation.

@github-actions github-actions Bot added triage PRs from the community core Kafka Broker labels Aug 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci-approved core Kafka Broker triage PRs from the community

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants