Hi,
I'm now trying to run MySQL replication setting with Pacemaker.
When I set op monitor OCF_CHECK_LEVEL=10,
mysql RA writes down the following log messages every monitor interval.
* Master
Nov 11 14:19:51 dl380g5c mysql[18766]: INFO: COUNT(*) 3
Nov 11 14:19:51 dl380g5c mysql[18766]: INFO:
Hi,
I am running MySQL replication setting with 2 nodes Master/Slave configuration.
If Slave status(secs_behind) is lager than Master's parameter(max_slave_lag),
Slave data is outdated, right?
check_slave() in mysql RA would run crm_master -v 0 in this
situation to mark Slave as outdated,
but if
Just FYI, I noticed I erroneously put the asterisk changes in the master
branch on my github repo; I've now moved them to a separate asterisk
branch. The direct links to commits, which I posted earlier, should
still work as the SHA IDs are unchanged. They just point to commits in a
different
Hi
It is not usually possible that an environment variable passes.
Therefore I revised java_home in a required parameter.
Regards,
Tomo
tomcat.patch
Description: Binary data
___
Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org
Hi,
The current mysql RA, it set hostname (= uname -n) as its replication network,
but I have the following restriction.
# uname -n
node01
# cat /etc/hosts
192.168.100.101 node01 # maintenance LAN for node01
192.168.100.101 node02 # maintenance LAN for node02
192.168.200.101 # replication LAN
Dejan/Lars,
I noticed I've had a bunch of minor changes to IPaddr2 sitting in a
branch since July, and never got around to asking for a review or
merging them. I've just rebased them to the current state of master. If
one of you could take a look, I'd much appreciate that. Thanks!
On 2011-07-29 10:22, Michael Schwartzkopff wrote:
Hi,
I hope I found the correct list. Playing with the VirtualDomain RA I found
two
problems. Please find the description and patches below.
Sorry for not tending to this for a while, and thanks to Dejan for the
reminder.
1) During stop
2) The next problem is that a graceful shutdown sometimes does not work
when the machine just booted. This patch makes the RA send a shutdown
command every 10 seconds while shutting down the machine. This catches
the boot problem.
@@ -234,6 +240,9 @@
On 2011-11-11 11:42, Michael Schwartzkopff wrote:
2) The next problem is that a graceful shutdown sometimes does not work
when the machine just booted. This patch makes the RA send a shutdown
command every 10 seconds while shutting down the machine. This catches
the boot problem.
@@ -234,6
