이 콘텐츠는 선택한 언어로 제공되지 않습니다.

16.4. Attaching a Tier to a Volume (Deprecated)


Warning

Tiering is considered deprecated as of Red Hat Gluster Storage 3.5. Red Hat no longer recommends its use, and does not support tiering in new deployments and existing deployments that upgrade to Red Hat Gluster Storage 3.5.3.
By default, tiering is not enabled on gluster volumes. An existing volume can be modified via a CLI command to have a hot tier. You must enable a volume by performing an attach tier operation. The attach command will declare an existing volume as cold tier and creates a new hot tier volume which is appended to it. Together, the combination is a single tiered volume.
It is highly recommended to provision your storage liberally and generously before attaching a tier. You create a normal volume and then attach bricks to it, which are the hot tier:
  1. Attach the tier to the volume by executing the following command:
    # gluster volume tier VOLNAME attach [replica COUNT] NEW-BRICK...
    For example,
    # gluster volume tier test-volume attach replica 3 server1:/rhgs/brick5/b1 server2:/rhgs/brick6/b2
    server1:/rhgs/brick7/b3 server2:/rhgs/brick8/b4
  2. Run gluster volume info command to optionally display the volume information.
    The command output displays information similar to the following:
    # gluster volume info test-volume
    Volume Name: test-volume
    Type: Tier
    Status: Started
    Number of Bricks: 8
    Transport-type: tcp
    Hot Tier :
    Hot Tier Type : Distributed-Replicate
    Number of Bricks: 2 x 2 = 4
    Brick1: server1:/rhgs/brick5/b1
    Brick2: server2:/rhgs/brick6/b2
    Brick3: server1:/rhgs/brick7/b3
    Brick4: server2:/rhgs/brick8/b4
    Cold Tier:
    Cold Tier Type : Distributed-Replicate
    Number of Bricks: 2 x 2 = 4
    Brick5: server1:/rhgs/brick1/b5
    Brick6: server2:/rhgs/brick2/b6
    Brick7: server1:/rhgs/brick3/b7
    Brick8: server2:/rhgs/brick4/b8
    Options Reconfigured:
    cluster.watermark-low: 70
    cluster.watermark-hi: 90
    cluster.tier-demote-frequency: 45
    cluster.tier-mode: cache
    features.ctr-enabled: on
    performance.readdir-ahead: on
The tier start command is triggered automatically after the tier has been attached. In some cases, if the tier process has not started you must start it manually using the gluster volume tier VOLNAME start force command.

16.4.1. Attaching a Tier to a Geo-replicated Volume (Deprecated)

Warning

Tiering is considered deprecated as of Red Hat Gluster Storage 3.5. Red Hat no longer recommends its use, and does not support tiering in new deployments and existing deployments that upgrade to Red Hat Gluster Storage 3.5.3.
You can attach a tier volume to the master volume of the geo-replication session for better performance.

Important

A crash has been observed in the Slave mounts when performance.quick-read option is enabled and geo-replicated from a tiered master volume. If the master volume is a tiered volume, you must disable the performance.quick-read option in the Slave Volume using the following command:
# gluster volume set Slavevol performance.quick-read off
  1. Stop geo-replication between the master and slave, using the following command:
    # gluster volume geo-replication MASTER_VOL SLAVE_HOST::SLAVE_VOL stop
    For example:
    # gluster volume geo-replication Volume1 example.com::slave-vol stop
  2. Attach the tier to the volume using the following command:
    # gluster volume tier VOLNAME attach [replica COUNT] NEW-BRICK...
    For example, to create a distributed-replicated tier volume with replica count two:
    # gluster volume tier test-volume attach replica 3 server1:/rhgs/brick1/b1 server2:/rhgs/brick2/b2
    server1:/rhgs/brick3/b3 server2:/rhgs/brick4/b4
  3. Restart the geo-replication sessions, using the following command:
    # gluster volume geo-replication MASTER_VOL SLAVE_HOST::SLAVE_VOL start
    For example
    # gluster volume geo-replication Volume1 example.com::slave-vol start
  4. Verify whether geo-replication session has started with tier's bricks, using the following command:
    # gluster volume geo-replication MASTER_VOL SLAVE_HOST::SLAVE_VOL status
    For example,
    # gluster volume geo-replication Volume1 example.com::slave-vol status
Red Hat logoGithubredditYoutubeTwitter

자세한 정보

평가판, 구매 및 판매

커뮤니티

Red Hat 문서 정보

Red Hat을 사용하는 고객은 신뢰할 수 있는 콘텐츠가 포함된 제품과 서비스를 통해 혁신하고 목표를 달성할 수 있습니다. 최신 업데이트를 확인하세요.

보다 포괄적 수용을 위한 오픈 소스 용어 교체

Red Hat은 코드, 문서, 웹 속성에서 문제가 있는 언어를 교체하기 위해 최선을 다하고 있습니다. 자세한 내용은 다음을 참조하세요.Red Hat 블로그.

Red Hat 소개

Red Hat은 기업이 핵심 데이터 센터에서 네트워크 에지에 이르기까지 플랫폼과 환경 전반에서 더 쉽게 작업할 수 있도록 강화된 솔루션을 제공합니다.

Theme

© 2026 Red Hat
맨 위로 이동