Skip to content

Conversation

@crtschin
Copy link

Closes #49

One issue with the current setup is that any action to elastic is always retried endlessly. This is problematic with logging, which (IMO) shouldn't be the reason an application hangs.

The hanging occurs because the cleanup (called on exit of the scope of withLogger in the calling thread) of a bulk logger attempts to flush it's buffer to the log-medium, in this case elastic which may be unavailable, doing a step & sync. This fixes it by allowing to specify a retry policy a la retry, that's used when attempting the action.

Introduces our own exceptions for the following error cases
- Not being able to connect to ES when determining versions.
- Not being able to parse version numbers.
- Not utilizing a secure connection on attempting to login.
@crtschin crtschin requested a review from arybczak October 27, 2025 09:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

withElasticSearchLogger continues past (Logger -> IO r) action when EL is unreachable

2 participants