I have a map/reduce job that is consistently failing with timeouts. The failing mapper log files contain a series of records similar to those below. When I look at the hbase and hdfs logs (on foo.net in this case) I don’t see anything obvious at these timestamps. The mapper task times out at/near attempt=25/35. Can anyone shed light on what these log entries mean?
Thanks - Brian 2014-09-07 09:36:51,421 INFO [htable-pool1-t1] org.apache.hadoop.hbase.client.AsyncProcess: #3, table=Host, primary, attempt=10/35 failed 1062 ops, last exception: null on foo.net,60020,1406043467187, tracking started null, retrying after 10029 ms, replay 1062 ops 2014-09-07 09:37:01,642 INFO [htable-pool1-t1] org.apache.hadoop.hbase.client.AsyncProcess: #3, table=Host, primary, attempt=11/35 failed 1062 ops, last exception: null on foo.net,60020,1406043467187, tracking started null, retrying after 10023 ms, replay 1062 ops 2014-09-07 09:37:12,064 INFO [htable-pool1-t1] org.apache.hadoop.hbase.client.AsyncProcess: #3, table=Host, primary, attempt=12/35 failed 1062 ops, last exception: null on foo.net,60020,1406043467187, tracking started null, retrying after 20182 ms, replay 1062 ops 2014-09-07 09:37:32,708 INFO [htable-pool1-t1] org.apache.hadoop.hbase.client.AsyncProcess: #3, table=Host, primary, attempt=13/35 failed 1062 ops, last exception: null on foo.net,60020,1406043467187, tracking started null, retrying after 20140 ms, replay 1062 ops 2014-09-07 09:37:52,940 INFO [htable-pool1-t1] org.apache.hadoop.hbase.client.AsyncProcess: #3, table=Host, primary, attempt=14/35 failed 1062 ops, last exception: null on foo.net,60020,1406043467187, tracking started null, retrying after 20041 ms, replay 1062 ops 2014-09-07 09:38:13,324 INFO [htable-pool1-t1] org.apache.hadoop.hbase.client.AsyncProcess: #3, table=Host, primary, attempt=15/35 failed 1062 ops, last exception: null on foo.net,60020,1406043467187, tracking started null, retrying after 20041 ms, replay 1062 ops