[jira] Created: (HDFS-1239) All datanodes are bad in 2nd phase

All datanodes are bad in 2nd phase -- Key: HDFS-1239 URL: https://issues.apache.org/jira/browse/HDFS-1239 Project: Hadoop HDFS Issue Type: Bug Components: hdfs client Affects Versions: 0.20.1

[jira] Created: (HDFS-1238) A block is stuck in ongoingRecovery due to exception not propagated

A block is stuck in ongoingRecovery due to exception not propagated Key: HDFS-1238 URL: https://issues.apache.org/jira/browse/HDFS-1238 Project: Hadoop HDFS Issue Type: Bu

[jira] Created: (HDFS-1237) Client logic for 1st phase and 2nd phase failover are different

Client logic for 1st phase and 2nd phase failover are different --- Key: HDFS-1237 URL: https://issues.apache.org/jira/browse/HDFS-1237 Project: Hadoop HDFS Issue Type: Bug

[jira] Updated: (HDFS-1236) Client uselessly retries recoverBlock 5 times

[ https://issues.apache.org/jira/browse/HDFS-1236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanh Do updated HDFS-1236: --- Description: Summary: Client uselessly retries recoverBlock 5 times The same behavior is also seen in append p

[jira] Updated: (HDFS-1236) Client uselessly retries recoverBlock 5 times

[ https://issues.apache.org/jira/browse/HDFS-1236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanh Do updated HDFS-1236: --- Description: Summary: Client uselessly retries recoverBlock 5 times The same behavior is also seen in append p

[jira] Created: (HDFS-1236) Client uselessly retries recoverBlock 5 times

Client uselessly retries recoverBlock 5 times - Key: HDFS-1236 URL: https://issues.apache.org/jira/browse/HDFS-1236 Project: Hadoop HDFS Issue Type: Bug Affects Versions: 0.20.1 Rep

[jira] Updated: (HDFS-1234) Datanode 'alive' but with its disk failed, Namenode thinks it's alive

[ https://issues.apache.org/jira/browse/HDFS-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanh Do updated HDFS-1234: --- Description: - Summary: Datanode 'alive' but with its disk failed, Namenode still thinks it's alive - Setup

[jira] Created: (HDFS-1235) Namenode returning the same Datanode to client, due to infrequent heartbeat

Namenode returning the same Datanode to client, due to infrequent heartbeat --- Key: HDFS-1235 URL: https://issues.apache.org/jira/browse/HDFS-1235 Project: Hadoop HDFS

[jira] Created: (HDFS-1234) Datanode 'alive' but with its disk failed, Namenode thinks it's alive

Datanode 'alive' but with its disk failed, Namenode thinks it's alive - Key: HDFS-1234 URL: https://issues.apache.org/jira/browse/HDFS-1234 Project: Hadoop HDFS Issue Type:

[jira] Created: (HDFS-1232) Corrupted block if a crash happens before writing to checksumOut but after writing to dataOut

Corrupted block if a crash happens before writing to checksumOut but after writing to dataOut - Key: HDFS-1232 URL: https://issues.apache.org/jira/browse/HDFS-1232

[jira] Created: (HDFS-1233) Bad retry logic at DFSClient

Bad retry logic at DFSClient Key: HDFS-1233 URL: https://issues.apache.org/jira/browse/HDFS-1233 Project: Hadoop HDFS Issue Type: Bug Components: hdfs client Affects Versions: 0.20.1 Rep

[jira] Created: (HDFS-1231) Generation Stamp mismatches, leading to failed append

Generation Stamp mismatches, leading to failed append - Key: HDFS-1231 URL: https://issues.apache.org/jira/browse/HDFS-1231 Project: Hadoop HDFS Issue Type: Bug Components: hdfs c

[jira] Updated: (HDFS-1229) DFSClient incorrectly asks for new block if primary crashes during first recoverBlock

[ https://issues.apache.org/jira/browse/HDFS-1229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanh Do updated HDFS-1229: --- Description: Setup: + # available datanodes = 2 + # disks / datanode = 1 + # failures = 1 + failure t

[jira] Updated: (HDFS-1229) DFSClient incorrectly asks for new block if primary crashes during first recoverBlock

[ https://issues.apache.org/jira/browse/HDFS-1229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanh Do updated HDFS-1229: --- Description: Setup: + # available datanodes = 2 + # disks / datanode = 1 + # failures = 1 + failure t

[jira] Created: (HDFS-1229) DFSClient incorrectly asks for new block if primary crashes during first recoverBlock

DFSClient incorrectly asks for new block if primary crashes during first recoverBlock - Key: HDFS-1229 URL: https://issues.apache.org/jira/browse/HDFS-1229 Project: H

[jira] Created: (HDFS-1228) CRC does not match when retrying appending a partial block

CRC does not match when retrying appending a partial block -- Key: HDFS-1228 URL: https://issues.apache.org/jira/browse/HDFS-1228 Project: Hadoop HDFS Issue Type: Bug Componen

[jira] Created: (HDFS-1227) UpdateBlock fails due to unmatched file length

UpdateBlock fails due to unmatched file length -- Key: HDFS-1227 URL: https://issues.apache.org/jira/browse/HDFS-1227 Project: Hadoop HDFS Issue Type: Bug Components: data-node Affect

[jira] Updated: (HDFS-1226) Last block is temporary unavailable for readers because of crashed appender

[ https://issues.apache.org/jira/browse/HDFS-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanh Do updated HDFS-1226: --- Description: - Summary: the last block is unavailable to subsequent readers if appender crashes in the middle

[jira] Updated: (HDFS-1226) Last block is temporary unavailable for readers because of crashed appender

[ https://issues.apache.org/jira/browse/HDFS-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanh Do updated HDFS-1226: --- Description: - Summary: the last block is unavailable to subsequent readers if appender crashes in the middle

[jira] Created: (HDFS-1226) Last block is temporary unavailable for readers because of crashed appender

Last block is temporary unavailable for readers because of crashed appender --- Key: HDFS-1226 URL: https://issues.apache.org/jira/browse/HDFS-1226 Project: Hadoop HDFS

[jira] Created: (HDFS-1225) Block lost when primary crashes in recoverBlock

Block lost when primary crashes in recoverBlock --- Key: HDFS-1225 URL: https://issues.apache.org/jira/browse/HDFS-1225 Project: Hadoop HDFS Issue Type: Bug Components: data-node Affe

[jira] Updated: (HDFS-1224) Stale connection makes node miss append

[ https://issues.apache.org/jira/browse/HDFS-1224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanh Do updated HDFS-1224: --- Description: - Summary: if a datanode crashes and restarts, it may miss an append. - Setup: + # available da

[jira] Updated: (HDFS-1224) Stale connection makes node miss append

[ https://issues.apache.org/jira/browse/HDFS-1224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanh Do updated HDFS-1224: --- Affects Version/s: 0.20.1 Component/s: data-node > Stale connection makes node miss append > ---

[jira] Created: (HDFS-1224) Stale connection makes node miss append

Stale connection makes node miss append --- Key: HDFS-1224 URL: https://issues.apache.org/jira/browse/HDFS-1224 Project: Hadoop HDFS Issue Type: Bug Reporter: Thanh Do - Summary: if a datanod

[jira] Created: (HDFS-1223) DataNode fails stop due to a bad disk (or storage directory)

DataNode fails stop due to a bad disk (or storage directory) Key: HDFS-1223 URL: https://issues.apache.org/jira/browse/HDFS-1223 Project: Hadoop HDFS Issue Type: Bug Comp

[jira] Created: (HDFS-1222) NameNode fail stop in spite of multiple metadata directories

NameNode fail stop in spite of multiple metadata directories Key: HDFS-1222 URL: https://issues.apache.org/jira/browse/HDFS-1222 Project: Hadoop HDFS Issue Type: Bug Comp

[jira] Created: (HDFS-1221) NameNode unable to start due to stale edits log after a crash

NameNode unable to start due to stale edits log after a crash - Key: HDFS-1221 URL: https://issues.apache.org/jira/browse/HDFS-1221 Project: Hadoop HDFS Issue Type: Bug Affects

[jira] Updated: (HDFS-1221) NameNode unable to start due to stale edits log after a crash

[ https://issues.apache.org/jira/browse/HDFS-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanh Do updated HDFS-1221: --- Description: - Summary: If a crash happens during FSEditLog.createEditLogFile(), the edits log file on disk m

[jira] Updated: (HDFS-1220) Namenode unable to start due to truncated fstime

[ https://issues.apache.org/jira/browse/HDFS-1220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanh Do updated HDFS-1220: --- Description: - Summary: updating fstime file on disk is not atomic, so it is possible that if a crash happens

[jira] Updated: (HDFS-1220) Namenode unable to start due to truncated fstime

[ https://issues.apache.org/jira/browse/HDFS-1220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanh Do updated HDFS-1220: --- Description: - Summary: updating fstime file on disk is not atomic, so it is possible that if a crash happens

[jira] Created: (HDFS-1220) Namenode unable to start due to truncated fstime

Namenode unable to start due to truncated fstime Key: HDFS-1220 URL: https://issues.apache.org/jira/browse/HDFS-1220 Project: Hadoop HDFS Issue Type: Bug Components: name-node Af

[jira] Updated: (HDFS-1220) Namenode unable to start due to truncated fstime

[ https://issues.apache.org/jira/browse/HDFS-1220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanh Do updated HDFS-1220: --- Description: - Summary: updating fstime file on disk is not atomic, so it is possible that if a crash happens

[jira] Created: (HDFS-1219) Data Loss due to edits log truncation

Data Loss due to edits log truncation - Key: HDFS-1219 URL: https://issues.apache.org/jira/browse/HDFS-1219 Project: Hadoop HDFS Issue Type: Bug Components: name-node Affects Versions: 0.20.2

<    1   2