[infinispan-dev] Cache stopping

[Galder Zamarreño]

Extending to dev list...

On Oct 18, 2012, at 4:32 PM, Vladimir Blagojevic <vblagoje at redhat.com> wrote:

> On 12-10-18 5:56 AM, Galder Zamarreño wrote:
>> On Oct 17, 2012, at 11:44 PM, Vladimir Blagojevic <vblagoje at redhat.com> wrote:
>> 
>>> Hey Galder,
>>> 
>>> I've noticed that some of the Map/Reduce tasks were failing due to CacheRemoveCommand timeouts.
>> Hmmm, who's calling remove cache?
> MapReduceTask is calling it when it cleans up and destroys temp cache.

Ok.

>>> I've noticed that sometimes cache stop command takes longer that default rpc timeout and was wondering why might be the cause?
>> Thread dumps? Logs?
> I'll take a look, no problem.
> 
>> 
>>> If there is nothing to be done for cache stopping timeout does it make sense to have an option of CacheRemoveCommand being asynchronous?
>> Well, before you consider that you need to figure out why remove cache is called, and if it's really needed.
>> 
> It is needed to remove tmp cache that MapReduceTask used for intermediate values.

Ok. At which point does it get called? When the cache stops?

And what would the effects be if all nodes deleted the temporary cache except one of them? What would be the implications of this?

> 
> Cheers,
> Vladimir
> 


--
Galder Zamarreño
galder at redhat.com
twitter.com/galderz

Project Lead, Escalante
http://escalante.io

Engineer, Infinispan
http://infinispan.org