You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Suresh Srinivas (JIRA)" <ji...@apache.org> on 2012/10/09 15:51:02 UTC
[jira] [Updated] (HDFS-4022) Replication not happening for appended
block
[ https://issues.apache.org/jira/browse/HDFS-4022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Suresh Srinivas updated HDFS-4022:
----------------------------------
Priority: Blocker (was: Major)
Changing this bug to a blocker.
> Replication not happening for appended block
> --------------------------------------------
>
> Key: HDFS-4022
> URL: https://issues.apache.org/jira/browse/HDFS-4022
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 2.0.0-alpha
> Reporter: suja s
> Priority: Blocker
>
> Block written and finalized
> Later append called. Block GenTS got changed.
> DN side log
> "Can't send invalid block BP-407900822-192.xx.xx.xx-1348830837061:blk_-9185630731157263852_108738" logged continously
> NN side log
> "INFO org.apache.hadoop.hdfs.server.namenode.NameNode: Error report from DatanodeRegistration(192.xx.xx.xx, storageID=DS-2040532042-192.xx.xx.xx-50010-1348830863443, infoPort=50075, ipcPort=50020, storageInfo=lv=-40;cid=123456;nsid=116596173;c=0): Can't send invalid block BP-407900822-192.xx.xx.xx-1348830837061:blk_-9185630731157263852_108738" also logged continuosly.
> The block checked for tansfer is the one with old genTS whereas the new block with updated genTS exist in the data dir.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira