[ClusterLabs] Antw: ringid interface FAULTY no resource move

[Rafał Sanocki]

I modify configuration of drbd but still nothing. I not mention the 
clusters are on hp blades machines. I plug out connection on switch by 
disabling port.

But still nothing :( , maybe add something like this to crm will do?

         ocf:pacemaker:ping \
         params host_list="172.17.10.81 172.17.10.89" multiplier=100 
name=ping_d \
         op monitor interval=5s timeout=5s \
         meta target-role=Started


Rafal


#cat drbd.conf

global {
     usage-count no;
}

common {
     syncer { rate 100M; }
     protocol      C;

handlers {
fence-peer "/usr/local/lib/drbd/crm-fence-peer.sh";
after-resync-target "/usr/local/lib/drbd/crm-unfence-peer.sh";
}

}

resource b1 {
     startup {
        wfc-timeout 0;
        degr-wfc-timeout        420;
     }
     disk {.
        on-io-error detach;
        fencing resource-only;
      }
     on csb01A {
        device      /dev/drbd2;
        disk        /dev/sda2;
        address     255.255.255.1:7791;
        meta-disk   internal;
     }
     on csb01B {
        device      /dev/drbd2;
        disk        /dev/sda2;
        address     255.255.255.9:7791;
        meta-disk   internal;
     }




W dniu 2016-05-05 o 16:29, Ken Gaillot pisze:
> On 05/05/2016 07:43 AM, Rafał Sanocki wrote:
>> for what?
>>
>> cluster working good when i stop pacemaker, resources go to second node,
>> but when connection is lost nothing happend.
>>
>> Failed Actions:
>> * p_ip_2_monitor_30000 on csb01B 'not running' (7): call=47,
>> status=complete, exitreason='none',
>>      last-rc-change='Wed May  4 17:34:50 2016', queued=0ms, exec=0ms
>>
>> I just want to move resources when connection on one ring is lost.
> If you have two working rings, and one is lost, then the other will be
> used automatically, with no resource failover required. "Nothing
> happened" in that case is the desired outcome.
>
> If you lose your only ring (or all rings), then fencing is required for
> the cluster to recover resources safely.
>
> As an example, let's say we have two nodes, and two networks, one used
> for public-facing services and one used for cluster communication, with
> an IP address as the highly available resource. If the cluster
> communication link fails but the public-facing link is still up, without
> fencing both nodes could bring up the IP address. That would lead to
> some packets going to one node and some to the other, rendering the
> service completely unusable. Fencing allows one node to be sure the
> other is not using the IP. Once you use shared storage, databases, and
> such, the risk is much greater -- a reconciliation nightmare at best,
> complete data loss at worst.
>
>> W dniu 2016-05-04 o 15:50, emmanuel segura pisze:
>>> use fencing and drbd fencing handler
>>>
>>> 2016-05-04 14:46 GMT+02:00 Rafał Sanocki<rafal.sanocki at gmail.com>:
>>>> Resources shuld move to second node when any  interface is down.
>>>>
>>>>
>>>>
>>>>
>>>> W dniu 2016-05-04 o 14:41, Ulrich Windl pisze:
>>>>
>>>>>>>> Rafal Sanocki<rafal.sanocki at gmail.com>  schrieb am 04.05.2016 um
>>>>>>>> 14:14
>>>>>>>> in
>>>>> Nachricht<78d882b1-a407-31e0-2b9e-b5f8406d4ee8 at gmail.com>:
>>>>>> Hello,
>>>>>> I cant find what i did wrong. I have 2 node cluster, Corosync
>>>>>> ,Pacemaker
>>>>>> , DRBD .  When i plug out cable nothing happend.
>>>>> "nothing"? The wrong cable?
>>>>>
>>>>> [...]
>>>>>
>>>>> Regards,
>>>>> Ulrich
> _______________________________________________
> Users mailing list:Users at clusterlabs.org
> http://clusterlabs.org/mailman/listinfo/users
>
> Project Home:http://www.clusterlabs.org
> Getting started:http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs:http://bugs.clusterlabs.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20160506/e5de495a/attachment.htm>