hama-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "MaoYuan Xian (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HAMA-764) In SpillingQueue, spilling thread dos not start when messages number less than threshold
Date Thu, 13 Jun 2013 12:47:20 GMT

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

MaoYuan Xian commented on HAMA-764:
-----------------------------------

oh, I will follow your way and waiting your patch in the future:)
And, by the way, seems there is another issue in SpillingQueue. I can find the message broken
when there is combiner, it seems related to writeInternal method in SpillingStream (brakes
messages in several buffers), I have not verify that, to be continue...
                
> In SpillingQueue, spilling thread dos not start when messages number less than threshold
> ----------------------------------------------------------------------------------------
>
>                 Key: HAMA-764
>                 URL: https://issues.apache.org/jira/browse/HAMA-764
>             Project: Hama
>          Issue Type: Bug
>          Components: bsp core
>    Affects Versions: 0.7.0
>            Reporter: MaoYuan Xian
>
> In the SpillingDataOutputBuffer.SpillingStream, we can find the following implementations
to starting the spilling thread.
> {code}
>    private void checkSpillStart() throws IOException {
>       if (bytesWritten_ >= thresholdSize_) {
>         try {
>           startSpilling();
>         } catch (InterruptedException e) {
>           throw new IOException("Internal error occured writing to buffer.", e);
>         }
>       }
>     }
> {code}
> But I encountered the message loss, when total bytes written number is less than thresholdSize.
Because the spilling thread is not invoked, and handleSpilledBuffer method of SpilledDataProcessor
can not get the chance to run.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message