Re: [ClusterLabs] Antw: Re: Antw: Re: from where does the default value for start/stop op of a resource come ?

On Wed, 2017-08-02 at 18:32 +0200, Lentes, Bernd wrote: > > - On Aug 2, 2017, at 10:42 AM, Ulrich Windl > ulrich.wi...@rz.uni-regensburg.de wrote: > > > > > > I thought the cluster does not perform actions that are not defined in the > > configuration (e.g. "monitor"). > > I think the

Re: [ClusterLabs] Antw: DRBD and SSD TRIM - Slow!

1) iotop did not show any significant io, just maybe 30k/second of drbd traffic. 2) okay. I've never done that before. I'll give it a shot. 3) I'm not sure what I'm looking at there. -- Eric Robinson > -Original Message- > From: Ulrich Windl [mailto:ulrich.wi...@rz.uni-regensburg.de] >

Re: [ClusterLabs] Antw: Re: Antw: Re: from where does the default value for start/stop op of a resource come ?

- On Aug 2, 2017, at 10:42 AM, Ulrich Windl ulrich.wi...@rz.uni-regensburg.de wrote: > > I thought the cluster does not perform actions that are not defined in the > configuration (e.g. "monitor"). I think the cluster performs and configures automatically start/stop operations if not

Re: [ClusterLabs] Antw: Re: Antw: Re: from where does the default value for start/stop op of a resource come ?

Ulrich Windl writes: > > See my proposal above. ;-) Hmm, yes. It's a possibility. Magic values rarely end up making things simpler though :/ Cheers, Kristoffer -- // Kristoffer Grönlund // kgronl...@suse.com ___

[ClusterLabs] Updated attribute is not displayed in crm_mon

Hi, In Pacemaker-1.1.17, the attribute updated while starting pacemaker is not displayed in crm_mon. In Pacemaker-1.1.16, it is displayed and results are different. https://github.com/ClusterLabs/pacemaker/commit/fe44f400a3116a158ab331a92a49a4ad8937170d This commit is the cause, but the

Re: [ClusterLabs] Antw: Re: Antw: Re: from where does the default value for start/stop op of a resource come ?

>>> Kristoffer Grönlund schrieb am 02.08.2017 um 10:32 in Nachricht <87bmny74ka@suse.com>: > Ulrich Windl writes: > > Kristoffer Grönlund schrieb am 02.08.2017 um 10:05 in >>> >>> One idea might be to have a

Re: [ClusterLabs] Antw: fence_vmware_soap: reads VM status but fails to reboot/on/off

Hey Hideo, Yes I'm using the free license for testing 6.5 version. We do have full license on production server but it is for an older version. I will install a full version key and get back with info but I'm sure after reading the info starting from your link that what you pointed out is the

Re: [ClusterLabs] Antw: Re: from where does the default value for start/stop op of a resource come ?

Ulrich Windl writes: > > What aout this priority for newly added resources:? > 1) Use the value specified explicitly > 2) Use the value the RA's metadata specifies > 3) Use the global default > > With "use" I mean "add it to the RA configuration". Yeah, I've

Re: [ClusterLabs] Antw: fence_vmware_soap: reads VM status but fails to reboot/on/off

Hi Octavian, Are you possibly using the free version of ESXi?  On the free version of ESXi, the operation on or off fails. The same phenomenon also occurs in connection with virsh.  - https://communities.vmware.com/thread/542433 Best Regards, Hideo Yamauchi. - Original Message - >From:

[ClusterLabs] Antw: Re: from where does the default value for start/stop op of a resource come ?

>>> Kristoffer Grönlund schrieb am 02.08.2017 um 09:33 in Nachricht <87h8xq77a1@suse.com>: > "Lentes, Bernd" writes: > >> Hi, >> >> i'm wondering from where the default values for operations of a resource > come from. > > [snip] >

Re: [ClusterLabs] from where does the default value for start/stop op of a resource come ?

"Lentes, Bernd" writes: > Hi, > > i'm wondering from where the default values for operations of a resource come > from. [snip] > > Is it hardcoded ? All timeouts i found in my config were explicitly related > to a dedicated resource. > What are the values

[ClusterLabs] Antw: DRBD and SSD TRIM - Slow!

Hi! I know little about trim operations, but you could try one of these: 1) iotop to see whether some I/O is done during trimming (assuming trimming itself is not considered to be I/O) 2) Try blocktrace on the affected devices to see what's going on. It's hard to set up and to extract the