You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Ron Dagostino (Jira)" <ji...@apache.org> on 2021/03/19 00:21:00 UTC

[jira] [Created] (KAFKA-12505) Should kafka-storage.sh accept a non-UUID for its --cluster-id parameter?

Ron Dagostino created KAFKA-12505:
-------------------------------------

             Summary: Should kafka-storage.sh accept a non-UUID for its --cluster-id parameter?
                 Key: KAFKA-12505
                 URL: https://issues.apache.org/jira/browse/KAFKA-12505
             Project: Kafka
          Issue Type: New Feature
            Reporter: Ron Dagostino


Should StorageTool support accepting non-UUIDs via its --cluster-id argument?  One purpose of the tool is to minimize the chance that a broker could use data from the wrong volume (i.e. data from another cluster). Generating a random UUID via the --random-uuid parameter encourages using a globally unique value for every cluster and is consistent with the behavior today with ZooKeeper, whereas allowing a non-UUID here would increase the chance that someone could reuse a Cluster ID value across clusters and short-circuit the risk mitigation that this tool provides.

Discuss...



--
This message was sent by Atlassian Jira
(v8.3.4#803005)