-
Notifications
You must be signed in to change notification settings - Fork 20
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
Galera macos #23
base: mariadb-4.x
Are you sure you want to change the base?
Galera macos #23
Conversation
…e-ssl-cert-chain-gen
…to phase-out-shared-4.ee-cleanup
…' into 4.ee-asio-server-handshake-failure
…o 4.ee-fix-wsrep-api-submodule
added pipeline logic for 4.ee
pipeline concept to replace multijob logic
Conflicts: gcs/src/gcs_defrag.cpp
1) Hide system error numbers and messages from thrown exceptions System error numbers and messages cause confusion when used in contexts where system calls are not involved. Hide the system error number and message from exception messages and create separate ThrowSystemError class and gu_throw_system_error() macro for contexts where the system error number is relevant. 2) Fix error and warning messages not to use strerror Using `strerror()` with error code in contexts where the error code does not come from a system call may cause very misleading error messages. Replace `strerror()` use around GCS code with two functions gcs_error_str() and gcs_state_transfer_error_str() in contexts where printing system error might be misleading. 4) Fix gcomm error logging Change several warning level messages into info level messages for cases which may happen during normal operation because of network partitionings or cluster configuration changes. Remove redundant warning messages in cases where the error handling is handled by caller. 5) Convert gcs warning messages to info Convert GCS messages which don't indicate any required action from admin (e.g. error conditions will be dealt with retrying or are result of expected conditions like network partitioning) into info or debug messages. 6) Propagate IST error to IST event handler The IST error is logged when the IST event queue becomes empty and one of the appliers read the error status. This is to avoid duplicate error logging from several contexts.
Conflicts: debian/changelog
…ructs gcs, gcs_core, gcs_group instead of using calloc() - make gcs_register_params() take gu::Coonfig& and return void in line with other such methods
tested 78f68e9 on MBP M3Max (
works well! I have managed to execute Galera node and join another node. |
@janlindstrom as tested, can the this be deconflicted and merged? |
Actually looking the the commit messages it looks like its all been merged in #32. Can you confirm? |
seems to be true - https://github.com/MariaDB/galera/blob/mariadb-4.x/gcs/src/gcs_core.cpp#L128 - gcs_core::gcs_core() now has constructor in |
No description provided.