-
Notifications
You must be signed in to change notification settings - Fork 217
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
New offset commiting mechanism with lag raporting #8
Comments
pjagielski
added a commit
that referenced
this issue
May 19, 2015
pjagielski
added a commit
that referenced
this issue
May 19, 2015
pjagielski
added a commit
that referenced
this issue
May 19, 2015
pjagielski
added a commit
that referenced
this issue
May 19, 2015
pjagielski
added a commit
that referenced
this issue
May 19, 2015
pjagielski
added a commit
that referenced
this issue
May 19, 2015
pjagielski
added a commit
that referenced
this issue
May 19, 2015
#8 new offset commit mechanism with lag reporting
pjagielski
added a commit
that referenced
this issue
May 19, 2015
in 0.7.2 |
Ejden
added a commit
that referenced
this issue
Jul 19, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Current offset commiting mechanism in extreme cases (quick output rate decrease) might lead to situations, when we commit events that might have not been sent. If sender is be okay - this is fine, but in case of any sender bugs, we will acknowledge unsent event.
This change might lead to situation, when lag is growing, as we don't commit messages. There should be some graphite metric (and log message) that we can observe and react.
The text was updated successfully, but these errors were encountered: