metron-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (METRON-227) Add Time-Based Flushing to Writer Bolt
Date Thu, 21 Jul 2016 13:34:20 GMT

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

ASF GitHub Bot commented on METRON-227:
---------------------------------------

Github user cestella commented on the issue:

    https://github.com/apache/incubator-metron/pull/188
  
    There is one downside that I see, but I think it's acceptable.  We currently keep configuration
around the indexing in zookeeper so that the topology configuration can be adjusted on the
fly in a running topology.  This would externalize that and keep the tick frequency in flux,
so to change it would require a topology restart.
    
    I think that this is acceptable, but it's worth pointing out.


> Add Time-Based Flushing to Writer Bolt
> --------------------------------------
>
>                 Key: METRON-227
>                 URL: https://issues.apache.org/jira/browse/METRON-227
>             Project: Metron
>          Issue Type: Bug
>            Reporter: Domenic Puzio
>            Assignee: Ajay Yadav
>              Labels: 0.2.1BETA
>             Fix For: 0.2.1BETA
>
>
> We need to change the BulkMessageWriterBolt and BulkWriterComponent to use time-based
flushing when writing data to Elasticsearch or Solr.
> Currently, we set a batch size, and the Writer waits for that number of tuples to build
up; however, Storm has a timeout value that prevents it from waiting for too long. If the
Writer does not get the batch size before the timeout, then it recycles the tuples through
the topology. In addition, Storm only allows so many pending messages that have not been acked
- if too many messages are waiting for the bulk Writer, then it will recycle them through
the topology. This is not desired behavior and directly impacts the performance of this Writer.
We would like to be able to specify a unit of time for which the topology would flush, writing
the data it's currently holding to Elasticsearch or Solr even if the batch size is not met.



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

Mime
View raw message