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 (Updated) (JIRA)" <ji...@apache.org> on 2012/01/04 08:12:40 UTC
[jira] [Updated] (HAMA-476) Splitter doesn't work correctly
[ https://issues.apache.org/jira/browse/HAMA-476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Edward J. Yoon updated HAMA-476:
--------------------------------
Attachment: patch_01.txt
This patch adds simple logic to extract proper size of tasks in the max task capacity.
{code}
root@Cnode1:/usr/local/src/hama-trunk# core/bin/hama jar examples/target/hama-examples-0.4.0-incubating-SNAPSHOT.jar sssp 3 result /user/root/sssp/sssp-small.seq 4
12/01/04 16:02:54 INFO bsp.FileInputFormat: Total input paths to process : 1
12/01/04 16:02:54 INFO bsp.FileInputFormat: Total # of splits: 2
12/01/04 16:03:03 INFO bsp.FileInputFormat: Total input paths to process : 4
12/01/04 16:03:03 INFO bsp.FileInputFormat: Total # of splits: 4
12/01/04 16:03:04 INFO bsp.BSPJobClient: Running job: job_201201041546_0005
12/01/04 16:03:07 INFO bsp.BSPJobClient: Launched tasks: 3/4
12/01/04 16:03:10 INFO bsp.BSPJobClient: Launched tasks: 4/4
12/01/04 16:03:19 INFO bsp.BSPJobClient: Current supersteps number: 23
12/01/04 16:03:22 INFO bsp.BSPJobClient: Current supersteps number: 44
12/01/04 16:03:25 INFO bsp.BSPJobClient: Current supersteps number: 84
12/01/04 16:03:28 INFO bsp.BSPJobClient: Current supersteps number: 104
12/01/04 16:03:31 INFO bsp.BSPJobClient: Current supersteps number: 125
12/01/04 16:03:34 INFO bsp.BSPJobClient: Current supersteps number: 147
{code}
> Splitter doesn't work correctly
> -------------------------------
>
> Key: HAMA-476
> URL: https://issues.apache.org/jira/browse/HAMA-476
> Project: Hama
> Issue Type: Bug
> Components: bsp
> Affects Versions: 0.3.0
> Reporter: Edward J. Yoon
> Assignee: Edward J. Yoon
> Fix For: 0.4.0
>
> Attachments: patch_01.txt
>
>
> - To split sequencefile as user requested size, there's no way to avoid read/write records. I think we have to use just blockSize.
> - Unlike MapReduce, we are unable to queuing tasks when exceeds cluster capacity (I have no idea at the moment).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira