[
https://issues.apache.org/jira/browse/NIFI-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16300518#comment-16300518
]
ASF GitHub Bot commented on NIFI-4428:
--------------------------------------
Github user vakshorton commented on the issue:
https://github.com/apache/nifi/pull/2310
@pvillard31 You are likely seeing a lot of dropped events because the
timestamps in the events are out of synch with the server clock. If your
segment granularity is set to 10 minutes, late window set to 1 minute and the
event timestamp is more than 11 minutes out of synch with the server time, that
data is considered "late" (since the target index task will have closed). What
kind of ingestion rates on what input volume? Are you seeing a lot of queuing?
Can you check your middle manager configuration/resource allocation?
> Implement PutDruid Processor and Controller
> -------------------------------------------
>
> Key: NIFI-4428
> URL: https://issues.apache.org/jira/browse/NIFI-4428
> Project: Apache NiFi
> Issue Type: New Feature
> Affects Versions: 1.3.0
> Reporter: Vadim Vaks
> Assignee: Matt Burgess
>
> Implement a PutDruid Processor and Controller using Tranquility API. This
> will enable Nifi to index contents of flow files in Druid. The implementation
> should also be able to handle late arriving data (event timestamp points to
> Druid indexing task that has closed, segment granularity and grace window
> period expired). Late arriving data is typically dropped. Nifi should allow
> late arriving data to be diverted to FAILED or DROPPED relationship. That
> would allow late arriving data to be stored on HDFS or S3 until a re-indexing
> task can merge it into the correct segment in deep storage.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
