J.D hi Well from the HBase POV at the end every thing is ok, but from the user POV he sees that HBase encontourned a problem while opening a Region. Then few line later HBase is fine with the file that previously got error. This is confusing for the user a little bit. But you are right, nothing can really be done to clarify the confusion untill the user get use to.
Thanks. Mikael.S On Wed, Nov 30, 2011 at 8:38 PM, Jean-Daniel Cryans <[email protected]>wrote: > On Tue, Nov 29, 2011 at 10:28 PM, Mikael Sitruk <[email protected]> > wrote: > > First thanks for answering, second i still have some question see inline > > > > Thanks > > Mikael.S > > > > --- > > 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)? > > We have 0 control on that stack trace because it comes from the depths > of the DFSClient: > > 2011-11-28 15:12:53,052 INFO org.apache.hadoop.hdfs.DFSClient > > So from the HBase POV, nothing wrong happened. Also I don't know why > it would say it failed to load something because it didn't, if you > look at you log carefully you'll see that each loaded bloom filter is > for a different file and none failed. > > > > > 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)? > > It would fail in a flamboyant way. > > J-D > -- Mikael.S
