Creating an EBS Volume and Attaching it to an Instance

This section describes how to create an EBS volume and attach it to your MarkLogic Server instance.

• In general, it is a best practice is to have one volume per node and one forest per volume.

• We recommend that you use large EBS volumes as opposed to multiple smaller ones for these reasons:

  • Larger EBS volumes (gp2) have faster I/O as described by the Amazon EBS Volume types.

  • Each EBS volume needs enough spare capacity to allow for merges.

• We recommend that you have one large EBS data volume per node. Having multiple volumes per instance is not worth the additional administrative complexity.

• When resizing, adopt a vertical scaling approach (that is, growing into a single bigger EBS volume versus adding multiple smaller volumes per node).

• S3 storage is eventually consistent; therefore, S3 can only be used for backups or read-only forests in MarkLogic Server (otherwise you risk the possibility of data loss).