Describes how HPE Ezmeral Data Fabric Database tables are implemented directly in the data-fabric filesystem, which allows HPE Ezmeral Data Fabric Database to leverage the same architecture as the rest of the data-fabric platform and results in minimal additional management.
As volumes are a management entity that logically organize a cluster’s data, they can be used to enforce disk usage limits, set replication levels, define snapshots and mirrors, and establish ownership and accountability.
Volumes do not have a fixed size and they do not occupy disk space until the data-fabric filesystem writes data to a container within the volume. A large volume may contain anywhere from 50-100 million containers.
Each region of a table, along with its corresponding write-ahead log (WAL) files, b-trees, and other associated structures, is stored in one container. Each container (which can be from 16 to 32 GB in size) can store more than one region (which by default is 4096MB in size). The recommended practice is to use the default size for a region and allow it to be split automatically. Massive regions can affect synchronization of containers and load balancing across a cluster. Smaller regions spread data better across more nodes.
For more information about containers, see Containers and the CLDB.