it's done,
Here is the log from the second node, thank for your help, it very
apreciated!:
Mar 23 13:54:53 node2 attrd: [3102]: info: find_hash_entry: Creating hash
entry for last-failure-mysqld
Mar 23 13:54:53 node2 attrd: [3102]: info: attrd_perform_update: Delaying
operation last-failure-mysql
The first thing you can do it's eliminate this "location
master-prefer-node-1 Cluster-VIP 25: node1"
because you have your virtual in group and i would like to see the log from
the second node
Thanks :-)
Il giorno 23 marzo 2012 13:42, coma ha scritto:
> Thank you for your responses,
>
> i have
Thank you for your responses,
i have fixed my migration-treshold problem with lsb:mysqld ressource (i can
see migration-threshold=2 with crm_mon failcounts so its ok) bu failover
still doesn't work when mysql fail (but work fine when node fail or
standby).
So i've tried with the ocf ressource agen
On 03/22/2012 03:23 PM, coma wrote:
> Thank you for your responses,
>
> I have added the migration-treshold on my mysqld ressource, when i kill
> or manually stop mysql on one node, there is not failover on the second
> node.
> Also, when i look crm_mon --failcounts, i can see "mysqld:
> migration
put migration-thresold global in your cluster property
Il giorno 22 marzo 2012 15:23, coma ha scritto:
> Thank you for your responses,
>
> I have added the migration-treshold on my mysqld ressource, when i kill or
> manually stop mysql on one node, there is not failover on the second node.
> Als
Thank you for your responses,
I have added the migration-treshold on my mysqld ressource, when i kill or
manually stop mysql on one node, there is not failover on the second node.
Also, when i look crm_mon --failcounts, i can see "mysqld:
migration-threshold=100 fail-count=100", so i don"t
On 03/22/2012 01:51 PM, coma wrote:
> Ah yes thank you, the service status mysql is now monitored, but the
> failover is not performed?
As long as local restarts are successful there is no need for a failover
... there is migration-treshold to limit local restart tries.
Regards,
Andreas
--
Need
if you set migration-thresold=2 after two operation fail-count it's
reached your resource trys to switch to an other node
http://www.clusterlabs.org/doc/en-US/Pacemaker/1.0/html/Pacemaker_Explained/s-failure-migration.html
Il giorno 22 marzo 2012 13:51, coma ha scritto:
> Ah yes thank you, th
Ah yes thank you, the service status mysql is now monitored, but the
failover is not performed?
2012/3/22 emmanuel segura
> sorry
> I think you missed the op monitor operetion in your primitive definition
>
>
>
> Il giorno 22 marzo 2012 11:52, emmanuel segura ha
> scritto:
>
> I think you mis
sorry
I think you missed the op monitor operetion in your primitive definition
Il giorno 22 marzo 2012 11:52, emmanuel segura ha
scritto:
> I think you missed the op monitor operetion you primitive definition
>
> Il giorno 22 marzo 2012 11:33, coma ha scritto:
>
>> Hello,
>>
>> I have a quest
I think you missed the op monitor operetion you primitive definition
Il giorno 22 marzo 2012 11:33, coma ha scritto:
> Hello,
>
> I have a question about mysql service monitoring into a MySQL HA cluster
> with pacemaker and DRBD,
> I have set up a configuration to allow a failover between two no
Hello,
I have a question about mysql service monitoring into a MySQL HA cluster
with pacemaker and DRBD,
I have set up a configuration to allow a failover between two nodes, it
work fine when a node is offline (or standby), but i want to know if
it is possible
to monitor the mysql service to perfo
12 matches
Mail list logo
