`server.ha.raft.setNodeId` rationale?

[maxb]

This Helm chart provides the boolean value server.ha.raft.setNodeId.

However, I have found no documentation that explains why you would or would not want to use it - so I have been studying the topic trying to figure it out for myself.

To recap the behaviour:

• If false (the default), the Raft node IDs will be generated UUIDs, persisted in the PVs.

• If true, the Raft node IDs will be the pod names.

This will only cause a significant behaviour difference, when a pod is restarted with loss of its PV data.

• If setNodeId is false, the new pod will be treated as a brand new node.

• If setNodeId is true, the new pod will implicitly replace the old one in the Raft configuration.

Here is where I'm slightly uncertain... is it actually safe for a Raft node to lose all its data, and still claim to the rest of the Raft cluster that it is the same node, to which data was in the past committed?

Is anyone able to comment on the history and rationale of the setNodeId value being configurable, so as to build a consensus which could be turned into documentation to clarify this point once and for all?

[pavan-kumar222]

@maxb were you able to find answer to your query, for a prod setup which one makes sense ?

[maxb]

No, I have no further information at this time.

[pavan-kumar222]

@maxb I see your comment on another thread. Want to correspond on the same, would you be interested in having a quick discussion? If yes, how can I reach you?

[maxb]

No, thank you.