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

Documentation of replication example for 5.6 is inaccurate #149

Closed
rhcarvalho opened this issue May 24, 2016 · 2 comments
Closed

Documentation of replication example for 5.6 is inaccurate #149

rhcarvalho opened this issue May 24, 2016 · 2 comments
Labels

Comments

@rhcarvalho
Copy link
Contributor

The documentation in 5.6/examples/replica/README.md is a copy-paste of 5.5/examples/replica/README.md, but the replication strategies are different.

5.5 uses binlog, and 5.6 uses GTID but that's not reflected in the documentation.

@rhcarvalho
Copy link
Contributor Author

@hhorak @bparees FYI

@bparees bparees added the P3 label May 24, 2016
hhorak added a commit to hhorak/mysql-container that referenced this issue May 23, 2018
* Do not dissable all repos every-time

It causes troubles when some other repositories are added by user or build system.
More at sclorg/s2i-base-container#148

* Use a better way to check whether subscription keys exist

* Use correct path for certificate inside the container to check whether the host is subscribed

* Do not enable repos when no are given

* Consider rhel-7-server-rpms and rhel-7-server-optional-rpms channels as default and enable them every time
DEFAULT_REPOS and SKIP_REPOS_ENABLE are intentionally undocumented, but might be used if we need to change this behaviour. Once we realize there are real use cases for using those variables, we should document them.

* Add some more messages to stdout and make variables really changeable.

* get rid of repos variable (thanks praiskup)
@phracek
Copy link
Member

phracek commented Apr 17, 2024

Closing it.

We do not have capacity to update README.md. Version 5.6 is deprecated.
In case it is still valid, feel free to re-open it.

@phracek phracek closed this as completed Apr 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants