Xue,I have added routingTableProvider after connect() and works now. But when
I add new node to cluster, in state model callback, I couldn't get fetch other
masters for given partition using routing table provider. is it possible that
state model call backs come earlier than routing table is
Thanks Xue.
So for all 3 (Controller, Participant, Spectator) do you expect calling thread
should get blocked after connect is called?Also In our case, participant needs
to know who is other master for synching. can we register routingTableProvider
using below code snippet before calling
For your issue,
1) how do I specify full auto mode using ./helix-admin.sh command? I don't
see mode parameter (may be am I missing something?)
You need -mode FULL_AUTO to let the resource be automatically assigned by
Helix with out your preference list.
2) Is there a way to specify delay for
The set up I have used is,
#Define the Resource and Partitioning#Create a Database with 6 Partitions using
the MasterSlave State Model
./helix-admin.sh --zkSvr ${zkSvr} --addResource ${CLUSTER} ${RESOURCE} 3
MasterSlave
#Let Helix Assign Partitions to Nodes
./helix-admin.sh --zkSvr ${zkSvr}
Hi Leela,
Are your resources all in SemiAuto mode? SemiAuto mode assignment is based
on your preference list in your IdealState list fields. If you want to
spread it out, you have to change your preference list node order for
different partitions.
If you are using FullAuto mode, you will not
Team,In my example(SEMI_AUTO), I have configured 3 partitions with 3 replicas
on 3 nodes. Once all nodes are started, external view shows as below. Here all
MASTER's are assigned to same node. Is there a way to spread MASTER's evenly?
is this behavior due to server booting order?
IdealState
