[ 
https://issues.apache.org/jira/browse/FLUME-2390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14191759#comment-14191759
 ] 

Benjamin Fiorini edited comment on FLUME-2390 at 10/31/14 12:49 PM:
--------------------------------------------------------------------

Duplicate of FLUME-2254, which has some hints to solve this in the 
ElasticSearch sink.
We had to implement something like this, because if for some reason a malformed 
message (on the ES point of view) get in the queue, then it will get stuck in 
the channel forever. The only solution then is to delete the entire channel and 
losing A LOT of data.


was (Author: bfiorini):
Duplicate of FLUME-2254, which has some hints to solve this in the 
ElasticSearch sink.
We had to implement something like this, because if for some reason a malformed 
message (on the ES point of view) get in the queue, then it will get stuck in 
the channel forever. The only solution then is to delete the entire channel.

> Flume-ElasticSearch Data gets posted multiple times when one of the event 
> fail validation at elastic search sink for JSON Data
> ------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: FLUME-2390
>                 URL: https://issues.apache.org/jira/browse/FLUME-2390
>             Project: Flume
>          Issue Type: Bug
>          Components: Sinks+Sources
>    Affects Versions: v1.4.0
>         Environment: CDH4.5
>            Reporter: Deepak Subhramanian
>
> Hi,
> I am using Elastic Search Sink to post JSON data. I used the temporary fix 
> mentioned in https://issues.apache.org/jira/browse/FLUME-2126 to get JSON 
> data posted to elastic search. When one of the message fail validation at 
> ElasticSearch mapping for JSON data ( For example - getting empty message) , 
> Flume seems to post the entire batch again and again until I restart Flume.  
> Because of that no of events went from an avg of 100 to avg of 2000 per 10 
> minutes. As a temporary fix I set a header in my FlumeHTTP Source for non 
> valid JSON and used a interceptor to send data to multiple ESSINKS which has 
> different index names. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to