-
Notifications
You must be signed in to change notification settings - Fork 287
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
Improve and clarify error retry logic #956
Labels
Comments
No changes in uploader.go yet
Not addressed yet. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem
Solution
server.error_retry_period_hours
configuration parameter that will work as default for all destinations (streaming and batch). Default value: 24 hourserror_retry_period_hours
parameter that will override default value on destination level.uploader.go unify fallback logic:
error_retry_period_hours
passes. (seems that currently for parsingErrors and failedEvents we flood fallback logs with copies of the same events on each uploader run)error_retry_period_hours
passes jitsu needs to archive incoming file and cleanup statusstreaming.go:
IsConnectionError
check – retry all errorsserver.streaming_retry_delay_minutes
parameter. Default: 1server.error_retry_period_hours
passes - stop retries and Fallback error events.AccountResult
and must be removed from there.documentation:
The text was updated successfully, but these errors were encountered: