• Buy Now
    • Rackspace Cloud
    • Email & Apps
    • Fanatical Support for AWS
    • Managed Google Cloud Platform
    • Office 365
  • Log In
    • MyRackspace Portal
    • Cloud Control Panel
    • Rackspace Webmail Login
    • Cloud Office Control Panel
  • Rackspace Logo
  • Developer Home
  • Developer Documentation
  • Blogs ▼
    • Technical Blog
    • Rackspace Blog
    • Solve: Thought Leadership
  • Support Documentation

Developer Docs


Let’s Build Something Powerful Together!

End-to-End Multicloud Solutions.   Solving Together.™   Learn more at Rackspace.com

Submit an issue
  • Rackspace Private Cloud, v14
  • Technical FAQ
    • Preface
      • About Rackspace Private Cloud Powered By Openstack
      • RPCO configuration
      • Rackspace Private Cloud support
    • FAQ
      • Operating system and architecture
      • Networking
      • Database architecture
      • Clustered queue management
      • Failover and high availability
      • Load balancing
      • Log aggregation and management
    • Supported Software
      • Rackspace Private Cloud v14
      • Rackspace Private Cloud v13
      • Special Notes
    • Document history and additional information
      • Additional resources
    • Disclaimer
  • Optimization and Visualization User Guide
    • RPCO Optimization and Visualization User Guide
    • Product overview
      • Architecture
      • Features
        • Alarms
        • Ceph monitor
        • Chargeback
        • Charts
        • Heat map
        • Metrics
        • Reports
    • How-To
      • Configure a dynamic threshold
      • Configure chargeback costs
  • Release Notes
    • Preface
      • About Rackspace Private Cloud Powered By Openstack
      • RPCO configuration
      • Rackspace Private Cloud support
    • Known issues
    • What's new
      • Block Storage service (cinder)
        • Prelude
        • Features
        • Unsupported
      • Compute service (nova)
        • Prelude
        • Critical
        • Upgrade
        • Deprecations
        • Unsupported
        • Features
      • Dashboard (horizon)
        • Prelude
        • Fixes
        • Features
      • Identity service (keystone)
        • Prelude
        • Security
        • Features
        • Deprecations
        • Unsupported
      • Image service (glance)
        • Prelude
        • Critical
        • Upgrade
        • Deprecations
        • Features
      • Networking service (neutron)
        • Prelude
        • Deprecations
        • Unsupported
      • Object Storage (swift)
        • Prelude
        • Fixes
        • Features
      • Orchestration (heat)
        • Prelude
        • Features
    • What's changed
      • RPCO changelog by release
    • Document history and additional information
      • Additional resources
    • Disclaimer
  • Stand-alone Object Storage for RPCO Guide
    • Preface
      • About Rackspace Private Cloud Powered By Openstack
      • RPCO configuration
      • Rackspace Private Cloud support
    • Object Storage overview
      • Components
      • Configuration
      • System requirements
    • Prerequisites
    • Install Object Storage
      • Example Object Storage installation architecture
      • Configure and mount storage devices
      • Create networks
      • Configure an Object Storage deployment
        • Update the stand-alone Object Storage configuration files
        • Allow Identity users to use Object Storage
      • Run the Object Storage playbooks
      • Verify the installation
    • Object Storage monitoring
      • Service and response
      • Object Storage monitors
    • Object Storage configuration files
    • Document history and additional information
      • Additional resources

Database architecture#

Get answers to common technical questions about database architecture for Rackspace Private Cloud Powered By OpenStack (RPCO) 14.0.

Why does RPCO use MariaDB with Galera?

Rackspace DBAs are familiar with MariaDB with Galera, and RPCO support can use this knowledge to better support customers.

What are the requirements and restrictions for a MariaDB with Galera database cluster?

The cluster must contain at least three database nodes. RPCO architecture has three infrastructure nodes. and one database container is deployed on each node.

MariaDB with Galera clusters with an odd number of nodes function more effectively than clusters with an even number. A cluster with an even number of nodes is possible, but we do not recommend it.

For more information, see How is the cluster scaled up?.

How does the database cluster behave when a node fails?

If the failure is not a catastrophic failure of all nodes in the cluster, the cluster handles the failure gracefully.

** How does a cluster recover from node failure?**

Node failure recovery is documented in the RPCO Operations Guide.

How is the cluster scaled up?

Scaling the cluster must be done in odd numbers. For example, when expanding from three nodes, you can expand to five nodes, but not four. Even numbers of nodes can cause a "split brain" condition within the cluster.

The cluster is scaled by simply adding new nodes to it. Galera initiates data replication from within the existing nodes in the cluster, and the expansion should be seamless.

Previous Networking
Next Clustered queue management
Developer Network
  • Developer Center
  • API Documentation and User Guides
  • SDKs
  • Rackspace How-To
Blogs
  • Technical Blog
  • Rackspace Blog
  • Solve: Thought Leadership
Other Information
  • Customer Stories
  • Events
  • Programs
  • Careers
  • Style Guide for Technical Content
©2020 Rackspace US, Inc.
  • ©2020 Rackspace US, Inc.
  • About Rackspace
  • Privacy Statement
  • Website Terms
  • Trademarks