This "firstbadlink" was an mis-configured log message in the code. It is innocuous and has since been fixed in 0.17 release. http://issues.apache.org/jira/browse/HADOOP-3029
thanks, dhruba On Sat, May 24, 2008 at 7:03 PM, C G <[EMAIL PROTECTED]> wrote: > Hi All: > > So far, running 0.16.4 has been a bit of a nightmare. The latest problem > I'm seeing concerns a series of odd messages concerning "firstbadlink". > I've attached one of these message sequences. I'm curious what it's trying > to tell me. This is from the master node, but the same pattern also occurs > on all the slaves as well. > > Thanks for any insight... > C G > > 2008-05-24 22:35:00,170 INFO org.apache.hadoop.dfs.DataNode: Receiving block > blk_-5166040941538436352 src: /10.2.13.1:41942 dest: /10.2.13.1:50010 > 2008-05-24 22:35:00,283 INFO org.apache.hadoop.dfs.DataNode: Datanode 2 got > response for connect ack from downstream datanode with firstbadlink as > 2008-05-24 22:35:00,283 INFO org.apache.hadoop.dfs.DataNode: Datanode 2 > forwarding connect ack to upstream firstbadlink is > 2008-05-24 22:35:00,313 INFO org.apache.hadoop.dfs.DataNode: Received block > blk_-5166040941538436352 of size 427894 from /10.2.13.1 > 2008-05-24 22:35:00,313 INFO org.apache.hadoop.dfs.DataNode: PacketResponder > 2 for block blk_-5166040941538436352 terminating > > > >
