[ 
https://issues.apache.org/jira/browse/HADOOP-2768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12565112#action_12565112
 ] 

Nigel Daley commented on HADOOP-2768:
-------------------------------------

In both core test runs above, TestBalancer failed with this exception:

{quote}
    [junit] 2008-02-02 00:51:29,097 INFO  dfs.DataNode 
(DataNode.java:writeBlock(1169)) - writeBlock blk_-4006373334377701738 received 
exception java.io.IOException: setBlockPosition trying to set position to 3 
which is not a multiple of bytesPerChecksum 10
    [junit] 2008-02-02 00:51:29,098 ERROR dfs.DataNode (DataNode.java:run(961)) 
- 127.0.0.1:49578:DataXceiver: java.io.IOException: setBlockPosition trying to 
set position to 3 which is not a multiple of bytesPerChecksum 10
    [junit]     at 
org.apache.hadoop.dfs.DataNode$BlockReceiver.setBlockPosition(DataNode.java:2301)
    [junit]     at 
org.apache.hadoop.dfs.DataNode$BlockReceiver.receivePacket(DataNode.java:2126)
    [junit]     at 
org.apache.hadoop.dfs.DataNode$BlockReceiver.receiveBlock(DataNode.java:2230)
    [junit]     at 
org.apache.hadoop.dfs.DataNode$DataXceiver.writeBlock(DataNode.java:1150)
    [junit]     at 
org.apache.hadoop.dfs.DataNode$DataXceiver.run(DataNode.java:938)
    [junit]     at java.lang.Thread.run(Thread.java:595)
{quote}



> DFSIO write performance benchmark shows a regression
> ----------------------------------------------------
>
>                 Key: HADOOP-2768
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2768
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: dfs
>    Affects Versions: 0.16.0
>            Reporter: Mukund Madhugiri
>            Assignee: dhruba borthakur
>            Priority: Blocker
>             Fix For: 0.16.0
>
>         Attachments: perf.patch, perf.patch
>
>
> We are seeing a performance regression in DFSIO write benchmark, possibly due 
> to Hadoop-1707. 
> Here is the data:
> - Aggregate cluster throughput went from 0.30G to 0.14G with 39 concurrent 
> clients, on 20 nodes
> - Aggregate cluster throughput went from 1.15G to 0.85G with 39 concurrent 
> clients, on 100 nodes

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

Reply via email to