| commit | 3679456c42fe9b2776cd9d47c21cbb15dd98d6c5 | [log] [tgz] |
|---|---|---|
| author | Adam Kocoloski <adam@cloudant.com> | Fri Feb 17 09:05:30 2012 -0500 |
| committer | Adam Kocoloski <adam@cloudant.com> | Fri Feb 17 09:05:30 2012 -0500 |
| tree | ea994d7b68d7aa122e20495bf2e453474865eff9 | |
| parent | 260b5e98c1abe18d7d68d370f9ed693f3d8800be [diff] |
Don't block rexi_server to send a message When a worker dies rexi_server needs to notify the remote client. If communication to the remote node is impaired rexi_server may block for several seconds trying to send the rexi_EXIT message. Fix is to use the same 'noconnect' and 'nosuspend' options in rexi_server that we use to submit jobs from a client. BugzID: 13298
Rexi is a tailor-made RPC server application for sending CouchDB operations to nodes in a cluster. It is used in BigCouch as the remote procedure vehicle to get fabric functions to execute on remote cluster nodes.
Rexi better fits the needs of the BigCouch distributed data store by dropping some unneeded overhead in rex, the RPC server that ships with Erlang/OTP. Rexi is optimized for the case when you need to spawn a bunch of remote processes. Cast messages are sent from the origin to the remote rexi server, and local processes are spawned from there, which is vastly more efficient than spawning remote processes from the origin. You still get monitoring of the remote processes, but the request-handling process doesn't get stuck trying to connect to an overloaded/dead node. ‘rexi_DOWN’ messages will arrive at the client eventually. This has been an extremely advantageous mix of latency and failure detection, vastly improving the performance of BigCouch.
Rexi is used in conjunction with ‘Fabric’ which is also an application within BigCouch, but can be used on a stand-alone basis.
Rexi requires R13B03 or higher and can be built with rebar, which comes bundled in the repository.