[
https://issues.apache.org/jira/browse/KAFKA-14710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17865204#comment-17865204
]
Chia-Ping Tsai commented on KAFKA-14710:
----------------------------------------
The uuid check was remove by https://github.com/apache/kafka/pull/14628, so I
will close it now.
For another, [~jolshan] How to handle the conflicts in encoding string?
Recently we run a temporary cluster using clusterId="lYEJ7pnYNO2ovNYiNRJBGl"
and the true cluster id used by kraft is "lYEJ7pnYNO2ovNYiNRJBGg". That case is
rare, so not sure whether it is worth having a fix/approach.
> KRaft cannot initialise storage for valid UUID
> ----------------------------------------------
>
> Key: KAFKA-14710
> URL: https://issues.apache.org/jira/browse/KAFKA-14710
> Project: Kafka
> Issue Type: Bug
> Components: kraft
> Affects Versions: 3.4.0
> Reporter: Tristan Stevens
> Priority: Major
>
> kafka-storage does not accept base64 UUIDs that include the plus symbol,
> which is valid base64 and works according to
> https://www.fileformat.info/tool/guid-base64.htm
>
> {noformat}
> /opt/kafka//bin/kafka-storage.sh format -t he+xntiAFrY5phFfhV1TFA -c
> /opt/kafka/config/server.properties
> Cluster ID string he+xntiAFrY5phFfhV1TFA does not appear to be a valid UUID:
> Illegal base64 character 2b{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
