Influxdata
/
docs-v2
mirror of https://github.com/influxdata/docs-v2.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

hotfix (#4234)

pull/4238/head
kelseiv 2022-07-20 15:03:13 -07:00 committed by GitHub
parent c20bb3bb0c
commit 43bf08e455
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
content/influxdb/v2.3/reference/release-notes/influxdb.md
View File

@ -12,6 +12,12 @@ weight: 101
This release includes the following [maintenance](#maintenance), [features](#features), [security updates](#security-updates) and [bug fixes](#bug-fixes).
{{% note %}}
#### Production ready: replicate data remotely
InfluxDB 2.2 introduced a technical preview of how to [replicate data from InfluxDB OSS to InfluxDB Cloud](/influxdb/v2.3/write-data/replication). This feature is now production ready.
{{% /note %}}
### Maintenance
- Upgrade from Flux 0.161.0 to [Flux 0.171.0](/flux/v0.x/release-notes/#v01710-2022-06-14).
@ -81,7 +87,7 @@ This release includes the following new [features](#features) and several [bug f
Add the option to [replicate data from InfluxDB OSS to InfluxDB Cloud](/influxdb/v2.3/write-data/replication).
{{% warn %}}
On rare occasions, remote write failures may cause data in the replication queue to get stuck. To ensure data is not dropped, restart the InfluxDB instance you're replicating data to as soon as possible.
On rare occasions, remote write failures may cause data in the replication queue to get stuck. To ensure data is not dropped, restart the InfluxDB instance replicating data.
To assess whether this issue is occurring, we recommend periodically doing one of the following:
- Verify your data is successfully replicated to your target bucket.