Hi Dejan

just some last questions on this subject :

1/ who has the responsability of the pcmk Stack ?

        is it someone from Pacemaker ?
        or Oracle ?

2/ in fact, if you re-consider my tests described in first msg,
    it is not completely stalled, it succeeds to write on both sides
    but one side is far far slower than the other as if the Locks
    was most of the time taken by one node and the other
    can take it much less often ... whereas I recall that the same
    test but on OCFS2 internal stack (so without Pacemaker) is
    working fine and much more load-balanced ...

    Is there some parameters to tune somewhere to get quite equivalent
    load of writes on FS on both nodes ?

Thanks
Alain


>> There's no need for another OCF RA here. You need to use the pcmk
>> stack if you want to run ocfs2 with pacemaker.
>>
>> > Thanks
>> >
>> > PS: the reason is because I 've done concurrent write access with this
>> > "Stack pcmk"
>> > on el6 and it does not work at all (seems to got many Lock problems)
>> > whereas the
>> > same tests works fine with the "Stack o2cb".
>>
>> Did you find this bug report:
>> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=587285





_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to