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
Many operations in the orchestrator need the members in the service registry to be sorted based on the number of locks they have available. One very optimal way to do this would be to keep track of a list of members for each number of locks up to the max (e.g. if max locks is 3, then there would be four lists: 0, 1, 2, 3). Then when a lock is acquired or given back the member is just moved from one list to the other.
The text was updated successfully, but these errors were encountered:
Many operations in the orchestrator need the members in the service registry to be sorted based on the number of locks they have available. One very optimal way to do this would be to keep track of a list of members for each number of locks up to the max (e.g. if max locks is 3, then there would be four lists: 0, 1, 2, 3). Then when a lock is acquired or given back the member is just moved from one list to the other.
The text was updated successfully, but these errors were encountered: