[ClusterLabs] השב: [cluster Labs] standby and unstandby commands

[Nurit Vilosny]

+1 ☺



נשלח ממכשיר ה-Samsung שלי


 הודעה מקורית 
מאת: Omar Jaber 
תאריך: 11/26/2016 00:36 (GMT+02:00)
אל: users@clusterlabs.org
נושא: [ClusterLabs] [cluster Labs] standby and unstandby commands

Hi all ,
I have cluster contains three  nodes  with different sore  for location  
constrain and  I have  group resource
Running  on the  node  the  have  the highest score  for   location constrain 
when I  try to move  the  resource  from the  node  that have  the highest sore
To other  node by run command  "pcs cluster standby "  the  resource  stop in the  
node  and  fail in new node(the resource still start-fail stat periodically )
I thought at the first the  problem  is from different sore but  I changed it 
and  the  problem still exist

And  when I run "pcs  status "  I  see  there  is action failed :
resource_monitor_1 on hostname for  the new node'not running' (7): 
call=268, status=complete, exitreason='none',
last-rc-change='Sat Nov 26 00:27:00 2016', queued=0ms, exec=0ms
___
Users mailing list: Users@clusterlabs.org
http://clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

[ClusterLabs] [cluster lab]

[Nurit Vilosny]

Hi,
I am working in a 3 node HA cluster with a resource group.  I am seeing a weird 
behavior - whenever I shutdown one of the standby nodes (one without the 
resources) or starting it up again, my application hangs and UI not responsive.
I see that the requests are pending or fail on get proxy error.

What I don't understand is why another node can affect the resources (apache) 
on the active node

Thanks for the help!
Nurit Vilosny
SW Cloud Solutions Manager

Mellanox Technologies
13 Zarchin St. Raanana, Israel
Office: 972-74-712-9410
Cell: 972-54-4713000
Fax: 972-74-712-9111


___
Users mailing list: Users@clusterlabs.org
http://clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

Re: [ClusterLabs] [cluster lab] session hang out and fails when shutting off a standby node

[Nurit Vilosny]

(sorry, now with the subject :) )

From: Nurit Vilosny
Sent: Thursday, September 15, 2016 2:27 PM
To: users@clusterlabs.org
Subject: [cluster lab]

Hi,
I am working in a 3 node HA cluster with a resource group.  I am seeing a weird 
behavior - whenever I shutdown one of the standby nodes (one without the 
resources) or starting it up again, my application hangs and UI not responsive.
I see that the requests are pending or fail on get proxy error.

What I don't understand is why another node can affect the resources (apache) 
on the active node

Thanks for the help!
Nurit Vilosny
SW Cloud Solutions Manager

Mellanox Technologies
13 Zarchin St. Raanana, Israel
Office: 972-74-712-9410
Cell: 972-54-4713000
Fax: 972-74-712-9111


___
Users mailing list: Users@clusterlabs.org
http://clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

[ClusterLabs] Pacemaker migration - how to?

[Nurit Vilosny]

Hi everyone,
I have a very basic question that I couldn't find an answer for.
I am using the pacemaker to control a 3 nodes cluster, with a private 
application that works in an active - standby - standby mode.
My node have priorities in which is better to migrate to. I implemented it via 
location constraint scores.
I want to give my user the ability to migrate / failover  from the active to 
one of the / or specific  standby.
What is the correct way to do it?
Currently I am changing the location constraint score to make pacemaker move my 
resources, but I think this method is wrong.

Thanks,
Nurit
___
Users mailing list: Users@clusterlabs.org
http://clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

Re: [ClusterLabs] pacemaker doesn't failover when httpd killed

[Nurit Vilosny]

Perfect! I did missed it. Thanks for the help!!

-Original Message-
From: Kristoffer Grönlund [mailto:kgronl...@suse.com] 
Sent: Monday, September 05, 2016 3:27 PM
To: Nurit Vilosny <nur...@mellanox.com>; users@clusterlabs.org
Subject: RE: [ClusterLabs] pacemaker doesn't failover when httpd killed

Nurit Vilosny <nur...@mellanox.com> writes:

> Here is the configuration for the httpd:
>
> # pcs resource show cluster_virtualIP
> Resource: cluster_virtualIP (class=ocf provider=heartbeat type=IPaddr2)
>   Attributes: ip=10.215.53.99
>   Operations: monitor interval=20s (cluster_virtualIP-monitor-interval-20s)
>   start interval=0s timeout=20s 
> (cluster_virtualIP-start-interval-0s)
>   stop interval=0s timeout=20s on-fail=restart 
> (cluster_virtualIP-stop-interval-0s)
>
> (yes - I have monitoring configured and yes I used the ocf)
>

Hi Nurit,

That's just the cluster resource for managing a virtual IP, not the resource 
for managing the httpd daemon itself.

If you've only got this resource, then there is nothing that monitors the web 
server. You need a cluster resource for the web server as well 
(ocf:heartbeat:apache, usually).

You are missing both that resource and the constraints that ensure that the 
virtual IP is active on the same node as the web server. The Clusters from 
Scratch document on the clusterlabs.org website shows you how to configure this.

Cheers,
Kristoffer

--
// Kristoffer Grönlund
// kgronl...@suse.com
___
Users mailing list: Users@clusterlabs.org
http://clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

Re: [ClusterLabs] pacemaker doesn't failover when httpd killed

[Nurit Vilosny]

Here is the configuration for the httpd:

# pcs resource show cluster_virtualIP
Resource: cluster_virtualIP (class=ocf provider=heartbeat type=IPaddr2)
  Attributes: ip=10.215.53.99
  Operations: monitor interval=20s (cluster_virtualIP-monitor-interval-20s)
  start interval=0s timeout=20s 
(cluster_virtualIP-start-interval-0s)
  stop interval=0s timeout=20s on-fail=restart 
(cluster_virtualIP-stop-interval-0s)

(yes - I have monitoring configured and yes I used the ocf)

Regrads,
Nurit

-Original Message-
From: Kristoffer Grönlund [mailto:kgronl...@suse.com] 
Sent: Monday, September 05, 2016 2:01 PM
To: Nurit Vilosny <nur...@mellanox.com>; users@clusterlabs.org
Subject: RE: [ClusterLabs] pacemaker doesn't failover when httpd killed

Nurit Vilosny <nur...@mellanox.com> writes:

> Hi Kristoffer,
> Thanks for the prompt answer.
> Result of kill -9 is a dead process. Restart is not being performed.
> Can you tell me what logs to attach, so I can add them?

Hi Nurit,

Start by attaching your configuration. Do you have a monitoring operation 
configured for your apache resource? Did you use the OCF resource agent?

Cheers,
Kristoffer

--
// Kristoffer Grönlund
// kgronl...@suse.com
___
Users mailing list: Users@clusterlabs.org
http://clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org