Glusterfs: Difference between revisions
(Added Knowledge Graph section) |
(Fix: remove --- horizontal lines (7 removed)) |
||
| Line 18: | Line 18: | ||
* 언제 사용하는가? - 서버 구성, 성능 튜닝, 문제 해결 시 | * 언제 사용하는가? - 서버 구성, 성능 튜닝, 문제 해결 시 | ||
== Purpose == | == Purpose == | ||
| Line 28: | Line 27: | ||
* Non-goals: 다른 주제로의 확장 | * Non-goals: 다른 주제로의 확장 | ||
== Key Concepts == | == Key Concepts == | ||
| Line 42: | Line 40: | ||
|} | |} | ||
== Detailed Explanation == | == Detailed Explanation == | ||
| Line 67: | Line 64: | ||
<nowiki>#</nowiki> gluster volume create ucmvolume nod1:/blok1 nod2:/blok1 | <nowiki>#</nowiki> gluster volume create ucmvolume nod1:/blok1 nod2:/blok1 | ||
== Best Practices == | == Best Practices == | ||
| Line 75: | Line 71: | ||
* 테스트 환경에서 먼저 검증 | * 테스트 환경에서 먼저 검증 | ||
== References == | == References == | ||
| Line 81: | Line 76: | ||
* [https://wiki.hpcmate.com Glusterfs] | * [https://wiki.hpcmate.com Glusterfs] | ||
== Related Pages == | == Related Pages == | ||
| Line 90: | Line 84: | ||
* [[Network]] | * [[Network]] | ||
[[Category:Linux]] | [[Category:Linux]] | ||
Revision as of 11:28, 17 July 2026
Overview
Glusterfs에 대한 기술 문서입니다.
Summary
- 무엇인가? - Glusterfs
- 왜 필요한가? - HPC 및 서버 환경에서 필수 개념
- 언제 사용하는가? - 서버 구성, 성능 튜닝, 문제 해결 시
Purpose
이 문서가 존재하는 이유
- Goal: Glusterfs에 대한 기술 정보 제공
- Scope: Glusterfs의 개념, 사용법, 설정
- Non-goals: 다른 주제로의 확장
Key Concepts
| Concept | Description | Related |
|---|---|---|
| Glusterfs | HPC/서버 환경에서 중요한 기술 개념 | Linux, Server |
Detailed Explanation
.glusterfs creates a hardlink for each of the file present in the brick. The contents of .glusterfs must not be touched unless you know very well what you are doing. Its apparent size is not real. It mostly contains hard-links to other files, so the net space usage contribution for this directory is very small.[1] If you use 'du' on the entire volume, you will get the actual used space because 'du' already takes into account hard links.
From the root of the brick, run this:
# du -sh * .glusterfs
# find .glusterfs -type f -links 1 #check if there are any files that have just 1 link
# find .glusterfs -type f | wc -l
Igor Cicimov describes well how to get rid of GlusterFS orphaned GFID hard links
# find /path-to-bric/.glusterfs -type f -links -2 -exec rm -fv {} \;
performance tuning, there are no magic values for these which work on all systems. The defaults in GlusterFS are configured at install time to provide best performance over mixed workloads. To squeeze performance out of GlusterFS, use an understanding of the below parameters and how them may be used in your setup. After making a change, be sure to restart all GlusterFS processes and begin benchmarking the new values.[2] # gluster peer status # gluster --remote-host=nod1 peer status # gluster pool list # gluster peer probe <IP> # gluster peer detach <node> # gluster peer detach <node> force # gluster volume create <Volume name> transport tcp <brick path> # gluster volume create ucmvolume nod1:/blok1 nod2:/blok1
Best Practices
- 최신 버전 사용 권장
- 공식 문서 참고
- 테스트 환경에서 먼저 검증
References
Related Pages
Knowledge Graph
Related