update 1.7.11 RNs and add new config option

content/enterprise_influxdb/v1.7/about-the-project/release-notes-changelog.md

@@ -8,6 +8,16 @@ menu:
     parent: About the project
 ---
 
+## v1.7.11 [2020-03-12]
+
+The InfluxDB Enterprise 1.7.11 release builds on the InfluxDB OSS 1.7.11 release.
+For details on changes incorporated from the InfluxDB OSS release, see
+[InfluxDB OSS release notes](/influxdb/v1.7/about_the_project/releasenotes-changelog/).
+
+### Features
+
+- Hinted handoff improvement to allow out-of-order writes. Add a configuration option `allow-out-of-order-writes` to the [`cluster`] section of the data node configuration file. This option defaults to `false` to match the existing behavior. There are some important operational considerations to review before enabling this feature. But, the result is enabling this option reduces the time required to drain the hinted handoff queue and increase throughput during recovery. See [allow-out-of-order-writes](/enterprise_influxdb/v1.7/administration/config-data-nodes/#allow-out-of-order-false) for more detail.
+
 ## v1.7.10 [2020-02-07]
 
 The InfluxDB Enterprise 1.7.10 release builds on the InfluxDB OSS 1.7.10 release.

content/enterprise_influxdb/v1.7/administration/config-data-nodes.md

@@ -385,6 +385,16 @@ so it is unlikely that changing this value will measurably improve performance b
 
 Environment variable: `INFLUXDB_CLUSTER_POOL_MAX_IDLE_STREAMS`
 
+#### allow-out-of-order = "false"
+
+By default, this option is set to false and writes are processed in the order that they are received. This means if any points are in the hinted handoff (HH) queue for a shard, all incoming points must go into the HH queue.
+
+If this option is set to true, writes are allowed to process in an order that differs from the order they were received. This can reduce the time required to drain the HH queue and increase throughput during recovery. **Do not enable if your use case involves updating points.** Updating a point means the measurement name, tag keys, and timestamp are the same as a previous write and only the value is different.
+
+Allowing out of order writes when updating points may cause incorrect values. For example, if the point `cpu v=1.0 1234` arrives on `node1` and attempts to replicate on `node2` but `node2` is down, `node1` writes the point to its local HH queue. If `node2` comes back online and a new point `cpu v=20. 1234` arrives at `node1` and updates the original point, the updated point is sent to `node2` (bypassing the HH queue). Because the updated point arrives at `node2` before the original point, and second point value is stored before the original point value.
+
+Environment variable: INFLUXDB_CLUSTER_ALLOW_OUT_OF_ORDER
+
 #### `shard-reader-timeout = "0"`
 
 The default timeout set on shard readers.

content/influxdb/v1.7/about_the_project/releasenotes-changelog.md

@@ -8,6 +8,19 @@ menu:
 v2: /influxdb/v2.0/reference/release-notes/influxdb/
 ---
 
+## v1.7.11 [2020-03-12]
+
+### Features
+
+- Update to Go 1.13.8.
+
+### Bug fixes
+
+- Update sorting method (`sortKey`) to use null byte as a delimiter, not comma.
+- Replace panic with error while encoding and decoding corrupt data.
+- Resolve incorrect error type in type switch.
+- Ensure the tsi log file (`activeLogFile`) has a READ lock.
+
 ## v1.7.10 [2020-02-07]
 
 ### Bug fixes