novaBBS - comp.os.vms - Re: stopping and starting failover queues

stopping and starting failover queues

<sfdg4b$2lt$1@gioia.aioe.org>

https://www.novabbs.com/computers/article-flat.php?id=16531&group=comp.os.vms#16531

Path: i2pn2.org!i2pn.org!aioe.org!UfCmT3SC3Tdw3oTV9WuLBQ.user.46.165.242.75.POSTED!not-for-mail
From: hel...@asclothestro.multivax.de (Phillip Helbig (undress to reply)
Newsgroups: comp.os.vms
Subject: stopping and starting failover queues
Date: Mon, 16 Aug 2021 10:54:03 -0000 (UTC)
Organization: Multivax C&R
Message-ID: <sfdg4b$2lt$1@gioia.aioe.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 8bit
Injection-Info: gioia.aioe.org; logging-data="2749"; posting-host="UfCmT3SC3Tdw3oTV9WuLBQ.user.gioia.aioe.org"; mail-complaints-to="abuse@aioe.org";
X-Notice: Filtered by postfilter v. 0.9.2

by: Phillip Helbig (undr - Mon, 16 Aug 2021 10:54 UTC

Consider a queue which can run on several nodes for failover. However,
if all nodes are up, one node might be preferred. How can one force the
jobs in it to run on the preferred node? One can do stop/ queu /on on
the node where it is running, get it to fail over (repeat if necessary),
then do ENABLE AUTOSTART/QUEUES and/or START/QUEUE where it was stopped
(to get all queues running again). However, there must be a better way.

Re: stopping and starting failover queues

<4fae5027-c1ad-4a1c-b043-764f26884f4fn@googlegroups.com>

copy mid

https://www.novabbs.com/computers/article-flat.php?id=16624&group=comp.os.vms#16624

copy link Newsgroups: comp.os.vms

X-Received: by 2002:a37:989:: with SMTP id 131mr17005956qkj.472.1630206167786;
Sat, 28 Aug 2021 20:02:47 -0700 (PDT)
X-Received: by 2002:a05:620a:165a:: with SMTP id c26mr15859031qko.498.1630206167582;
Sat, 28 Aug 2021 20:02:47 -0700 (PDT)
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!proxad.net!feeder1-2.proxad.net!209.85.160.216.MISMATCH!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.os.vms
Date: Sat, 28 Aug 2021 20:02:47 -0700 (PDT)
In-Reply-To: <sfdg4b$2lt$1@gioia.aioe.org>
Injection-Info: google-groups.googlegroups.com; posting-host=190.140.8.179; posting-account=J7Az2goAAAAy7QkVPXLRTUymtqPHVvgD
NNTP-Posting-Host: 190.140.8.179
References: <sfdg4b$2lt$1@gioia.aioe.org>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <4fae5027-c1ad-4a1c-b043-764f26884f4fn@googlegroups.com>
Subject: Re: stopping and starting failover queues
From: ulloa.ed...@gmail.com (Edgar Ulloa)
Injection-Date: Sun, 29 Aug 2021 03:02:47 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

by: Edgar Ulloa - Sun, 29 Aug 2021 03:02 UTC

El lunes, 16 de agosto de 2021 a las 5:54:08 UTC-5, Phillip Helbig (undress to reply) escribió:
> Consider a queue which can run on several nodes for failover. However,
> if all nodes are up, one node might be preferred. How can one force the
> jobs in it to run on the preferred node? One can do stop/ queu /on on
> the node where it is running, get it to fail over (repeat if necessary),
> then do ENABLE AUTOSTART/QUEUES and/or START/QUEUE where it was stopped
> (to get all queues running again). However, there must be a better way.

Maybe it's not the best way but it works for me like this

Instead of sending it to the generic queue that contains the various nodes
I made the queue on the dedicated server and with that only the jobs sent to that queue will be executed on the dedicated node.
regards

Re: stopping and starting failover queues

<sgfeo6$j38$1@gioia.aioe.org>

copy mid

https://www.novabbs.com/computers/article-flat.php?id=16625&group=comp.os.vms#16625

copy link Newsgroups: comp.os.vms

Path: i2pn2.org!i2pn.org!aioe.org!xaSwvIbIP8a1lD0yeckEuA.user.46.165.242.75.POSTED!not-for-mail
From: hel...@asclothestro.multivax.de (Phillip Helbig (undress to reply)
Newsgroups: comp.os.vms
Subject: Re: stopping and starting failover queues
Date: Sun, 29 Aug 2021 07:59:02 -0000 (UTC)
Organization: Multivax C&R
Message-ID: <sgfeo6$j38$1@gioia.aioe.org>
References: <sfdg4b$2lt$1@gioia.aioe.org> <4fae5027-c1ad-4a1c-b043-764f26884f4fn@googlegroups.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 8bit
Injection-Info: gioia.aioe.org; logging-data="19560"; posting-host="xaSwvIbIP8a1lD0yeckEuA.user.gioia.aioe.org"; mail-complaints-to="abuse@aioe.org";
X-Notice: Filtered by postfilter v. 0.9.2

by: Phillip Helbig (undr - Sun, 29 Aug 2021 07:59 UTC

In article <4fae5027-c1ad-4a1c-b043-764f26884f4fn@googlegroups.com>,
Edgar Ulloa <ulloa.edgar@gmail.com> writes:

> El lunes, 16 de agosto de 2021 a las 5:54:08 UTC-5, Phillip Helbig (undress=
> to reply) escribi=C3=B3:
> > Consider a queue which can run on several nodes for failover. However,=20
> > if all nodes are up, one node might be preferred. How can one force the=
> =20
> > jobs in it to run on the preferred node? One can do stop/ queu /on on=20
> > the node where it is running, get it to fail over (repeat if necessary),=
> =20
> > then do ENABLE AUTOSTART/QUEUES and/or START/QUEUE where it was stopped=
> =20
> > (to get all queues running again). However, there must be a better way.
>
> Maybe it's not the best way but it works for me like this
>
> Instead of sending it to the generic queue that contains the various nodes=
> =20
> I made the queue on the dedicated server and with that only the jobs sent t=
> o that queue will be executed on the dedicated node.
> regards

There is no generic queue pointing to more than one specific queue; it
is a single queue on more than one node. The former is good for
failover (if one SUBMITs and programs correctly) and load distribution;
the latter is only for failover and easier to implement.

System going down in 5 minutes.

computers / comp.os.vms / Re: stopping and starting failover queues

Subject	Author
stopping and starting failover queues	Phillip Helbig (undress to reply
Re: stopping and starting failover queues	Edgar Ulloa
Re: stopping and starting failover queues	Phillip Helbig (undress to reply