couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From kxepal <>
Subject [GitHub] couchdb-documentation pull request: A base to build on for 2.0
Date Sun, 12 Apr 2015 16:06:08 GMT
Github user kxepal commented on a diff in the pull request:
    --- Diff: src/cluster/sharding.rst ---
    @@ -0,0 +1,289 @@
    +.. Licensed under the Apache License, Version 2.0 (the "License"); you may not
    +.. use this file except in compliance with the License. You may obtain a copy of
    +.. the License at
    +.. Unless required by applicable law or agreed to in writing, software
    +.. distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
    +.. WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
    +.. License for the specific language governing permissions and limitations under
    +.. the License.
    +.. _cluster/sharding:
    +.. _cluster/sharding/scaling-out:
    +Scaling out
    +Normally you start small and grow over time. In the beginning you might do just
    +fine with one node, but as your data and number of clients grows, you need to
    +scale out.
    +For simplicity we will start fresh and small.
    +Start node1 and add a database to it. To keep it simple we will have 2 shards
    +and no replicas.
    +.. code-block:: bash
    +    curl -X PUT "" --user daboss
    +If you look in the directory ``data/shards`` you will find the 2 shards.
    +.. code-block:: text
    +    data
    --- End diff --
    How about to explicitly how here that data, shards and others are directories? Like:
    +-- shards/
         +-- 00000000-7fffffff/
         |   +-- small.1425202577.couch
         +-- 80000000-ffffffff/
             +-- small.1425202577.couch

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message