Red Hat Gluster Storage 3 (formerly Red Hat Storage Server 3): Supported and Recommended Workloads

Updated -

Describes the sweet spot workloads for Red Hat Gluster Storage (formerly Red Hat Storage Server) as well as workloads to avoid.

Overview

This article describes the workloads that are best suited for Red Hat Gluster Storage (formerly Red Hat Storage Server).

Environment

  • Red Hat Gluster Storage 3
  • Red Hat Gluster Storage for On-premise

Best Fit and Optimal Workloads

Red Hat Gluster Storage offers an open software-defined storage solution for reliable and cost-effective storage of unstructured file based data. It is highly reliable and provides optimum performance for deployments that typically involve the following use case:

  • Cold Storage for Splunk Analytics Workloads
  • Hadoop Compatible File System for running Hadoop Analytics
  • ownCloud File Sync n' Share
  • Digital multi-media (video, audio, pictures) serving (e.g., content delivery networks, online radio)
  • Disaster Recovery using Geo-replication
  • Live virtual machine image store for Red Hat Enterprise Virtualization
  • Large File & Object Store (using either NFS, SMB or FUSE client)
  • Active archiving and near-line storage
  • Backup target for Commvault Simpana
  • Shared storage for ActiveMQ
  • Shared storage for Tibco EMS
  • Enterprise NAS dropbox & object Store / Cloud Storage for service providers
  • Transactional database workloads in RHGS+RHEV environment where RHGS is the back-end store for VMs.
  • Persistent storage for containers in an OpenShift environment

Workloads to Avoid

Red Hat Gluster Storage is not recommended to be used for workloads that are

  • Write-mostly and involve a lot of contention
  • RHGS as backend for VMWare for storing live VM image

Related Knowledgebase Articles

See also this KBase for exceptions, unsupported workloads, and the architecture review process Red Hat Gluster Storage 3 (formerly Red Hat Storage Server 3): Architecture Review Process

Was this helpful?

We appreciate your feedback. Leave a comment if you would like to provide more detail.
It looks like we have some work to do. Leave a comment to let us know how we could improve.