Enable DEBUG in your log4j. Doing this, shell emits the names of regions as it loads them. Before you hit the NPE, you'll see the name of the problematic region. Take the name found and then using the UI figure which host is supposedly carrying it. Grep its logs for the problematic region to see if you can figure what its recent history has been.
Did you retry yesterday's loadings with haoop 0.19.1 release candidate? St.Ack On Sun, Feb 22, 2009 at 12:51 PM, Amandeep Khurana <[email protected]> wrote: > I had given a count command for a table from the shell. It counted for a > while after which it failed with the following error: > > > Current count: 2078000, row: 605428239 > > NativeException: java.lang.NullPointerException: null > from java.lang.String:-1:in `<init>' > from org/apache/hadoop/hbase/util/Bytes.java:92:in `toString' > from org/apache/hadoop/hbase/client/RetriesExhaustedException.java:50:in > `getMessage' > > > What could be going wrong? > > Amandeep > > Amandeep Khurana > Computer Science Graduate Student > University of California, Santa Cruz >
