Skip to content

Update exposer's Redis retry exception handling - #35

Open
aokhovat wants to merge 1 commit into
bloomberg:mainfrom
aokhovat:exposer-redis-error
Open

Update exposer's Redis retry exception handling#35
aokhovat wants to merge 1 commit into
bloomberg:mainfrom
aokhovat:exposer-redis-error

Conversation

@aokhovat

@aokhovat aokhovat commented Mar 5, 2026

Copy link
Copy Markdown
Contributor

Description

  • Avoid Errors: During handling of the above exception, another exception occurred
  • Distinguish Redis ConnectionError as warning, so alerts on log monitoring can catch "errors".

Type of Change

  • Bugfix
  • New Feature
  • Breaking Change
  • Refactor
  • Documentation
  • Other (please describe)

Checklist

  • I have read the contributing guidelines
  • Existing issues have been referenced (where applicable)
  • I have verified this change is not present in other open pull requests
  • Functionality is documented
  • [X ] New code contribution is covered by automated tests

@aokhovat
aokhovat requested a review from a team as a code owner March 5, 2026 19:34
if not rs_conn.ping():
raise Exception("connection established but redis is not pinging")
return rs_conn
except redis.exceptions.ConnectionError as ex:

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What non-ConnectionError exceptions are we expecting to catch here though? If its just the ping check above, could we not just remove that exception and replace it with a log, sleep & continue?

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.

2 participants