Just out of my curiosity, what was wrong with the shipped pgsql RA and why you had to create a custom one? Does pgsql RA needs some improvement?
On Thu, Nov 13, 2008 at 8:48 AM, Alex Balashov <[EMAIL PROTECTED]> wrote: > Dominik Klein wrote: >> >> Hi Alex >> >>> Thank you. However, I tried this and it did not work; the resource >>> thrashes between monitor & start on the same node in perpetuity. >> >> Which version do you use? >> >> crmadmin -version > > HA Version 2.1.4, CRM Version 2.0 (CIB feature set 2.0) node: > aa909246edb386137b986c5773344b98c6969999 > >>> <constraints> >>> <rsc_location id="rsc_location_group_1" rsc="group_1"> >>> <rule id="prefered_location_group_1" score="100"> >>> <expression attribute="#uname" >>> id="prefered_location_group_1_expr" operation="eq" value="ipc-1"/> >>> </rule> >>> </rsc_location> >>> </constraints> >> >> That should leave the other node with a score of 0, which should be good >> enough to run the resource. > > I think that may be where the disconnect is happening. I ran ptest -Ls as > you suggested and found that for my service, the score on the primary node > is 0 and the score on the secondary node is -1000000. Could that be because > I am also setting the default-resource-stickiness to -INFINITY, as I > interpreted the FAQ to suggest? > > It is very strange, actually; I appear to have two sets of scores. ptest > -Ls output gives me two sets of values appended to each other. Here is my > simplification of the output exactly as it appears: > > group_1 allocation score on secondary: 0 > group_1 allocation score on primary: 0 > IP address allocation score on secondary: 0 > IP address allocation score on primary: 100 > DRBD allocation score on secondary: 0 > DRBD allocation score on primary: 0 > Filesystem allocation score on secondary: 0 > Filesystem allocation score on primary: 0 > PostgreSQL allocation score on secondary: 0 > PostgreSQL allocation score on primary: 0 > Kamailio (my custom service) allocation score on secondary: 0 > Kamailio (my custom service) allocation score on primary: 0 > IP address allocation score on secondary: 0 > IP address allocation score on primary: 100 > DRBD allocation score on secondary: -1000000 > DRBD allocation score on primary: 0 > Filesystem allocation score on secondary: -1000000 > Filesystem allocation score on primary: 0 > PostgreSQL allocation score on secondary: -1000000 > PostgreSQL allocation score on primary: 0 > Kamailio (my custom service) allocation score on secondary: -1000000 > Kamailio (my custom service) allocation score on primary: 0 > >> It never hurts to attach your entire config, maybe something else is >> causing this. >> >> cibadmin -Ql > my.xml > > OK. Here is something else very strange; when I look at my cib.xml, I see > the -INFINITY values I've assigned for default-resource-stickiness and > default-resource-failure-stickiness. But when I look at cibadmin -Q, I see > them as being set to 0. What gives? > > cib.xml: http://pastebin.com/f610c9a0a > cibadmin -Q: http://pastebin.com/f21748793 > > Thank you very much for your help! > > -- Alex > > -- > Alex Balashov > Evariste Systems > Web : http://www.evaristesys.com/ > Tel : (+1) (678) 954-0670 > Direct : (+1) (678) 954-0671 > Mobile : (+1) (706) 338-8599 > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems > -- Serge Dubrouski. _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
