See http://search-hadoop.com/m/3NMzFay1Ha1
On Fri, Oct 4, 2013 at 2:44 PM, Tianying Chang wrote:
> Hi,
>
> The hdfs and zookeeper are both up running. When I try to start the HBase,
> it failed with this error below. I even tried to change the
> security.group.mpapping to ShellBasedUnixGroupsMa
Hi,
The hdfs and zookeeper are both up running. When I try to start the HBase, it
failed with this error below. I even tried to change the
security.group.mpapping to ShellBasedUnixGroupsMappingWithFallback, still not
working. Anyone know what could went wrong?
Caused by: java.lang.Unsatisfie
hbase.master was removed when we added zookeeper, so now a client will do a
lookup in ZK instead of talking to a pre-determined master. So in a
way, hbase.zookeeper.quorum is what replaces hbase.master
FWIW that was done in 0.20.0 which was released in September of 2009, so
hbase.master has been r
Oh wow. looking in the source this really is an old parameter: It appears
that the answer to my question is :
that these are the master parameters:
src/main/resources/hbase-default.xml:hbase.master.port
src/main/resources/hbase-default.xml:hbase.master.info.port
src/main/resources/hbase-d
Thanks for the feedback !
So - are you sure it has no effect? By "obsolete" - do we mean deprecated?
In this case - which parameters have replaced it and how [specifically] ?
Any help on this issue would be appreciated , because im seeing an effect
when i have the parameter , will check my hbas
[SOLVED] I find what was going on and it had nothing to do with Hbase...
I have forgotten to add the hostname and IP of the new RS to the YCSB
server VM :-(
Thanks again Bharath for your interest
On 10/04/2013 02:18 PM, Thanasis Naskos wrote:
One possibility could be that the regions got b
One possibility could be that the regions got balanced after the write load
is complete. That means, when the regions were being written they were with
one RS and once that is done, the region got assigned to the idle RS.
I think that this is the case, but why is this wrong? I write the data
to
One possibility could be that the regions got balanced after the write load
is complete. That means, when the regions were being written they were with
one RS and once that is done, the region got assigned to the idle RS.
Are you sure you are that YCSB writes to the regions after balancing too?
Al
I'm setting up a Hbase cluster on a cloud infrastructure.
HBase version: 0.94.11
Hadoop version: 1.0.4
Currently I have 4 nodes in my cluster (1 master, 3 regionservers) and
I'm using YCSB (yahoo benchmarks) to create a table (500.000 rows) and
send requests (Asynchronous requests). Everything
If you mean "insert and query" spatial data, look at algorithms that are
"distributed databases compliant" : geohash, z-index, voronoi diagram...
Well, that makes me want to write a blog article about these topics :)
On Tue, Sep 24, 2013 at 3:43 PM, Ted Yu wrote:
> There're plenty of examples
10 matches
Mail list logo
