state callback about raft HOT 7 CLOSED

I plan to add some kind of support for this in the v1 version of the API, currently being worked on. See #130 (comment) to get some feel of how it will look like.

from raft.

Please would you also elaborate on why you need such a state change callback in the first place?

There might be valid use cases, but as far as I can tell most applications should not need to react to Raft state changes, and they typically just need to check what the current state is, using raft_state().

The fact that you think you need it this callback might be a design smell.

from raft.

@freeekanayaka any news on this callback? In our case the interest is to disable/enable a rpc server based on leadership state, seems like a valid use case, but feel free to suggest alternatives.

from raft.

Why do you need to disable the server? Can't the server just call raft_state() as part of the request handling logic and reply some kind of error if it's not the leader? That'd be a very typical thing to do.

from raft.

@skypexu @pyssling ping

from raft.

That works for protocols that contain error responses, but many protocols expect socket state to reflect availability. For these I need a callback to open/close the socket.

from raft.

yes, raft_state() may work in most cases

from raft.