THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Code Block |
---|
=== DESCRIBE FEATURES === # Get cluster-wide finalized features, and features supported by a specific broker. # - Use `--bootstrap-server` to provide a broker host:port to which queries should be issued. # - Optionally, provide `--controller` flag directing the tool to issue the query to the # controller (while discovering the controller via the bootstrap server). # This can be useful for debugging purposes. $> kafka-features.sh describe \ --bootstrap-server kafka-broker0.prn1:9071 \ [--controller] { "status": "OK", "supported_features": { "group_coordinator": { "minVersion": 1, "maxVersion": 2 }, "transaction_coordinator": { "minVersion": 0, "maxVersion": 5 }, "consumer_offsets_topic_schema": { "minVersion": 0, "maxVersion": 0 } }, "finalized_features": { "epoch": 0, "group_coordinator": { "version": 1 }, "transaction_coordinator": { "version": 4 } }, "host": "kafka-broker0.prn1", "port": 9071 } === ADD_OR_UPDATE FEATURES === # Add or update a list of cluster-wide finalized features. # - Use `--bootstrap-server` to provide a broker host:port to which MetadataRequest query should be issued. # The MetadataResponse will be used to discover the Controller, to which the actual ADD_OR_UPDATE request is issued. # - Use `--upgrade` to provide a comma-separated list of features and new finalized max version to ADD_OR_UPDATE. # - Use `--force-downgrade` to provide a comma-separated list of features and new finalized max version, with a downgrade allowed for feature versions. This should be used only when required. $> kafka-features.sh update \ --bootstrap-server kafka-broker0.prn1:9071 \ --upgrade group_coordinator:2,my_new_feature:0 \ --force-downgrade transaction_coordinator:3 \ Please confirm before downgrading the following features: 1.transaction_coordinator from v4 (existing) to v3 (new) [Y/n]? Y { "status": "OK", "supported_features": { "group_coordinator": { "minVersion": 1, "maxVersion": 2 }, "transaction_coordinator": { "minVersion": 0, "maxVersion": 5 }, "consumer_offsets_topic_schema": { "minVersion": 0, "maxVersion": 0 } }, "finalized_features": { "epoch": 1, "group_coordinator": { "version": 2 }, "transaction_coordinator": { "version": 3 }, "consumer_offsets_topic_schema": { "version": 0 } }, "host": "kafka-broker0.prn1", "port": 9071 } === DISABLE FEATURES === # Disable a list of cluster-wide finalized features. # - Use `--bootstrap-server` to provide a broker host:port to which MetadataRequest query should be issued. # The MetadataResponse will be used to discover the Controller, to which the actual delete request is issued. # - Use `--features` to provide a comma-separated list of features to be disabled. $> kafka-features.sh disable \ --bootstrap-server kafka-broker0.prn1:9071 \ --features group_coordinator,transaction_coordinator Please confirm disabling of the following features. Note that the latest finalized feature version value for the disabled feature, will be lost forever: 1. group_coordinator 2. transaction_coordinator [Y/n] Y { "status": "OK", "supported_features": { "group_coordinator": { "minVersion": 1, "maxVersion": 2 }, "transaction_coordinator": { "minVersion": 0, "maxVersion": 5 }, "consumer_offsets_topic_schema": { "minVersion": 0, "maxVersion": 0 } }, "finalized_features": { "epoch": 2, "consumer_offsets_topic_schema": { "version": 0 } }, "host": "kafka-broker0.prn1", "port": 9071 } |
...