storm-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Lakshmanan Muthuraman <lakshma...@tokbox.com>
Subject Re: external/storm-elasticsearch - upgrade requested
Date Fri, 01 Apr 2016 18:32:25 GMT
1."ES-Hadoop also provides a good support of time-based index-rolling which
is great for logging-type use-cases."
2. If trident is not needed, ES-Hadoop is simple enough to use.

The above is a big usecase for us that we are able to accomplish with
ElasticSearch-Hadoop


On Wed, Mar 30, 2016 at 11:50 AM, Aaron.Dossett <Aaron.Dossett@target.com>
wrote:

> Size of cluster is TBD, but we ultimately want to ingest tens of millions
> of events per minute.
>
> On Mar 30, 2016, at 1:31 PM, Tech Id <tech.login.id2@gmail.com> wrote:
>
>
> Hey Aaron,
>
> Do you have a target throughput that you want to achieve through ES-Bolt ?
> How many storm machines you plan to run your topology on?
>
> Thanks
>
>
> On Wed, Mar 30, 2016 at 10:53 AM, Aaron.Dossett <Aaron.Dossett@target.com>
> wrote:
>
>> In setting up a storm -> ES topology today I ran across that same fact.
>> The EsIndexBolt is also synchronous mode only, with no option for asynch.
>> This week I’ll evaluate adding batching/async to storm-elasticsearch or
>> switching to ES-hadoop for my use use cases.
>>
>> From: Tech Id <tech.login.id2@gmail.com>
>> Reply-To: "user@storm.apache.org" <user@storm.apache.org>
>> Date: Wednesday, March 30, 2016 at 10:24 AM
>> To: "user@storm.apache.org" <user@storm.apache.org>
>> Subject: Re: external/storm-elasticsearch - upgrade requested
>>
>> One thing I see in favor of the elasticsearch-hadoop is that it provides
>> batching without Trident.
>>
>
>

Mime
View raw message