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
Context
We have an automated workflow that we are in the process of applying to a large chunk of our MDS+ database. At the moment the going is slow because we limit the amount of concurrent instances of this workflow to avoid overloading our MDS+ server.
The workflow is launched by a service account, and if the MDS+ server would automatically hold concurrent connections from this service account when a certain threshold is reached, we could scale-up without having to worry about our MDS+ server.
Question
Is it possible to automatically hold connection attempts for a specific user once a threshold of connections has already been opened by this user. Note that we want to hold them and not reject them as that would cause unacceptable failures in our workflow downstream.
The text was updated successfully, but these errors were encountered:
AreWeDreaming
changed the title
Is it possible to limit the amount of concurrent connections a specific user
Is it possible to limit the amount of concurrent connections of a specific user
May 14, 2024
My initial guess (perhaps wrong) is that is not possible in current versions of MDSplus. However, I will investigate and post a definitive answer in the next day or two.
If limiting concurrent connections per user can't be done at the moment, we might be able to add that capability as a new feature. That too would require some investigation to determine feasibility.
My colleagues have confirmed that MDSplus presently cannot limit concurrent mdsip connections per user. (Using the standard features of Linux, it is possible to apply "rate limiting" to all connections, but that likely isn't what is needed for your automated workflow).
If you decide that this is a feature that MDSplus should have, let us know if this issue should be upgraded to a feature request.
Affiliation
General Atomics/DIII-D
Context
We have an automated workflow that we are in the process of applying to a large chunk of our MDS+ database. At the moment the going is slow because we limit the amount of concurrent instances of this workflow to avoid overloading our MDS+ server.
The workflow is launched by a service account, and if the MDS+ server would automatically hold concurrent connections from this service account when a certain threshold is reached, we could scale-up without having to worry about our MDS+ server.
Question
Is it possible to automatically hold connection attempts for a specific user once a threshold of connections has already been opened by this user. Note that we want to hold them and not reject them as that would cause unacceptable failures in our workflow downstream.
The text was updated successfully, but these errors were encountered: