That's right. You need add resource to your cluster. The state model you
are using is applied to each partition of a resource. Once you add a
resource, the state transitions will be invoked and nodes will, for
example, take LEADER/MASTER/FOLLOWER state for partitions. You will see
the partition->node->state mapping under
/{clusterName}/EXTERNALVIEW/{resourceName}. You may have multiple
resources in one cluster.Thanks, Jason On 2/20/14 12:53 PM, "Sandeep Nayak" <[email protected]> wrote: >Thanks Jason for the pointers. I do see the nodes and InstanceConfigs >but there is no indication of which is master, do I need to add >resources to the cluster for that information to surface? If nodes are >added to the cluster should I be able to see which is the master or >leader and which are the followers? > >Sandeep > >On Thu, Feb 20, 2014 at 11:51 AM, Zhen Zhang <[email protected]> wrote: >> For checking external-view, you can use zoo inspector: >> http://helix.apache.org/0.7.0-incubating-docs/Quickstart.html >> >> The zookeeper path is for the external view is >> /{clusterName}/{externalView}/{resourceName} >> >> If you want do it programmatically, you can use spectator: >> http://helix.apache.org/0.7.0-incubating-docs/tutorial_spectator.html >> >> >> The time for a node to transit to its target state depends on how long >>the >> state transition takes. >> >> In normal case, if the external-view matches the ideal-state, it >>indicates >> the cluster converges. >> >> Thanks, >> Jason >> >> On 2/20/14 11:29 AM, "Sandeep Nayak" <[email protected]> wrote: >> >>>I probably missed it in the documentation, but how can I check the >>>external view? Also, is there a time period after which the first node >>>logs that it has identified itself as the leader? Just wanted to know >>>what is the indicator that things work and I do have a leader and >>>follower in the cluster? >>> >>>Thanks, >>> >>>Sandeep >>> >>>On Thu, Feb 20, 2014 at 9:34 AM, Kanak Biscuitwala <[email protected]> >>>wrote: >>>> We didn't, but now we do. >>>> ________________________________ >>>>> Date: Thu, 20 Feb 2014 09:26:10 -0800 >>>>> Subject: Re: Helix 0.6.2- Messages on startup >>>>> From: [email protected] >>>>> To: [email protected] >>>>> >>>>> Do we have a jira for this ? >>>>> >>>>> >>>>> On Wed, Feb 19, 2014 at 11:20 PM, Kanak Biscuitwala >>>>> <[email protected]<mailto:[email protected]>> wrote: >>>>> Hi Sandeep, >>>>> >>>>> Does Helix still generate an external view correctly despite these >>>>>log >>>>> messages? >>>>> >>>>> I believe the first message is a known issue: the callbacks are >>>>> initialized once by the HelixManager implementation, and then >>>>> initialized again when the controller becomes leader (for the first >>>>> controller, these will happen very close to one another). It's >>>>> generally a harmless message. >>>>> >>>>> The second one indicates that the controller is getting events (which >>>>> path was changed to trigger the event?), but hasn't yet become >>>>>leader. >>>>> When it does, it will invoke the pipeline and do the right thing. >>>>> >>>>> I think in either case, a race is causing the log messages to appear, >>>>> but it shouldn't affect the correctness of the Helix controller >>>>> operation. >>>>> >>>>> Kanak >>>>> >>>>> Date: Wed, 19 Feb 2014 23:13:19 -0800 >>>>> Subject: Helix 0.6.2- Messages on startup >>>>> From: [email protected]<mailto:[email protected]> >>>>> To: [email protected]<mailto:[email protected]> >>>>> >>>>> Hi guys, >>>>> >>>>> So I finally got my setup done with states etc. But when I start the >>>>> first node I see the following messages >>>>> >>>>> expected types: [CALLBACK, FINALIZE] but was INIT >>>>> I see this for /cluster/Controller, >>>>> /cluster/INSTANCES/Instance/MESSAGES and several other paths. >>>>> The other message I see is >>>>> Cluster manager: first-node is not leader. Pipeline will not be >>>>>invoked >>>>> Any ideas on what I am missing here? >>>>> Thanks, >>>>> Sandeep >>>>> >>
