Control Center application data storage

Control Center uses a dedicated LVM thin pool on the master host to store application data and snapshots of application data.
  • The distributed file system (DFS) of each tenant application that serviced manages is stored in separate virtual devices. The initial size of each tenant device is copied from the base device, which is created during the initial startup of serviced.
  • Snapshots of tenant data, used as temporary restore points, are stored in separate virtual devices, outside of tenant virtual devices. The size of a snapshot depends on the size of the tenant device, and grows over time.
The Control Center master host requires high-performance, persistent storage. Storage can be local or remote.
  • For local storage, solid-state disk (SSD) devices are recommended.
  • For remote storage, storage-area network (SAN) systems have been tested. High-performance SAN systems are recommended, as is assigning separate logical unit numbers (LUNs) for each mounted path.
The overall response times of master host storage affect the performance and stability of Control Center internal services and the applications it manages. For example, ZooKeeper (a key internal service) is sensitive to storage latency greater than 1000 milliseconds.
Control Center includes the serviced-storage utility for creating and managing its thin pool. The serviced-storage utility can:
  • use physical devices or partitions, or LVM volume groups, to create a new LVM thin pool for application data
  • add space to a tenant device at any time
  • identify and clean up orphaned snapshots
  • create an LVM thin pool for Docker data