3.2. Base Configuration

3.2.1. Base CouchDB Options

[couchdb]

  • attachment_stream_buffer_size

    Higher values may result in better read performance due to fewer read operations and/or more OS page cache hits. However, they can also increase overall response time for writes when there are many attachment write requests in parallel.

    1. [couchdb]
    2. attachment_stream_buffer_size = 4096

  • database_dir

    Specifies location of CouchDB database files (*.couch named). This location should be writable and readable for the user the CouchDB service runs as (couchdb by default).

    1. [couchdb]
    2. database_dir = /var/lib/couchdb

  • default_security

    Changed in version 3.0: admin_only is now the default.

    Default security object for databases if not explicitly set. When set to everyone, anyone can performs reads and writes. When set to admin_only, only admins can read and write. When set to admin_local, sharded databases can be read and written by anyone but the shards can only be read and written by admins.

    [couchdb] default_security = admin_only

  • enable_database_recovery

    Enable this to only “soft-delete” databases when DELETE /{db} DELETE requests are made. This will place a .recovery directory in your data directory and move deleted databases/shards there instead. You can then manually delete these files later, as desired.

    Default is false.

    1. [couchdb]
    2. enable_database_recovery = false

  • file_compression

    Changed in version 1.2: Added Google Snappy compression algorithm.

    Method used to compress everything that is appended to database and view index files, except for attachments (see the attachments section). Available methods are:

    • none: no compression
    • snappy: use Google Snappy, a very fast compressor/decompressor
    • deflate_N: use zlib’s deflate; N is the compression level which ranges from 1 (fastest, lowest compression ratio) to 9 (slowest, highest compression ratio)
    1. [couchdb]
    2. file_compression = snappy

  • maintenance_mode

    A CouchDB node may be put into two distinct maintenance modes by setting this configuration parameter.

    • true: The node will not respond to clustered requests from other nodes and the /_up endpoint will return a 404 response.
    • nolb: The /_up endpoint will return a 404 response.
    • false: The node responds normally, /_up returns a 200 response.

    It is expected that the administrator has configured a load balancer in front of the CouchDB nodes in the cluster. This load balancer should use the /_up endpoint to determine whether or not to send HTTP requests to any particular node. For HAProxy, the following config is appropriate:

    1. http-check disable-on-404
    2. option httpchk GET /_up

  • max_dbs_open

    This option places an upper bound on the number of databases that can be open at once. CouchDB reference counts database accesses internally and will close idle databases as needed. Sometimes it is necessary to keep more than the default open at once, such as in deployments where many databases will be replicating continuously.

    1. [couchdb]
    2. max_dbs_open = 100

  • max_document_size

    Changed in version 3.0.0.

    Limit maximum document body size. Size is calculated based on the serialized Erlang representation of the JSON document body, because that reflects more accurately the amount of storage consumed on disk. In particular, this limit does not include attachments.

    HTTP requests which create or update documents will fail with error code 413 if one or more documents is larger than this configuration value.

    In case of _update handlers, document size is checked after the transformation and right before being inserted into the database.

    1. [couchdb]
    2. max_document_size = 8000000 ; bytes

  • os_process_timeout

    If an external process, such as a query server or external process, runs for this amount of milliseconds without returning any results, it will be terminated. Keeping this value smaller ensures you get expedient errors, but you may want to tweak it for your specific needs.

    1. [couchdb]
    2. os_process_timeout = 5000 ; 5 sec

  • single_node

    New in version 3.0.0.

    When this configuration setting is set to true, automatically create the system databases on startup. Must be set false for a clustered CouchDB installation.

  • uri_file

    This file contains the full URI that can be used to access this instance of CouchDB. It is used to help discover the port CouchDB is running on (if it was set to 0 (e.g. automatically assigned any free one). This file should be writable and readable for the user that runs the CouchDB service (couchdb by default).

    1. [couchdb]
    2. uri_file = /var/run/couchdb/couchdb.uri

  • users_db_security_editable

    New in version 3.0.0.

    When this configuration setting is set to false, reject any attempts to modify the _users database security object. Modification of this object is deprecated in 3.x and will be completely disallowed in CouchDB 4.x.

  • users_db_suffix

    Specifies the suffix (last component of a name) of the system database for storing CouchDB users.

    1. [couchdb]
    2. users_db_suffix = _users

  • util_driver_dir

    Specifies location of binary drivers (icu, ejson, etc.). This location and its contents should be readable for the user that runs the CouchDB service.

    1. [couchdb]
    2. util_driver_dir = /usr/lib/couchdb/erlang/lib/couch-1.5.0/priv/lib

  • uuid

    New in version 1.3.

    Unique identifier for this CouchDB server instance.

    1. [couchdb]
    2. uuid = 0a959b9b8227188afc2ac26ccdf345a6

  • view_index_dir

    Specifies location of CouchDB view index files. This location should be writable and readable for the user that runs the CouchDB service (couchdb by default).

    1. [couchdb]
    2. view_index_dir = /var/lib/couchdb