add a comment that sometimes sending remote calls straight to the

lmaster instead of what the nodes think is the dmaster (which might be
stale) improve performance.

(This used to be ctdb commit f535f79e6a2a6c6d07141b96e0b957fa93c684f4)

diff --git a/ctdb/common/ctdb_call.c b/ctdb/common/ctdb_call.c
index d81cca9e6f31bb77cf957239550efe827a44b78c..8db795d8897adc5760fbcb28f2207597720485c3 100644 (file)
--- a/ctdb/common/ctdb_call.c
+++ b/ctdb/common/ctdb_call.c
@@ -716,6 +716,14 @@ struct ctdb_call_state *ctdb_daemon_call_send_remote(struct ctdb_db_context *ctd
        state->c->hdr.ctdb_version = CTDB_VERSION;
        state->c->hdr.operation = CTDB_REQ_CALL;
        state->c->hdr.destnode  = header->dmaster;
+       /*
+          always sending the remote call straight to the lmaster
+          improved performance slightly in some tests.
+          worth investigating further in the future
+       state->c->hdr.destnode  = ctdb_lmaster(ctdb_db->ctdb, &(call->key));
+       */
+
+
        state->c->hdr.srcnode   = ctdb->vnn;
        /* this limits us to 16k outstanding messages - not unreasonable */
        state->c->hdr.reqid     = idr_get_new(ctdb->idr, state, 0xFFFF);