You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, we use Client::get_leader_id to get the current leader id from a curp cluster. The client maintains its own state. The leader_id returned by get_leader_id may be outdated, because it will read from the client's state first.
Read pr #276 and issue #251 for more detail. I'll file a new pr to resolve this issue.
The text was updated successfully, but these errors were encountered:
Finally, in that sharing the State structure between RawCurp and Client will break our present encapsulation, we've decided to add another method named get_leader_info_from_curp to solve this issue. The get_leader_info_from_curp will fetch the current leader and term from the curp server which is on the same node as the client. Therefore, from the curp server perspective, the leader_id won't be outdated.
Currently, we use
Client::get_leader_id
to get the current leader id from a curp cluster. The client maintains its own state. Theleader_id
returned byget_leader_id
may be outdated, because it will read from the client's state first.Read pr #276 and issue #251 for more detail. I'll file a new pr to resolve this issue.
The text was updated successfully, but these errors were encountered: