[ClusterLabs] Fence agent executing thousands of API calls per hour

2018-07-30 Thread Casey & Gina
I've set up a number of clusters in a VMware environment, and am using the fence_vmware_rest agent for fencing (from fence-agents 4.2.1), as follows: Stonith Devices: Resource: vmware_fence (class=stonith type=fence_vmware_rest) Attributes: ip= username= password= ssl_insecure=1 pcmk_host_che

Re: [ClusterLabs] Fence agent executing thousands of API calls per hour

2018-07-30 Thread Andrei Borzenkov
Отправлено с iPhone > 31 июля 2018 г., в 2:47, Casey & Gina написал(а): > > I've set up a number of clusters in a VMware environment, and am using the > fence_vmware_rest agent for fencing (from fence-agents 4.2.1), as follows: > > Stonith Devices: > Resource: vmware_fence (class=stonith typ

Re: [ClusterLabs] Fence agent executing thousands of API calls per hour

2018-07-30 Thread Klaus Wenninger
On 07/31/2018 01:47 AM, Casey & Gina wrote: > I've set up a number of clusters in a VMware environment, and am using the > fence_vmware_rest agent for fencing (from fence-agents 4.2.1), as follows: > > Stonith Devices: > Resource: vmware_fence (class=stonith type=fence_vmware_rest) > Attributes

Re: [ClusterLabs] Fence agent executing thousands of API calls per hour

2018-07-31 Thread Casey Allen Shobe
Aha, thank you! I missed the blatantly obvious. I will discuss with my colleague and likely use a longer interval. > On Jul 30, 2018, at 11:25 PM, Klaus Wenninger wrote: > >> On 07/31/2018 01:47 AM, Casey & Gina wrote: >> I've set up a number of clusters in a VMware environment, and am using

Re: [ClusterLabs] Fence agent executing thousands of API calls per hour

2018-08-01 Thread Casey & Gina
How is the interval adjusted? Based on an example I found online, I thought `pcs resource op monitor interval=15m vmware_fence` should work, but after executing that `pcs config` still shows a monitor interval of 60s. Thank you, -- Casey > On 2018-07-31, at 9:11 AM, Casey Allen Shobe wrote:

Re: [ClusterLabs] Fence agent executing thousands of API calls per hour

2018-08-01 Thread Casey & Gina
Actually, is it even necessary at all? Based on my other E-mail to the list (Fence agent ends up stopped with no clear reason why), it seems that sometimes the monitor fails with an "unknown error", resulting in a cluster that won't fail over due to inability to fence. I tried looking at the f

Re: [ClusterLabs] Fence agent executing thousands of API calls per hour

2018-08-01 Thread Ken Gaillot
On Wed, 2018-08-01 at 14:47 -0600, Casey & Gina wrote: > Actually, is it even necessary at all?  Based on my other E-mail to > the list (Fence agent ends up stopped with no clear reason why), it > seems that sometimes the monitor fails with an "unknown error", > resulting in a cluster that won't fa

Re: [ClusterLabs] Fence agent executing thousands of API calls per hour

2018-08-01 Thread Emmanuel Gelati
Maybe you need to use pcs resource update 2018-08-01 22:26 GMT+02:00 Casey & Gina : > How is the interval adjusted? Based on an example I found online, I > thought `pcs resource op monitor interval=15m vmware_fence` should work, > but after executing that `pcs config` still shows a monitor in

Re: [ClusterLabs] Fence agent executing thousands of API calls per hour

2018-08-02 Thread Casey Allen Shobe
Eh? Then why does pcs config show nothing new after that command is run? > On Aug 1, 2018, at 3:08 PM, Ken Gaillot wrote: > > A resource can have more than one monitor, so that command by itself > just adds a second monitor. You have to delete the original one > separately with pcs resource op

Re: [ClusterLabs] Fence agent executing thousands of API calls per hour

2018-08-03 Thread Tomas Jelinek
It does not show anything new because your command `pcs resource op monitor interval=15m vmware_fence` is not a valid pcs command. There is a bug in pcs so when this command is executed, pcs does nothing and exits with 0. It should report the command does not exist. I think you meant: pcs reso