On Fri, Mar 25, 2011 at 2:07 PM, Alain.Moulle alain.mou...@bull.net wrote:
Hi,
I tried but it does not work :
crm_resource -r resname -p target-role -v started
because it adds a target-role=started as params
whereis I already have a meta target-role=Stopped
so resource does not start.
So I
Hi,
Thanks, but in fact, I give these commands as examples for the latency
problem,
but in reality, this latency leads to problems for me on crm configure
(primitive, group, etc.) commands,
as we have the same latency problems with these crm configure commands.
Alain
On Thu, Mar 10, 2011 at
Hi,
On Wed, Mar 09, 2011 at 10:02:01AM +0100, Alain.Moulle wrote:
Hi Dejan
I tried to reproduce the latency pb between commands, bt with only
some Dummy resources :
Resource Group: group-dummy1
resname1 (ocf::pacemaker:Dummy): Started chili2
resname2 (ocf::pacemaker:Dummy):
On Thu, Mar 10, 2011 at 02:49:01PM +0100, Dejan Muhamedagic wrote:
Hi,
On Wed, Mar 09, 2011 at 10:02:01AM +0100, Alain.Moulle wrote:
Hi Dejan
I tried to reproduce the latency pb between commands, bt with only
some Dummy resources :
Resource Group: group-dummy1
resname1
On Thu, Mar 10, 2011 at 03:18:30PM +0100, Lars Ellenberg wrote:
On Thu, Mar 10, 2011 at 02:49:01PM +0100, Dejan Muhamedagic wrote:
Hi,
On Wed, Mar 09, 2011 at 10:02:01AM +0100, Alain.Moulle wrote:
Hi Dejan
I tried to reproduce the latency pb between commands, bt with only
some
Hi Dejan
I tried to reproduce the latency pb between commands, bt with only
some Dummy resources :
Resource Group: group-dummy1
resname1 (ocf::pacemaker:Dummy): Started chili2
resname2 (ocf::pacemaker:Dummy): Started chili2
resname3 (ocf::pacemaker:Dummy): Started chili2
Hi Dejan,
OK I'll do it as soon as possible.
But I have this behavior since a long time ... I think since I switch from
fedora12 to rhel6 ... perhaps ...
Alain
Dejan Muhamedagic a écrit :
On Tue, Mar 01, 2011 at 04:29:26PM +0100, Alain.Moulle wrote:
Hi Dejan,
whatever command , i.e a crm
Hi,
On Tue, Mar 01, 2011 at 03:15:10PM +0100, Alain.Moulle wrote:
Hi,
Suppose we execute a crm command on a resource, it is quickly taken in
account.
Now, we execute a new crm command, there is a delay of around 40 to 60s
before this new command is taken in account in Pacemaker.
I
Hi Dejan,
whatever command , i.e a crm start on a resource, an then a start or on
another
resource, the first one is instaneously taken in account, the second one
takes
around 45/50s . Or a start on a resource and just after the start, a crm
resource
stop on the same resource, the command
On Tue, Mar 01, 2011 at 04:29:26PM +0100, Alain.Moulle wrote:
Hi Dejan,
whatever command , i.e a crm start on a resource, an then a start or on
another
resource, the first one is instaneously taken in account, the second one
takes
around 45/50s . Or a start on a resource and just after the
10 matches
Mail list logo
