-
-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: Remove old containers after 4.x data migration #1255
Conversation
- data corruption - when multiple CouchDb installations are accessing the same data source. | ||
- data loss - when multiple CouchDb installation are exposing on the same port. | ||
|
||
To get a list of all containers run: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unsure of how comprehensive / extended these instructions should be.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
From this list, you should find the names for : | ||
- containers that ran CHT-Core 3.x, likely named `medic-os` and `haproxy`. | ||
- temporary single node CouchDb containers, likely named `couchdb-single-couchdb-1` | ||
- temporary clustered CouchDb containers, likely named `couchdb-cluster-couchdb-2.local-1`, `couchdb-cluster-couchdb-1.local-1` and `couchdb-cluster-couchdb-3.local-1` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it worth reminding people what the names of the new production containers are, and that they should not be removed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unfortunately, we don't know the names :(
It will depend on how they start them, the folder name or the compose project name.
@dianabarsan Is this ready to merge? |
I suppose so. I guess we waited long enough for input. |
Description
After having multiple instances with preexisting containers have outages due to resource allocation conflicts.
License
The software is provided under AGPL-3.0. Contributions to this project are accepted under the same license.