commit | 9b6a5cf123faaedbc6b5e3d756a933bc7ee36a74 | [log] [tgz] |
---|---|---|
author | Adam Kocoloski <adam@cloudant.com> | Mon Jun 27 15:16:50 2011 -0400 |
committer | Adam Kocoloski <adam@cloudant.com> | Mon Jun 27 15:16:50 2011 -0400 |
tree | 68aeb95f0322179eae2147f3134a28c4086ae94b | |
parent | 9fd372245ff550c34e988caf8f09722631f8ef76 [diff] |
Add an index keyed on client reference This prevents table scans triggered by the kill handler from causing the server to fall over under very high throughput. I also took the opportunity to refactor a bit and use #job records throughout the server instead of raw tuples. BugzID: 12344
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.