-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EPH and network issues #214
Comments
This is interesting, looks like token has expired and leaser now fails requesting the blob:
|
Okay, it looks that I've missed somehow the refresher variable in token constructor, now it is working. I have now met another issue:
It is raised by this call: The code:
And I see that there are no retry attempts for those things with tokens. |
Hi! Thanks for reaching out. I'm taking a look at the information you provided and will get back to you on where the issue may be. |
I have tested work with refresher with a long idle periods and it is working fine. So this issue if a feature request to add retries to token getters/refreshers, and if possible, add some method to get EPH status if something happened inside, when starting as non-blocking. |
I'm also interested in getting some health information from an eph to include in kubernetes health probes. |
can you elaborate on this? We are also facing a similar issue with v3.5.0 where we are seeing a drop in number of events received after a day. We are using Sas token provider. I'm wondering if what we are experiencing is the related. |
Expected Behavior
Hello,
We are using pretty default eph functionality, waiting for events, while context is a global context which ends with application close.
The problem is that after some time - application stops receiving events.
Currently there are only few events per day, so periods between them can be 10-15 hours.
I can't see any way to get proper
error
fromeph
to know that we need to restart it, for example.Code:
I have started it with
tags=debug
andDEBUG_LEVEL=3
, will give more information.Actual Behavior
With the flow of time eph stops receiving events.
Environment
The text was updated successfully, but these errors were encountered: