A store abstraction and analytics system for real-time event data.
Change it to 17000 or something
Other than 9200
changed.... no luck
/usr/local/Cellar/hbase/1.1.2/bin/start-hbase.sh starting master, logging to /usr/local/Cellar/hbase/1.1.2/libexec/bin/../logs/hbase-mukesh-master-MUKESHs-MacBook-Pro.local.out Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=128m; support was removed in 8.0 Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=128m; support was removed in 8.0
Please create a gist with the full output and/or create an issue...
We will take a look
Which version of hbase are you using?
I'm traveling now
.will respond a little later
Please create a gist with the full output of initialize..
Also check the pom.xml files inside for foxtrot and see the hbase version in use
Hbase keeps on changing its rpc format.. Upgrades are not simple amd stable so we don't support all versions
Flipkart/foxtrot#118 let me know if you need any other information
@mukeshkdangi Are you able to run any query in HBase ? Try to login to shell and run query - list . Is it printing correct output ? Which version of HBase are you using ? Currently client uses - 0.94.15
Also, please follow the steps suggested by @r0goyal to verify your install
yeah ..i googled it already ....nothing worked out
i'll give one more shot
Please try the commands suggested by @r0goyal to validate your hbase discussion
@mukeshkdangi can you try with hbase version 0.94 and let us know
We could even try changing the zookeeper znode to hbase in hbase-site.xml.
getting following error in
ERROR: The node /hbase is not in ZooKeeper. It should have been written by the master. Check the value configured in 'zookeeper.znode.parent'. There could be a mismatch with the one configured in the master.
in case you are aware about this error - Not a host:port pair: PBUF
while executing ---...itialize config/local.yml
What is the default level of nesting supported in the events? somewhere I start to see x.y.0.field.empty : false and x.y.0.field.traversableAgain : true . Is there anyway to stop this?