Hi Team, A curious question !! From server 1 to 20...
# random
m
Hi Team, A curious question !! From server 1 to 20. Call it as pinot001, 002 ..020.
Copy code
If I create a segment, the primary is going to 001 and replica to 002.
Its always the same for all segments, if the segment is created in 013 its replica is in 014. I haven't done any instance assignment, this is the situation by default. Is this sequence for replica is voluntarily done, if yes, what is the reason behind?
m
I think this happens to be the behavior of the default segment assignment strategy that tries to uniformly distributed segments. If you are asking if it explicitly to looks for the server with next number, then no it does not.
ack 1
m
So its randomly uniform 🙂
Well here is the surprise. I enabled RA the external state showed up randomness like
Copy code
SegA-Primary: goes to Server13 
SegA-Secondary: goes to Server05
Now when I check it after few days, its back to sequencing.
Copy code
SegA-Primary: goes to Server13
SegA-Secondary: goes to Server14
Yet it is adhering to RA pooling , am not sure if its by luck or it does sequence distibution at the same time maintaining RA.
Also, one more clarification when i perform RA changes. Is it required to keep Table disabled or consuming disable any such thing?
m
The contract is to only maintain replication with given constraints. Are you relying on server names for that? You shouldn’t. Changing replication requires rebalance
ack 1