Hello everyone,
A few weeks ago I asked you if you use or managed to use the DB HA
Cloudstack feature (db.ha.enabled)[1] and after reading some of the
replies and doing intensive testing myself I have found out that the
feature is indeed non-functional, it's broken.
In my testing I discovere
+1 it's a broken feature that at least doesn't work with MySQL 8.x, I'm not
sure if it worked with prior versions of MySQL. However, we need to document
some sort of suggested MySQL HA setup in our docs.
Regards.
From: Nux
Sent: Tuesday, August 22, 2023 18:54
Happy to contribute a doc on how to achieve HA if we decide to remove
this.
Thanks
On 2023-08-22 15:01, Rohit Yadav wrote:
+1 it's a broken feature that at least doesn't work with MySQL 8.x, I'm
not sure if it worked with prior versions of MySQL. However, we need to
document some sort of sugg
Thanks for the update, Wei.
Good job so far!
On 2023-08-21 12:48, Wei ZHOU wrote:
Hi all,
In the last weeks, we have merged a few bug fixes into the 4.18 branch.
We
are still working on remaining bug fixes and reviewing pull requests.
22 pull requests are open for review:
https://github.com/
Do you have a picture of them?
Thanks
On 2023-08-21 13:14, Ivet Petrova wrote:
Hi all,
I am happy to announce that we have a special surprise for the early
birds! As you know the CloudStack Collaboration Conference will happen
on November 23-24th in Paris, France.
Now we have a special surpr
We faced some issues when running Galera. We went back to master slave.
Anyone using Galera in production for a long time?
Regards,
Shiv
> On 22-Aug-2023, at 19:34, Nux wrote:
>
> Happy to contribute a doc on how to achieve HA if we decide to remove this.
>
> Thanks
>
> On 2023-08-22 15:01,
But what do you think of the removal of DB HA code?
When using Galera you need to query against a single node, don't spread
the load among all 3, as this will break certain locking functionality
in Cloudstack and lead to problems.
In a Haproxy configuration you should be keeping just one acti
Well, if it is broken and it is not prominently mentioned anywhere new adopters
may go ahead with that on production. So I guess best to remove or at least
mention that it is not production grade.
Thanks
Shiv
> On 22-Aug-2023, at 20:12, Nux wrote:
>
> But what do you think of the removal of D
Shiv, Lucian, all,
It's a known limitation for all available MySQL clustering solutions such as
Galera, Percona XtraDB, Innodb Cluster that GET_LOCK [1] isn't supported
[2][3]. The GET_LOCK is used by CloudStack for global locking critical code
when more than one management server(s) are runnin
Thanks for elaborating, Rohit.
On 2023-08-22 16:25, Rohit Yadav wrote:
Shiv, Lucian, all,
It's a known limitation for all available MySQL clustering solutions
such as Galera, Percona XtraDB, Innodb Cluster that GET_LOCK [1] isn't
supported [2][3]. The GET_LOCK is used by CloudStack for globa
New adopters may not go ahead with it in production because they won't
get it working, unless they fix a lot of code, that would be a nice pull
request. :)
On 2023-08-22 16:25, K B Shiv Kumar wrote:
Well, if it is broken and it is not prominently mentioned anywhere new
adopters may go ahead w
Hello Lucian and all,
I am -1 on removing the whole DB HA feature from CloudStack.
As we discussed on July[1], the current properties we have on
"db.properties" regarding DB HA are hardcoded and only address some MySQL
properties, which are not fully compatible with the properties for
configuring
Sure, Daniel
PR #7895 is currently in draft as we need to do some more tests.
However, the intention is to enable users to configure the DB connection
URI directly through `db.properties` file. These are the tests that have
been done so far with ACS without this PR changeset:
Using the curre
13 matches
Mail list logo
