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
Given a list of urls or a string containing multiple urls to the Kombu Connection object, I see that kombu currently supports switching between broker urls for connection failovers i.e. when trying to create connections.
For Operational failovers like publish failures, it retries the same url according the given retry_policy. We were wondering if kombu has any plans to support switching connections to other broker urls as specified by the failover_strategy and try to publish to the new broker url.
This would be an additional feature that would be supported by a new variable.
Solution:
I played around with the solution a bit and found that adding self.maybe_switch_next() line at https://github.com/celery/kombu/blob/main/kombu/connection.py#L577 would solve the issue. But, I am not completely sure if this needs to be added anywhere else as well.
Ofc, the above needs to be tested. Let me know if kombu already has plans to implement such option. Thanks.
The text was updated successfully, but these errors were encountered:
Good evening folks,
Given a list of urls or a string containing multiple urls to the Kombu Connection object, I see that kombu currently supports switching between broker urls for connection failovers i.e. when trying to create connections.
For Operational failovers like publish failures, it retries the same url according the given retry_policy. We were wondering if kombu has any plans to support switching connections to other broker urls as specified by the failover_strategy and try to publish to the new broker url.
This would be an additional feature that would be supported by a new variable.
Solution:
I played around with the solution a bit and found that adding self.maybe_switch_next() line at https://github.com/celery/kombu/blob/main/kombu/connection.py#L577 would solve the issue. But, I am not completely sure if this needs to be added anywhere else as well.
Ofc, the above needs to be tested. Let me know if kombu already has plans to implement such option. Thanks.
The text was updated successfully, but these errors were encountered: