Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Handling large messages, do we drop them? Log them to disk? Callback in confirm? #402

Open
haf opened this issue Mar 13, 2019 · 2 comments
Open

Handling large messages, do we drop them? Log them to disk? Callback in confirm? #402

haf opened this issue Mar 13, 2019 · 2 comments
Labels
question

Comments

@haf
Copy link
Member

haf commented Mar 13, 2019 •
edited
Loading

For example, we have Rutta ingesting messages over HTTP and once in a while someone sends a large message >134 KiB, which causes the Stackdriver target to crash and restart, until all too-large messages have been crash-rejected (since we don't have a "will" in that target).
@haf haf added the question label Mar 13, 2019
@lust4life
Copy link
Contributor

what is the use case? seems disk or queue are something like target. is it for when target can not catch up with log message producer ?

@haf
Copy link
Member Author

haf commented Mar 14, 2019

Updated description

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@haf @lust4life