On 04/22/2016 08:16 AM, Ulrich Windl wrote:
Ken Gaillot schrieb am 21.04.2016 um 19:50 in
Nachricht
> <571912f3.2060...@redhat.com>:
>
> [...]
>> The alerts section can have any number of alerts, which look like:
>>
>>> path="/srv/pacemaker/pcmk_alert_sample.sh">
>>
>>
Ken Gaillot writes:
> Each alert may have any number of recipients configured. These values
> will simply be passed to the script as arguments. The first recipient
> will also be passed as the CRM_alert_recipient environment variable,
> for compatibility with existing scripts that only support on
On 04/22/2016 10:55 AM, Ferenc Wágner wrote:
> Ken Gaillot writes:
>
>> Each alert may have any number of recipients configured. These values
>> will simply be passed to the script as arguments. The first recipient
>> will also be passed as the CRM_alert_recipient environment variable,
>> for comp
Hi Ken,
We waited for this function.
I confirm this function from today.
If there are any problem and opinion, I feed back.
Best Regards,
Hideo Yamauchi.
- Original Message -
> From: Ken Gaillot
> To: Cluster Labs - All topics related to open-source clustering welcomed
>
> Cc:
> D
Hello community,
I am facing following situation with a Pacemaker 2 nodes DB cluster (3
resources configured into the cluster - 1 MySQL DB resource, 1 Apache
resource, 1 IP resource )
-at every 61 seconds an MySQL monitoring action is started and have a 1200
sec timeout.
In some situation due to
> Gesendet: Mittwoch, 20. April 2016 um 19:35 Uhr
> Von: "Ken Gaillot"
> An: users@clusterlabs.org
> Betreff: Re: [ClusterLabs] pacemaker apache and umask on CentOS 7
>
> On 04/20/2016 12:20 PM, Klaus Wenninger wrote:
> > On 04/20/2016 05:35 PM, fatcha...@gmx.de wrote:
> >>
> >>> Gesendet: Mittw
On 04/22/2016 03:29 PM, John Gogu wrote:
> Hello community,
> I am facing following situation with a Pacemaker 2 nodes DB cluster
> (3 resources configured into the cluster - 1 MySQL DB resource, 1
> Apache resource, 1 IP resource )
> -at every 61 seconds an MySQL monitoring action is started and
Hi,
Are recurring monitor operations constrained by the batch-limit cluster
option? I ask because I'd like to limit the number of parallel start
and stop operations (because they are resource hungry and potentially
take long) without starving other operations, especially monitors.
--
Thanks,
Fer
On 04/21/2016 06:09 PM, Adam Spiers wrote:
> Ken Gaillot wrote:
>> Hello everybody,
>>
>> The release cycle for 1.1.15 will be started soon (hopefully tomorrow)!
>>
>> The most prominent feature will be Klaus Wenninger's new implementation
>> of event-driven alerts -- the ability to call scripts w
On 04/22/2016 02:43 AM, Klaus Wenninger wrote:
> On 04/22/2016 08:16 AM, Ulrich Windl wrote:
> Ken Gaillot schrieb am 21.04.2016 um 19:50 in
> Nachricht
>> <571912f3.2060...@redhat.com>:
>>
>> [...]
>>> The alerts section can have any number of alerts, which look like:
>>>
>>>>>
On 04/22/2016 05:19 AM, Klaus Wenninger wrote:
> On 04/22/2016 10:55 AM, Ferenc Wágner wrote:
>> Ken Gaillot writes:
>>
>>> Each alert may have any number of recipients configured. These values
>>> will simply be passed to the script as arguments. The first recipient
>>> will also be passed as the
On 04/22/2016 08:57 AM, Klaus Wenninger wrote:
> On 04/22/2016 03:29 PM, John Gogu wrote:
>> Hello community,
>> I am facing following situation with a Pacemaker 2 nodes DB cluster
>> (3 resources configured into the cluster - 1 MySQL DB resource, 1
>> Apache resource, 1 IP resource )
>> -at every
ClusterLabs is happy to announce the first release candidate for
Pacemaker version 1.1.15. Source code is available at:
https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-1.1.15-rc1
The most significant enhancements in this release are:
* A new "alerts" section of the CIB allows you
Ken Gaillot wrote:
> On 04/21/2016 06:09 PM, Adam Spiers wrote:
> > Ken Gaillot wrote:
> >> Hello everybody,
> >>
> >> The release cycle for 1.1.15 will be started soon (hopefully tomorrow)!
> >>
> >> The most prominent feature will be Klaus Wenninger's new implementation
> >> of event-driven ale
14 matches
Mail list logo