Red Hat Summit Red Hat SummitSupportConsoleDéveloppeursCommencer un essaiContact

Ce contenu n'est pas disponible dans la langue sélectionnée.

11.3. Expanding Volumes

Volumes can be expanded while the trusted storage pool is online and available. For example, you can add a brick to a distributed volume, which increases distribution and adds capacity to the Red Hat Gluster Storage volume. Similarly, you can add a group of bricks to a replicated or distributed replicated volume, which increases the capacity of the Red Hat Gluster Storage volume.

Note

When expanding replicated or distributed replicated volumes, the number of bricks being added must be a multiple of the replica count. For example, to expand a distributed replicated volume with a replica count of 2, you need to add bricks in multiples of 2 (such as 4, 6, 8, etc.).

Important

Converting an existing distribute volume to replicate or distribute-replicate volume is not supported.

Expanding a Volume

  1. From any server in the trusted storage pool, use the following command to probe the server on which you want to add a new brick : 
    # gluster peer probe HOSTNAMEgluster peer probe HOSTNAME
    Copy to Clipboard Toggle word wrap
    For example: 
    # gluster peer probe server5
Probe successful

# gluster peer probe server6
Probe successful
    Copy to Clipboard Toggle word wrap
  2. Add the bricks using the following command: 
    # gluster volume add-brick VOLNAME NEW_BRICKgluster volume add-brick VOLNAME NEW_BRICKgluster volume add-brick VOLNAME NEW_BRICK
    Copy to Clipboard Toggle word wrap
    For example: 
    # gluster volume add-brick test-volume server5:/rhgs/brick5/ server6:/rhgs/brick6/
Add Brick successful
    Copy to Clipboard Toggle word wrap
  3. Check the volume information using the following command: 
    # gluster volume info
    Copy to Clipboard Toggle word wrap
    The command output displays information similar to the following: 
    Volume Name: test-volume
Type: Distribute-Replicate
Status: Started
Number of Bricks: 6
Bricks:
Brick1: server1:/rhgs/brick1
Brick2: server2:/rhgs/brick2
Brick3: server3:/rhgs/brick3
Brick4: server4:/rhgs/brick4
Brick5: server5:/rhgs/brick5
Brick6: server6:/rhgs/brick6
    Copy to Clipboard Toggle word wrap
  4. Rebalance the volume to ensure that files will be distributed to the new brick. Use the rebalance command as described in Section 11.7, “Rebalancing Volumes”.
    The add-brick command should be followed by a rebalance operation to ensure better utilization of the added bricks.

11.3.1. Expanding a Tiered Volume
Copier lien

You can add a group of bricks to a cold tier volume and to the hot tier volume to increase the capacity of the Red Hat Gluster Storage volume.

11.3.1.1. Expanding a Cold Tier Volume
Copier lien

Expanding a cold tier volume is same as a non-tiered volume. If you are reusing the brick, ensure to perform the steps listed in “Section 5.4.3, “ Reusing a Brick from a Deleted Volume ”” section.
  1. Detach the tier by performing the steps listed in Section 17.7, “Detaching a Tier from a Volume”
  2. From any server in the trusted storage pool, use the following command to probe the server on which you want to add a new brick : 
    # gluster peer probe HOSTNAMEgluster peer probe HOSTNAME
    Copy to Clipboard Toggle word wrap
    For example: 
    # gluster peer probe server5
Probe successful

# gluster peer probe server6
Probe successful
    Copy to Clipboard Toggle word wrap
  3. Add the bricks using the following command: 
    # gluster volume add-brick VOLNAME NEW_BRICKgluster volume add-brick VOLNAME NEW_BRICKgluster volume add-brick VOLNAME NEW_BRICK
    Copy to Clipboard Toggle word wrap
    For example: 
    # gluster volume add-brick test-volume server5:/rhgs/brick5/ server6:/rhgs/brick6/
    Copy to Clipboard Toggle word wrap
  4. Rebalance the volume to ensure that files will be distributed to the new brick. Use the rebalance command as described in Section 11.7, “Rebalancing Volumes”.
    The add-brick command should be followed by a rebalance operation to ensure better utilization of the added bricks.
  5. Reattach the tier to the volume with both old and new (expanded) bricks:
    # gluster volume tier VOLNAME attach [replica COUNT] NEW-BRICK...

    Important

    When you reattach a tier, an internal process called fix-layout commences internally to prepare the hot tier for use. This process takes time and there will a delay in starting the tiering activities.
    If you are reusing the brick, be sure to clearly wipe the existing data before attaching it to the tiered volume.

11.3.1.2. Expanding a Hot Tier Volume
Copier lien

