@Sean, thanks. I saw sometimes Cloudera guys help here. I also used
Cloudera community forum.
@Jean-Marc, nothing special, just maven-plugin wrapper around
miniHbaseCluster
Here is the code where failure happen: new MiniHBaseCluster(configuration,
1);
There are nothing special from my side. I'm
I see these lines:
2015-07-20 21:27:21,791 INFO [RegionOpenAndInitThread-hbase:namespace-1]
regionserver.HRegion (HRegion.java:createHRegion(5598)) - creating HRegion
hbase:namespace HTD == 'hbase:namespace', {NAME = 'info', BLOOMFILTER =
'ROW', VERSIONS = '10', IN_MEMORY = 'true',
omg, looks like -Djava.net.preferIPv4Stack=true helped...
probably some weird macos update...
2015-07-20 23:56 GMT+02:00 Serega Sheypak serega.shey...@gmail.com:
I degrade project with hbase testing utility to these versions:
hadoop.version2.5.0-cdh5.2.0/hadoop.version
I degrade project with hbase testing utility to these versions:
hadoop.version2.5.0-cdh5.2.0/hadoop.version
hadoop.mr.version2.5.0-mr1-cdh5.2.0/hadoop.mr.version
hbase.version0.98.6-cdh5.2.0/hbase.version
It works.
I upgrade to these:
hadoop.version2.6.0-cdh5.4.4/hadoop.version
Did your shutdown leave any state in ZK (if you are using zk for
assignment) or did some regionservers leave behind WALs?
You can trace AssignmentManager.joinCluster() and more specifically
AssignmentManager.processDeadServersAndRegionsInTransition(). Can you see
any condition where you got
I believe a lot of people experience this problem when restarting their
clusters. What do you guys think of a flag which we pass to start-hbase.sh
which tells master to do the failover steps but instead of letting the
balancer assign the rest of the regions.
In
