Mohammad,
The NN is low write, and has pretty static memory usage. You will see
the NN memory usage go up as you add blocks/files. Since, HBase has memory
limitations(GC's Fault), and should have ~1 file per store you will not
have a lot of memory pressure on the NN. The JT is the same way,
Hello All,
I learn hbase almost from papers and books, according to my
understanding, HBase is the kind of architecture which is more appliable
to a big cluster. We should have many HDFS nodes, and many HBase(region
server) nodes. If we only have several severs(5-8), it seems hbase is
not a good
Hi Ning,
I'm personally running HBase in production with only 8 nodes.
As you will see here: http://wiki.apache.org/hadoop/Hbase/PoweredBy
some are also running small clusters.
So I will say it more depend on you need than on the size.
I will say the minimum is 4 to make sure you have your
Hello there,
IMHO, 5-8 servers are sufficient enough to start with. But it's all
relative to the data you have and the intensity of your reads/writes. You
should have different strategies though, based on whether it's 'read' or
'write'. You actually can't define 'big' in absolute terms.
Oh, you already have heavyweight's input :).
Thanks JM.
Warm Regards,
Tariq
cloudfront.blogspot.com
On Sat, Jun 22, 2013 at 8:05 PM, Mohammad Tariq donta...@gmail.com wrote:
Hello there,
IMHO, 5-8 servers are sufficient enough to start with. But it's
all relative to the data you
Thanks for your response.
Now if 5 servers are enough, how can I install and configure my nodes?
If I need 3 replicas in case data loss, I should at least have 3
datanodes, we still have namenode, regionserver and HMaster nodes,
zookeeper nodes, some of them must be installed in the same
With 8 machines you can do something like this :
Machine 1 - NN+JT
Machine 2 - SNN+ZK1
Machine 3 - HM+ZK2
Machine 4-8 - DN+TT+RS
(You can run ZK3 on a slave node with some additional memory).
DN and RS run on the same machine. Although RSs are said to hold the data,
the data is actually stored
You HAVE TO run a ZK3, or else you don't need to have ZK2 and any ZK
failure will be an issue. You need to have an odd number of ZK
servers...
Also, if you don't run MR jobs, you don't need the TT and JT... Else,
everything below is correct. But there is many other options, all
depend on your
If you run ZK with a DN/TT/RS please make sure to dedicate a hard drive and
a core to the ZK process. I have seen many strange occurrences.
On Jun 22, 2013 12:10 PM, Jean-Marc Spaggiari jean-m...@spaggiari.org
wrote:
You HAVE TO run a ZK3, or else you don't need to have ZK2 and any ZK
failure
Yeah, I forgot to mention that no. of ZKs should be odd. Perhaps those
parentheses made that statement look like an optional statement. Just to
clarify it was mandatory.
Warm Regards,
Tariq
cloudfront.blogspot.com
On Sat, Jun 22, 2013 at 9:45 PM, Kevin O'dell kevin.od...@cloudera.comwrote:
If
Hi Mohammad,
I am curious why you chose not to put the third ZK on the NN+JT? I was
planning on doing that on a new cluster and want to confirm it would be
okay.
--
Iain Wright
Cell: (562) 852-5916
http://www.labctsi.org/
This email message is confidential, intended only for the recipient(s)
Hello Iain,
You would put a lot of pressure on the RAM if you do that. NN
already has high memory requirement and then having JT+ZK on the same
machine would be too heavy, IMHO.
Warm Regards,
Tariq
cloudfront.blogspot.com
On Sun, Jun 23, 2013 at 4:07 AM, iain wright iainw...@gmail.com
12 matches
Mail list logo
