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
When upgrading from Aeron v1.41.3 to v1.44.6, we observed a change in the behavior of the Client Conductor's error handling.
In v1.41.3, when the Media Driver (aeronmd) shuts down, the error_handler is called every 0.5 seconds to report the lost connection. However, in v1.44.6, the error_handler is called in a tight loop, resulting in a continuous stream of "MediaDriver has been shutdown" messages. This creates excessive log output (we log within the error_handler)
Questions
1). Is this change intentional or are we doing something wrong?
2). How can we reduce the frequency of error_handler calls?
Is there a way to apply a backoff strategy to the frequency of error_handler calls when the Media Driver goes down?
Alternatively, is the expectation that such a backoff strategy should be implemented by the user within the error_handler?
Steps to Reproduce
1). Start a local Media Driver instance with the following script:
[critical] Aeron error: MediaDriver has been shutdown
[critical] Aeron error: MediaDriver has been shutdown
[critical] Aeron error: MediaDriver has been shutdown
...
Greatly appreciate any help or advice here!
The text was updated successfully, but these errors were encountered:
Description
When upgrading from Aeron v1.41.3 to v1.44.6, we observed a change in the behavior of the Client Conductor's error handling.
In v1.41.3, when the Media Driver (aeronmd) shuts down, the error_handler is called every 0.5 seconds to report the lost connection. However, in v1.44.6, the error_handler is called in a tight loop, resulting in a continuous stream of "MediaDriver has been shutdown" messages. This creates excessive log output (we log within the error_handler)
Questions
1). Is this change intentional or are we doing something wrong?
2). How can we reduce the frequency of error_handler calls?
Steps to Reproduce
1). Start a local Media Driver instance with the following script:
2). Run the following application code:
3). Kill the Media Driver
4). Observe continuous stream of error messages:
Greatly appreciate any help or advice here!
The text was updated successfully, but these errors were encountered: