InfluxDB Enterprise 1.9.6 (influxdata#3650)

* Document meta-node HTTP access logging (influxdata#3486) * Document `influxd-ctl backup -estimate` flag (influxdata#3484) Closes influxdata#3480 * add new option for SIGTERM (influxdata#3496) * Document `-meta-only-overwrite-force` restore flag for Enterprise (influxdata#3487) * Document `max-concurrent-deletes` option (influxdata#3697) * Update Enterprise cluster metrics: add `openConnections` (influxdata#3703) Closes influxdata#3653 * Remove marketplace offerings from Enterprise * Use bytes in certain Enterprise config examples (influxdata#3743) * InfluxDB Enterprise 1.9: remove default values from configuration headings (influxdata#3759) Co-authored-by: kelseiv <[email protected]> Co-authored-by: Scott Anderson <[email protected]> Co-authored-by: Sam Arnold <[email protected]>
beefcakefu · Feb 17, 2022 · 7793554 · 7793554
1 parent 4d2b8d1
commit 7793554
Show file tree

Hide file tree

Showing 32 changed files with 711 additions and 579 deletions.
diff --git a/...t/enterprise_influxdb/v1.8/install-and-deploy/production_installation/_index.md b/...t/enterprise_influxdb/v1.8/install-and-deploy/production_installation/_index.md
@@ -15,5 +15,3 @@ Complete the following steps to install an InfluxDB Enterprise cluster in your o
 1. [Install InfluxDB Enterprise meta nodes](/enterprise_influxdb/v1.8/install-and-deploy/production_installation/meta_node_installation/)
 2. [Install InfluxDB data nodes](/enterprise_influxdb/v1.8/install-and-deploy/production_installation/data_node_installation/)
 3. [Install Chronograf](/enterprise_influxdb/v1.8/install-and-deploy/production_installation/chrono_install/)
-
-> **Note:** If you're looking for cloud infrastructure and services, check out how to deploy InfluxDB Enterprise (production-ready) on a cloud provider of your choice: [Azure](/enterprise_influxdb/v1.8/install-and-deploy/deploying/azure/), [GCP](/enterprise_influxdb/v1.8/install-and-deploy/deploying/google-cloud-platform/), or [AWS](/enterprise_influxdb/v1.8/install-and-deploy/deploying/aws/).
diff --git a/content/enterprise_influxdb/v1.9/about-the-project/release-notes-changelog.md b/content/enterprise_influxdb/v1.9/about-the-project/release-notes-changelog.md
@@ -9,6 +9,52 @@ menu:
     parent: About the project
 ---
 
+## 1.9.6 [2022-02-16]
+
+{{% note %}} InfluxDB Enterprise offerings are no longer available on AWS, Azure, and GCP marketplaces. Please [contact Sales](https://www.influxdata.com/contact-sales/) to request an license key to [install InfluxDB Enterprise in your own environment](/enterprise_influxdb/v1.9/introduction/installation/).
+{{% /note %}}
+
+### Features
+
+#### Backup enhancements
+
+- **Revert damaged meta nodes to a previous state**: Add the `-meta-only-overwrite-force` option to [`influxd-ctl restore`](/enterprise_influxdb/v1.9/tools/influxd-ctl/#restore) to revert damaged meta nodes in an existing cluster to a previous state when restoring an InfluxDB Enterprise database.
+
+- **Estimate the size of a backup** (full or incremental) and provide progress messages. Add `-estimate` option to [`influxd-ctl backup`](/enterprise_influxdb/v1.9/tools/influxd-ctl/#backup) to estimate the size of a backup (full or incremental) and provide progress messages. Prints the number of files to back up, the percentage of bytes transferred for each file (organized by shard), and the estimated time remaining to complete the backup.
+
+#### Logging enhancements
+
+- **Log active queries when a process is terminated**: Add the [`termination-query-log`](/enterprise_influxdb/v1.9/administration/configure/config-data-nodes/#termination-query-log--false) configuration option. When set to `true` all running queries are printed to the log when a data node process receives a `SIGTERM` (for example, a Kubernetes process exceeds the container memory limit or the process is terminated).
+
+- **Log details of HTTP calls to meta nodes**. When [`cluster-tracing`](/enterprise_influxdb/v1.9/administration/configure/config-meta-nodes/#cluster-tracing--false) is enabled, all API calls to meta nodes are now logged with details providing an audit trail including IP address of caller, specific API being invoked, action being invoked, and more.
+
+### Maintenance updates
+
+- Update to [Flux v0.140](/flux/v0.x/release-notes/#v01400-2021-11-22).
+- Upgrade to Go 1.17.
+- Upgrade `protobuf` library.
+
+### Bug fixes
+
+#### Data
+
+-  Adjust shard start and end times to avoid overlaps in existing shards. This resolves issues with existing shards (truncated or not) that have a different shard duration than the current default.
+- `DROP SHARD` now successfully ignores "shard not found errors."
+
+#### Errors
+
+- Fix panic when running `influxd config`.
+- Ensure `influxd-ctl entropy` commands use the correct TLS settings.
+
+#### Profiling
+
+- Resolve issue to enable [mutex profiling](/enterprise_influxdb/v1.9/tools/api/#debugpprof-http-endpoint).
+
+#### influx-ctl updates
+
+- Improve [`influxd-ctl join`](/enterprise_influxdb/v1.9/tools/influxd-ctl/#join) robustness and provide better error messages on failure.
+- Add user friendly error message when accessing a TLS-enabled server without TLS enabled on client.
+
 ## v1.9.5 [2021-10-11]
 
 {{% note %}}
@@ -67,7 +113,7 @@ Changes below are included in InfluxDB Enterprise 1.9.5.
 - Add [configurable password hashing](/enterprise_influxdb/v1.9/administration/configure-password-hashing/) with `bcrypt` and `pbkdf2` support.
 - Add retry with exponential back-off to anti-entropy repair.
 - Add logging to compaction.
-- Add [`total-buffer-bytes`](/enterprise_influxdb/v1.9/administration/config-data-nodes/#total-buffer-bytes--0) configuration parameter to subscriptions.
+- Add [`total-buffer-bytes`](/enterprise_influxdb/v1.9/administration/configure/config-data-nodes/#total-buffer-bytes) configuration parameter to subscriptions.
   This option is intended to help alleviate out-of-memory errors.
 - Update to [Flux v0.120.1.](/influxdb/v2.0/reference/release-notes/flux/#v01201-2021-07-06)
 
@@ -99,15 +145,15 @@ in that there is no corresponding InfluxDB OSS release.
   These queries now return a `cardinality estimation` column header where before they returned `count`.
 - Improve diagnostics for license problems.
   Add [license expiration date](/enterprise_influxdb/v1.9/features/clustering-features/#entitlements) to `debug/vars` metrics.
-- Add improved [ingress metrics](/enterprise_influxdb/v1.9/administration/config-data-nodes/#ingress-metric-by-measurement-enabled--false) to track points written by measurement and by login.
+- Add improved [ingress metrics](/enterprise_influxdb/v1.9/administration/configure/config-data-nodes/#ingress-metric-by-measurement-enabled) to track points written by measurement and by login.
   Allow for collection of statistics regarding points, values, and new series written per measurement and by login.
   This data is collected and exposed at the data node level.
   With these metrics you can, for example:
   aggregate the write requests across the entire cluster,
   monitor the growth of series within a measurement,
   and track what user credentials are being used to write data.
 - Support authentication for Kapacitor via LDAP.
-- Support for [configuring Flux query resource usage](/enterprise_influxdb/v1.9/administration/config-data-nodes/#flux-controller) (concurrency, memory, etc.).
+- Support for [configuring Flux query resource usage](/enterprise_influxdb/v1.9/administration/configure/config-data-nodes/#flux-controller) (concurrency, memory, etc.).
 - Upgrade to [Flux v0.113.0](/influxdb/v2.0/reference/release-notes/flux/#v01130-2021-04-21).
 - Update Prometheus remote protocol to allow streamed reading.
 - Improve performance of sorted merge iterator.

diff --git a/content/enterprise_influxdb/v1.9/administration/backup-and-restore.md b/content/enterprise_influxdb/v1.9/administration/backup-and-restore.md
@@ -176,9 +176,9 @@ $ ls ./telegrafbackup
 20160803T222811Z.manifest  20160803T222811Z.meta  20160803T222811Z.s4.tar.gz
 ```
 
-#### Perform a metastore only backup
+#### Perform a metadata only backup
 
-Perform a meta store only backup into a specific directory with the command below.
+Perform a metadata only backup into a specific directory with the command below.
 The directory must already exist.
 
 ```bash
@@ -316,8 +316,8 @@ Restored from my-incremental-backup/ in 83.892591ms, transferred 588800 bytes
 
 ##### Restore from a metadata backup
 
-In this example, the `restore` command restores an metadata backup stored
-in the `metadata-backup/` directory.
+In this example, the `restore` command restores a [metadata backup](#perform-a-metadata-only-backup)
+stored in the `metadata-backup/` directory.
 
 ```bash
 # Syntax
@@ -402,6 +402,29 @@ time                  written
 1970-01-01T00:00:00Z  471
 ```
 
+##### Restore (overwrite) metadata from a full or incremental backup to fix damaged metadata
+
+1. Identify a backup with uncorrupted metadata from which to restore.
+2. Restore from backup with `-meta-only-overwrite-force`.
+
+   {{% warn %}}
+   Only use the `-meta-only-overwrite-force` flag to restore from backups of the target cluster.
+   If you use this flag with metadata from a different cluster, you will lose data.
+   (since metadata includes shard assignments to data nodes).
+   {{% /warn %}}
+
+   ```bash
+   # Syntax
+   influxd-ctl restore -meta-only-overwrite-force <path-to-backup-directory>
+
+   # Example
+   $ influxd-ctl restore -meta-only-overwrite-force my-incremental-backup/
+   Using backup directory: my-incremental-backup/
+   Using meta backup: 20200101T000000Z.meta
+   Restoring meta data... Done. Restored in 21.373019ms, 1 shards mapped
+   Restored from my-incremental-backup/ in 19.2311ms, transferred 588 bytes
+   ```
+
 #### Common issues with restore
 
 ##### Restore writes information not part of the original backup

diff --git a/content/enterprise_influxdb/v1.9/administration/configure/anti-entropy/_index.md b/content/enterprise_influxdb/v1.9/administration/configure/anti-entropy/_index.md
@@ -34,7 +34,7 @@ If data inconsistencies are detected among shards in a shard group, [invoke the
 In the repair process, the Anti-Entropy service will sync the necessary updates from other shards
 within a shard group.
 
-By default, the service performs consistency checks every 5 minutes. This interval can be modified in the [`anti-entropy.check-interval`](/enterprise_influxdb/v1.9/administration/config-data-nodes/#check-interval-5m) configuration setting.
+By default, the service performs consistency checks every 5 minutes. This interval can be modified in the [`anti-entropy.check-interval`](/enterprise_influxdb/v1.9/administration/config-data-nodes/#check-interval) configuration setting.
 
 The Anti-Entropy service can only address missing or inconsistent shards when
 there is at least one copy of the shard available.
@@ -178,7 +178,7 @@ until it either shows as being in the queue, being repaired, or no longer in the
 
 ## Configuration
 
-The configuration settings for the Anti-Entropy service are described in [Anti-Entropy settings](/enterprise_influxdb/v1.9/administration/config-data-nodes#anti-entropy) section of the data node configuration.
+The configuration settings for the Anti-Entropy service are described in [Anti-Entropy settings](/enterprise_influxdb/v1.9/administration/config-data-nodes/#anti-entropy-ae-settings) section of the data node configuration.
 
 To enable the Anti-Entropy service, change the default value of the `[anti-entropy].enabled = false` setting to `true` in the `influxdb.conf` file of each of your data nodes.