[infinispan-issues] [JBoss JIRA] (ISPN-4453) MapReduceTask#executeAsynchronously() isn't asynchronous

RH Bugzilla Integration (JIRA) issues at jboss.org
Thu Jul 10 00:06:25 EDT 2014


    [ https://issues.jboss.org/browse/ISPN-4453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12983709#comment-12983709 ] 

RH Bugzilla Integration commented on ISPN-4453:
-----------------------------------------------

Dave Stahl <dstahl at redhat.com> changed the Status of [bug 1116979|https://bugzilla.redhat.com/show_bug.cgi?id=1116979] from MODIFIED to ON_QA

> MapReduceTask#executeAsynchronously() isn't asynchronous
> --------------------------------------------------------
>
>                 Key: ISPN-4453
>                 URL: https://issues.jboss.org/browse/ISPN-4453
>             Project: Infinispan
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 6.0.2.Final
>            Reporter: Rich DiCroce
>            Assignee: Vladimir Blagojevic
>             Fix For: 7.0.0.Alpha5
>
>
> Quote from the linked forum thread:
> {quote}
> MapReduceTask#executeAsynchronously() doesn't actually do anything asynchronously. It just returns a MapReduceTaskFuture containing a Callable that calls execute(). The only place I see that Callable being called is in MapReduceTaskFuture#get().
>  
> In other words, the task isn't actually started until you call Future#get(), which isn't asynchronous at all! On top of that, MapReduceTaskFuture extends AbstractInProcessFuture, which "implements" the get(long, TimeUnit) method by just calling get(). Which means that MapReduceTaskFuture doesn't respect the timeout parameters and will just run until it completes.
> {quote}



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)


More information about the infinispan-issues mailing list