Here is the content of the binary file
/hbase/-ROOT-/70236052/info/110463219710538426. you can see the IP address
10.110.24.55 inside.
This shows the hbase is saving the IP address of my cluster into the ROOT
data file. when I run the scan command
under shell , the log says it was trying to connect to 10.110.24.xx
machines.
Jimmy
DATABLK*#?
.META.,,1inforegioninfo&?Ph=.META.,,1.META.IS_ROOTfalseIS_METAtrueMEMSTORE_FLUSHSIZE16384
historian BLOOMFILTERfalse COMPRESSIONNONEVERSIONS2147483647TTL604800
BLOCKSIZE8192 IN_MEMORYfalse
BLOCKCACHEfalseinfo BLOOMFILTERfalse COMPRESSIONNONEVERSIONS10TTL
2147483647 BLOCKSIZE8192 IN_MEMORYfalse
BLOCKCACHEfalseI3
.META.,,1infoserver'J??10.110.24.88:60020 .META.,,1infoserver'0?}?10.110.24.85:60020
.META.,,1infoserver'0?{?10.110.24.56:60020 .META.,,1infoserver'&^?10.110.24.54:60020
.META.,,1infoserver'#??10.110.24.55:60020 .META.,,1infoserver'??10.110.24.54:60020
.META.,,1infoserver'B??10.110.24.56:60020 .META.,,1infoserver'R?z10.110.24.55:60020
.META.,,1infoserver&?NN?10.110.24.54:60020
.META.,,1infoserver&?S?410.110.24.55:60020( .META.,,1infoserverstartcode'J??'J?(
.META.,,1infoserverstartcode'0?}?'0?V?( .META.,,1infoserverstartcode'0?{?'&?C(
.META.,,1infoserverstartcode'&^?'&5?( .META.,,1infoserverstartcode'#??'?(
.META.,,1infoserverstartcode'??'
( .META.,,1infoserverstartcode'B??'Q??(.META.,,1infoserverstartcode'R?z'Q??( .META.,,1infoserverstartcode&?NN?&?N&G( .META.,,1infoserverstartcode&?S?4&?R??MAJOR_COMPACTION_KEY?MAX_SEQ_ID_KEYN ?hfile.AVG_KEY_LEN#hfile.AVG_VALUE_LEN!hfile.COMPARATOR2org.apache.hadoop.hbase.KeyValue$RootKeyComparatorhfile.LASTKEY( .META.,,1infoserverstartcode&?S?4IDXBLK)+`#
.META.,,1inforegioninfo&?Ph=TRABLK"$`D`
--------------------------------------------------
From: "Stack" <[email protected]>
Sent: Tuesday, March 16, 2010 5:15 PM
To: <[email protected]>
Subject: Re: can't read all hbase tables after hbase cluster IP netmask
change
On Tue, Mar 16, 2010 at 5:02 PM, Jinsong Hu <[email protected]>
wrote:
yes, the dns name resolution is working file. it is not dns issue. it
looks
I have to regenerate my hbase data again
from my raw data.
We don't write machine names or ips into the data. You can take your
data, copy it to another cluster altogether and it'll serve it without
modification.
Another observation I have is that if one region server dies, the region
served by that server won't be accessible any
more because of this binding to IP. the only way to resolve this is to
build
a new machine that takes over that IP and
add it to cluster.
Your premise is incorrect. The above does not hold at all.
St.Ack
