storm-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dinesh Babu K G <dinesh....@gmail.com>
Subject Re: When to use MemoryMapState while performing a persistentAggregate in Trident?
Date Wed, 26 Oct 2016 09:17:02 GMT
Thanks Arun. Does storm recommend any specific in-memory store for
persistence? I see memached given as an example in the storm documentation
but no word about other stores.

On Wed, Oct 26, 2016 at 2:37 PM Arun Mahadevan <arunm@apache.org> wrote:

>
>
> MemoryMapState is more for testing and does not provide any persistence.
> It uses a HashMap internally. If you want persistence you need use the one
> based on redis or other.
>
>
>
> Thanks,
>
> Arun
>
>
>
> *From: *Dinesh Babu K G <dinesh.ddt@gmail.com>
> *Reply-To: *"user@storm.apache.org" <user@storm.apache.org>
> *Date: *Wednesday, October 26, 2016 at 2:31 PM
> *To: *"user@storm.apache.org" <user@storm.apache.org>
> *Subject: *When to use MemoryMapState while performing a
> persistentAggregate in Trident?
>
>
>
> Hi all,
>
>
>
> I would like to understand when to use MemoryMapState v/s using a state
> that is based on a in-memory data store (like memcached, redis or
> aerospike) while doing persistentAggregate() in Trident.
>
>
>
> Are there any pros & cons between the two approaches?
>
>
>
> Thanks,
>
> Dinesh Babu K.G
>

Mime
View raw message