Either it really takes time to replicate your data to 3 datanodes (latency is what's important here, network or datanodes being just a bit too slow), or you have GC going on.
J-D On Tue, Jun 14, 2011 at 8:00 PM, Gaojinchao <[email protected]> wrote: > In my performance cluster(hbase vesion 0.90.3). > There are a lot of warn logs, below as: > > 2011-05-21 11:35:10,325 WARN org.apache.hadoop.hbase.regionserver.wal.HLog: > IPC Server handler 43 on 20020 took 11569 ms appending an edit to hlog; > editcount=23862, len~=4.8k > 2011-05-21 11:50:23,610 WARN org.apache.hadoop.hbase.regionserver.wal.HLog: > IPC Server handler 8 on 20020 took 1118 ms appending an edit to hlog; > editcount=37591, len~=5.4k > 2011-05-21 11:53:27,703 WARN org.apache.hadoop.hbase.regionserver.wal.HLog: > IPC Server handler 82 on 20020 took 11203 ms appending an edit to hlog; > editcount=38388, len~=1.9k > 2011-05-21 12:14:54,469 WARN org.apache.hadoop.hbase.regionserver.wal.HLog: > IPC Server handler 27 on 20020 took 12013 ms appending an edit to hlog; > editcount=36144, len~=7.6k > 2011-05-21 12:54:08,440 WARN org.apache.hadoop.hbase.regionserver.wal.HLog: > IPC Server handler 85 on 20020 took 3330 ms appending an edit to hlog; > editcount=2, len~=6.3k > > The resource(RAM, CPU, network) seems enough. Is it a bug for hdfs? > >
