adding a client implementation about openraft HOT 3 CLOSED

Like all interesting questions the answer is "it depends" ...

• Yes. The implementation pointed to is convenient and kind of solves the problem in practice. I think there is a theoretical risk of an infinite recursion for unlikely failure scenarios that have to be considered (cf metasrv in the databend repo).
• My main purpose with suggesting a client implementation was clarity and being explicit.
• In practice, handling this on the client side can be more efficient since if the client contacts a node that is not the leader and that node forwards to the leader we have to pay for the node to leader request each time. If the client gets an error and updates its belief of who's the leader that extra cost goes away for all future requests which IMHO is much better.

I think that our outlined solutions are not mutually exclusive. I just wanted to bring your attention to more "interesting aspects" of the original question.

from openraft.

👋 Thanks for opening this issue!

Get help or engage by:

• /help : to print help messages.
• /assignme : to assign this issue to you.

from openraft.

@drmingdrmer @MikaelCall I successfully sorted that by doing this: https://github.com/ppamorim/openraft/blob/example/example-raft-kv/src/network/api.rs#L39-L72

from openraft.