From 9b6d91efb8151a3f9cc9e4d93f202b73f4e05b03 Mon Sep 17 00:00:00 2001 From: Gunnar Aasen Date: Tue, 26 Mar 2024 09:43:50 -0700 Subject: [PATCH 1/4] Update download links for OSSv2 --- content/influxdb/v2/install/_index.md | 26 +++++++++---------- .../v2/reference/cli/influx/_index.md | 12 ++++----- content/influxdb/v2/tools/influx-cli.md | 14 +++++----- .../influxdb-templates/stacks/save-time.md | 2 +- 4 files changed, 27 insertions(+), 27 deletions(-) diff --git a/content/influxdb/v2/install/_index.md b/content/influxdb/v2/install/_index.md index a94d24c11..08d11852b 100644 --- a/content/influxdb/v2/install/_index.md +++ b/content/influxdb/v2/install/_index.md @@ -74,11 +74,11 @@ For information about using the `influx` CLI, see the 1. In your browser or your terminal, download the InfluxDB package. - InfluxDB v2 (macOS) + InfluxDB v2 (macOS) ```sh # Download using cURL - curl -O https://dl.influxdata.com/influxdb/releases/influxdb2-{{< latest-patch >}}_darwin_amd64.tar.gz \ + curl -O https://download.influxdata.com/influxdb/releases/influxdb2-{{< latest-patch >}}_darwin_amd64.tar.gz \ --output-dir ~/Downloads ``` @@ -165,7 +165,7 @@ If `gpg` is not available, see the [GnuPG homepage](https://gnupg.org/download/) and then use `gpg` to verify the download signature--for example: ```sh - curl -s https://dl.influxdata.com/influxdb/releases/influxdb2-{{< latest-patch >}}_darwin_amd64.tar.gz.asc \ + curl -s https://download.influxdata.com/influxdb/releases/influxdb2-{{< latest-patch >}}_darwin_amd64.tar.gz.asc \ | gpg --verify - ~/Downloads/influxdb2-{{< latest-patch >}}_darwin_amd64.tar.gz \ 2>&1 | grep 'InfluxData Package Signing Key ' ``` @@ -218,25 +218,25 @@ _You'll install the `influx CLI` in a [later step](#download-and-install-the-inf ```sh # Ubuntu/Debian AMD64 - curl -O https://dl.influxdata.com/influxdb/releases/influxdb2_{{< latest-patch >}}-1_amd64.deb + curl -O https://download.influxdata.com/influxdb/releases/influxdb2_{{< latest-patch >}}-1_amd64.deb sudo dpkg -i influxdb2_{{< latest-patch >}}-1_amd64.deb ``` ```sh # Ubuntu/Debian ARM64 - curl -O https://dl.influxdata.com/influxdb/releases/influxdb2_{{< latest-patch >}}-1_arm64.deb + curl -O https://download.influxdata.com/influxdb/releases/influxdb2_{{< latest-patch >}}-1_arm64.deb sudo dpkg -i influxdb2_{{< latest-patch >}}-1_arm64.deb ``` ```sh # Red Hat/CentOS/Fedora x86-64 (x64, AMD64) - curl -O https://dl.influxdata.com/influxdb/releases/influxdb2-{{< latest-patch >}}-1.x86_64.rpm + curl -O https://download.influxdata.com/influxdb/releases/influxdb2-{{< latest-patch >}}-1.x86_64.rpm sudo yum localinstall influxdb2-{{< latest-patch >}}-1.x86_64.rpm ``` ```sh # Red Hat/CentOS/Fedora AArch64 (ARMv8-A) - curl -O https://dl.influxdata.com/influxdb/releases/influxdb2-{{< latest-patch >}}-1.aarch64.rpm + curl -O https://download.influxdata.com/influxdb/releases/influxdb2-{{< latest-patch >}}-1.aarch64.rpm sudo yum localinstall influxdb2-{{< latest-patch >}}-1.aarch64.rpm ``` @@ -292,17 +292,17 @@ You can use systemd to customize [InfluxDB configuration options](/influxdb/v2/r 1. In your browser or your terminal, download the InfluxDB binary for your system architecture (AMD64 or ARM). - InfluxDB v2 (amd64) - InfluxDB v2 (arm) + InfluxDB v2 (amd64) + InfluxDB v2 (arm) ```sh # Use curl to download the amd64 binary. - curl -O https://dl.influxdata.com/influxdb/releases/influxdb2-{{< latest-patch >}}_linux_amd64.tar.gz + curl -O https://download.influxdata.com/influxdb/releases/influxdb2-{{< latest-patch >}}_linux_amd64.tar.gz ``` ```sh # Use curl to download the arm64 binary. - curl -O https://dl.influxdata.com/influxdb/releases/influxdb2-{{< latest-patch >}}_linux_arm64.tar.gz + curl -O https://download.influxdata.com/influxdb/releases/influxdb2-{{< latest-patch >}}_linux_arm64.tar.gz ``` 2. Extract the downloaded binary. @@ -390,7 +390,7 @@ To install `gpg`, see the [GnuPG installation instructions](https://gnupg.org/do and then use `gpg` to verify the download signature--for example: ```sh - curl -s https://dl.influxdata.com/influxdb/releases/influxdb2-{{< latest-patch >}}_linux_amd64.tar.gz.asc \ + curl -s https://download.influxdata.com/influxdb/releases/influxdb2-{{< latest-patch >}}_linux_amd64.tar.gz.asc \ | gpg --verify - influxdb2-{{< latest-patch >}}_linux_amd64.tar.gz \ 2>&1 | grep 'InfluxData Package Signing Key ' ``` @@ -441,7 +441,7 @@ _You'll install the `influx CLI` in a [later step](#download-and-install-the-inf {{% /note %}} -InfluxDB v2 (Windows) +InfluxDB v2 (Windows) Expand the downloaded archive into `C:\Program Files\InfluxData\` and rename the files if desired. diff --git a/content/influxdb/v2/reference/cli/influx/_index.md b/content/influxdb/v2/reference/cli/influx/_index.md index c48f787d5..30fcce5a1 100644 --- a/content/influxdb/v2/reference/cli/influx/_index.md +++ b/content/influxdb/v2/reference/cli/influx/_index.md @@ -91,7 +91,7 @@ brew list | grep influxdb-cli 1. **Download the `influx` CLI package.** - influx CLI v{{< latest-patch cli=true >}} (macOS) + influx CLI v{{< latest-patch cli=true >}} (macOS) 2. **Unpackage the downloaded package.** @@ -140,17 +140,17 @@ brew list | grep influxdb-cli #### Download from your browser - influx CLI v{{< latest-patch cli=true >}} (amd64) - influx CLI v{{< latest-patch cli=true >}} (arm) + influx CLI v{{< latest-patch cli=true >}} (amd64) + influx CLI v{{< latest-patch cli=true >}} (arm) #### Download from the command line ```sh # amd64 - wget https://dl.influxdata.com/influxdb/releases/influxdb2-client-{{< latest-patch cli=true >}}-linux-amd64.tar.gz + wget https://download.influxdata.com/influxdb/releases/influxdb2-client-{{< latest-patch cli=true >}}-linux-amd64.tar.gz # arm - wget https://dl.influxdata.com/influxdb/releases/influxdb2-client-{{< latest-patch cli=true >}}-linux-arm64.tar.gz + wget https://download.influxdata.com/influxdb/releases/influxdb2-client-{{< latest-patch cli=true >}}-linux-arm64.tar.gz ``` 4. **Unpackage the downloaded package.** @@ -191,7 +191,7 @@ Command Prompt is not fully compatible. 1. **Download the `influx` CLI package.** - influx CLI v{{< latest-patch cli=true >}} (Windows) + influx CLI v{{< latest-patch cli=true >}} (Windows) 2. **Expand the downloaded archive.** diff --git a/content/influxdb/v2/tools/influx-cli.md b/content/influxdb/v2/tools/influx-cli.md index ef50b10c4..853a41daf 100644 --- a/content/influxdb/v2/tools/influx-cli.md +++ b/content/influxdb/v2/tools/influx-cli.md @@ -81,12 +81,12 @@ brew list | grep influxdb-cli #### Download from your browser - influx CLI v{{< latest-patch cli=true >}} (macOS) + influx CLI v{{< latest-patch cli=true >}} (macOS) #### Download from the command line ```sh - curl -O https://dl.influxdata.com/influxdb/releases/influxdb2-client-{{< latest-patch cli=true >}}-darwin-amd64.tar.gz \ + curl -O https://download.influxdata.com/influxdb/releases/influxdb2-client-{{< latest-patch cli=true >}}-darwin-amd64.tar.gz \ --output-dir ~/Downloads ``` @@ -153,19 +153,19 @@ brew list | grep influxdb-cli #### Download from your browser - influx CLI v{{< latest-patch cli=true >}} (amd64) - influx CLI v{{< latest-patch cli=true >}} (arm) + influx CLI v{{< latest-patch cli=true >}} (amd64) + influx CLI v{{< latest-patch cli=true >}} (arm) #### Download from the command line ```sh # amd64 - wget https://dl.influxdata.com/influxdb/releases/influxdb2-client-{{< latest-patch cli=true >}}-linux-amd64.tar.gz + wget https://download.influxdata.com/influxdb/releases/influxdb2-client-{{< latest-patch cli=true >}}-linux-amd64.tar.gz ``` ```sh # arm - wget https://dl.influxdata.com/influxdb/releases/influxdb2-client-{{< latest-patch cli=true >}}-linux-arm64.tar.gz + wget https://download.influxdata.com/influxdb/releases/influxdb2-client-{{< latest-patch cli=true >}}-linux-arm64.tar.gz ``` 2. Unpackage the downloaded binary. @@ -215,7 +215,7 @@ Command Prompt is not fully compatible. 1. Download the `influx` CLI package. - influx CLI v{{< latest-patch cli=true >}} (Windows) + influx CLI v{{< latest-patch cli=true >}} (Windows) 2. Expand the downloaded archive. diff --git a/content/influxdb/v2/tools/influxdb-templates/stacks/save-time.md b/content/influxdb/v2/tools/influxdb-templates/stacks/save-time.md index de04a5361..e22a97537 100644 --- a/content/influxdb/v2/tools/influxdb-templates/stacks/save-time.md +++ b/content/influxdb/v2/tools/influxdb-templates/stacks/save-time.md @@ -132,7 +132,7 @@ jobs: GITHUB_BRANCH: ${{ github.ref }} run: | cd /tmp - wget https://dl.influxdata.com/platform/nightlies/influx_nightly_linux_amd64.tar.gz + wget https://download.influxdata.com/platform/nightlies/influx_nightly_linux_amd64.tar.gz tar xvfz influx_nightly_linux_amd64.tar.gz sudo cp influx_nightly_linux_amd64/influx /usr/local/bin/ cd $GITHUB_WORKSPACE From b6d77062fc4bce4e54b04866d60a2e6c720b72f2 Mon Sep 17 00:00:00 2001 From: Jason Stirnaman Date: Tue, 16 Apr 2024 09:27:43 -0500 Subject: [PATCH 2/4] fix(v2): Missing description for Letsencypted certificates (#5425) Fixes #5422 --- .../influxdb/v2/admin/security/enable-tls.md | 99 ++++++++++++------- 1 file changed, 61 insertions(+), 38 deletions(-) diff --git a/content/influxdb/v2/admin/security/enable-tls.md b/content/influxdb/v2/admin/security/enable-tls.md index 65e3328b8..a7a854166 100644 --- a/content/influxdb/v2/admin/security/enable-tls.md +++ b/content/influxdb/v2/admin/security/enable-tls.md @@ -18,7 +18,12 @@ When configured with a signed certificate, TLS also allows clients to verify the To set up TLS over HTTPS, do the following: - [Obtain requirements](#obtain-requirements) + - [Single domain certificates signed by a Certificate Authority (CA)](#single-domain-certificates-signed-by-a-certificate-authority-ca) + - [Wildcard certificates signed by a Certificate Authority](#wildcard-certificates-signed-by-a-certificate-authority) + - [Self-signed certificates](#self-signed-certificates) - [Configure InfluxDB to use TLS](#configure-influxdb-to-use-tls) +- [Connect Telegraf to a secured InfluxDB instance](#connect-telegraf-to-a-secured-influxdb-instance) + - [Example configuration](#example-configuration) {{% warn %}} InfluxData **strongly recommends** enabling HTTPS, especially if you plan on sending requests to InfluxDB over a network. @@ -29,24 +34,24 @@ InfluxData **strongly recommends** enabling HTTPS, especially if you plan on sen To enable HTTPS with InfluxDB, you need a Transport Layer Security (TLS) certificate, also known as a Secured Sockets Layer (SSL) certificate. InfluxDB supports three types of TLS certificates: -* **Single domain certificates signed by a [Certificate Authority](https://en.wikipedia.org/wiki/Certificate_authority)** +### Single domain certificates signed by a Certificate Authority (CA) - Single domain certificates provide cryptographic security to HTTPS requests and allow clients to verify the identity of the InfluxDB server. - These certificates are signed and issued by a trusted, third-party Certificate Authority (CA). - With this certificate option, every InfluxDB instance requires a unique single domain certificate. +Single domain certificates provide cryptographic security to HTTPS requests and allow clients to verify the identity of the InfluxDB server. +These certificates are signed and issued by a trusted, third-party [Certificate Authority (CA)](https://en.wikipedia.org/wiki/Certificate_authority). +With this certificate option, every InfluxDB instance requires a unique single domain certificate. -* **Wildcard certificates signed by a Certificate Authority** +### Wildcard certificates signed by a Certificate Authority - Wildcard certificates provide cryptographic security to HTTPS requests and allow clients to verify the identity of the InfluxDB server. - Wildcard certificates can be used across multiple InfluxDB instances on different servers. +Wildcard certificates provide cryptographic security to HTTPS requests and allow clients to verify the identity of the InfluxDB server. +Wildcard certificates can be used across multiple InfluxDB instances on different servers. -* **Self-signed certificates** +### Self-signed certificates - Self-signed certificates are _not_ signed by a trusted, third-party CA. - Unlike CA-signed certificates, self-signed certificates only provide cryptographic security to HTTPS requests. - They do not allow clients to verify the identity of the InfluxDB server. - With this certificate option, every InfluxDB instance requires a unique self-signed certificate. - You can generate a self-signed certificate on your own machine. +Self-signed certificates are _not_ signed by a trusted, third-party CA. +Unlike CA-signed certificates, self-signed certificates only provide cryptographic security to HTTPS requests. +They do not allow clients to verify the identity of the InfluxDB server. +With this certificate option, every InfluxDB instance requires a unique self-signed certificate. +You can generate a self-signed certificate on your own machine. @@ -55,41 +60,55 @@ InfluxDB supports three types of TLS certificates: 1. **Download or generate certificate files** - If using a certificate provided by a CA, follow their instructions to download the certificate files. + If using a [certificate signed by a CA](#single-domain-certificates-signed-by-a-certificate-authority-ca), follow their instructions to download and install the certificate files. + Note the location where certificate files are installed, and then continue to [set certificate file permissions](#set-certificate-file-permissions). - If using a self-signed certificate, use the `openssl` utility to create a certificate. + {{% note %}} + #### Where are my certificates? - The following command generates a private key file (.key) and a self-signed certificate file (.crt) with required permissions - and saves them to `/etc/ssl/`. - (Other paths will also work.) + The location of your certificate files depends on your system, domain, and certificate authority. + + For example, if [Let's Encrypt](https://letsencrypt.org/) is your CA and you use [certbot](https://certbot.eff.org/) to install certificates, the default location is + `/etc/letsencrypt/live/$domain`. For more information about Let's Encrypt certificate paths, see [Where are my certificates?](https://eff-certbot.readthedocs.io/en/latest/using.html#where-are-my-certificates) + {{% /note %}} + + To generate [self-signed certificates](#self-signed-certificates), use the `openssl` command on your system. + + The following example shows how to generate certificates located in `/etc/ssl`. Files remain valid for the specified `NUMBER_OF_DAYS`. + The `openssl` command prompts you for optional fields that you can fill out or leave blank; both actions generate valid certificate files. - ```sh + ```bash sudo openssl req -x509 -nodes -newkey rsa:2048 \ -keyout /etc/ssl/influxdb-selfsigned.key \ -out /etc/ssl/influxdb-selfsigned.crt \ -days ``` - The command will prompt you for more information. - You can choose to fill out these fields or leave them blank; both actions generate valid certificate files. +1. **Set certificate file permissions** + -2. **Set certificate file permissions** - - The user running InfluxDB must have read permissions on the TLS certificate. + The user running InfluxDB must have read permissions on the TLS certificate files. {{% note %}}You may opt to set up multiple users, groups, and permissions. Ultimately, make sure all users running InfluxDB have read permissions for the TLS certificate. {{% /note %}} - Run the following command to give InfluxDB read and write permissions on the certificate files. + In your terminal, run `chmod` to set permissions on your installed certificate files--for example: ```bash - sudo chmod 644 /etc/ssl/ - sudo chmod 600 /etc/ssl/ + sudo chmod 644 + sudo chmod 600 ``` -3. **Run `influxd` with TLS flags** + The following example shows how to set read permissions on the self-signed certificate files saved in `/etc/ssl`: + + ```bash + sudo chmod 644 /etc/ssl/influxdb-selfsigned.crt + sudo chmod 600 /etc/ssl/influxdb-selfsigned.key + ``` + +2. **Run `influxd` with TLS flags** Start InfluxDB with TLS command line flags: @@ -99,24 +118,28 @@ InfluxDB supports three types of TLS certificates: --tls-key="" ``` -4. **Verify TLS connection** +3. **Verify TLS connection** + To test your certificates, access InfluxDB using the `https://` protocol--for example, using cURL: - Ensure you can connect over HTTPS by running - - ``` - curl -v https://localhost:8086/api/v2/ping + ```bash + curl --verbose https://localhost:8086/api/v2/ping ``` - If using a self-signed certificate, use the `-k` flag to skip certificate verification: + If using a self-signed certificate, skip certificate verification--for example, in a cURL command, + pass the `-k, --insecure` flag: - ``` - curl -vk https://localhost:8086/api/v2/ping + ```bash + curl --verbose --insecure https://localhost:8086/api/v2/ping ``` - With this command, you should see output confirming a succussful TLS handshake. + If successful, the `curl --verbose` output shows a TLS handshake--for example: -You can further configure TLS settings using + ```bash + * [CONN-0-0][CF-SSL] TLSv1.3 (IN), TLS handshake + ``` + +You can further configure TLS settings using [`tls-min-version`](/influxdb/v2/reference/config-options/#tls-min-version) and [`tls-strict-ciphers`](/influxdb/v2/reference/config-options/#tls-strict-ciphers). From caca0a71b6297fbc454a9e28552931b9cc370680 Mon Sep 17 00:00:00 2001 From: Jack <56563911+jdockerty@users.noreply.github.com> Date: Tue, 16 Apr 2024 16:00:46 +0100 Subject: [PATCH 3/4] docs(clustered): data ingest lifecycle (#5369) * docs: object versioning, lifecycle rule best practices * docs: trim whitespace * docs: include appinstance configuration * docs: update gc env var wording Co-authored-by: Fraser Savage * chore: use suggested wording Co-authored-by: Dom * docs: dedicated mention of versioning recommendation The versioning really depends on an organisation's backups/DR strategy. I've pulled this more inline with how the lifecylce of the ingested data can be managed through the garbage-collector. * docs: wording * docs: use scenario wording suggestion Co-authored-by: Dom * docs: use suggested extension for gc service Co-authored-by: Dom * docs: no versioning suggestion Co-authored-by: Dom * docs: hint requirements for retention Co-authored-by: Dom * docs: mention object store sizing with lower cutoff * docs: add warning for 3h cutoff * suggested edits to the clustered ingest lifecycle guide (#5427) * docs: use suggestion for configurable cutoff floor Co-authored-by: Scott Anderson --------- Co-authored-by: Fraser Savage Co-authored-by: Dom Co-authored-by: Scott Anderson --- .../best-practices/data-lifecycle.md | 187 ++++++++++++++++++ 1 file changed, 187 insertions(+) create mode 100644 content/influxdb/clustered/write-data/best-practices/data-lifecycle.md diff --git a/content/influxdb/clustered/write-data/best-practices/data-lifecycle.md b/content/influxdb/clustered/write-data/best-practices/data-lifecycle.md new file mode 100644 index 000000000..91420dbd5 --- /dev/null +++ b/content/influxdb/clustered/write-data/best-practices/data-lifecycle.md @@ -0,0 +1,187 @@ +--- +title: Data ingest lifecycle best practices +description: > + Best practices for managing the lifecycle of data ingested into InfluxDB. +menu: + influxdb_clustered: + name: Data ingest lifecycle + parent: write-best-practices +weight: 204 +--- + +Data ingested into InfluxDB must conform to the retention period of the database +in which it is stored. +Points with timestamps outside of the retention period are no longer queryable, +but may still have references maintained in +[Object storage](/influxdb/clustered/reference/internals/storage-engine/#object-store) +or the [Catalog](/influxdb/clustered/reference/internals/storage-engine/#catalog), +resulting in an increase in operational overhead and cost. +To reduce these factors, it is important to manage the lifecycle of ingested data. + +Use the following best practices to manage the lifecycle of data in your +InfluxDB cluster: + +- [Use appropriate retention periods](#use-appropriate-retention-periods) +- [Tune garbage collection](#tune-garbage-collection) + +## Use appropriate retention periods + +When [creating or updating a database](/influxdb/clustered/admin/databases/#create-a-database), +use a retention period that is appropriate for your requirements. +Storing data longer than is required adds unnecessary operational cost to your +InfluxDB cluster. + +## Tune garbage collection + +Once data falls outside of a database's retention period, the garbage collection +service can remove all artifacts associated with the data from the Catalog and Object store. +Tune the garbage collector cutoff period to ensure that data is removed in a timely manner. + +Use the following environment variables to tune the garbage collector: + +- `INFLUXDB_IOX_GC_OBJECTSTORE_CUTOFF`: the age at which Parquet files not + referenced in the Catalog become eligible for deletion from Object storage. + The default is `30d`. +- `INFLUXDB_IOX_GC_PARQUETFILE_CUTOFF`: how long to retain rows in the Catalog + that reference Parquet files marked for deletion. The default is `30d`. + +{{% warn %}} +To ensure there is a grace period before files and references are removed, the +minimum garbage collector (GC) object store and Parquet file cutoff time is +three hours (`3h`). +{{% /warn %}} + +We recommend setting these options to a value aligned to your organization's +backup and recovery strategy. +For example, a value of `6h` (6 hours) would be appropriate for running a lean +Catalog that only maintains references to recent data and does not require backups. + +### Use case examples + +Use the following scenarios as a guide for different use cases: + +{{< expand-wrapper >}} +{{% expand "Leading edge data with no backups" %}} + +When only the most recent data is important and backups are not required, use a +very low cutoff point for the garbage collector. +Using a low value means that the garbage collection service will promptly delete +files from the Object store and remove rows associated rows from the Catalog. +This results in a lean Catalog with lower operational overhead and less files +in the Object store. + +```yaml +apiVersion: kubecfg.dev/v1alpha1 +kind: AppInstance +metadata: + name: influxdb + namespace: influxdb +spec: + package: + # ... + spec: + components: + garbage-collector: + template: + containers: + iox: + env: + INFLUXDB_IOX_GC_OBJECTSTORE_CUTOFF: '6h' + INFLUXDB_IOX_GC_PARQUETFILE_CUTOFF: '6h' +``` + +{{% /expand %}} + +{{% expand "Custom backup window _with_ object storage versioning" %}} + +When backups are required and you are leveraging the versioning capability of your +Object store (provided by your object store provider), use a low cutoff point +for the garbage collector service. Your object versioning policy ensures expired +files are kept for the specified backup window time. + +Object versioning maintains Parquet files in Objects storage after data expires, +but allows the Catalog to remove references to the Parquet files. +Non-current objects should be configured to be expired as soon as possible, but +retained long enough to satisfy your organization's backup policy. + +The following illustrates an [AWS S3 lifecycle rule](https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lifecycle-mgmt.html) +that expires non-current objects after 90 days: + +```json +{ + "Rules": [ + { + "ID": "my-lifecycle-rule", + "Filter": { + "Prefix": "" + }, + "Status": "Enabled", + "NoncurrentVersionExpiration": { + "NoncurrentDays": 90 + } + } + ] +} +``` + +Set the `garbage-collector` to use low cutoff points. +The following example uses `6h`: + +```yaml +apiVersion: kubecfg.dev/v1alpha1 +kind: AppInstance +metadata: + name: influxdb + namespace: influxdb +spec: + package: + # ... + spec: + components: + garbage-collector: + template: + containers: + iox: + env: + INFLUXDB_IOX_GC_OBJECTSTORE_CUTOFF: '6h' + INFLUXDB_IOX_GC_PARQUETFILE_CUTOFF: '6h' +``` +{{% /expand %}} + +{{% expand "Custom backup window _without_ object storage versioning" %}} + +If you cannot make use of object versioning policies but still requires a backup +window, configure the garbage collector to retain Parquet files for as long as +your backup period requires. + +This will likely result in higher operational costs as the Catalog maintains +more references to associated Parquet files and the Parquet files persist for +longer in the Object store. + +{{% note %}} +If possible, we recommend using object versioning. +{{% /note %}} + +The following example sets the garbage collector cutoffs to `100d`: + +```yaml +apiVersion: kubecfg.dev/v1alpha1 +kind: AppInstance +metadata: + name: influxdb + namespace: influxdb +spec: + package: + # ... + spec: + components: + garbage-collector: + template: + containers: + iox: + env: + INFLUXDB_IOX_GC_OBJECTSTORE_CUTOFF: '100d' + INFLUXDB_IOX_GC_PARQUETFILE_CUTOFF: '100d' +``` +{{% /expand %}} +{{< /expand-wrapper >}} From 89f16122789efd2dc635c0b9b0a55e5669a865aa Mon Sep 17 00:00:00 2001 From: Scott Anderson Date: Tue, 16 Apr 2024 15:11:37 -0600 Subject: [PATCH 4/4] influx CLI v2.7.5 (#5430) --- .../v2/reference/release-notes/influx-cli.md | 20 ++++++++++++++++--- data/products.yml | 2 +- 2 files changed, 18 insertions(+), 4 deletions(-) diff --git a/content/influxdb/v2/reference/release-notes/influx-cli.md b/content/influxdb/v2/reference/release-notes/influx-cli.md index fea6bc775..0f08633f2 100644 --- a/content/influxdb/v2/reference/release-notes/influx-cli.md +++ b/content/influxdb/v2/reference/release-notes/influx-cli.md @@ -8,14 +8,28 @@ menu: name: influx CLI --- +## v2.7.5 {date="2024-04-16"} + +### Maintenance + +- Upgrade to Go 1.21.9. + +## v2.7.4 {date="2024-04-05"} + +### Bug fixes + +- Disable password length checks to allow InfluxDB to validate passwords. +- Handle line protocol line-wrapping with `--skipRowOnError`. + ## v2.7.3 {date="2023-04-28"} -### Bug Fixes +### Bug fixes - Correct packaging for RPM and Windows ZIPs. - Properly handle multiple cookies with `--username-password` flag. ### Maintenance + - Upgrade `go` to 1.20.3. ## v2.7.1 {date="2023-04-05"} @@ -24,7 +38,7 @@ menu: - Add new replication field to better show queue synchronization progress. -### Bug Fixes +### Bug fixes - Update the API for deleting secrets so `influx secret delete` command works correctly. - Fix typo in alias of `bucket update` command. @@ -47,7 +61,7 @@ menu: ## v2.6.0 {date="2022-12-15"} -### Bug Fixes +### Bug fixes - When using [`influx task create`](/influxdb/v2/reference/cli/influx/task/create/) to create a new task, only override the `every` task option defined in the Flux diff --git a/data/products.yml b/data/products.yml index b0bf42b02..8456a8251 100644 --- a/data/products.yml +++ b/data/products.yml @@ -24,7 +24,7 @@ influxdb: v2: 2.7.6 v1: 1.8.10 latest_cli: - v2: 2.7.3 + v2: 2.7.5 influxdb_cloud: name: InfluxDB Cloud (TSM)