Database configuration

Database configuration files general match up with the payload to the /manage/v2/databases endpoints of the MarkLogic Management API.

Forests

The default database configuration lists the forests that will be attached to a database. In the following example, a forest called "my-content-01" will be attached to a database called "my-content".

{
  "database-name": "my-content",
  "schema-database": "Schemas",
  "triggers-database": "Triggers",
  "triple-index": "false",
  "forest": [
    "my-content-01"
  ]
}

The definition of the "my-content-01" forest is expected to be in the settings/[base-configuration|environments]/forests/ directory.

Forests Per Host

Instead of explicitly listing the forests, you may tell mlsound how many forests you want created on each host.

{
  "database-name": "my-content",
  "schema-database": "Schemas",
  "triggers-database": "Triggers",
  "triple-index": "false",
  "forest": {
    "forests-per-host": 4
  }
}

mlsound will see this configuration and will create, in this case, four forests for each host in the cluster, then attach them to the "my-content" database. The forests will be named with a "[db-name]-[host-index]-[forest-index]" convention, where "host-index" and "forest-index" are a three-digit (zero-padded) numbers.

When using the "forests-per-host" property, remove any corresponding settings/*/forests/ files.

Forest Removal

During wipe, mlsound will detach and remove those forests that are attached to the target database, rather than those specified by the configuration. This is by design, as the configuration may change, but wipe should not leave forests behind.