Reader small image

You're reading from  Getting Started with Hazelcast

Product typeBook
Published inAug 2013
Reading LevelBeginner
Publisher
ISBN-139781782167303
Edition1st Edition
Languages
Right arrow
Author (1)
Matthew Johns
Matthew Johns
author image
Matthew Johns

contacted on 6 may '16 ________ Matthew Johns is an agile software engineer and hands-on technical/solution architect; specialising in designing and delivering highly scaled and available distributed systems, with broad experience across the whole stack. He is the solution architect and lead engineer at Sky.
Read more about Matthew Johns

Right arrow

Under manual control


In a very similar manner to the way we previously used a thin client to connect to the cluster rather than automatically discovering it, we can nominate a number of nodes that can be used to discover the presence of the wider cluster. This is akin to registering a node's presence with a set of arbiters; then using them to both find existing peers and distributing the appearance of that new node to others in the cluster. There is a higher expectation of availability of the nodes used in this role. Should all of them fail, no new node will be able to join the cluster without adjusting their configuration to address this situation.

So the process works a bit like this. When the 10.0.0.101 node attempts to connect to the cluster that is configured with the knowledge, it should expect peers to exist at 10.0.0.1 and 10.0.0.2. Once it has successfully connected to either of these, it can learn about the rest of the topology of the cluster and establish the required connections...

lock icon
The rest of the page is locked
Previous PageNext Page
You have been reading a chapter from
Getting Started with Hazelcast
Published in: Aug 2013Publisher: ISBN-13: 9781782167303

Author (1)

author image
Matthew Johns

contacted on 6 may '16 ________ Matthew Johns is an agile software engineer and hands-on technical/solution architect; specialising in designing and delivering highly scaled and available distributed systems, with broad experience across the whole stack. He is the solution architect and lead engineer at Sky.
Read more about Matthew Johns