Yes, servers and clients will all need to be on 0.20.4... that's the tradeoff for more flexibility in the future (see http://issues.apache.org/jira/browse/HBASE-2219).
J-D On Thu, Mar 11, 2010 at 10:52 AM, Ted Yu <yuzhih...@gmail.com> wrote: > That makes sense. > This means we have to replace hbase client when we upgrade to 0.20.4, right > ? > > On Thu, Mar 11, 2010 at 10:36 AM, Jean-Daniel Cryans <jdcry...@apache.org> > wrote: >> >> We are about to commit it to 0.20.4 since we voted on it breaking RPC >> compatibility. >> >> In this case the DNS lookup gives a different address, so the master >> treats it as a different region server and gives it a new startcode. >> In the web ui the two lines should have the same address, but not the >> same code at the end. >> >> J-D >> >> On Thu, Mar 11, 2010 at 10:33 AM, Ted Yu <yuzhih...@gmail.com> wrote: >> > 0.20.5 seems a bit far in the future :-) >> > >> > What I couldn't explain is that why serversToServerInfo, backed by >> > ConcurrentHashMap, would contain two entries with same key - X.com. >> > >> > On Thu, Mar 11, 2010 at 10:19 AM, Jean-Daniel Cryans >> > <jdcry...@apache.org>wrote: >> > >> >> Bringing the discussion in hbase-user >> >> >> >> That usually happens after a DNS hiccup. There's a fix for that in >> >> https://issues.apache.org/jira/browse/HBASE-2174 >> >> >> >> J-D >> >> >> >> On Wed, Mar 10, 2010 at 1:41 PM, Ted Yu <yuzhih...@gmail.com> wrote: >> >> > I noticed two lines for the same region server on HBase Master page: >> >> > X.com:60030 1268160765854 requests=0, regions=16, >> >> > usedHeap=1068, >> >> > maxHeap=6127 >> >> > X.com:60030 1268250726442 requests=21, regions=9, >> >> > usedHeap=1258, >> >> > maxHeap=6127 >> >> > >> >> > I checked there is only one >> >> > org.apache.hadoop.hbase.regionserver.HRegionServer instance running >> >> > on >> >> that >> >> > machine. >> >> > >> >> > This is from region server log: >> >> > >> >> > 2010-03-10 13:25:38,157 ERROR [IPC Server handler 43 on 60020] >> >> > regionserver.HRegionServer(844): >> >> > org.apache.hadoop.hbase.NotServingRegionException: >> >> ruletable,,1268083966723 >> >> > at >> >> > >> >> >> >> org.apache.hadoop.hbase.regionserver.HRegionServer.getRegion(HRegionServer.java:2307) >> >> > at >> >> > >> >> >> >> org.apache.hadoop.hbase.regionserver.HRegionServer.get(HRegionServer.java:1784) >> >> > at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown >> >> > Source) >> >> > at >> >> > >> >> >> >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >> >> > at java.lang.reflect.Method.invoke(Method.java:597) >> >> > at >> >> > org.apache.hadoop.hbase.ipc.HBaseRPC$Server.call(HBaseRPC.java:648) >> >> > at >> >> > >> >> > org.apache.hadoop.hbase.ipc.HBaseServer$Handler.run(HBaseServer.java:915) >> >> > 2010-03-10 13:25:38,189 ERROR [IPC Server handler 0 on 60020] >> >> > regionserver.HRegionServer(844): >> >> > org.apache.hadoop.hbase.NotServingRegionException: >> >> ruletable,,1268083966723 >> >> > at >> >> > >> >> >> >> org.apache.hadoop.hbase.regionserver.HRegionServer.getRegion(HRegionServer.java:2307) >> >> > at >> >> > >> >> >> >> org.apache.hadoop.hbase.regionserver.HRegionServer.get(HRegionServer.java:1784) >> >> > at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown >> >> > Source) >> >> > at >> >> > >> >> >> >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >> >> > at java.lang.reflect.Method.invoke(Method.java:597) >> >> > at >> >> > org.apache.hadoop.hbase.ipc.HBaseRPC$Server.call(HBaseRPC.java:648) >> >> > at >> >> > >> >> > org.apache.hadoop.hbase.ipc.HBaseServer$Handler.run(HBaseServer.java:915) >> >> > >> >> > If you know how to troubleshoot, please share. >> >> > >> >> >> > > >
