Does anyone have a workaround for running multiple workers with UBL?
Already the workers using Remote Control require different ports so they don’t clash, the default is 5054.
Redshift UBL also uses 5054, so changing the Remote Control to 5555, 5556, 5557, 5558 etc should allow the UBL to run on 5054.
But each instance wants to connect to UBL on 5054, so only one Worker instance gets the UBL license.
I’m not sure if the UBL differs from the standard license which is licensed per host?
Ideally the secondary workers can use the UBL license from the first worker, I’m not sure if this is possible or the worker can see the license from the first. Just wondering if anyone else found a workaround for this?
Thanks
Ant
If you’re not aware, UBL is licensed per worker, so running two worker instances on the same machine would consume twice as much UBL.
Running concurrent tasks on one worker avoids this. IE a machine with two GPUs can have “concurrent tasks limit” set to two, and “GPUs per task” set to one on the Redshift job. The only downside I’ve come across is that the worker won’t start working on the next job while >= 1 tasks are still working on the previous job.
I did have the same port conflict issue when using multiple worker instances, but I didn’t figure it out due to not wanting to pay more for UBL.
1 Like
cheers, glad to see I’m not the only one! cost not an issue, just hoping for a workaround. I did hope there may have been some local port forwarding workaround, but i guess it all goes out the same port…