First thanks for answering, second i still have some question see inline Thanks Mikael.S
On Tue, Nov 29, 2011 at 8:04 PM, Jean-Daniel Cryans <[email protected]>wrote: > Inline. > > J-D > > On Tue, Nov 29, 2011 at 12:46 AM, Mikael Sitruk <[email protected]> > wrote: > > Hi > > > > I have a strange error in log of HBase (0.90.2) > > > > 2011-11-28 15:12:53,049 INFO > > This part right up here is important, it's INFO level. > > > then few line later i can see > > 2011-11-28 15:12:53,139 INFO > > org.apache.hadoop.hbase.regionserver.StoreFile$Reader: Loaded col bloom > > filter metadata > > for > hdfs://hadoop89:8020/hbase/TC/2833a916eba1c562cdc5533b6af3ddc0/PI/6153988896004900741 > > So can i deduce that even if the first operation failed everything is ok, > > or is something is lost? > > The client failed to connect for some reason to the local data node, > you might get a clue by looking at the DN's log. But since there's 2 > other replicas, it's all good. Worst case if the replica is really > lost the Namenode is going to fix it in the background. > --- Shouldn't be an added value to add some information in the original message like (failed to load ... will try later), then when the bloom filter is successfully loaded to print a corresponding message like - (loaded col bloom filter .... successfully after x attempt)? Let assume that the 2 other replica are lost too, what hbase will indicate in this case? will an error be created (big enough to bring attention to someone)? > > > > > Second and Certainly i need to post this question to hdfs guys, (since > this > > is a dfs output) - from the first line i see that the same node that is > the > > source of the request will add itself as a dead node isn't it strange? > > No, it adds the _local datanode_ as a dead node. > > J-D > -- Mikael.S
