You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using hdfs command to download a file in directories where EC enabled following exception occurs:
read failed: ERROR (opReadBlock BP-1187583696-10.2.56.184-1541663887733:blk_-9223372036831322912_257597259 received exception org.apache.hadoop.hdfs.server.datanode.ReplicaNotFoundException: Replica not found for BP-1187583696-10.2.56.184-1541663887733:blk_-9223372036831322912_257597259. The block may have been removed recently by the balancer or by intentionally reducing the replication factor. This condition is usually harmless. To be certain, please check the preceding datanode log messages for signs of a more serious issue.)
Downloading the same file with standard hdfs client from apache works.
./hdfs --version
gohdfs version 36a28bc8afc433619d3dc3f8b8d6fbeeb1cb1e8a
Also downloading files in directories without EC is working.
Is this a configuration issue or a bug ?
BR,
Thorsten
The text was updated successfully, but these errors were encountered:
Hello!
When using hdfs command to download a file in directories where EC enabled following exception occurs:
read failed: ERROR (opReadBlock BP-1187583696-10.2.56.184-1541663887733:blk_-9223372036831322912_257597259 received exception org.apache.hadoop.hdfs.server.datanode.ReplicaNotFoundException: Replica not found for BP-1187583696-10.2.56.184-1541663887733:blk_-9223372036831322912_257597259. The block may have been removed recently by the balancer or by intentionally reducing the replication factor. This condition is usually harmless. To be certain, please check the preceding datanode log messages for signs of a more serious issue.)
Downloading the same file with standard hdfs client from apache works.
Also downloading files in directories without EC is working.
Is this a configuration issue or a bug ?
BR,
Thorsten
The text was updated successfully, but these errors were encountered: