On 3/29/21 8:44 AM, d tbsky wrote:
Reid Wahl
An order constraint set with kind=Serialize (which is mentioned in the first
reply to the thread you linked) seems like the most logical option to me. You
could serialize a set of resource sets, where each inner set contains a
VirtualDomain
On 3/29/21 5:24 PM, Tomas Jelinek wrote:
If you stopped a node and you want it to start and reconnect to its
cluster, run 'pcs cluster start' on the node. You may also run 'pcs
cluster start --all' or (in your case) 'pcs cluster start node1' on
any cluster node.
Maybe for better
On 29.03.2021 20:12, Ken Gaillot wrote:
> On Sun, 2021-03-28 at 09:20 +0300, Andrei Borzenkov wrote:
>> On 28.03.2021 07:16, Strahil Nikolov wrote:
>>> I didn't mean DC as a designated coordinator, but as a physical
>>> Datecenter location.
>>> Last time I checked, the node attributes for all
Thank you.
Then, if a node disconnected then how it could back to the cluster chain?
On Monday, March 29, 2021, 06:13:09 PM GMT+4:30, Tomas Jelinek
wrote:
Hi Jason,
Regarding point 3:
Most pcs commands operate on the local node. If you stop a cluster on a
node, pcs is unable to
Scores are in the range -1,000,000 to +1,000,000 (also known as
"infinity").
Numerically higher scores are preferred in whatever the context is
(e.g. higher stickiness means more sticky, higher colocation score
means more likely to stay together, etc.).
On Mon, 2021-03-29 at 13:05 +0200, Ulrich
On Mon, 2021-03-29 at 13:01 +0200, Ulrich Windl wrote:
> > > > Reid Wahl schrieb am 29.03.2021 um 12:47 in
> > > > Nachricht
>
> :
> > On Mon, Mar 29, 2021 at 3:35 AM Ulrich Windl <
> > ulrich.wi...@rz.uni-regensburg.de> wrote:
> >
> > > > > > d tbsky schrieb am 29.03.2021 um 04:01
> > > > > >
On Sun, 2021-03-28 at 09:20 +0300, Andrei Borzenkov wrote:
> On 28.03.2021 07:16, Strahil Nikolov wrote:
> > I didn't mean DC as a designated coordinator, but as a physical
> > Datecenter location.
> > Last time I checked, the node attributes for all nodes seemed the
> > same.I will verify that
I've made a note of these as ideas for 1.2/2.0 :)
On Sun, 2021-03-28 at 03:03 +0200, Ulrich Windl wrote:
> On 3/26/21 11:17 PM, Ken Gaillot wrote:
> > OCF 1.1 is now formally adopted!
> >
> > https://github.com/ClusterLabs/OCF-spec/blob/master/ra/1.1/resource-agent-api.md
> >
> > Thanks to
On 29.03.2021 11:11, Ulrich Windl wrote:
Andrei Borzenkov schrieb am 27.03.2021 um 06:37 in
> Nachricht <7c294034-56c3-baab-73c6-7909ab554...@gmail.com>:
>> On 26.03.2021 22:18, Reid Wahl wrote:
>>> On Fri, Mar 26, 2021 at 6:27 AM Andrei Borzenkov
>>> wrote:
>>>
On Fri, Mar 26, 2021 at
If you stopped a node and you want it to start and reconnect to its
cluster, run 'pcs cluster start' on the node. You may also run 'pcs
cluster start --all' or (in your case) 'pcs cluster start node1' on any
cluster node.
Tomas
Dne 29. 03. 21 v 16:25 Jason Long napsal(a):
Thank you.
Then,
Hi Jason,
Regarding point 3:
Most pcs commands operate on the local node. If you stop a cluster on a
node, pcs is unable to connect to cluster daemons on the node (since
they are not running) and prints an error message denoting that. This is
expected behavior.
Regards,
Tomas
Dne 27. 03.
Hi!
The question may sound completely stupid, but I didn't find the formal
definition of a "high priority" in the pacemaker docs.
Many years ago I thought lower numbers are higher priorities, but then I
flipped the concept, thinking higher numbers are higher priorities.
As it seems resource
>>> Reid Wahl schrieb am 29.03.2021 um 12:47 in Nachricht
:
> On Mon, Mar 29, 2021 at 3:35 AM Ulrich Windl <
> ulrich.wi...@rz.uni-regensburg.de> wrote:
>
>> >>> d tbsky schrieb am 29.03.2021 um 04:01 in Nachricht
>> :
>> > Hi:
>> >since the vm start/stop at once will consume disk IO, I
On Mon, Mar 29, 2021 at 3:35 AM Ulrich Windl <
ulrich.wi...@rz.uni-regensburg.de> wrote:
> >>> d tbsky schrieb am 29.03.2021 um 04:01 in Nachricht
> :
> > Hi:
> >since the vm start/stop at once will consume disk IO, I want to
> > start/stop the vm
> > one‑by‑one with delay.
>
> I'm surprised
>>> Antony Stone schrieb am 29.03.2021 um
10:30 in
Nachricht <202103291030.56200.antony.st...@ha.open.source.it>:
> On Monday 29 March 2021 at 09:03:10, Ulrich Windl wrote:
>
>> >> So, that would be an extra parameter to the resource definition in
>> >> cluster.cib?
>> >>
>> >> Change:
>> >>
>>> d tbsky schrieb am 29.03.2021 um 04:01 in Nachricht
:
> Hi:
>since the vm start/stop at once will consume disk IO, I want to
> start/stop the vm
> one‑by‑one with delay.
I'm surprised that in these days of fast disks and SSDs this is still an
issue.
Maybe don't delay the start, but limit
>>> Reid Wahl schrieb am 28.03.2021 um 00:42 in Nachricht
:
> On Sat, Mar 27, 2021 at 4:28 PM Strahil Nikolov
> wrote:
>
>> I had to tune the fence_ipmi recently on some older HPE blades. The
>> default settings were working, but also returning some output about
>> problems negotiating the
On Monday 29 March 2021 at 09:03:10, Ulrich Windl wrote:
> >> So, that would be an extra parameter to the resource definition in
> >> cluster.cib?
> >>
> >> Change:
> >>
> >> primitive Asterisk asterisk meta migration-threshold=3 op monitor
> >> interval=5 timeout=30 on-fail=restart
>>> Andrei Borzenkov schrieb am 27.03.2021 um 06:37 in
Nachricht <7c294034-56c3-baab-73c6-7909ab554...@gmail.com>:
> On 26.03.2021 22:18, Reid Wahl wrote:
>> On Fri, Mar 26, 2021 at 6:27 AM Andrei Borzenkov
>> wrote:
>>
>>> On Fri, Mar 26, 2021 at 10:17 AM Ulrich Windl
>>> wrote:
>>>
>>> Reid Wahl schrieb am 26.03.2021 um 20:39 in Nachricht
:
> If you have an enterprise support agreement, be sure to also explore
> whether your vendor supports one and not the other. For example, Red Hat
> currently supports pgsql but not PAF (though there is an open BZ to add
> support for
>>> Reid Wahl schrieb am 26.03.2021 um 23:28 in Nachricht
:
...
>> So, that would be an extra parameter to the resource definition in
>> cluster.cib?
>>
>> Change:
>>
>> primitive Asterisk asterisk meta migration-threshold=3 op monitor
>> interval=5
>> timeout=30 on-fail=restart
>>> Andrei Borzenkov schrieb am 26.03.2021 um 14:26 in
Nachricht
:
> On Fri, Mar 26, 2021 at 10:17 AM Ulrich Windl
> wrote:
>>
>> >>> Andrei Borzenkov schrieb am 26.03.2021 um 06:19
in
>> Nachricht <534274b3‑a6de‑5fac‑0ae4‑d02c305f1...@gmail.com>:
>> > On 25.03.2021 21:45, Reid Wahl wrote:
>>
Reid Wahl
>
> An order constraint set with kind=Serialize (which is mentioned in the first
> reply to the thread you linked) seems like the most logical option to me. You
> could serialize a set of resource sets, where each inner set contains a
> VirtualDomain resource and an
An order constraint set with kind=Serialize (which is mentioned in the
first reply to the thread you linked) seems like the most logical option to
me. You could serialize a set of resource sets, where each inner set
contains a VirtualDomain resource and an ocf:heartbeat:Delay resource.
5.3.1.
24 matches
Mail list logo
