Hello guys,
Over at http://search-hadoop.com we index ZooKeeper project's mailing lists,
wiki, web site,
source code, javadoc, jira...
Would the community be interested in a patch that replaces the
Google-powered
search with that from search-hadoop.com, set to search only ZooKeeper
project by
Hi,
Is there a way to know/measure the size of a znode? My average znode has a name
of 32 bytes and user data of max 128 bytes.
Or is the only way to run a smoke test and watch the heap growth via jconsole
or so?
Thanks, Maarten
Hi Marten,
The usual memory footprint of a znode is around 40-80 bytes.
I think Ben is planning to document a way to calculate approximate memory
footprint of your zk servers given a set of updates and there sizes.
thanks
mahadev
On 8/25/10 11:49 AM, Maarten Koopmans maar...@vrijheid.net
I am definitely a +1 on this, given that its powered by Solr.
Thanks
mahadev
On 8/25/10 9:22 AM, Alex Baranau alex.barano...@gmail.com wrote:
Hello guys,
Over at http://search-hadoop.com we index ZooKeeper project's mailing lists,
wiki, web site,
source code, javadoc, jira...
Would
Hey guys,
Forgive me if this is documented somewhere, but I can't find an
answer. Our application is not enormous, so we will be using 4
application nodes that will also initially run Zookeeper. As our load
increases, Zookeeper will be moved to nodes that only run ZK and no
other processes.
Thanks for that Dave. If I do not configure it as an observer just a
normal member, what will the last even node to join do?
1. Will it participate as a voter on startup? (I'm assuming not, just
read only)
2. If one of the voter nodes 1 through 3 dies, does it become a voter?
todd
SENIOR
I'm not an expert on voting, so there may be a better answer, but from my
understanding all 4 nodes participate in the voting and you need a majority
of 3 to elect a leader.
-Dave
On Wed, Aug 25, 2010 at 6:09 PM, Todd Nine t...@spidertracks.co.nz wrote:
Thanks for that Dave. If I do not
Dave is correct - if you have N nodes you need (N/2) + 1 votes (i.e. a
majority) in the standard case to get a vote to pass.
Adding a fourth voting node to a three node cluster will cause the size of a
majority to jump from 2 to 3. The number of nodes that need to fail before
you can no longer
Do I get any read performance increase (similar to an observer) since
the node will not have a voting role?
On Wed, 2010-08-25 at 15:18 -0700, Henry Robinson wrote:
Dave is correct - if you have N nodes you need (N/2) + 1 votes (i.e. a
majority) in the standard case to get a vote to pass.
Just use 3 nodes. Life will be better.
You can configure the fourth node in the event of one of the first three
failing and bring it on line. Then you can re-configure and restart each of
the others one at a time. This gives you flexibility because you have 4
nodes, but doesn't decrease your
Thanks Dave. I've been using Cassandra, so I'm trying to get my head
around the configuration/operational differences with ZK. You state
that using 4 would actually decrease my reliability. Can you explain
that further? I was under the impression that a 4th node would act as a
non voting read
Todd -
No, this is not the case. There are no 'backup' or 'failover' nodes in
ZooKeeper. All servers that can vote are working as part of the cluster
until they fail. You need a majority of your voting servers alive.
If you have three servers, a majority is of size two. The number of nodes
that
Awesome, thanks guys. Your patience and input is greatly appreciated.
On Wed, 2010-08-25 at 21:30 -0700, Henry Robinson wrote:
Todd -
No, this is not the case. There are no 'backup' or 'failover' nodes in
ZooKeeper. All servers that can vote are working as part of the
cluster
13 matches
Mail list logo
