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, Xline supports two different clients: the etcd client and the Xline client.
For the etcd client, its request path is as follows:
etcd client — RPC call —> KvServer — inner client propose —> CurpServer —> Command Executor —> KvStore
For the Xline client, its request path is as follows:
Xline client — outer client —> CurpServer —> Command Executor —> KvStore
As shown in the request paths above, Xline client requests do not pass through KvServer. Therefore, some backend-related request checks, such as check_range_request, are not invoked when interacting with an Xline client and Xline. Hence, we need to add the corresponding request checks to KvStore based on the request path of the Xline client.
Version
0.4.1 (Default)
Relevant log output
No response
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Description about the bug
Currently, Xline supports two different clients: the etcd client and the Xline client.
For the etcd client, its request path is as follows:
etcd client — RPC call —> KvServer — inner client propose —> CurpServer —> Command Executor —> KvStore
For the Xline client, its request path is as follows:
Xline client — outer client —> CurpServer —> Command Executor —> KvStore
As shown in the request paths above, Xline client requests do not pass through
KvServer
. Therefore, some backend-related request checks, such ascheck_range_request
, are not invoked when interacting with an Xline client and Xline. Hence, we need to add the corresponding request checks toKvStore
based on the request path of the Xline client.Version
0.4.1 (Default)
Relevant log output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: