Tickets and Pool Default Behaviour

General discussions and questions.
Post Reply
Anti-Distinctlyminty
Posts: 23
Joined: Sat Jan 08, 2022 4:15 pm

Tickets and Pool Default Behaviour

Post by Anti-Distinctlyminty »

(Related other thread: viewtopic.php?t=3513)

I'm having trouble working out exactly how the ticketing & services works with hosts & pools.
Afanasy's behaviour seems to be to allow everything. For example, if I have a job that consumes one ticket and my farm has no tickets or services defined at all, then every host will be used. Here's an actual example of that in action:
afwatch_98xjMy4kjD.png
afwatch_98xjMy4kjD.png (89.9 KiB) Viewed 5123 times

As you can see, even though no tickets or services are defined, Afanasy assumes that all hosts can be used (which is the tickets are in an italic font?), which is not what I thought would happen.
Another example is where I place a single REDSHIFT ticket on a host:
explorer_XeD1CH9NgG.png
explorer_XeD1CH9NgG.png (90.25 KiB) Viewed 5123 times
And as you can see, it just renders Redshift and consumed REDSHIFT tickets on every host, even though only one has a REDHISFT ticket.

So, if I'm trying to restrict the Redshift rendering to that single host, how do I do that? Is there any way to tell Afanasy that it can only use hosts that have tickets/services explicitly defined?
User avatar
timurhai
Site Admin
Posts: 916
Joined: Sun Jan 15, 2017 8:40 pm
Location: Russia, Korolev
Contact:

Re: Tickets and Pool Default Behaviour

Post by timurhai »

Hi! Sorry for a delay. I was away.
pc1928 does know nothing about redshift. It itself and all it parent pools has no tickets/services settings. Host does not ask any other hosts for tickets/services settings, it just asks only parent pools for it.
So you should configure parent pool(s).
Configure services at the root pool at first. Do not create redshift on the root poll. Create redshift service just only on pc1921.
Timur Hairulin
CGRU 3.3.1, Ubuntu 20.04, 22.04, MS Windows 10 (clients only).
Anti-Distinctlyminty
Posts: 23
Joined: Sat Jan 08, 2022 4:15 pm

Re: Tickets and Pool Default Behaviour

Post by Anti-Distinctlyminty »

timurhai wrote: Tue Jun 13, 2023 9:51 am Hi! Sorry for a delay. I was away.
No problem. I'm grateful for your input.

I'll try to explain in a slightly different way.

So, imagine I have the following setup:
* root pool with no settings
* pc01, under the root pool
* redshift pool, with 2xREDSHIFT tickets and a generic service (to do redshift command line rendering)
* pc02 and pc03 under the /redshift pool

Code: Select all

/ 
│  pc01
│
└─ /redshift (tickets: REDSHIFT x2, services: generic)
        pc02
        pc03
Now, if I were to submit a generic job that consumes a REDSHIFT ticket, then every pc would start rendering, including pc01.
pc01 has no REDSHIFT tickets, so why does it try to render?
The only way I can stop pc01 trying to render it is to set it up as follows:

Code: Select all

/ (tickets: REDSHIFT x0)
│  pc01
│
└─ /redshift (tickets: REDSHIFT x2, services: generic)
        pc02
        pc03
I must explicitly set all tickets to 0 on the root. If I do not pc01 consumes a REDSHIFT ticket even though there is not one available.
Post Reply