hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Harsh J (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-1526) Dfs client name for a map/reduce task should have some randomness
Date Sun, 18 Dec 2011 13:34:30 GMT

    [ https://issues.apache.org/jira/browse/HDFS-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13171865#comment-13171865

Harsh J commented on HDFS-1526:

Noticed this today while poking around with 0.23.0:

If its not mapreduce, labelling it as 'NONMAPREDUCE' only makes it harder to grep, cause there's
still some 'MAPREDUCE' in it? Its a nitpick (cause IDs don't carry that string), but perhaps
you may consider switching to something more 'REGULAR'?
> Dfs client name for a map/reduce task should have some randomness
> -----------------------------------------------------------------
>                 Key: HDFS-1526
>                 URL: https://issues.apache.org/jira/browse/HDFS-1526
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: hdfs client
>            Reporter: Hairong Kuang
>            Assignee: Hairong Kuang
>             Fix For: 0.23.0
>         Attachments: clientName.patch, randClientId1.patch, randClientId2.patch, randClientId3.patch
> Fsck shows one of the files in our dfs cluster is corrupt.
> /bin/hadoop fsck aFile -files -blocks -locations
> aFile: 4633 bytes, 2 block(s): 
> aFile: CORRUPT block blk_-4597378336099313975
> OK
> 0. blk_-4597378336099313975_2284630101 len=0 repl=3 [...]
> 1. blk_5024052590403223424_2284630107 len=4633 repl=3 [...]Status: CORRUPT
> On disk, these two blocks are of the same size and the same content. It turns out the
writer of the file is from a multiple threaded map task. Each thread may write to the same
file. One possible interaction of two threads might make this to happen:
> [T1: create aFile] [T2: delete aFile] [T2: create aFile][T1: addBlock 0 to aFile][T2:
addBlock1 to aFile]...
> Because T1 and T2 have the same client name, which is the map task id, the above interactions
could be done without any lease exception, thus eventually leading to a corrupt file. To solve
the problem, a mapreduce task's client name could be formed by its task id followed by a random

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


View raw message