diff options
| author | Raghavendra G <rgowdapp@redhat.com> | 2018-06-03 11:24:18 +0530 |
|---|---|---|
| committer | Raghavendra G <rgowdapp@redhat.com> | 2018-06-04 12:57:42 +0530 |
| commit | 3894f4262d53d1c1c593a78b21d72ba1103c86cd (patch) | |
| tree | ce4744ca47344f4ec6096e4569a77e0b32b1551a /rpc/rpc-lib/src/libgfrpc.sym | |
| parent | a6f0e7a4f1ca203762cae2ed5e426b52124c74dc (diff) | |
rpc/clnt: Don't let consumers manage "connected" state
The state management of "connected" in rpc is ad-hoc as far as the
responsibility goes. Note that there is nothing wrong with
functionality itself. rpc layer manages this state in disconnect
codepath and has exposed an api to manage this one from
consumers. Note that rpc layer never sets "connected" to true by
itself, which forces the consumers to use this api to get a working
rpc connection. The situation is best captured from a comment in code
from Jeff Darcy in glusterfsd/src/gf-attach.c:
-/*
- * In a sane world, the generic RPC layer would be capable of tracking
- * connection status by itself, with no help from us. It might invoke our
- * callback if we had registered one, but only to provide information. Sadly,
- * we don't live in that world. Instead, the callback *must* exist and *must*
- * call rpc_clnt_{set,unset}_connected, because that's the only way those
- * fields get set (with RPC both above and below us on the stack). If we don't
- * do that, then rpc_clnt_submit doesn't think we're connected even when we
- * are. It calls the socket code to reconnect, but the socket code tracks this
- * stuff in a sane way so it knows we're connected and returns EINPROGRESS.
- * Then we're stuck, connected but unable to use the connection. To make it
- * work, we define and register this trivial callback.
- */
Also, consumers of rpc know about state of connection only through the
notifications sent by rpc-clnt. So, consumers don't have any extra
information to manage the state and hence letting them manage the
state is counter intuitive. This patch cleans that up and instead
moves the responsibility of state management of rpc layer into
itself.
Change-Id: I31e641a60795fc480ca753917f4b2579f1e05094
Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
Fixes: bz#1585585
Diffstat (limited to 'rpc/rpc-lib/src/libgfrpc.sym')
| -rw-r--r-- | rpc/rpc-lib/src/libgfrpc.sym | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/rpc/rpc-lib/src/libgfrpc.sym b/rpc/rpc-lib/src/libgfrpc.sym index 4fab688c66d..a7cb5f6b5cb 100644 --- a/rpc/rpc-lib/src/libgfrpc.sym +++ b/rpc/rpc-lib/src/libgfrpc.sym @@ -10,11 +10,9 @@ rpc_clnt_reconnect rpc_clnt_reconnect_cleanup rpc_clnt_ref rpc_clnt_register_notify -rpc_clnt_set_connected rpc_clnt_start rpc_clnt_submit rpc_clnt_unref -rpc_clnt_unset_connected rpc_reply_to_xdr rpcsvc_auth_array rpcsvc_auth_check |