It seems that the local job runner spawns multiple threads to do work
and perhaps it's getting caught up in a spot where the map is being
modified in the StackElement.getTrapCollector method while being
closed in the StackElement.closeTraps() method.
I haven't seen this when running on the cluster although it doesn't
happen locally very often either.. typical of a thread related bug so
I can't say if this is a bug only in local mode or not. I am running
Cascading 1.1.1
Thanks!
Amit
Strange. Didn't realize LocalJobRunner would spawn multiple threads. I'll see what I can do for the next maint release.
cheers,
chris
> --
> You received this message because you are subscribed to the Google Groups "cascading-user" group.
> To post to this group, send email to cascadi...@googlegroups.com.
> To unsubscribe from this group, send email to cascading-use...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/cascading-user?hl=en.
>
--
Chris K Wensel
ch...@concurrentinc.com
http://www.concurrentinc.com
http://www.concurrentinc.com/downloads/
Sorry for the delay.
cheers,
chris
On May 25, 2010, at 3:24 PM, ANithian wrote: