[ 
https://issues.apache.org/jira/browse/CRAIL-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16873034#comment-16873034
 ] 

Jonas Pfefferle commented on CRAIL-98:
--------------------------------------

David,

Can you please test this branch: 
[https://github.com/PepperJo/incubator-crail/tree/nvmf_keepalive_daemon]

It should fix the issue.

> Crail, used as temporary results storage (type2 storage), misses close from 
> TeraSort
> ------------------------------------------------------------------------------------
>
>                 Key: CRAIL-98
>                 URL: https://issues.apache.org/jira/browse/CRAIL-98
>             Project: Apache Crail
>          Issue Type: Bug
>    Affects Versions: 1.2
>            Reporter: David Crespi
>            Assignee: Jonas Pfefferle
>            Priority: Major
>
> Running the latest Crail: v1.1-7-ga6e622f
> I’m running Crail as the temporary backend storage for Terasort.
> After each section (TeraGen, TeraSort, TeraVerify)
> the program waits until a Cntl-C is given, then moves on to the next
> section. 
>  
> Here’s a small snippet of the output.  Terasort waits where the
> bolded “Number of records” is listed, until the ^c is given.  Each of the 
> three programs does the same, but the program does finish without errors.
> 19/06/18 15:13:19 DEBUG TaskSchedulerImpl: parentName: , name:TaskSet_1.0, 
> runningTasks: 1
> 19/06/18 15:13:19 INFO TaskSetManager: Finished task 1.0 in stage 1.0 (TID 3) 
> in 142 ms on 192.168.3.10 (executor 4) (1/2)
> 19/06/18 15:13:19 INFO BlockManagerInfo: Added broadcast_1_piece0 in memory 
> on 192.168.3.12:34011 (size: 1825.0 B, free: 366.3 MB)
> 19/06/18 15:13:19 DEBUG TaskSchedulerImpl: parentName: , name: TaskSet_1.0, 
> runningTasks: 0
> 19/06/18 15:13:19 INFO TaskSetManager: Finished task 0.0 in stage 1.0 (TID 2) 
> in 977 ms on 192.168.3.12 (executor 3) (2/2)
> 19/06/18 15:13:19 INFO TaskSchedulerImpl: Removed TaskSet 1.0, whose tasks 
> have all completed, from pool
> 19/06/18 15:13:19 INFO DAGScheduler: ResultStage 1 (count at 
> TeraGen.scala:94) finished in 0.995 s
> 19/06/18 15:13:19 DEBUG DAGScheduler: After removal of stage 1, remaining 
> stages = 0
> 19/06/18 15:13:19 INFO DAGScheduler: Job 1 finished: count at 
> TeraGen.scala:94, took 1.003537 s
> *Number of records written: 10000*
> {color:#FF0000}*^C*{color}19/06/18 15:13:36 INFO SparkContext: Invoking 
> stop() from shutdown hook



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to