influxdb3 manage cleanup-parquet

Use influxdb3 manage cleanup-parquet to permanently remove Parquet-era data that a completed storage engine upgrade (Parquet-to-PachaTree) left behind. Any node in the cluster accepts the request, but the compactor node executes the cleanup.

This deletes data permanently

  • Parquet files superseded by the PachaTree migration are deleted.
  • The operation is irreversible.
  • After cleanup, influxdb3 manage downgrade-to-parquet is no longer possible.

Run with --dry-run first to see what a real cleanup would delete.

Usage

influxdb3 manage cleanup-parquet [OPTIONS]

Options

OptionDescriptionDefaultEnvironment variable
--dry-runReport what would be deleted without deleting anything
--yesSkip the confirmation prompt. Conflicts with --dry-run
--waitPoll every 5 seconds until the cleanup completes or fails. Exits non-zero on failure
--status-onlyPrint the status of the current or last cleanup, then exit. Conflicts with --dry-run, --yes, and --wait
-H--host <HOST_URL>InfluxDB 3 Enterprise server URLhttp://127.0.0.1:8181INFLUXDB3_HOST_URL
--token <AUTH_TOKEN>Authentication tokenINFLUXDB3_AUTH_TOKEN
--tls-ca <CA_CERT>Path to a custom TLS certificate authorityINFLUXDB3_TLS_CA
--tls-no-verifyDisable TLS certificate verificationINFLUXDB3_TLS_NO_VERIFY
-h--helpPrint help information

Examples

Preview what a cleanup would delete

influxdb3 manage cleanup-parquet \
  --host http://localhost:8181 \
  --token 
AUTH_TOKEN
\
--dry-run

Run a cleanup and wait for it to finish

influxdb3 manage cleanup-parquet \
  --host http://localhost:8181 \
  --token 
AUTH_TOKEN
\
--yes \ --wait

Check the status of the current or last cleanup

influxdb3 manage cleanup-parquet \
  --host http://localhost:8181 \
  --token 
AUTH_TOKEN
\
--status-only

Was this page helpful?

Thank you for your feedback!