kubectl confluent kraft log-length

Park the surviving region’s controllers and print each one’s metadata log end offset.

To install the Confluent plugin, see Confluent plugin.

Synopsis

Step 1 of quorum-loss recovery.

Parks every KRaftController pod in the namespace in maintenance mode, then runs ‘kafka-metadata-recovery reconfig log-length’ on each and prints the output verbatim, labeled by pod. The operator reads the offsets and picks the pod with the highest log end offset as the recovery seed.

Parking restarts every controller in the target, so the cluster (–context) and namespace (-n) must both be given explicitly and the action is confirmed before any pod is touched. Pods are left parked so the next step can act on them:

kubectl confluent kraft recover-region –context <ctx> -n <ns> –seed-pod <pod>

Example:

kubectl confluent kraft log-length –context gke_proj_region_rb2 -n rb2

kubectl confluent kraft log-length [flags]

Options

-h, --help                      help for log-length
    --metadata-log-dir string   metadata log dir (parent of __cluster_metadata-0); default: auto-detected from each pod's kafka.properties (log.dirs)
    --timeout duration          overall timeout for parking pods and reading offsets (default 5m0s)
    --yes                       proceed without the interactive confirmation prompt

Options inherited from parent commands

    --as string                      Username to impersonate for the operation. User could be a regular user or a service account in a namespace.
    --as-group stringArray           Group to impersonate for the operation, this flag can be repeated to specify multiple groups.
    --as-uid string                  UID to impersonate for the operation.
    --cache-dir string               Default cache directory (default "$HOME/.kube/cache")
    --certificate-authority string   Path to a cert file for the certificate authority
    --client-certificate string      Path to a client certificate file for TLS
    --client-key string              Path to a client key file for TLS
    --cluster string                 The name of the kubeconfig cluster to use
    --context string                 The name of the kubeconfig context to use
    --disable-compression            If true, opt-out of response compression for all requests to the server
    --insecure-skip-tls-verify       If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure
    --kubeconfig string              Path to the kubeconfig file to use for CLI requests.
-n, --namespace string               If present, the namespace scope for this CLI request
    --request-timeout string         The length of time to wait before giving up on a single server request. Non-zero values should contain a corresponding time unit (e.g. 1s, 2m, 3h). A value of zero means don't timeout requests. (default "0")
-s, --server string                  The address and port of the Kubernetes API server
    --tls-server-name string         Server name to use for server certificate validation. If it is not provided, the hostname used to contact the server is used
    --token string                   Bearer token for authentication to the API server
    --user string                    The name of the kubeconfig user to use

SEE ALSO