-
Notifications
You must be signed in to change notification settings - Fork 843
Event subscriptions failing if one of them is not correct #3291
Comments
@orimarti thanks a bunch for reporting this! I can confirm that Marathon fails to send events to the rest of the registered http endpoints if one of them is malformed. Case 1In this case, one of the registered endpoints (http://host:3535) doesn't respond to requests. Marathon retries to send the event data to this endpoint and proceeds with the rest as intended. All good. Config
Log
Case 2In the second case, one of the registered endpoints (host:3535) is malformed. Marathon fails to send the event data to the rest of the registered http endpoints due to an Config
Log
I consider this as a minor issue as it shouldn't break "properly" configured setups but some kind of startup validation as well as exception handling would be nice. Pull request welcome! |
Fixes #3291 | Event subscriptions validation
It seems that if a host is not correct, marathon fails to send the subscriptions to all the next nodes in the subscription list.
For example, if I have the next subscription list, where the second one is not correct:
The first host on the list is receiving the events and the third one is not receiving it.
I'm seeing this logs on marathon:
The text was updated successfully, but these errors were encountered: