hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wei-Chiu Chuang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-3584) Blocks are getting marked as corrupt with append operation under high load.
Date Mon, 23 Jul 2018 22:39:00 GMT

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

Wei-Chiu Chuang commented on HDFS-3584:
---------------------------------------

This is definitely the same as HDFS-10240, and it is reproducible even with one client thread.

> Blocks are getting marked as corrupt with append operation under high load.
> ---------------------------------------------------------------------------
>
>                 Key: HDFS-3584
>                 URL: https://issues.apache.org/jira/browse/HDFS-3584
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>    Affects Versions: 2.0.0-alpha
>            Reporter: Brahma Reddy Battula
>            Priority: Major
>
> Scenario:
> ========= 
> 1. There are 2 clients cli1 and cli2 cli1 write a file F1 and not closed
> 2. The cli2 will call append on unclosed file and triggers a leaserecovery
> 3. Cli1 is closed
> 4. Lease recovery is completed and with updated GS in DN and got BlockReport since there
is a mismatch in GS the block got corrupted
> 5. Now we got a CommitBlockSync this will also fail since the File is already closed
by cli1 and state in NN is Finalized



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org


Mime
View raw message