-
Notifications
You must be signed in to change notification settings - Fork 238
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In the case of auto_forwarding_= true, an error of "socket is already in use, race happened on connection to " appears for the append_entries of the follower #184
Comments
hi @greensky00 I suggest Is it possible to add serial and parallel modes in "asio_rpc_client" and "asio_rpc_listener", Serial in operations such as append entry and parallel in foward request to leader. |
Thanks, @nicelulu @marising for suggesting this. We will consider supporting multiple in-flight messages. But please note that auto-forwarding has endless edge-cases that may cause potential problems, and that's why we don't recommend it (also we don't internally use it). For example, a follower forwards a message to the leader, and the leader succeeds to replicate it, but the response of the "forwarding" is lost. There is no way for this follower to know whether it should retry or not. There are a number of such complicated issues and we will not cover them. It should be handled at your own risk. |
Thanks @greensky00 for your reply. |
@greensky00 Thank you for solving this problem. I met some error logs during the test : |
Hi @nicelulu |
Hi,
In the case of
auto_forwarding_= true
, can theappend_entries
of the follower only forward messages to the leader one by one?The text was updated successfully, but these errors were encountered: