You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue #307 was closed but the issue it refers to #1066 never solved the mutiple subnet feature.
The Yaml allows for multiplt subnets per queue, but at creation it is refused.
Create multiple queues in different subnets is also refused.
I understand the need for low latency when different jobs communicate to each other, but if the use case is just many compute jobs with or without dependencies, access to more instances accorss AZs is more important and is at the moment impossible.
The text was updated successfully, but these errors were encountered:
Issue #307 was closed but the issue it refers to #1066 never solved the mutiple subnet feature.
The Yaml allows for multiplt subnets per queue, but at creation it is refused.
Create multiple queues in different subnets is also refused.
I understand the need for low latency when different jobs communicate to each other, but if the use case is just many compute jobs with or without dependencies, access to more instances accorss AZs is more important and is at the moment impossible.
The text was updated successfully, but these errors were encountered: