On 2 Jun 2014, at 5:43 pm, K Mehta wrote:
> Andrew,
> Will you let me know if using the rule (assuming this rule works) pcs -f
> $CLUSTER_CREATE_LOG constraint location vha-$uuid rule score=-INFINITY
> \#uname ne vsanqa11 and \#uname ne vsanqa12 might help in resolving
> unexpected demote ?
Andrew,
Will you let me know if using the rule (assuming this rule works) pcs -f
$CLUSTER_CREATE_LOG constraint location vha-$uuid rule score=-INFINITY
\#uname ne vsanqa11 and \#uname ne vsanqa12 might help in resolving
unexpected demote ?
Regards,
Kiran
On Fri, May 30, 2014 at 11:58 AM, K Meh
any update ?
On Thu, May 29, 2014 at 9:08 AM, K Mehta wrote:
> In which pcs version is this issue fixed ?
>
>
> On Wednesday, May 28, 2014, K Mehta wrote:
> > Chris,
> > Here is the required information
> > [root@vsanqa11 ~]# rpm -qa | grep pcs ; rpm -qa | grep pacemaker ;
> uname -a ; cat /et
In which pcs version is this issue fixed ?
On Wednesday, May 28, 2014, K Mehta wrote:
> Chris,
> Here is the required information
> [root@vsanqa11 ~]# rpm -qa | grep pcs ; rpm -qa | grep pacemaker ; uname
-a ; cat /etc/redhat-release
> pcs-0.9.90-2.el6.centos.2.noarch
> pacemaker-cli-1.1.10-14.el
Chris,
Here is the required information
[root@vsanqa11 ~]# rpm -qa | grep pcs ; rpm -qa | grep pacemaker ; uname -a
; cat /etc/redhat-release
pcs-0.9.90-2.el6.centos.2.noarch
pacemaker-cli-1.1.10-14.el6_5.3.x86_64
pacemaker-libs-1.1.10-14.el6_5.3.x86_64
pacemaker-1.1.10-14.el6_5.3.x86_64
pacemake
On 05/27/14 05:38, K Mehta wrote:
One more question.
With crmsh, it was easy to add constraint to avoid a resource from running only
a subset(say vsanqa11 and vsanqa12) of nodes using the following command
crm configure location ms-${uuid}-nodes ms-$uuid rule -inf: \#uname ne vsanqa11
and \#unam
One more question.
With crmsh, it was easy to add constraint to avoid a resource from running
only a subset(say vsanqa11 and vsanqa12) of nodes using the following
command
crm configure location ms-${uuid}-nodes ms-$uuid rule -inf: \#uname ne
vsanqa11 and \#uname ne vsanqa12
[root@vsanqa11 ~]# pc
On 27 May 2014, at 2:37 pm, K Mehta wrote:
> So is globally-unique=false correct in my case ?
yes
>
>
> On Tue, May 27, 2014 at 5:30 AM, Andrew Beekhof wrote:
>
> On 26 May 2014, at 9:56 pm, K Mehta wrote:
>
> > What I understand from "globally-unique=false" is as follows
> > Agent handl
So is globally-unique=false correct in my case ?
On Tue, May 27, 2014 at 5:30 AM, Andrew Beekhof wrote:
>
> On 26 May 2014, at 9:56 pm, K Mehta wrote:
>
> > What I understand from "globally-unique=false" is as follows
> > Agent handling the resource does exactly same processing on all nodes.
>
On 26 May 2014, at 9:56 pm, K Mehta wrote:
> What I understand from "globally-unique=false" is as follows
> Agent handling the resource does exactly same processing on all nodes. For
> processing this resource, agent on all nodes will use exactly same resources
> (files, processes, same parame
What I understand from "globally-unique=false" is as follows
Agent handling the resource does exactly same processing on all nodes. For
processing this resource, agent on all nodes will use exactly same
resources (files, processes, same parameters to agent entry points, etc).
In case of my resourc
On 22 May 2014, at 11:20 pm, K Mehta wrote:
> > May 13 01:38:36 vsanqa28 pengine[4310]: notice: LogActions: Promote
> > vha-924bf029-93a2-41a0-adcf-f1c1a42956e5:0#011(Slave -> Master vsanqa28)
> > May 13 01:38:36 vsanqa28 pengine[4310]: notice: LogActions: Demote
> > vha-924bf029-93a2-41a
On 22 May 2014, at 11:20 pm, K Mehta wrote:
>
signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http:/
Attached is the file
On Thu, May 22, 2014 at 4:00 PM, Andrew Beekhof wrote:
>
> On 22 May 2014, at 4:33 pm, K Mehta wrote:
>
> > Hi,
> >vsanqa27 is promoted to master and vsanqa28 is slave. Suddently,
> vsanqa27 is demoted and vsanqa28 is promoted.
> >
> >
> > [root@vsanqa28 vsh-mp-05]# rp
On 22 May 2014, at 4:33 pm, K Mehta wrote:
> Hi,
>vsanqa27 is promoted to master and vsanqa28 is slave. Suddently, vsanqa27
> is demoted and vsanqa28 is promoted.
>
>
> [root@vsanqa28 vsh-mp-05]# rpm -qa | grep pcs; rpm -qa | grep ccs ; rpm -qa |
> grep pacemaker ; rpm -qa | grep corosyn
Hi,
vsanqa27 is promoted to master and vsanqa28 is slave. Suddently,
vsanqa27 is demoted and vsanqa28 is promoted.
[root@vsanqa28 vsh-mp-05]# rpm -qa | grep pcs; rpm -qa | grep ccs ; rpm -qa
| grep pacemaker ; rpm -qa | grep corosync
pcs-0.9.90-2.el6.centos.2.noarch
ccs-0.16.2-69.el6_5.1.x86_6
16 matches
Mail list logo
