You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Chris Douglas (JIRA)" <ji...@apache.org> on 2008/06/20 03:03:45 UTC

[jira] Updated: (HADOOP-3603) Setting spill threshold to 100% fails to detect spill for records

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

Chris Douglas updated HADOOP-3603:
----------------------------------

    Status: Patch Available  (was: Open)

> Setting spill threshold to 100% fails to detect spill for records
> -----------------------------------------------------------------
>
>                 Key: HADOOP-3603
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3603
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.17.0
>            Reporter: Chris Douglas
>            Assignee: Chris Douglas
>             Fix For: 0.18.0
>
>         Attachments: 3603-0.patch
>
>
> If io.sort.record.percent is set to 1.0, the simultaneous collection and spill is disabled. However, if one exhausts the offset allocation before the serialization allocation, the limit will not be detected and the write will block forever.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.