-
Notifications
You must be signed in to change notification settings - Fork 64
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
4.x: Document that evs.version = 1 #175
Comments
@byte Can I change the evs.version default value to 1? |
Hi @kirjaamo -- this is a problem when we keep Galera Cluster 3 and Galera Cluster 4 documentation in the same place. Because, please read this as well: https://galeracluster.com/library/documentation/auto-eviction.html#upgrade-evs "Releases of Galera Cluster prior to version 3.8 use EVS Protocol version 0, which is not directly compatible with version 1. As such, when you upgrade Galera Cluster for a node, the node continues to use EVS Protocol version 0." How do you propose to change evs.version=1 when there are older installations of Galera Cluster around as well? |
Can we replace sentence "The default value is version 0, for backwards compatibility." with: |
Yes, this is OK. But can you also ensure that in the documentation you find a way to let people know what version of Galera Cluster they are using? We do not have a mapping of released versions and cluster versions I suspect |
Who would know more about finding the version one uses? |
@temeo can you help here? |
This version information is quite scattered for historical reasons. Versions related to gcomm can be found from Galera parameters: https://galeracluster.com/library/documentation/galera-parameters.html#evs-version These should be visible in
Galera version is shown in |
The wsrep_profvider_version example vale is 25.3.5-wheezy(rXXXX). Does this mean that Galera version is 3.5? |
@kirjaamo this should be some inspiration for a new doc https://mariadb.com/kb/en/meta/galera-versions/ Remember that we have to do this for... MySQL provided by Codership, and I think for added value, have the above meta information, and maybe also include Percona XtraDB Cluster (PXC). So we become the canonical source of all information relation to Galera Cluster |
and the answer to this is yes! |
Do you mean that we add the tables from https://mariadb.com/kb/en/meta/galera-versions/ to our documentation, and create similar tables for MySQL and PXC? |
I think this is a good idea. People need to have such information available to them, and it should come from our documentation. |
Who could collect the versions to a table? |
Besides MariaDB, I haven't found something similar, so I presume this is something you will have to do |
e.g. we are going to release "Codership is pleased to announce the release of Galera Replication library 4.8, |
I understand. Can you propose a solution that I am able to do? The table that we started turned out to be too complicated, as I cannot find the necessary information. |
@byte Now that we have the release versions page and have explained |
@byte You mentioned that we should "become the canonical source of all information relation to Galera Cluster". I took a look at MariaDB and PXC versioning info. If I were to update our versions table, would the example below be correct?
|
I think I got them right. Next, I'll add links. By the way, do you know if there is a reason why we keep tables in documentation so narrow? Maybe tablet use? |
In particular, autoeviction.html should be changed accordingly.
The text was updated successfully, but these errors were encountered: