You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hama.apache.org by "Edward J. Yoon (JIRA)" <ji...@apache.org> on 2014/01/10 08:58:51 UTC

[jira] [Updated] (HAMA-842) Add persistent queue option to JobConf

     [ https://issues.apache.org/jira/browse/HAMA-842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Edward J. Yoon updated HAMA-842:
--------------------------------

    Attachment: HAMA-842_v01.patch

Attach my progress.

I'll update for DiskQueue and Sorted Spilling Queue.

> Add persistent queue option to JobConf
> --------------------------------------
>
>                 Key: HAMA-842
>                 URL: https://issues.apache.org/jira/browse/HAMA-842
>             Project: Hama
>          Issue Type: New Feature
>    Affects Versions: 0.6.3
>            Reporter: Edward J. Yoon
>            Assignee: Edward J. Yoon
>             Fix For: 0.7.0
>
>         Attachments: HAMA-842_v01.patch
>
>
> By default, incoming (local) queue will be reset in every superstep. It means that unconsumed messages will be lost. If this is persistent queue, unconsumed messages will be persisted in incoming queue.
> {code}
>   public final void clearOutgoingQueues() {
>     if (localQueue != null) {
>       localQueue.close();
>     }
>     localQueue = localQueueForNextIteration.getMessageQueue();
>     localQueue.prepareRead();
>     localQueueForNextIteration = getSynchronizedReceiverQueue();
>     notifyInit();
>   }
> {code}
> Simply we can add unconsumed messages to localQueueForNextIteration before switching local queue.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)