hama-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Edward J. Yoon (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HAMA-842) Add persistent queue option to JobConf
Date Mon, 13 Jan 2014 01:28:50 GMT

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

Edward J. Yoon commented on HAMA-842:
-------------------------------------

BTW, I think we have to rename the Queue implementations as consistently.

- DiskTransferProtocolQueue
- MemoryTransferProtocol
- SortedMessageTransferProtocol
- SpillingQueueTransferProtocol



> 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)

Mime
View raw message