influxdata / influxdata/docs-v2
Moving from InfluxDB OSS to a single node Enterprise setup.
@pierwill is already working on this.
Since Nov 2, 2021.
- Dominant language
- JavaScript
- Stars
- 82
- Forks
- 326
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 82
Description
It seems like we lost the instructions for how to go from InfluxDB OSS to InfluxDB Enterprise -- where the Enterprise cluster contains only 1 data node.
I would suggest revisiting these instructions: https://docs.influxdata.com/enterprise_influxdb/v1.9/guides/migration/
I think there are a couple of scenarios here:
1. Moving from OSS to single node Enterprise
2. Moving from OSS to a multi-node Enterprise
I'd suggest a new landing page for OSS -> Enterprise migration with separate instructions for the different paths.
For 1. it seems like these instructions were potentially lost in the move to Enterprise 1.9. I feel like these instructions still apply if you want to upgrade in-place ->> https://docs.influxdata.com/enterprise_influxdb/v1.8/guides/migration/#migrate-a-data-set-with-downtime
There are a few outstanding questions about the handling of the OSS user meta data (and permissions) and whether that information "migrates" without doing a `-portable` backup. So...a manual review of this and validation of this seems important.
For 2. The current instructions seem to be focused on a multi-node setup with zero downtime. Meaning a -portable backup is required.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.