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.

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

Add better detection of failed storage target #13

Open
BenFradet opened this issue Jul 3, 2017 · 1 comment
Open

Add better detection of failed storage target #13

BenFradet opened this issue Jul 3, 2017 · 1 comment
Assignees

Comments

@BenFradet
Copy link
Contributor

from snowplow/snowplow#2918:

Currently the Kinesis Elasticsearch Sink is far to quick to decide that the data is at fault and will then simply pass it of to the bad path. We need two tiers of detection:
On entering the emitter ascertain whether the storage target is available for bulk event indexing.
On any failure to bulk index we need to ascertain exactly what caused that failure.

@alexanderdean
Copy link
Member

Scheduling as a priority given that this is a data loss issue.

/cc @jbeemster

@chuwy chuwy modified the milestones: Version 0.11.0, Version 1.0.0 - New bad rows, cats, circe Feb 10, 2020
@chuwy chuwy modified the milestones: Version 1.0.0 - New bad rows, cats, circe, Version 0.12.0 Feb 24, 2020
@chuwy chuwy removed this from the Version 1.0.0 - New bad rows, cats, circe milestone Mar 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants