Hi Andrew,
I registered a problem in Bugzilla.
And I attached a file of crm_report.
* http://bugs.clusterlabs.org/show_bug.cgi?id=5213
Best Regards,
Hideo Yamauchi.
--- On Thu, 2014/5/15, renayama19661...@ybb.ne.jp
wrote:
> Hi Andrew,
>
> > >> Your config looks reasonable... almost certain
Hi Andrew,
> >> Your config looks reasonable... almost certainly a bug in the PE.
> >> Do you happen to have the relevant pengine input file available?
> >
> > Really?
>
> I would expect that:
>
> colocation rsc_colocation-master-1 INFINITY: msPostgresql:Master A-master
>
> would only promot
On 15 May 2014, at 9:57 am, renayama19661...@ybb.ne.jp wrote:
> Hi Andrew,
>
> Thank you for comments.
>
>>> We do not want to be promoted to Master in the node that primitive resource
>>> does not start.
>>> Is there the setting of colocation and order which are not promoted to
>>> Master of
Hi Andrew,
Thank you for comments.
> > We do not want to be promoted to Master in the node that primitive resource
> > does not start.
> > Is there the setting of colocation and order which are not promoted to
> > Master of the Master node?
>
> Your config looks reasonable... almost certainly
On 13 May 2014, at 3:14 pm, renayama19661...@ybb.ne.jp wrote:
> Hi All,
>
> We assume special resource constitution.
> Master of master-slave depends on primitive resource for the constitution.
>
> We performed the setting that Master stopped becoming it in Slave node
> experimentally.
>
>
>
Hi All,
We assume special resource constitution.
Master of master-slave depends on primitive resource for the constitution.
We performed the setting that Master stopped becoming it in Slave node
experimentally.
location rsc_location-msStateful-1 msPostgresql \
rule $role="master" 20
