old leaf discovery strategy gone?

[natmurella]

Hi,

my previous pulled version had cluster leaves use cluster.node="" to inform the cluster root, who would then inform all existing leaves of the new leaf, creating the full connection mapping.

I merged latest main (bit over a week ago), but the node variable is removed, and it seems i need to manually add the full list of relays in each cluster.connect in each relay (seems inefficient, especially compared to the previous discovery method).

Is there a better leaf discovery process (not manual), that I missed in the new version?

[kixelated]

The cluster nodes now proxy, so there can be multiple hops.

San Jose - > Texas -> Virginia -> London

Before, every node would connect to every other node directly (ex. San Jose -> London). Hurting the cache efficiency.

But yeah the downside is you need to manually specify the hop possibilities for each node. San Jose would only connect to Texas.

We could add back the hostname gossip if you want a mesh network?

[kixelated]

@natmurella lemme know if you want the old behavior and I'll actually review that PR lul

[natmurella]

Thanks for the explanation, yes I'd like the old behavior if it's not too much trouble.

Can i ask what the plan is for the node discovery strategy in the future? Are you moving towards an explicit mapping on node startup, or something different? I personally favor the gossip style discovery, since it can let me add nodes mid deployment