[jira] [Commented] (KAFKA-19988) KRaft migration doc should account for ZK cluster id with a leading dash
[
https://issues.apache.org/jira/browse/KAFKA-19988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18047178#comment-18047178
]
ASF GitHub Bot commented on KAFKA-19988:
mumrah merged PR #760:
URL: https://github.com/apache/kafka-site/pull/760
> KRaft migration doc should account for ZK cluster id with a leading dash
>
>
> Key: KAFKA-19988
> URL: https://issues.apache.org/jira/browse/KAFKA-19988
> Project: Kafka
> Issue Type: Bug
> Components: docs, documentation, kraft, migration
>Affects Versions: 3.9.1
>Reporter: Gergely Harmadás
>Assignee: Gergely Harmadás
>Priority: Minor
> Fix For: 3.9.2
>
>
> When preparing for the migration, there is a small chance that the retrieved
> cluster id from ZooKeeper contains a leading dash. Currently the 3.9
> documentation specifies the following during the step "Provisioning the KRaft
> controller quorum":
> {code:bash}
> # Save the previously retrieved cluster ID from ZooKeeper in a variable
> called zk-cluster-id
> $ bin/kafka-storage.sh format --standalone -t -c
> config/kraft/controller.properties{code}
> However the above command will fail with a less fortunate cluster id like
> -{{{}Yh6XyBIQ9CeAlMwJ8f7Hg{}}}, eg.:
> {noformat}
> bin/kafka-storage.sh format --standalone -t -Yh6XyBIQ9CeAlMwJ8f7Hg -c
> config/server.properties
> 25/12/12 09:24:54 INFO utils.Log4jControllerRegistration$: [main]:
> Registered `kafka:type=kafka.Log4jController` MBean
> usage: kafka-storage format [-h] --config CONFIG --cluster-id CLUSTER_ID
> [--add-scram ADD_SCRAM] [--ignore-formatted] [--release-version
> RELEASE_VERSION] [--feature FEATURE] [--standalone |
> --no-initial-controllers | --initial-controllers
> INITIAL_CONTROLLERS]
> kafka-storage: error: argument --cluster-id/-t: expected one argument
> {noformat}
> A similar problem came up with KRaft which was addressed in KAFKA-13741. In
> our case the cluster id is already specified, there is no way to change it. I
> was able to come up with a simple solution by using the full name of the
> argument like "--cluster-id=" instead of the shorthand "-t
> ". Full example:
> {code:bash}
> bin/kafka-storage.sh format --cluster-id=-Yh6XyBIQ9CeAlMwJ8f7Hg -c
> config/kraft/controller.properties{code}
> I would propose to change the documentation based on my findings so we will
> be able to cover also ZooKeeper based cluster ids with a leading dash.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (KAFKA-19988) KRaft migration doc should account for ZK cluster id with a leading dash
[
https://issues.apache.org/jira/browse/KAFKA-19988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18047097#comment-18047097
]
ASF GitHub Bot commented on KAFKA-19988:
harmadasg commented on PR #760:
URL: https://github.com/apache/kafka-site/pull/760#issuecomment-3683837297
@mumrah thanks for the approve. You are correct, this is only a possible
problem for ZooKeeper based cluster ids.
Unfortunately I don't have the option to merge the PR (maybe because the
failing CI check?) Could you please do it for me? Or in case we have to do
something about the docker image issue, what would be the next step?
> KRaft migration doc should account for ZK cluster id with a leading dash
>
>
> Key: KAFKA-19988
> URL: https://issues.apache.org/jira/browse/KAFKA-19988
> Project: Kafka
> Issue Type: Bug
> Components: docs, documentation, kraft, migration
>Affects Versions: 3.9.1
>Reporter: Gergely Harmadás
>Assignee: Gergely Harmadás
>Priority: Minor
> Fix For: 3.9.2
>
>
> When preparing for the migration, there is a small chance that the retrieved
> cluster id from ZooKeeper contains a leading dash. Currently the 3.9
> documentation specifies the following during the step "Provisioning the KRaft
> controller quorum":
> {code:bash}
> # Save the previously retrieved cluster ID from ZooKeeper in a variable
> called zk-cluster-id
> $ bin/kafka-storage.sh format --standalone -t -c
> config/kraft/controller.properties{code}
> However the above command will fail with a less fortunate cluster id like
> -{{{}Yh6XyBIQ9CeAlMwJ8f7Hg{}}}, eg.:
> {noformat}
> bin/kafka-storage.sh format --standalone -t -Yh6XyBIQ9CeAlMwJ8f7Hg -c
> config/server.properties
> 25/12/12 09:24:54 INFO utils.Log4jControllerRegistration$: [main]:
> Registered `kafka:type=kafka.Log4jController` MBean
> usage: kafka-storage format [-h] --config CONFIG --cluster-id CLUSTER_ID
> [--add-scram ADD_SCRAM] [--ignore-formatted] [--release-version
> RELEASE_VERSION] [--feature FEATURE] [--standalone |
> --no-initial-controllers | --initial-controllers
> INITIAL_CONTROLLERS]
> kafka-storage: error: argument --cluster-id/-t: expected one argument
> {noformat}
> A similar problem came up with KRaft which was addressed in KAFKA-13741. In
> our case the cluster id is already specified, there is no way to change it. I
> was able to come up with a simple solution by using the full name of the
> argument like "--cluster-id=" instead of the shorthand "-t
> ". Full example:
> {code:bash}
> bin/kafka-storage.sh format --cluster-id=-Yh6XyBIQ9CeAlMwJ8f7Hg -c
> config/kraft/controller.properties{code}
> I would propose to change the documentation based on my findings so we will
> be able to cover also ZooKeeper based cluster ids with a leading dash.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (KAFKA-19988) KRaft migration doc should account for ZK cluster id with a leading dash
[
https://issues.apache.org/jira/browse/KAFKA-19988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18046784#comment-18046784
]
ASF GitHub Bot commented on KAFKA-19988:
mumrah commented on PR #760:
URL: https://github.com/apache/kafka-site/pull/760#issuecomment-3677310221
Ah, interesting.
```
ERROR: failed to build: failed to solve: failed to push
ghcr.io/apache/kafka-site:pr-760: denied: installation not allowed to Write
organization package
Error: buildx failed with: ERROR: failed to build: failed to solve: failed
to push ghcr.io/apache/kafka-site:pr-760: denied: installation not allowed to
Write organization package
```
I guess that makes sense that only committers could publish a Docker image
from a PR.
> KRaft migration doc should account for ZK cluster id with a leading dash
>
>
> Key: KAFKA-19988
> URL: https://issues.apache.org/jira/browse/KAFKA-19988
> Project: Kafka
> Issue Type: Bug
> Components: docs, documentation, kraft, migration
>Affects Versions: 3.9.1
>Reporter: Gergely Harmadás
>Assignee: Gergely Harmadás
>Priority: Minor
> Fix For: 3.9.2
>
>
> When preparing for the migration, there is a small chance that the retrieved
> cluster id from ZooKeeper contains a leading dash. Currently the 3.9
> documentation specifies the following during the step "Provisioning the KRaft
> controller quorum":
> {code:bash}
> # Save the previously retrieved cluster ID from ZooKeeper in a variable
> called zk-cluster-id
> $ bin/kafka-storage.sh format --standalone -t -c
> config/kraft/controller.properties{code}
> However the above command will fail with a less fortunate cluster id like
> -{{{}Yh6XyBIQ9CeAlMwJ8f7Hg{}}}, eg.:
> {noformat}
> bin/kafka-storage.sh format --standalone -t -Yh6XyBIQ9CeAlMwJ8f7Hg -c
> config/server.properties
> 25/12/12 09:24:54 INFO utils.Log4jControllerRegistration$: [main]:
> Registered `kafka:type=kafka.Log4jController` MBean
> usage: kafka-storage format [-h] --config CONFIG --cluster-id CLUSTER_ID
> [--add-scram ADD_SCRAM] [--ignore-formatted] [--release-version
> RELEASE_VERSION] [--feature FEATURE] [--standalone |
> --no-initial-controllers | --initial-controllers
> INITIAL_CONTROLLERS]
> kafka-storage: error: argument --cluster-id/-t: expected one argument
> {noformat}
> A similar problem came up with KRaft which was addressed in KAFKA-13741. In
> our case the cluster id is already specified, there is no way to change it. I
> was able to come up with a simple solution by using the full name of the
> argument like "--cluster-id=" instead of the shorthand "-t
> ". Full example:
> {code:bash}
> bin/kafka-storage.sh format --cluster-id=-Yh6XyBIQ9CeAlMwJ8f7Hg -c
> config/kraft/controller.properties{code}
> I would propose to change the documentation based on my findings so we will
> be able to cover also ZooKeeper based cluster ids with a leading dash.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (KAFKA-19988) KRaft migration doc should account for ZK cluster id with a leading dash
[
https://issues.apache.org/jira/browse/KAFKA-19988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18046781#comment-18046781
]
ASF GitHub Bot commented on KAFKA-19988:
mumrah closed pull request #760: KAFKA-19988: change example kafka-storage
command in the migration section
URL: https://github.com/apache/kafka-site/pull/760
> KRaft migration doc should account for ZK cluster id with a leading dash
>
>
> Key: KAFKA-19988
> URL: https://issues.apache.org/jira/browse/KAFKA-19988
> Project: Kafka
> Issue Type: Bug
> Components: docs, documentation, kraft, migration
>Affects Versions: 3.9.1
>Reporter: Gergely Harmadás
>Assignee: Gergely Harmadás
>Priority: Minor
> Fix For: 3.9.2
>
>
> When preparing for the migration, there is a small chance that the retrieved
> cluster id from ZooKeeper contains a leading dash. Currently the 3.9
> documentation specifies the following during the step "Provisioning the KRaft
> controller quorum":
> {code:bash}
> # Save the previously retrieved cluster ID from ZooKeeper in a variable
> called zk-cluster-id
> $ bin/kafka-storage.sh format --standalone -t -c
> config/kraft/controller.properties{code}
> However the above command will fail with a less fortunate cluster id like
> -{{{}Yh6XyBIQ9CeAlMwJ8f7Hg{}}}, eg.:
> {noformat}
> bin/kafka-storage.sh format --standalone -t -Yh6XyBIQ9CeAlMwJ8f7Hg -c
> config/server.properties
> 25/12/12 09:24:54 INFO utils.Log4jControllerRegistration$: [main]:
> Registered `kafka:type=kafka.Log4jController` MBean
> usage: kafka-storage format [-h] --config CONFIG --cluster-id CLUSTER_ID
> [--add-scram ADD_SCRAM] [--ignore-formatted] [--release-version
> RELEASE_VERSION] [--feature FEATURE] [--standalone |
> --no-initial-controllers | --initial-controllers
> INITIAL_CONTROLLERS]
> kafka-storage: error: argument --cluster-id/-t: expected one argument
> {noformat}
> A similar problem came up with KRaft which was addressed in KAFKA-13741. In
> our case the cluster id is already specified, there is no way to change it. I
> was able to come up with a simple solution by using the full name of the
> argument like "--cluster-id=" instead of the shorthand "-t
> ". Full example:
> {code:bash}
> bin/kafka-storage.sh format --cluster-id=-Yh6XyBIQ9CeAlMwJ8f7Hg -c
> config/kraft/controller.properties{code}
> I would propose to change the documentation based on my findings so we will
> be able to cover also ZooKeeper based cluster ids with a leading dash.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (KAFKA-19988) KRaft migration doc should account for ZK cluster id with a leading dash
[
https://issues.apache.org/jira/browse/KAFKA-19988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18046782#comment-18046782
]
ASF GitHub Bot commented on KAFKA-19988:
harmadasg opened a new pull request, #760:
URL: https://github.com/apache/kafka-site/pull/760
When preparing for the migration, there is a small chance that the retrieved
cluster id from ZooKeeper contains a leading dash. Currently the 3.9
documentation specifies the following during the step "Provisioning the KRaft
controller quorum":
```
# Save the previously retrieved cluster ID from ZooKeeper in a variable
called zk-cluster-id
$ bin/kafka-storage.sh format --standalone -t -c
config/kraft/controller.properties
```
However the above command will fail with a less fortunate cluster id like
`-Yh6XyBIQ9CeAlMwJ8f7Hg`, eg.:
```
bin/kafka-storage.sh format --standalone -t -Yh6XyBIQ9CeAlMwJ8f7Hg -c
config/server.properties
25/12/12 09:24:54 INFO utils.Log4jControllerRegistration$: [main]:
Registered `kafka:type=kafka.Log4jController` MBean
usage: kafka-storage format [-h] --config CONFIG --cluster-id CLUSTER_ID
[--add-scram ADD_SCRAM] [--ignore-formatted] [--release-version
RELEASE_VERSION] [--feature FEATURE] [--standalone |
--no-initial-controllers | --initial-controllers
INITIAL_CONTROLLERS]
kafka-storage: error: argument --cluster-id/-t: expected one argument
```
A similar problem came up with KRaft which was addressed in
[KAFKA-13741](https://issues.apache.org/jira/browse/KAFKA-13741). In our case
the cluster id is already specified, there is no way to change it. I was able
to come up with a simple solution by using the full name of the argument like
`--cluster-id=` instead of the shorthand `-t `.
Full example:
```
bin/kafka-storage.sh format --cluster-id=-Yh6XyBIQ9CeAlMwJ8f7Hg -c
config/kraft/controller.properties
```
I would propose to change the documentation based on my findings so we will
be able to cover also ZooKeeper based cluster ids with a leading dash.
> KRaft migration doc should account for ZK cluster id with a leading dash
>
>
> Key: KAFKA-19988
> URL: https://issues.apache.org/jira/browse/KAFKA-19988
> Project: Kafka
> Issue Type: Bug
> Components: docs, documentation, kraft, migration
>Affects Versions: 3.9.1
>Reporter: Gergely Harmadás
>Assignee: Gergely Harmadás
>Priority: Minor
> Fix For: 3.9.2
>
>
> When preparing for the migration, there is a small chance that the retrieved
> cluster id from ZooKeeper contains a leading dash. Currently the 3.9
> documentation specifies the following during the step "Provisioning the KRaft
> controller quorum":
> {code:bash}
> # Save the previously retrieved cluster ID from ZooKeeper in a variable
> called zk-cluster-id
> $ bin/kafka-storage.sh format --standalone -t -c
> config/kraft/controller.properties{code}
> However the above command will fail with a less fortunate cluster id like
> -{{{}Yh6XyBIQ9CeAlMwJ8f7Hg{}}}, eg.:
> {noformat}
> bin/kafka-storage.sh format --standalone -t -Yh6XyBIQ9CeAlMwJ8f7Hg -c
> config/server.properties
> 25/12/12 09:24:54 INFO utils.Log4jControllerRegistration$: [main]:
> Registered `kafka:type=kafka.Log4jController` MBean
> usage: kafka-storage format [-h] --config CONFIG --cluster-id CLUSTER_ID
> [--add-scram ADD_SCRAM] [--ignore-formatted] [--release-version
> RELEASE_VERSION] [--feature FEATURE] [--standalone |
> --no-initial-controllers | --initial-controllers
> INITIAL_CONTROLLERS]
> kafka-storage: error: argument --cluster-id/-t: expected one argument
> {noformat}
> A similar problem came up with KRaft which was addressed in KAFKA-13741. In
> our case the cluster id is already specified, there is no way to change it. I
> was able to come up with a simple solution by using the full name of the
> argument like "--cluster-id=" instead of the shorthand "-t
> ". Full example:
> {code:bash}
> bin/kafka-storage.sh format --cluster-id=-Yh6XyBIQ9CeAlMwJ8f7Hg -c
> config/kraft/controller.properties{code}
> I would propose to change the documentation based on my findings so we will
> be able to cover also ZooKeeper based cluster ids with a leading dash.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (KAFKA-19988) KRaft migration doc should account for ZK cluster id with a leading dash
[
https://issues.apache.org/jira/browse/KAFKA-19988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18046777#comment-18046777
]
ASF GitHub Bot commented on KAFKA-19988:
harmadasg opened a new pull request, #760:
URL: https://github.com/apache/kafka-site/pull/760
When preparing for the migration, there is a small chance that the retrieved
cluster id from ZooKeeper contains a leading dash. Currently the 3.9
documentation specifies the following during the step "Provisioning the KRaft
controller quorum":
```
# Save the previously retrieved cluster ID from ZooKeeper in a variable
called zk-cluster-id
$ bin/kafka-storage.sh format --standalone -t -c
config/kraft/controller.properties
```
However the above command will fail with a less fortunate cluster id like
`-Yh6XyBIQ9CeAlMwJ8f7Hg`, eg.:
```
bin/kafka-storage.sh format --standalone -t -Yh6XyBIQ9CeAlMwJ8f7Hg -c
config/server.properties
25/12/12 09:24:54 INFO utils.Log4jControllerRegistration$: [main]:
Registered `kafka:type=kafka.Log4jController` MBean
usage: kafka-storage format [-h] --config CONFIG --cluster-id CLUSTER_ID
[--add-scram ADD_SCRAM] [--ignore-formatted] [--release-version
RELEASE_VERSION] [--feature FEATURE] [--standalone |
--no-initial-controllers | --initial-controllers
INITIAL_CONTROLLERS]
kafka-storage: error: argument --cluster-id/-t: expected one argument
```
A similar problem came up with KRaft which was addressed in
[KAFKA-13741](https://issues.apache.org/jira/browse/KAFKA-13741). In our case
the cluster id is already specified, there is no way to change it. I was able
to come up with a simple solution by using the full name of the argument like
`--cluster-id=` instead of the shorthand `-t `.
Full example:
```
bin/kafka-storage.sh format --cluster-id=-Yh6XyBIQ9CeAlMwJ8f7Hg -c
config/kraft/controller.properties
```
I would propose to change the documentation based on my findings so we will
be able to cover also ZooKeeper based cluster ids with a leading dash.
> KRaft migration doc should account for ZK cluster id with a leading dash
>
>
> Key: KAFKA-19988
> URL: https://issues.apache.org/jira/browse/KAFKA-19988
> Project: Kafka
> Issue Type: Bug
> Components: docs, documentation, kraft, migration
>Affects Versions: 3.9.1
>Reporter: Gergely Harmadás
>Assignee: Gergely Harmadás
>Priority: Minor
> Fix For: 3.9.2
>
>
> When preparing for the migration, there is a small chance that the retrieved
> cluster id from ZooKeeper contains a leading dash. Currently the 3.9
> documentation specifies the following during the step "Provisioning the KRaft
> controller quorum":
> {code:bash}
> # Save the previously retrieved cluster ID from ZooKeeper in a variable
> called zk-cluster-id
> $ bin/kafka-storage.sh format --standalone -t -c
> config/kraft/controller.properties{code}
> However the above command will fail with a less fortunate cluster id like
> -{{{}Yh6XyBIQ9CeAlMwJ8f7Hg{}}}, eg.:
> {noformat}
> bin/kafka-storage.sh format --standalone -t -Yh6XyBIQ9CeAlMwJ8f7Hg -c
> config/server.properties
> 25/12/12 09:24:54 INFO utils.Log4jControllerRegistration$: [main]:
> Registered `kafka:type=kafka.Log4jController` MBean
> usage: kafka-storage format [-h] --config CONFIG --cluster-id CLUSTER_ID
> [--add-scram ADD_SCRAM] [--ignore-formatted] [--release-version
> RELEASE_VERSION] [--feature FEATURE] [--standalone |
> --no-initial-controllers | --initial-controllers
> INITIAL_CONTROLLERS]
> kafka-storage: error: argument --cluster-id/-t: expected one argument
> {noformat}
> A similar problem came up with KRaft which was addressed in KAFKA-13741. In
> our case the cluster id is already specified, there is no way to change it. I
> was able to come up with a simple solution by using the full name of the
> argument like "--cluster-id=" instead of the shorthand "-t
> ". Full example:
> {code:bash}
> bin/kafka-storage.sh format --cluster-id=-Yh6XyBIQ9CeAlMwJ8f7Hg -c
> config/kraft/controller.properties{code}
> I would propose to change the documentation based on my findings so we will
> be able to cover also ZooKeeper based cluster ids with a leading dash.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (KAFKA-19988) KRaft migration doc should account for ZK cluster id with a leading dash
[
https://issues.apache.org/jira/browse/KAFKA-19988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18046776#comment-18046776
]
ASF GitHub Bot commented on KAFKA-19988:
mumrah closed pull request #760: KAFKA-19988: change example kafka-storage
command in the migration section
URL: https://github.com/apache/kafka-site/pull/760
> KRaft migration doc should account for ZK cluster id with a leading dash
>
>
> Key: KAFKA-19988
> URL: https://issues.apache.org/jira/browse/KAFKA-19988
> Project: Kafka
> Issue Type: Bug
> Components: docs, documentation, kraft, migration
>Affects Versions: 3.9.1
>Reporter: Gergely Harmadás
>Assignee: Gergely Harmadás
>Priority: Minor
> Fix For: 3.9.2
>
>
> When preparing for the migration, there is a small chance that the retrieved
> cluster id from ZooKeeper contains a leading dash. Currently the 3.9
> documentation specifies the following during the step "Provisioning the KRaft
> controller quorum":
> {code:bash}
> # Save the previously retrieved cluster ID from ZooKeeper in a variable
> called zk-cluster-id
> $ bin/kafka-storage.sh format --standalone -t -c
> config/kraft/controller.properties{code}
> However the above command will fail with a less fortunate cluster id like
> -{{{}Yh6XyBIQ9CeAlMwJ8f7Hg{}}}, eg.:
> {noformat}
> bin/kafka-storage.sh format --standalone -t -Yh6XyBIQ9CeAlMwJ8f7Hg -c
> config/server.properties
> 25/12/12 09:24:54 INFO utils.Log4jControllerRegistration$: [main]:
> Registered `kafka:type=kafka.Log4jController` MBean
> usage: kafka-storage format [-h] --config CONFIG --cluster-id CLUSTER_ID
> [--add-scram ADD_SCRAM] [--ignore-formatted] [--release-version
> RELEASE_VERSION] [--feature FEATURE] [--standalone |
> --no-initial-controllers | --initial-controllers
> INITIAL_CONTROLLERS]
> kafka-storage: error: argument --cluster-id/-t: expected one argument
> {noformat}
> A similar problem came up with KRaft which was addressed in KAFKA-13741. In
> our case the cluster id is already specified, there is no way to change it. I
> was able to come up with a simple solution by using the full name of the
> argument like "--cluster-id=" instead of the shorthand "-t
> ". Full example:
> {code:bash}
> bin/kafka-storage.sh format --cluster-id=-Yh6XyBIQ9CeAlMwJ8f7Hg -c
> config/kraft/controller.properties{code}
> I would propose to change the documentation based on my findings so we will
> be able to cover also ZooKeeper based cluster ids with a leading dash.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (KAFKA-19988) KRaft migration doc should account for ZK cluster id with a leading dash
[
https://issues.apache.org/jira/browse/KAFKA-19988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18046506#comment-18046506
]
ASF GitHub Bot commented on KAFKA-19988:
harmadasg commented on PR #760:
URL: https://github.com/apache/kafka-site/pull/760#issuecomment-3673872819
@mumrah sure no problem, feel free to use this PR to test the CI
> KRaft migration doc should account for ZK cluster id with a leading dash
>
>
> Key: KAFKA-19988
> URL: https://issues.apache.org/jira/browse/KAFKA-19988
> Project: Kafka
> Issue Type: Bug
> Components: docs, documentation, kraft, migration
>Affects Versions: 3.9.1
>Reporter: Gergely Harmadás
>Assignee: Gergely Harmadás
>Priority: Minor
> Fix For: 3.9.2
>
>
> When preparing for the migration, there is a small chance that the retrieved
> cluster id from ZooKeeper contains a leading dash. Currently the 3.9
> documentation specifies the following during the step "Provisioning the KRaft
> controller quorum":
> {code:bash}
> # Save the previously retrieved cluster ID from ZooKeeper in a variable
> called zk-cluster-id
> $ bin/kafka-storage.sh format --standalone -t -c
> config/kraft/controller.properties{code}
> However the above command will fail with a less fortunate cluster id like
> -{{{}Yh6XyBIQ9CeAlMwJ8f7Hg{}}}, eg.:
> {noformat}
> bin/kafka-storage.sh format --standalone -t -Yh6XyBIQ9CeAlMwJ8f7Hg -c
> config/server.properties
> 25/12/12 09:24:54 INFO utils.Log4jControllerRegistration$: [main]:
> Registered `kafka:type=kafka.Log4jController` MBean
> usage: kafka-storage format [-h] --config CONFIG --cluster-id CLUSTER_ID
> [--add-scram ADD_SCRAM] [--ignore-formatted] [--release-version
> RELEASE_VERSION] [--feature FEATURE] [--standalone |
> --no-initial-controllers | --initial-controllers
> INITIAL_CONTROLLERS]
> kafka-storage: error: argument --cluster-id/-t: expected one argument
> {noformat}
> A similar problem came up with KRaft which was addressed in KAFKA-13741. In
> our case the cluster id is already specified, there is no way to change it. I
> was able to come up with a simple solution by using the full name of the
> argument like "--cluster-id=" instead of the shorthand "-t
> ". Full example:
> {code:bash}
> bin/kafka-storage.sh format --cluster-id=-Yh6XyBIQ9CeAlMwJ8f7Hg -c
> config/kraft/controller.properties{code}
> I would propose to change the documentation based on my findings so we will
> be able to cover also ZooKeeper based cluster ids with a leading dash.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (KAFKA-19988) KRaft migration doc should account for ZK cluster id with a leading dash
[
https://issues.apache.org/jira/browse/KAFKA-19988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18046450#comment-18046450
]
ASF GitHub Bot commented on KAFKA-19988:
harmadasg opened a new pull request, #760:
URL: https://github.com/apache/kafka-site/pull/760
When preparing for the migration, there is a small chance that the retrieved
cluster id from ZooKeeper contains a leading dash. Currently the 3.9
documentation specifies the following during the step "Provisioning the KRaft
controller quorum":
```
# Save the previously retrieved cluster ID from ZooKeeper in a variable
called zk-cluster-id
$ bin/kafka-storage.sh format --standalone -t -c
config/kraft/controller.properties
```
However the above command will fail with a less fortunate cluster id like
`-Yh6XyBIQ9CeAlMwJ8f7Hg`, eg.:
```
bin/kafka-storage.sh format --standalone -t -Yh6XyBIQ9CeAlMwJ8f7Hg -c
config/server.properties
25/12/12 09:24:54 INFO utils.Log4jControllerRegistration$: [main]:
Registered `kafka:type=kafka.Log4jController` MBean
usage: kafka-storage format [-h] --config CONFIG --cluster-id CLUSTER_ID
[--add-scram ADD_SCRAM] [--ignore-formatted] [--release-version
RELEASE_VERSION] [--feature FEATURE] [--standalone |
--no-initial-controllers | --initial-controllers
INITIAL_CONTROLLERS]
kafka-storage: error: argument --cluster-id/-t: expected one argument
```
A similar problem came up with KRaft which was addressed in
[KAFKA-13741](https://issues.apache.org/jira/browse/KAFKA-13741). In our case
the cluster id is already specified, there is no way to change it. I was able
to come up with a simple solution by using the full name of the argument like
`--cluster-id=` instead of the shorthand `-t `.
Full example:
```
bin/kafka-storage.sh format --cluster-id=-Yh6XyBIQ9CeAlMwJ8f7Hg -c
config/kraft/controller.properties
```
I would propose to change the documentation based on my findings so we will
be able to cover also ZooKeeper based cluster ids with a leading dash.
> KRaft migration doc should account for ZK cluster id with a leading dash
>
>
> Key: KAFKA-19988
> URL: https://issues.apache.org/jira/browse/KAFKA-19988
> Project: Kafka
> Issue Type: Bug
> Components: docs, documentation, kraft, migration
>Affects Versions: 3.9.1
>Reporter: Gergely Harmadás
>Assignee: Gergely Harmadás
>Priority: Minor
> Fix For: 3.9.2
>
>
> When preparing for the migration, there is a small chance that the retrieved
> cluster id from ZooKeeper contains a leading dash. Currently the 3.9
> documentation specifies the following during the step "Provisioning the KRaft
> controller quorum":
> {code:bash}
> # Save the previously retrieved cluster ID from ZooKeeper in a variable
> called zk-cluster-id
> $ bin/kafka-storage.sh format --standalone -t -c
> config/kraft/controller.properties{code}
> However the above command will fail with a less fortunate cluster id like
> -{{{}Yh6XyBIQ9CeAlMwJ8f7Hg{}}}, eg.:
> {noformat}
> bin/kafka-storage.sh format --standalone -t -Yh6XyBIQ9CeAlMwJ8f7Hg -c
> config/server.properties
> 25/12/12 09:24:54 INFO utils.Log4jControllerRegistration$: [main]:
> Registered `kafka:type=kafka.Log4jController` MBean
> usage: kafka-storage format [-h] --config CONFIG --cluster-id CLUSTER_ID
> [--add-scram ADD_SCRAM] [--ignore-formatted] [--release-version
> RELEASE_VERSION] [--feature FEATURE] [--standalone |
> --no-initial-controllers | --initial-controllers
> INITIAL_CONTROLLERS]
> kafka-storage: error: argument --cluster-id/-t: expected one argument
> {noformat}
> A similar problem came up with KRaft which was addressed in KAFKA-13741. In
> our case the cluster id is already specified, there is no way to change it. I
> was able to come up with a simple solution by using the full name of the
> argument like "--cluster-id=" instead of the shorthand "-t
> ". Full example:
> {code:bash}
> bin/kafka-storage.sh format --cluster-id=-Yh6XyBIQ9CeAlMwJ8f7Hg -c
> config/kraft/controller.properties{code}
> I would propose to change the documentation based on my findings so we will
> be able to cover also ZooKeeper based cluster ids with a leading dash.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (KAFKA-19988) KRaft migration doc should account for ZK cluster id with a leading dash
[
https://issues.apache.org/jira/browse/KAFKA-19988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18046449#comment-18046449
]
ASF GitHub Bot commented on KAFKA-19988:
mumrah commented on PR #760:
URL: https://github.com/apache/kafka-site/pull/760#issuecomment-3672572344
Thanks @harmadasg! I'm going to close and reopen this to test our build
> KRaft migration doc should account for ZK cluster id with a leading dash
>
>
> Key: KAFKA-19988
> URL: https://issues.apache.org/jira/browse/KAFKA-19988
> Project: Kafka
> Issue Type: Bug
> Components: docs, documentation, kraft, migration
>Affects Versions: 3.9.1
>Reporter: Gergely Harmadás
>Assignee: Gergely Harmadás
>Priority: Minor
> Fix For: 3.9.2
>
>
> When preparing for the migration, there is a small chance that the retrieved
> cluster id from ZooKeeper contains a leading dash. Currently the 3.9
> documentation specifies the following during the step "Provisioning the KRaft
> controller quorum":
> {code:bash}
> # Save the previously retrieved cluster ID from ZooKeeper in a variable
> called zk-cluster-id
> $ bin/kafka-storage.sh format --standalone -t -c
> config/kraft/controller.properties{code}
> However the above command will fail with a less fortunate cluster id like
> -{{{}Yh6XyBIQ9CeAlMwJ8f7Hg{}}}, eg.:
> {noformat}
> bin/kafka-storage.sh format --standalone -t -Yh6XyBIQ9CeAlMwJ8f7Hg -c
> config/server.properties
> 25/12/12 09:24:54 INFO utils.Log4jControllerRegistration$: [main]:
> Registered `kafka:type=kafka.Log4jController` MBean
> usage: kafka-storage format [-h] --config CONFIG --cluster-id CLUSTER_ID
> [--add-scram ADD_SCRAM] [--ignore-formatted] [--release-version
> RELEASE_VERSION] [--feature FEATURE] [--standalone |
> --no-initial-controllers | --initial-controllers
> INITIAL_CONTROLLERS]
> kafka-storage: error: argument --cluster-id/-t: expected one argument
> {noformat}
> A similar problem came up with KRaft which was addressed in KAFKA-13741. In
> our case the cluster id is already specified, there is no way to change it. I
> was able to come up with a simple solution by using the full name of the
> argument like "--cluster-id=" instead of the shorthand "-t
> ". Full example:
> {code:bash}
> bin/kafka-storage.sh format --cluster-id=-Yh6XyBIQ9CeAlMwJ8f7Hg -c
> config/kraft/controller.properties{code}
> I would propose to change the documentation based on my findings so we will
> be able to cover also ZooKeeper based cluster ids with a leading dash.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (KAFKA-19988) KRaft migration doc should account for ZK cluster id with a leading dash
[
https://issues.apache.org/jira/browse/KAFKA-19988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18046448#comment-18046448
]
ASF GitHub Bot commented on KAFKA-19988:
mumrah closed pull request #760: KAFKA-19988: change example kafka-storage
command in the migration section
URL: https://github.com/apache/kafka-site/pull/760
> KRaft migration doc should account for ZK cluster id with a leading dash
>
>
> Key: KAFKA-19988
> URL: https://issues.apache.org/jira/browse/KAFKA-19988
> Project: Kafka
> Issue Type: Bug
> Components: docs, documentation, kraft, migration
>Affects Versions: 3.9.1
>Reporter: Gergely Harmadás
>Assignee: Gergely Harmadás
>Priority: Minor
> Fix For: 3.9.2
>
>
> When preparing for the migration, there is a small chance that the retrieved
> cluster id from ZooKeeper contains a leading dash. Currently the 3.9
> documentation specifies the following during the step "Provisioning the KRaft
> controller quorum":
> {code:bash}
> # Save the previously retrieved cluster ID from ZooKeeper in a variable
> called zk-cluster-id
> $ bin/kafka-storage.sh format --standalone -t -c
> config/kraft/controller.properties{code}
> However the above command will fail with a less fortunate cluster id like
> -{{{}Yh6XyBIQ9CeAlMwJ8f7Hg{}}}, eg.:
> {noformat}
> bin/kafka-storage.sh format --standalone -t -Yh6XyBIQ9CeAlMwJ8f7Hg -c
> config/server.properties
> 25/12/12 09:24:54 INFO utils.Log4jControllerRegistration$: [main]:
> Registered `kafka:type=kafka.Log4jController` MBean
> usage: kafka-storage format [-h] --config CONFIG --cluster-id CLUSTER_ID
> [--add-scram ADD_SCRAM] [--ignore-formatted] [--release-version
> RELEASE_VERSION] [--feature FEATURE] [--standalone |
> --no-initial-controllers | --initial-controllers
> INITIAL_CONTROLLERS]
> kafka-storage: error: argument --cluster-id/-t: expected one argument
> {noformat}
> A similar problem came up with KRaft which was addressed in KAFKA-13741. In
> our case the cluster id is already specified, there is no way to change it. I
> was able to come up with a simple solution by using the full name of the
> argument like "--cluster-id=" instead of the shorthand "-t
> ". Full example:
> {code:bash}
> bin/kafka-storage.sh format --cluster-id=-Yh6XyBIQ9CeAlMwJ8f7Hg -c
> config/kraft/controller.properties{code}
> I would propose to change the documentation based on my findings so we will
> be able to cover also ZooKeeper based cluster ids with a leading dash.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (KAFKA-19988) KRaft migration doc should account for ZK cluster id with a leading dash
[
https://issues.apache.org/jira/browse/KAFKA-19988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18046125#comment-18046125
]
Gergely Harmadás commented on KAFKA-19988:
--
Hi [~chia7712], since you showed interests in this task, may I please ask for
your assistance to review the changes if you have some time? FYI I had to open
a new PR for kafka-site due to the recent changes regarding the documentation
format [kafka-site#760|https://github.com/apache/kafka-site/pull/760]
> KRaft migration doc should account for ZK cluster id with a leading dash
>
>
> Key: KAFKA-19988
> URL: https://issues.apache.org/jira/browse/KAFKA-19988
> Project: Kafka
> Issue Type: Bug
> Components: docs, documentation, kraft, migration
>Affects Versions: 3.9.1
>Reporter: Gergely Harmadás
>Assignee: Gergely Harmadás
>Priority: Minor
> Fix For: 3.9.2
>
>
> When preparing for the migration, there is a small chance that the retrieved
> cluster id from ZooKeeper contains a leading dash. Currently the 3.9
> documentation specifies the following during the step "Provisioning the KRaft
> controller quorum":
> {code:bash}
> # Save the previously retrieved cluster ID from ZooKeeper in a variable
> called zk-cluster-id
> $ bin/kafka-storage.sh format --standalone -t -c
> config/kraft/controller.properties{code}
> However the above command will fail with a less fortunate cluster id like
> -{{{}Yh6XyBIQ9CeAlMwJ8f7Hg{}}}, eg.:
> {noformat}
> bin/kafka-storage.sh format --standalone -t -Yh6XyBIQ9CeAlMwJ8f7Hg -c
> config/server.properties
> 25/12/12 09:24:54 INFO utils.Log4jControllerRegistration$: [main]:
> Registered `kafka:type=kafka.Log4jController` MBean
> usage: kafka-storage format [-h] --config CONFIG --cluster-id CLUSTER_ID
> [--add-scram ADD_SCRAM] [--ignore-formatted] [--release-version
> RELEASE_VERSION] [--feature FEATURE] [--standalone |
> --no-initial-controllers | --initial-controllers
> INITIAL_CONTROLLERS]
> kafka-storage: error: argument --cluster-id/-t: expected one argument
> {noformat}
> A similar problem came up with KRaft which was addressed in KAFKA-13741. In
> our case the cluster id is already specified, there is no way to change it. I
> was able to come up with a simple solution by using the full name of the
> argument like "--cluster-id=" instead of the shorthand "-t
> ". Full example:
> {code:bash}
> bin/kafka-storage.sh format --cluster-id=-Yh6XyBIQ9CeAlMwJ8f7Hg -c
> config/kraft/controller.properties{code}
> I would propose to change the documentation based on my findings so we will
> be able to cover also ZooKeeper based cluster ids with a leading dash.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (KAFKA-19988) KRaft migration doc should account for ZK cluster id with a leading dash
[
https://issues.apache.org/jira/browse/KAFKA-19988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18046123#comment-18046123
]
ASF GitHub Bot commented on KAFKA-19988:
harmadasg commented on PR #760:
URL: https://github.com/apache/kafka-site/pull/760#issuecomment-3668912797
Original PR https://github.com/apache/kafka-site/pull/756 has been closed
due to the changes related to
[KIP-1133](https://cwiki.apache.org/confluence/display/KAFKA/KIP-1133%3A+AK+Documentation+and+Website+in+Markdown),
so I opened the current PR to comply with the new markdown format.
> KRaft migration doc should account for ZK cluster id with a leading dash
>
>
> Key: KAFKA-19988
> URL: https://issues.apache.org/jira/browse/KAFKA-19988
> Project: Kafka
> Issue Type: Bug
> Components: docs, documentation, kraft, migration
>Affects Versions: 3.9.1
>Reporter: Gergely Harmadás
>Assignee: Gergely Harmadás
>Priority: Minor
> Fix For: 3.9.2
>
>
> When preparing for the migration, there is a small chance that the retrieved
> cluster id from ZooKeeper contains a leading dash. Currently the 3.9
> documentation specifies the following during the step "Provisioning the KRaft
> controller quorum":
> {code:bash}
> # Save the previously retrieved cluster ID from ZooKeeper in a variable
> called zk-cluster-id
> $ bin/kafka-storage.sh format --standalone -t -c
> config/kraft/controller.properties{code}
> However the above command will fail with a less fortunate cluster id like
> -{{{}Yh6XyBIQ9CeAlMwJ8f7Hg{}}}, eg.:
> {noformat}
> bin/kafka-storage.sh format --standalone -t -Yh6XyBIQ9CeAlMwJ8f7Hg -c
> config/server.properties
> 25/12/12 09:24:54 INFO utils.Log4jControllerRegistration$: [main]:
> Registered `kafka:type=kafka.Log4jController` MBean
> usage: kafka-storage format [-h] --config CONFIG --cluster-id CLUSTER_ID
> [--add-scram ADD_SCRAM] [--ignore-formatted] [--release-version
> RELEASE_VERSION] [--feature FEATURE] [--standalone |
> --no-initial-controllers | --initial-controllers
> INITIAL_CONTROLLERS]
> kafka-storage: error: argument --cluster-id/-t: expected one argument
> {noformat}
> A similar problem came up with KRaft which was addressed in KAFKA-13741. In
> our case the cluster id is already specified, there is no way to change it. I
> was able to come up with a simple solution by using the full name of the
> argument like "--cluster-id=" instead of the shorthand "-t
> ". Full example:
> {code:bash}
> bin/kafka-storage.sh format --cluster-id=-Yh6XyBIQ9CeAlMwJ8f7Hg -c
> config/kraft/controller.properties{code}
> I would propose to change the documentation based on my findings so we will
> be able to cover also ZooKeeper based cluster ids with a leading dash.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (KAFKA-19988) KRaft migration doc should account for ZK cluster id with a leading dash
[
https://issues.apache.org/jira/browse/KAFKA-19988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18046121#comment-18046121
]
ASF GitHub Bot commented on KAFKA-19988:
harmadasg opened a new pull request, #760:
URL: https://github.com/apache/kafka-site/pull/760
When preparing for the migration, there is a small chance that the retrieved
cluster id from ZooKeeper contains a leading dash. Currently the 3.9
documentation specifies the following during the step "Provisioning the KRaft
controller quorum":
```
# Save the previously retrieved cluster ID from ZooKeeper in a variable
called zk-cluster-id
$ bin/kafka-storage.sh format --standalone -t -c
config/kraft/controller.properties
```
However the above command will fail with a less fortunate cluster id like
`-Yh6XyBIQ9CeAlMwJ8f7Hg`, eg.:
```
bin/kafka-storage.sh format --standalone -t -Yh6XyBIQ9CeAlMwJ8f7Hg -c
config/server.properties
25/12/12 09:24:54 INFO utils.Log4jControllerRegistration$: [main]:
Registered `kafka:type=kafka.Log4jController` MBean
usage: kafka-storage format [-h] --config CONFIG --cluster-id CLUSTER_ID
[--add-scram ADD_SCRAM] [--ignore-formatted] [--release-version
RELEASE_VERSION] [--feature FEATURE] [--standalone |
--no-initial-controllers | --initial-controllers
INITIAL_CONTROLLERS]
kafka-storage: error: argument --cluster-id/-t: expected one argument
```
A similar problem came up with KRaft which was addressed in
[KAFKA-13741](https://issues.apache.org/jira/browse/KAFKA-13741). In our case
the cluster id is already specified, there is no way to change it. I was able
to come up with a simple solution by using the full name of the argument like
`--cluster-id=` instead of the shorthand `-t `.
Full example:
```
bin/kafka-storage.sh format --cluster-id=-Yh6XyBIQ9CeAlMwJ8f7Hg -c
config/kraft/controller.properties
```
I would propose to change the documentation based on my findings so we will
be able to cover also ZooKeeper based cluster ids with a leading dash.
> KRaft migration doc should account for ZK cluster id with a leading dash
>
>
> Key: KAFKA-19988
> URL: https://issues.apache.org/jira/browse/KAFKA-19988
> Project: Kafka
> Issue Type: Bug
> Components: docs, documentation, kraft, migration
>Affects Versions: 3.9.1
>Reporter: Gergely Harmadás
>Assignee: Gergely Harmadás
>Priority: Minor
> Fix For: 3.9.2
>
>
> When preparing for the migration, there is a small chance that the retrieved
> cluster id from ZooKeeper contains a leading dash. Currently the 3.9
> documentation specifies the following during the step "Provisioning the KRaft
> controller quorum":
> {code:bash}
> # Save the previously retrieved cluster ID from ZooKeeper in a variable
> called zk-cluster-id
> $ bin/kafka-storage.sh format --standalone -t -c
> config/kraft/controller.properties{code}
> However the above command will fail with a less fortunate cluster id like
> -{{{}Yh6XyBIQ9CeAlMwJ8f7Hg{}}}, eg.:
> {noformat}
> bin/kafka-storage.sh format --standalone -t -Yh6XyBIQ9CeAlMwJ8f7Hg -c
> config/server.properties
> 25/12/12 09:24:54 INFO utils.Log4jControllerRegistration$: [main]:
> Registered `kafka:type=kafka.Log4jController` MBean
> usage: kafka-storage format [-h] --config CONFIG --cluster-id CLUSTER_ID
> [--add-scram ADD_SCRAM] [--ignore-formatted] [--release-version
> RELEASE_VERSION] [--feature FEATURE] [--standalone |
> --no-initial-controllers | --initial-controllers
> INITIAL_CONTROLLERS]
> kafka-storage: error: argument --cluster-id/-t: expected one argument
> {noformat}
> A similar problem came up with KRaft which was addressed in KAFKA-13741. In
> our case the cluster id is already specified, there is no way to change it. I
> was able to come up with a simple solution by using the full name of the
> argument like "--cluster-id=" instead of the shorthand "-t
> ". Full example:
> {code:bash}
> bin/kafka-storage.sh format --cluster-id=-Yh6XyBIQ9CeAlMwJ8f7Hg -c
> config/kraft/controller.properties{code}
> I would propose to change the documentation based on my findings so we will
> be able to cover also ZooKeeper based cluster ids with a leading dash.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (KAFKA-19988) KRaft migration doc should account for ZK cluster id with a leading dash
[
https://issues.apache.org/jira/browse/KAFKA-19988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18046001#comment-18046001
]
ASF GitHub Bot commented on KAFKA-19988:
mumrah commented on PR #756:
URL: https://github.com/apache/kafka-site/pull/756#issuecomment-3667252482
As per KIP-1133, we have converted our docs over to Markdown. This repo has
also changed its base branch to `markdown`. If you still want this change
applied, please reopen a PR using Markdown against the `markdown` branch.
Thanks!
> KRaft migration doc should account for ZK cluster id with a leading dash
>
>
> Key: KAFKA-19988
> URL: https://issues.apache.org/jira/browse/KAFKA-19988
> Project: Kafka
> Issue Type: Bug
> Components: docs, documentation, kraft, migration
>Affects Versions: 3.9.1
>Reporter: Gergely Harmadás
>Assignee: Gergely Harmadás
>Priority: Minor
> Fix For: 3.9.2
>
>
> When preparing for the migration, there is a small chance that the retrieved
> cluster id from ZooKeeper contains a leading dash. Currently the 3.9
> documentation specifies the following during the step "Provisioning the KRaft
> controller quorum":
> {code:bash}
> # Save the previously retrieved cluster ID from ZooKeeper in a variable
> called zk-cluster-id
> $ bin/kafka-storage.sh format --standalone -t -c
> config/kraft/controller.properties{code}
> However the above command will fail with a less fortunate cluster id like
> -{{{}Yh6XyBIQ9CeAlMwJ8f7Hg{}}}, eg.:
> {noformat}
> bin/kafka-storage.sh format --standalone -t -Yh6XyBIQ9CeAlMwJ8f7Hg -c
> config/server.properties
> 25/12/12 09:24:54 INFO utils.Log4jControllerRegistration$: [main]:
> Registered `kafka:type=kafka.Log4jController` MBean
> usage: kafka-storage format [-h] --config CONFIG --cluster-id CLUSTER_ID
> [--add-scram ADD_SCRAM] [--ignore-formatted] [--release-version
> RELEASE_VERSION] [--feature FEATURE] [--standalone |
> --no-initial-controllers | --initial-controllers
> INITIAL_CONTROLLERS]
> kafka-storage: error: argument --cluster-id/-t: expected one argument
> {noformat}
> A similar problem came up with KRaft which was addressed in KAFKA-13741. In
> our case the cluster id is already specified, there is no way to change it. I
> was able to come up with a simple solution by using the full name of the
> argument like "--cluster-id=" instead of the shorthand "-t
> ". Full example:
> {code:bash}
> bin/kafka-storage.sh format --cluster-id=-Yh6XyBIQ9CeAlMwJ8f7Hg -c
> config/kraft/controller.properties{code}
> I would propose to change the documentation based on my findings so we will
> be able to cover also ZooKeeper based cluster ids with a leading dash.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (KAFKA-19988) KRaft migration doc should account for ZK cluster id with a leading dash
[
https://issues.apache.org/jira/browse/KAFKA-19988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18046000#comment-18046000
]
ASF GitHub Bot commented on KAFKA-19988:
mumrah closed pull request #756: KAFKA-19988: change example kafka-storage
command in the migration section
URL: https://github.com/apache/kafka-site/pull/756
> KRaft migration doc should account for ZK cluster id with a leading dash
>
>
> Key: KAFKA-19988
> URL: https://issues.apache.org/jira/browse/KAFKA-19988
> Project: Kafka
> Issue Type: Bug
> Components: docs, documentation, kraft, migration
>Affects Versions: 3.9.1
>Reporter: Gergely Harmadás
>Assignee: Gergely Harmadás
>Priority: Minor
> Fix For: 3.9.2
>
>
> When preparing for the migration, there is a small chance that the retrieved
> cluster id from ZooKeeper contains a leading dash. Currently the 3.9
> documentation specifies the following during the step "Provisioning the KRaft
> controller quorum":
> {code:bash}
> # Save the previously retrieved cluster ID from ZooKeeper in a variable
> called zk-cluster-id
> $ bin/kafka-storage.sh format --standalone -t -c
> config/kraft/controller.properties{code}
> However the above command will fail with a less fortunate cluster id like
> -{{{}Yh6XyBIQ9CeAlMwJ8f7Hg{}}}, eg.:
> {noformat}
> bin/kafka-storage.sh format --standalone -t -Yh6XyBIQ9CeAlMwJ8f7Hg -c
> config/server.properties
> 25/12/12 09:24:54 INFO utils.Log4jControllerRegistration$: [main]:
> Registered `kafka:type=kafka.Log4jController` MBean
> usage: kafka-storage format [-h] --config CONFIG --cluster-id CLUSTER_ID
> [--add-scram ADD_SCRAM] [--ignore-formatted] [--release-version
> RELEASE_VERSION] [--feature FEATURE] [--standalone |
> --no-initial-controllers | --initial-controllers
> INITIAL_CONTROLLERS]
> kafka-storage: error: argument --cluster-id/-t: expected one argument
> {noformat}
> A similar problem came up with KRaft which was addressed in KAFKA-13741. In
> our case the cluster id is already specified, there is no way to change it. I
> was able to come up with a simple solution by using the full name of the
> argument like "--cluster-id=" instead of the shorthand "-t
> ". Full example:
> {code:bash}
> bin/kafka-storage.sh format --cluster-id=-Yh6XyBIQ9CeAlMwJ8f7Hg -c
> config/kraft/controller.properties{code}
> I would propose to change the documentation based on my findings so we will
> be able to cover also ZooKeeper based cluster ids with a leading dash.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (KAFKA-19988) KRaft migration doc should account for ZK cluster id with a leading dash
[
https://issues.apache.org/jira/browse/KAFKA-19988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18044859#comment-18044859
]
Gergely Harmadás commented on KAFKA-19988:
--
Hi [~chia7712], I have opened a new PR for kafka-site
[kafka-site#756|https://github.com/apache/kafka-site/pull/756]
> KRaft migration doc should account for ZK cluster id with a leading dash
>
>
> Key: KAFKA-19988
> URL: https://issues.apache.org/jira/browse/KAFKA-19988
> Project: Kafka
> Issue Type: Bug
> Components: docs, documentation, kraft, migration
>Affects Versions: 3.9.1
>Reporter: Gergely Harmadás
>Assignee: Gergely Harmadás
>Priority: Minor
> Fix For: 3.9.2
>
>
> When preparing for the migration, there is a small chance that the retrieved
> cluster id from ZooKeeper contains a leading dash. Currently the 3.9
> documentation specifies the following during the step "Provisioning the KRaft
> controller quorum":
> {code:bash}
> # Save the previously retrieved cluster ID from ZooKeeper in a variable
> called zk-cluster-id
> $ bin/kafka-storage.sh format --standalone -t -c
> config/kraft/controller.properties{code}
> However the above command will fail with a less fortunate cluster id like
> -{{{}Yh6XyBIQ9CeAlMwJ8f7Hg{}}}, eg.:
> {noformat}
> bin/kafka-storage.sh format --standalone -t -Yh6XyBIQ9CeAlMwJ8f7Hg -c
> config/server.properties
> 25/12/12 09:24:54 INFO utils.Log4jControllerRegistration$: [main]:
> Registered `kafka:type=kafka.Log4jController` MBean
> usage: kafka-storage format [-h] --config CONFIG --cluster-id CLUSTER_ID
> [--add-scram ADD_SCRAM] [--ignore-formatted] [--release-version
> RELEASE_VERSION] [--feature FEATURE] [--standalone |
> --no-initial-controllers | --initial-controllers
> INITIAL_CONTROLLERS]
> kafka-storage: error: argument --cluster-id/-t: expected one argument
> {noformat}
> A similar problem came up with KRaft which was addressed in KAFKA-13741. In
> our case the cluster id is already specified, there is no way to change it. I
> was able to come up with a simple solution by using the full name of the
> argument like "--cluster-id=" instead of the shorthand "-t
> ". Full example:
> {code:bash}
> bin/kafka-storage.sh format --cluster-id=-Yh6XyBIQ9CeAlMwJ8f7Hg -c
> config/kraft/controller.properties{code}
> I would propose to change the documentation based on my findings so we will
> be able to cover also ZooKeeper based cluster ids with a leading dash.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (KAFKA-19988) KRaft migration doc should account for ZK cluster id with a leading dash
[
https://issues.apache.org/jira/browse/KAFKA-19988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18044858#comment-18044858
]
ASF GitHub Bot commented on KAFKA-19988:
harmadasg opened a new pull request, #756:
URL: https://github.com/apache/kafka-site/pull/756
When preparing for the migration, there is a small chance that the retrieved
cluster id from ZooKeeper contains a leading dash. Currently the 3.9
documentation specifies the following during the step "Provisioning the KRaft
controller quorum":
```
# Save the previously retrieved cluster ID from ZooKeeper in a variable
called zk-cluster-id
$ bin/kafka-storage.sh format --standalone -t -c
config/kraft/controller.properties
```
However the above command will fail with a less fortunate cluster id like
`-Yh6XyBIQ9CeAlMwJ8f7Hg`, eg.:
```
bin/kafka-storage.sh format --standalone -t -Yh6XyBIQ9CeAlMwJ8f7Hg -c
config/server.properties
25/12/12 09:24:54 INFO utils.Log4jControllerRegistration$: [main]:
Registered `kafka:type=kafka.Log4jController` MBean
usage: kafka-storage format [-h] --config CONFIG --cluster-id CLUSTER_ID
[--add-scram ADD_SCRAM] [--ignore-formatted] [--release-version
RELEASE_VERSION] [--feature FEATURE] [--standalone |
--no-initial-controllers | --initial-controllers
INITIAL_CONTROLLERS]
kafka-storage: error: argument --cluster-id/-t: expected one argument
```
A similar problem came up with KRaft which was addressed in
[KAFKA-13741](https://issues.apache.org/jira/browse/KAFKA-13741). In our case
the cluster id is already specified, there is no way to change it. I was able
to come up with a simple solution by using the full name of the argument like
`--cluster-id=` instead of the shorthand `-t `.
Full example:
```
bin/kafka-storage.sh format --cluster-id=-Yh6XyBIQ9CeAlMwJ8f7Hg -c
config/kraft/controller.properties
```
I would propose to change the documentation based on my findings so we will
be able to cover also ZooKeeper based cluster ids with a leading dash.
> KRaft migration doc should account for ZK cluster id with a leading dash
>
>
> Key: KAFKA-19988
> URL: https://issues.apache.org/jira/browse/KAFKA-19988
> Project: Kafka
> Issue Type: Bug
> Components: docs, documentation, kraft, migration
>Affects Versions: 3.9.1
>Reporter: Gergely Harmadás
>Assignee: Gergely Harmadás
>Priority: Minor
> Fix For: 3.9.2
>
>
> When preparing for the migration, there is a small chance that the retrieved
> cluster id from ZooKeeper contains a leading dash. Currently the 3.9
> documentation specifies the following during the step "Provisioning the KRaft
> controller quorum":
> {code:bash}
> # Save the previously retrieved cluster ID from ZooKeeper in a variable
> called zk-cluster-id
> $ bin/kafka-storage.sh format --standalone -t -c
> config/kraft/controller.properties{code}
> However the above command will fail with a less fortunate cluster id like
> -{{{}Yh6XyBIQ9CeAlMwJ8f7Hg{}}}, eg.:
> {noformat}
> bin/kafka-storage.sh format --standalone -t -Yh6XyBIQ9CeAlMwJ8f7Hg -c
> config/server.properties
> 25/12/12 09:24:54 INFO utils.Log4jControllerRegistration$: [main]:
> Registered `kafka:type=kafka.Log4jController` MBean
> usage: kafka-storage format [-h] --config CONFIG --cluster-id CLUSTER_ID
> [--add-scram ADD_SCRAM] [--ignore-formatted] [--release-version
> RELEASE_VERSION] [--feature FEATURE] [--standalone |
> --no-initial-controllers | --initial-controllers
> INITIAL_CONTROLLERS]
> kafka-storage: error: argument --cluster-id/-t: expected one argument
> {noformat}
> A similar problem came up with KRaft which was addressed in KAFKA-13741. In
> our case the cluster id is already specified, there is no way to change it. I
> was able to come up with a simple solution by using the full name of the
> argument like "--cluster-id=" instead of the shorthand "-t
> ". Full example:
> {code:bash}
> bin/kafka-storage.sh format --cluster-id=-Yh6XyBIQ9CeAlMwJ8f7Hg -c
> config/kraft/controller.properties{code}
> I would propose to change the documentation based on my findings so we will
> be able to cover also ZooKeeper based cluster ids with a leading dash.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (KAFKA-19988) KRaft migration doc should account for ZK cluster id with a leading dash
[
https://issues.apache.org/jira/browse/KAFKA-19988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18044818#comment-18044818
]
Chia-Ping Tsai commented on KAFKA-19988:
yes, we occasionally overlook consistency between the two repos. Could you
please open a corresponding patch for kafka-site?
> KRaft migration doc should account for ZK cluster id with a leading dash
>
>
> Key: KAFKA-19988
> URL: https://issues.apache.org/jira/browse/KAFKA-19988
> Project: Kafka
> Issue Type: Bug
> Components: docs, documentation, kraft, migration
>Affects Versions: 3.9.1
>Reporter: Gergely Harmadás
>Assignee: Gergely Harmadás
>Priority: Minor
> Fix For: 3.9.2
>
>
> When preparing for the migration, there is a small chance that the retrieved
> cluster id from ZooKeeper contains a leading dash. Currently the 3.9
> documentation specifies the following during the step "Provisioning the KRaft
> controller quorum":
> {code:bash}
> # Save the previously retrieved cluster ID from ZooKeeper in a variable
> called zk-cluster-id
> $ bin/kafka-storage.sh format --standalone -t -c
> config/kraft/controller.properties{code}
> However the above command will fail with a less fortunate cluster id like
> -{{{}Yh6XyBIQ9CeAlMwJ8f7Hg{}}}, eg.:
> {noformat}
> bin/kafka-storage.sh format --standalone -t -Yh6XyBIQ9CeAlMwJ8f7Hg -c
> config/server.properties
> 25/12/12 09:24:54 INFO utils.Log4jControllerRegistration$: [main]:
> Registered `kafka:type=kafka.Log4jController` MBean
> usage: kafka-storage format [-h] --config CONFIG --cluster-id CLUSTER_ID
> [--add-scram ADD_SCRAM] [--ignore-formatted] [--release-version
> RELEASE_VERSION] [--feature FEATURE] [--standalone |
> --no-initial-controllers | --initial-controllers
> INITIAL_CONTROLLERS]
> kafka-storage: error: argument --cluster-id/-t: expected one argument
> {noformat}
> A similar problem came up with KRaft which was addressed in KAFKA-13741. In
> our case the cluster id is already specified, there is no way to change it. I
> was able to come up with a simple solution by using the full name of the
> argument like "--cluster-id=" instead of the shorthand "-t
> ". Full example:
> {code:bash}
> bin/kafka-storage.sh format --cluster-id=-Yh6XyBIQ9CeAlMwJ8f7Hg -c
> config/kraft/controller.properties{code}
> I would propose to change the documentation based on my findings so we will
> be able to cover also ZooKeeper based cluster ids with a leading dash.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (KAFKA-19988) KRaft migration doc should account for ZK cluster id with a leading dash
[
https://issues.apache.org/jira/browse/KAFKA-19988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18044719#comment-18044719
]
Gergely Harmadás commented on KAFKA-19988:
--
[~chia7712] Thanks for checking the Jira. I have opened
[kafka#21137|https://github.com/apache/kafka/pull/21137] for the fix. FYI
currently {{ops.html}} is out of sync between [kafka
3.9|https://github.com/apache/kafka/blob/3.9/docs/ops.html] and
[kafka-site|https://github.com/apache/kafka-site/blob/asf-site/39/ops.html].
What I gathered is the following:
# [kafka#19158|https://github.com/apache/kafka/pull/19158] was opened to kafka
3.9 but the author was advised to instead open it directly to kafka-site since
the 3.9 docs was already published
# [kafka-site#667|https://github.com/apache/kafka-site/pull/667] was merged
# The newly added section was accidentally overridden in
[kafka-site#687|https://github.com/apache/kafka-site/pull/687] during the 3.9.1
release since it was not part of [ops.html in
kafka|https://github.com/apache/kafka/blob/3.9/docs/ops.html]
# [kafka-site#695|https://github.com/apache/kafka-site/pull/695] was merged in
order to revert some 3.9 doc changes that were unexpectedly overwritten
including the section about the kafka-storage tool command
All in all the section about the kafka-storage tool command is still missing
from [ops.html in
kafka|https://github.com/apache/kafka/blob/3.9/docs/ops.html]. I included in my
PR since I have to modify it anyway and this way there is no chance for an
accidental removal from kafka-site.
> KRaft migration doc should account for ZK cluster id with a leading dash
>
>
> Key: KAFKA-19988
> URL: https://issues.apache.org/jira/browse/KAFKA-19988
> Project: Kafka
> Issue Type: Bug
> Components: docs, documentation, kraft, migration
>Affects Versions: 3.9.1
>Reporter: Gergely Harmadás
>Assignee: Gergely Harmadás
>Priority: Minor
> Fix For: 3.9.2
>
>
> When preparing for the migration, there is a small chance that the retrieved
> cluster id from ZooKeeper contains a leading dash. Currently the 3.9
> documentation specifies the following during the step "Provisioning the KRaft
> controller quorum":
> {code:bash}
> # Save the previously retrieved cluster ID from ZooKeeper in a variable
> called zk-cluster-id
> $ bin/kafka-storage.sh format --standalone -t -c
> config/kraft/controller.properties{code}
> However the above command will fail with a less fortunate cluster id like
> -{{{}Yh6XyBIQ9CeAlMwJ8f7Hg{}}}, eg.:
> {noformat}
> bin/kafka-storage.sh format --standalone -t -Yh6XyBIQ9CeAlMwJ8f7Hg -c
> config/server.properties
> 25/12/12 09:24:54 INFO utils.Log4jControllerRegistration$: [main]:
> Registered `kafka:type=kafka.Log4jController` MBean
> usage: kafka-storage format [-h] --config CONFIG --cluster-id CLUSTER_ID
> [--add-scram ADD_SCRAM] [--ignore-formatted] [--release-version
> RELEASE_VERSION] [--feature FEATURE] [--standalone |
> --no-initial-controllers | --initial-controllers
> INITIAL_CONTROLLERS]
> kafka-storage: error: argument --cluster-id/-t: expected one argument
> {noformat}
> A similar problem came up with KRaft which was addressed in KAFKA-13741. In
> our case the cluster id is already specified, there is no way to change it. I
> was able to come up with a simple solution by using the full name of the
> argument like "--cluster-id=" instead of the shorthand "-t
> ". Full example:
> {code:bash}
> bin/kafka-storage.sh format --cluster-id=-Yh6XyBIQ9CeAlMwJ8f7Hg -c
> config/kraft/controller.properties{code}
> I would propose to change the documentation based on my findings so we will
> be able to cover also ZooKeeper based cluster ids with a leading dash.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (KAFKA-19988) KRaft migration doc should account for ZK cluster id with a leading dash
[
https://issues.apache.org/jira/browse/KAFKA-19988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18044665#comment-18044665
]
Chia-Ping Tsai commented on KAFKA-19988:
[~harmadasg] Will you have a chance to prepare this patch for 3.9.2 release?
> KRaft migration doc should account for ZK cluster id with a leading dash
>
>
> Key: KAFKA-19988
> URL: https://issues.apache.org/jira/browse/KAFKA-19988
> Project: Kafka
> Issue Type: Bug
> Components: docs, documentation, kraft, migration
>Affects Versions: 3.9.1
>Reporter: Gergely Harmadás
>Assignee: Gergely Harmadás
>Priority: Minor
> Fix For: 3.9.2
>
>
> When preparing for the migration, there is a small chance that the retrieved
> cluster id from ZooKeeper contains a leading dash. Currently the 3.9
> documentation specifies the following during the step "Provisioning the KRaft
> controller quorum":
> {code:bash}
> # Save the previously retrieved cluster ID from ZooKeeper in a variable
> called zk-cluster-id
> $ bin/kafka-storage.sh format --standalone -t -c
> config/kraft/controller.properties{code}
> However the above command will fail with a less fortunate cluster id like
> -{{{}Yh6XyBIQ9CeAlMwJ8f7Hg{}}}, eg.:
> {noformat}
> bin/kafka-storage.sh format --standalone -t -Yh6XyBIQ9CeAlMwJ8f7Hg -c
> config/server.properties
> 25/12/12 09:24:54 INFO utils.Log4jControllerRegistration$: [main]:
> Registered `kafka:type=kafka.Log4jController` MBean
> usage: kafka-storage format [-h] --config CONFIG --cluster-id CLUSTER_ID
> [--add-scram ADD_SCRAM] [--ignore-formatted] [--release-version
> RELEASE_VERSION] [--feature FEATURE] [--standalone |
> --no-initial-controllers | --initial-controllers
> INITIAL_CONTROLLERS]
> kafka-storage: error: argument --cluster-id/-t: expected one argument
> {noformat}
> A similar problem came up with KRaft which was addressed in KAFKA-13741. In
> our case the cluster id is already specified, there is no way to change it. I
> was able to come up with a simple solution by using the full name of the
> argument like "--cluster-id=" instead of the shorthand "-t
> ". Full example:
> {code:bash}
> bin/kafka-storage.sh format --cluster-id=-Yh6XyBIQ9CeAlMwJ8f7Hg -c
> config/kraft/controller.properties{code}
> I would propose to change the documentation based on my findings so we will
> be able to cover also ZooKeeper based cluster ids with a leading dash.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
