I am in the process of deploying new render nodes to replace some old ones, but I don’t want to replace the old until I am sure that I am happy with the new. So I changed the padding on our render nodes to reflect our new schema that calls for three zero padding, versus two.
What I have found is that there is no way for these machines to co-exist in deadline. If I add them to a limit or power group, they end up replacing the corresponding two zero padded named machines.
Any ideas?
Deadline uses the Worker’s name as the unique key in the database. That name is the hostname of the machine, and if there are multiple Workers on the machine then it appends the Worker’s name to the end.
So rendernode and rendernode-01 are two Workers running on a computer named rendernode.
All that to say - are the names formatted exactly as you’ve said, or have they got a hyphen in place? I know we compare the whole Worker name, not just the first couple characters. 
Do both Workers appear in the Worker list in the Monitor? And which version of Deadline are you running?
No. The host name is render001 and render01, render001 is replacing render01, and is to be decommissioned soon. So they are newly spun up machines each running a single worker.
I do not know if this is a database issue, or literally a UI/UX issue with Monitor.
Weird! So both render01 and render001 show up in the Monitor’s Worker panel (which pulls direct from the database) but render001 replaces render01 in the configure groups, configure limits, and so on windows?
Which version of Deadline are you running, I should be able to re-create this with some EC2 instances (famous last words)?
I’ll confirm what version I have installed tomorrow, but yes, this is the behavior I’m seeing. If I gave two machines, render001 and render01 I cannot add them both to the same limit or power management group, they’ll just replace. I’ve had the same experience with both “cgrender00x/0x” and “render00x/0x” alike, both have this odd behavior.l, it it wasn’t a one time glitch.
It was definitely happening on Monitor for Windows. I’m not sure if I saw this behavior on Linux or not.
