>>> Christopher Lumens schrieb am 02.12.2020 um 19:14 in
Nachricht <851583983.28225008.1606932881629.javamail.zim...@redhat.com>:
> Hi all,
>
> The final release of Pacemaker version 2.0.5 is now available at:
[...]
>
> * crm_mon additionally supports a --resource= option for resource-based
>
Hi Guy,
DB2 is not configured for auto start. So that is ruled out. I had some errors
in shell script. Just solved that issue and things are ok now.
Hi Reid,
I am like extremely new to pacemaker. I do not even know that ordered resource
group is implicitly a constraint like behaviour.
So I have
Constraints' values are varying from:
infinity which equals to score of 100
to:
- infinity which equals to score of -100
You can usually set a positive score on the prefered node which is bigger than
on the other node.
For example setting a location constraint like this will prefer
How did you resolve the issue? I see a problem in the CIB, and it may
be related to the issue you encountered. Even if not, it may cause
other issues later.
You have the following resource group:
You have the
if node is restarted, db2 is coming up, probably by autostart
that is what you want to keep the standby in sync ?
you can turn the node offline if maintenance is needed..
On Tue, 1 Dec 2020 at 18:51, Harishkumar Pathangay <
harishpathan...@outlook.com> wrote:
> Hi,
>
> I have DB2 resource
Hi sbd - developers & users!
Thanks to everybody for contributing to tests and
further development.
Improvements in build/CI-friendlyness and
added robustness against misconfiguration
justify labeling the repo v1.4.2.
I tried to quickly summarize the changes in the
repo since it was labeled
Hi all,
The final release of Pacemaker version 2.0.5 is now available at:
https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-2.0.5
Highlights include:
* A fix for the ACL bypassing bug previously mentioned on this mailing
list and described in CVE-2020-25654.
* The CIB now
On 2020-11-30 23:21, Petr Bena wrote:
Hello,
Is there a way to setup a preferred node for a service? I know how to
create constrain that will make it possible to run a service ONLY on
certain node, or constrain that will make it impossible to run 2
services on same node, but I don't want any of
Hello,
Is there a way to setup a preferred node for a service? I know how to
create constrain that will make it possible to run a service ONLY on
certain node, or constrain that will make it impossible to run 2
services on same node, but I don't want any of that, as in
catastrophical scenarios
Hi,
I realized it can be used in standard mode only after you pointing to that.
Anyways, writing custom agent always gives me a good understanding of the
resources start/stop/monitor etc…
My custom agent still has lot of “hard coded” values, but it is meant for
studying and understanding
On Wed, Dec 2, 2020 at 2:16 AM Harishkumar Pathangay
wrote:
>
> Just got the issue resolved.
Nice work!
> Any case I will send the cib.xml and my custom db2 resource agent.
>
> The existing resource agent is for HADR database, where there are two
> databases one running as Primary and other as
Just got the issue resolved.
Any case I will send the cib.xml and my custom db2 resource agent.
The existing resource agent is for HADR database, where there are two databases
one running as Primary and other as standby.
I have created a script which will start/stop db2 instances with a single
ClusterLabs is happy to announce resource-agents v4.7.0 rc1.
Source code is available at:
https://github.com/ClusterLabs/resource-agents/releases/tag/v4.7.0rc1
The most significant enhancements in this release are:
- bugfixes and enhancements:
- Build: fix systemd paths when using non standard
13 matches
Mail list logo