You can expand a hot tier volume by attaching and adding bricks for the hot tier.
  1. Detach the tier by performing the steps listed in Section 17.7, “Detaching a Tier from a Volume”
  2. Reattach the tier to the volume with both old and new (expanded) bricks:
    # gluster volume tier VOLNAME attach [replica COUNT] NEW-BRICK...
    For example, 
    # gluster volume tier test-volume attach replica 2 server1:/rhgs/tier5 server2:/rhgs/tier6 server1:/rhgs/tier7 server2:/rhgs/tier8
    Copy to Clipboard Toggle word wrap

    Important

    When you reattach a tier, an internal process called fix-layout commences internally to prepare the hot tier for use. This process takes time and there will a delay in starting the tiering activities.
    If you are reusing the brick, be sure to clearly wipe the existing data before attaching it to the tiered volume.

11.3.2. Expanding a Dispersed or Distributed-dispersed Volume
Copier lien

Expansion of a dispersed or distributed-dispersed volume can be done by adding new bricks. The number of additional bricks should be in multiple of basic configuration of the volume. For example, if you have a volume with configuration (4+2 = 6), then you must only add 6 (4+2) or multiple of 6 bricks (such as 12, 18, 24 and so on).

Note

If you add bricks to a Dispersed volume, it will be converted to a Distributed-Dispersed volume, and the existing dispersed volume will be treated as dispersed subvolume.
  1. From any server in the trusted storage pool, use the following command to probe the server on which you want to add new bricks: 
    # gluster peer probe HOSTNAMEgluster peer probe HOSTNAME
    Copy to Clipboard Toggle word wrap
    For example: 
    # gluster peer probe server4
Probe successful

# gluster peer probe server5
Probe successful

# gluster peer probe server6
Probe successful
    Copy to Clipboard Toggle word wrap
  2. Add the bricks using the following command: 
    # gluster volume add-brick VOLNAME NEW_BRICKgluster volume add-brick VOLNAME NEW_BRICKgluster volume add-brick VOLNAME NEW_BRICK
    Copy to Clipboard Toggle word wrap
    For example: 
    # gluster volume add-brick test-volume server4:/rhgs/brick7 server4:/rhgs/brick8 server5:/rhgs/brick9 server5:/rhgs/brick10 server6:/rhgs/brick11 server6:/rhgs/brick12
    Copy to Clipboard Toggle word wrap
  3. (Optional) View the volume information after adding the bricks: 
    # gluster volume info VOLNAMEgluster volume info VOLNAME
    Copy to Clipboard Toggle word wrap
    For example: 
    # gluster volume info test-volume
Volume Name: test-volume
Type: Distributed-Disperse
Volume ID: 2be607f2-f961-4c4b-aa26-51dcb48b97df
Status: Started
Snapshot Count: 0
Number of Bricks: 2 x (4 + 2) = 12
Transport-type: tcp
Bricks:
Brick1: server1:/rhgs/brick1
Brick2: server1:/rhgs/brick2
Brick3: server2:/rhgs/brick3
Brick4: server2:/rhgs/brick4
Brick5: server3:/rhgs/brick5
Brick6: server3:/rhgs/brick6
Brick7: server4:/rhgs/brick7
Brick8: server4:/rhgs/brick8
Brick9: server5:/rhgs/brick9
Brick10: server5:/rhgs/brick10
Brick11: server6:/rhgs/brick11
Brick12: server6:/rhgs/brick12
Options Reconfigured:
transport.address-family: inet
performance.readdir-ahead: on
nfs.disable: on
    Copy to Clipboard Toggle word wrap
  4. Rebalance the volume to ensure that the files will be distributed to the new brick. Use the rebalance command as described in Section 11.7, “Rebalancing Volumes”.
    The add-brick command should be followed by a rebalance operation to ensure better utilization of the added bricks.
Retour au début
Red Hat logoGithubredditYoutubeTwitter

Apprendre

Essayez, achetez et vendez

Communautés

À propos de la documentation Red Hat

Nous aidons les utilisateurs de Red Hat à innover et à atteindre leurs objectifs grâce à nos produits et services avec un contenu auquel ils peuvent faire confiance. Découvrez nos récentes mises à jour.

Rendre l’open source plus inclusif

Red Hat s'engage à remplacer le langage problématique dans notre code, notre documentation et nos propriétés Web. Pour plus de détails, consultez le Blog Red Hat.

À propos de Red Hat

Nous proposons des solutions renforcées qui facilitent le travail des entreprises sur plusieurs plates-formes et environnements, du centre de données central à la périphérie du réseau.

Theme

© 2025 Red Hat