pmap behavior with err_stop = true #7808
Closed
simonster opened this Issue on Aug 1, 2014 · 3 comments
Projects

Decision Needed in Julia
Labels
decision
parallel
Milestone
 
0.6.0
Assignees
No one assigned
4 participants
@simonster
@amitmurthy
@samoconnor
@StefanKarpinski
Notifications

You’re not receiving notifications from this thread.
@simonster
The Julia Language member
simonster commented on Aug 1, 2014

Right now, the code:

pmap((x)->(sleep(x); println(x); error("error")), 1:2; err_stop=true)

gives output

        From worker 2:  1
exception on 2: ERROR: error
 in error at error.jl:21
 in anonymous at none:1
 in anonymous at multi.jl:855
 in run_work_thunk at multi.jl:621
 in anonymous at task.jl:855
        From worker 3:  2
exception on 3: ERROR: error
 in error at error.jl:21
 in anonymous at none:1
 in anonymous at multi.jl:855
 in run_work_thunk at multi.jl:621
 in anonymous at task.jl:855
2-element Array{Any,1}:
 ErrorException("error")
 ErrorException("error")

If a worker throws an error, maybe pmap should interupt the other workers immediately rather than waiting for them to finish their jobs? Also, if err_stop = true, maybe the error should be rethrown?
@simonster simonster added decision parallel labels on Aug 1, 2014
@amitmurthy
The Julia Language member
amitmurthy commented on Sep 4, 2014

Sounds right. Both your suggestions are consistent with what is expected when err_stop = true
@simonster simonster referenced this issue on Sep 1, 2015
Closed
RemoteException not re-thrown by pmap() #12908
@samoconnor
samoconnor commented on Oct 14, 2015

See fix here #12943
@multidis multidis referenced this issue in JuliaOpt/Optim.jl on Nov 23, 2015
Closed
Linesearch output in teh/constrained branch #151
@StefanKarpinski StefanKarpinski added this to the 0.6.0 milestone on Sep 13
@amitmurthy
The Julia Language member
amitmurthy commented 28 days ago

err_stop has been replaced with on_error and retry_n keyword args in 0.5
@amitmurthy amitmurthy closed this 28 days ago