gluster scalability issues with more bricks and snapshots

Solution In Progress - Updated -

Issue

Imagine a gluster cluster where many brick processes are running on a node.

Ex: A distributed dispersed volume of the type 36x(4+2) running in a 6 node cluster. This will lead to 36 brick processes per node for that volume.

If volume snapshots are taken for the volume, then more brick processes will be running per node.

In such cases, a node restart will make some processes timing out. It also creates resources shortage such as running out of ports, running out of pid name space for the processes etc.

Environment

  • RHS-3.0
  • RHGS-3.1

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.