Skip to content
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

Merged
merged 1 commit into from
Jan 25, 2024

Conversation

dianabarsan
Copy link
Member

@dianabarsan dianabarsan commented Dec 19, 2023

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.

- 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:
Copy link
Member Author

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.

Copy link
Member

@garethbowen garethbowen left a 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`
Copy link
Member

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?

Copy link
Member Author

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.

@garethbowen
Copy link
Member

@dianabarsan Is this ready to merge?

@dianabarsan
Copy link
Member Author

I suppose so. I guess we waited long enough for input.

@dianabarsan dianabarsan merged commit cb2d3e8 into main Jan 25, 2024
2 checks passed
@dianabarsan dianabarsan deleted the migration-deletes branch January 25, 2024 09:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants