First, understand why you had to create an ‘auto restart’ script.
Taking down HBase completely (probably including zookeeper) and do a full
restart would probably fix the issue of data locality.
On May 9, 2015, at 5:05 PM, rahul malviya malviyarahul2...@gmail.com wrote:
Hi,
My HBase
Major compactions will restore locality to the cluster.
On Sat, May 9, 2015 at 3:36 PM, Michael Segel michael_se...@hotmail.com
wrote:
First, understand why you had to create an ‘auto restart’ script.
Taking down HBase completely (probably including zookeeper) and do a full
restart would
Thanks for suggestion. I will try this and update the thread if the data
locality is restored.
Thanks,
Rahul
On Sat, May 9, 2015 at 6:36 PM, Dave Latham lat...@davelink.net wrote:
Major compactions will fix locality, so long as there is space on the
local data nodes and they actually happen.
Hi,
My HBase cluster went through a rough patch recently where lot of region
server started dying because of sudden increase in amount of data being
funneled to the HBase cluster and we have to place a auto start script for
regionservers.
After this all my data locality is lost which does not
Major compactions will fix locality, so long as there is space on the
local data nodes and they actually happen. Also, if there is already
only a single HFile in a store, major compaction may be skipped.
Newer versions of hbase have a parameter
hbase.hstore.min.locality.to.skip.major.compact that
