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 2013/05/15 06:33:18 UTC

[jira] [Resolved] (HAMA-757) The partitioning job output should be un-splitable

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

Edward J. Yoon resolved HAMA-757.
---------------------------------

    Resolution: Fixed
      Assignee: MaoYuan Xian

I've committed this to TRUNK, thanks MaoYuan!

P.S., Since the tab size can be different depending on environment, many OSS uses space indentation. If you use eclipse, Please use Hama formatter[1] in the future. 

1. http://hama.apache.org/files/hama-eclipse-formatter.xml
                
> The partitioning job output should be un-splitable
> --------------------------------------------------
>
>                 Key: HAMA-757
>                 URL: https://issues.apache.org/jira/browse/HAMA-757
>             Project: Hama
>          Issue Type: Bug
>          Components: bsp core
>    Affects Versions: 0.6.1
>            Reporter: MaoYuan Xian
>            Assignee: MaoYuan Xian
>             Fix For: 0.6.2
>
>         Attachments: HAMA-757.patch
>
>
> When the output sequence files from partitioning job are large(bigger than two hdfs file block size), the second round of the job (using these sequence file as input) will start up more tasks than client want. Some times, this uncertainty make the job exceed the cluster slot capacity.
> In the real project, I implemented an new Inputformat which marked as un-splitable to solve the problem. Is there any better way?

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