Or simply disable the db ha in /etc/cloudstack/management/db.properties” if
you really not required, till you upgrade to the next version.
On 02-Sep-2014, at 9:33 am, Rajani Karuturi raj...@apache.org wrote:
I think you are hitting this defect
.
Regards
Ian
On 24 Jun 2014, at 06:42, Damoder Reddy damoder.re...@citrix.com wrote:
The problem with MariaDB/galera is it does not support explicit locking of
tables etc.. which are used inside Cloudstack code..
https://mariadb.com/kb/en/mariadb-galera-cluster-known-limitations/
Thanks
The problem with MariaDB/galera is it does not support explicit locking of
tables etc.. which are used inside Cloudstack code..
https://mariadb.com/kb/en/mariadb-galera-cluster-known-limitations/
Thanks Regards
Damodar/
-Original Message-
From: Ian Marshall
Hi,
Please cherry-pick the following commit to 4.4 from 4.4-forward
24401e0b2b575d1aa151dbf5d4e0e0e1de4e9361 - The fix is for
https://issues.apache.org/jira/browse/CLOUDSTACK-6444
Thanks Regards
Damodar/
Message-
From: Damoder Reddy [mailto:damoder.re...@citrix.com]
Sent: 10 June 2014 05:48
To: users@cloudstack.apache.org
Subject: RE: Examples of configuring DB HA?
I think the issue here is the mysql connector jar is loaded using tomcat's
common class loader and the jar cloud-plugin-database
...@shapeblue.com
wrote:
Hi Damodar,
Comments inline.
On 06-Jun-2014, at 10:53 am, Damoder Reddy
damoder.re...@citrix.com
wrote:
Hi Adrian,
For your question, . Is the CS side purely for failover or does it
actually set up part of the replication for you? The answer is, the
Cloud
Hi Adrian,
For your question, . Is the CS side purely for failover or does it
actually set up part of the replication for you? The answer is, the Cloud Stack
does only failover configuration and the actual replication process on the
mysql side has to be done by own.
For the second
