게시물 1,376건
   
[Ceph] PLACEMENT GROUP STATES
글쓴이 : 최고관리자 날짜 : 2018-05-15 (화) 16:24 조회 : 13365
글주소 :
                                

PLACEMENT GROUP STATES

When checking a cluster’s status (e.g., running ceph -w or ceph -s), Ceph will report on the status of the placement groups. A placement group has one or more states. The optimum state for placement groups in the placement group map is active + clean.

creating
Ceph is still creating the placement group.

activating
The placement group is peered but not yet active.

active
Ceph will process requests to the placement group.

clean
Ceph replicated all objects in the placement group the correct number of times.

down
A replica with necessary data is down, so the placement group is offline.
(필요한 데이타가 있는 복제본이 다운되어있어 PG가 오프라인 상태)

scrubbing
Ceph is checking the placement group metadata for inconsistencies.
(PG 메타데이타의 일관성 체크중)

deep
Ceph is checking the placement group data against stored checksums.
(PG 저장된 체크섬에 대해 체크중)

degraded
Ceph has not replicated some objects in the placement group the correct number of times yet.
(PG내 약간의 object들이 올바른 수대로 아직 복제되지 않은상태)

inconsistent
Ceph detects inconsistencies in the one or more replicas of an object in the placement group (e.g. objects are the wrong size, objects are missing from one replica after recovery finished, etc.).
(PG내 object에서 한개이상의 복제본에서 불일치를 감지 / 객체의 크기가 잘못되었거나 복구완료이후에 하나의 복제본에서 누락)

peering
The placement group is undergoing the peering process
(PG 피어링 프로세서 진행중)

repair
Ceph is checking the placement group and repairing any inconsistencies it finds (if possible).
(PG를 확인하고 불일치 복구(가능한경우))

recovering
Ceph is migrating/synchronizing objects and their replicas.

forced_recovery
High recovery priority of that PG is enforced by user.

recovery_wait
The placement group is waiting in line to start recover.

recovery_toofull
A recovery operation is waiting because the destination OSD is over its full ratio.

recovery_unfound
Recovery stopped due to unfound objects.

backfilling
Ceph is scanning and synchronizing the entire contents of a placement group instead of inferring what contents need to be synchronized from the logs of recent operations. Backfill is a special case of 
recovery.

forced_backfill
High backfill priority of that PG is enforced by user.

backfill_wait
The placement group is waiting in line to start backfill.

backfill_toofull
A backfill operation is waiting because the destination OSD is over its full ratio.
(OSD 비율을 초과하여 (디스크 저장공간이 부족)해서 backfill 작업이 대기중(계속할수 없는 상태))

backfill_unfound
Backfill stopped due to unfound objects.
(backfill 알려지지 않은 객체로 인해 중지)

incomplete
Ceph detects that a placement group is missing information about writes that may have occurred, or does not have any healthy copies. If you see this state, try to start any failed OSDs that may contain the needed information. In the case of an erasure coded pool temporarily reducing min_size may allow recovery.

stale
The placement group is in an unknown state - the monitors have not received an update for it since the placement group mapping changed.

remapped
The placement group is temporarily mapped to a different set of OSDs from what CRUSH specified.
(PG가 CRUSH로 지정한것과 다른 OSD에 임시로 맵핑)

undersized
The placement group has fewer copies than the configured pool replication level.
(PG에 복제본수가 Pool 복제본 수준보다 적다)

peered
The placement group has peered, but cannot serve client IO due to not having enough copies to reach the pool’s configured min_size parameter. Recovery may occur in this state, so the pg may heal up to min_size eventually.

snaptrim
Trimming snaps.

snaptrim_Wait
Queued to trim snaps.

snaptrim_Error
Error stopped trimming snaps.

이름 패스워드
비밀글 (체크하면 글쓴이만 내용을 확인할 수 있습니다.)
왼쪽의 글자를 입력하세요.
   

 



 
사이트명 : 모지리네 | 대표 : 이경현 | 개인커뮤니티 : 랭키닷컴 운영체제(OS) | 경기도 성남시 분당구 | 전자우편 : mojily골뱅이chonnom.com Copyright ⓒ www.chonnom.com www.kyunghyun.net www.mojily.net. All rights reserved.