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
Is your feature request related to a problem? Please describe.
Currently mirth handles polling on a server level. It would be super nice if we can specify which server is polling per channel to allow for better resource utilization when clustering servers together.
Describe your use case
Polling is handled at a server level thus if there are multiple servers in a cluster all polling channels are going to be running on server A. In our use case we have a large majority of channels doing some sort of polling. This cause one server to handle a large majority of the work and the other servers handling very little. It would be helpful if in some way we can specify channel 1 poll on server A, channel 2 poll on server B.
Describe alternatives you've considered
Seems like the only way to accomplish this is to separate the mirth instances and not have them clustered together but completely independent.
Additional context
Mirth clustering solution is more of a failover option then a true resource load-balancing solution in it current iteration.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Currently mirth handles polling on a server level. It would be super nice if we can specify which server is polling per channel to allow for better resource utilization when clustering servers together.
Describe your use case
Polling is handled at a server level thus if there are multiple servers in a cluster all polling channels are going to be running on server A. In our use case we have a large majority of channels doing some sort of polling. This cause one server to handle a large majority of the work and the other servers handling very little. It would be helpful if in some way we can specify channel 1 poll on server A, channel 2 poll on server B.
Describe alternatives you've considered
Seems like the only way to accomplish this is to separate the mirth instances and not have them clustered together but completely independent.
Additional context
Mirth clustering solution is more of a failover option then a true resource load-balancing solution in it current iteration.
The text was updated successfully, but these errors were encountered: