commit | 5d0995966c117e3cf946216aff41116c2020c212 | [log] [tgz] |
---|---|---|
author | Paul J. Davis <paul.joseph.davis@gmail.com> | Tue Feb 10 21:49:40 2015 -0600 |
committer | ILYA Khlopotov <iilyak@ca.ibm.com> | Mon Jul 11 12:22:19 2016 -0700 |
tree | e85f1abd74b4f8868521e83aeb5900ac7848ad1b | |
parent | c38c692fcf0b8b69f94109ead3c5370144090f8f [diff] |
Use the correct sequence for shard replacement The call to unpack the since sequence for _changes incorrectly filtered the value for any shard that didn't exist. This means that any shard that was moved ended up requiring a complete rescan which is a bug. This just sets the update sequence to the range of the shard being replaced rather than zero. COUCHDB-3055
Fabric is a collection of proxy functions for CouchDB operations in a cluster. These functions are used in CouchDB as the remote procedure endpoints on each of the cluster nodes.
For example, creating a database is a straightforward task in CouchDB 1.x, but for a clustered CouchDB, each node that will store a shard for the database needs to receive and execute a fabric function. The node handling the request also needs to compile the results from each of the nodes and respond accordingly to the client.
Fabric is used in conjunction with ‘Rexi’ which is also an application within CouchDB.
Fabric requires R13B03 or higher and can be built with rebar.