Shulou(Shulou.com)06/03 Report--

GlusterFS Overview introduction to GlusterFS

Open source distributed file system

It is composed of storage server, client and NFS/Samba storage gateway.

No metadata server

RDMA: the characteristics of GlusterFS responsible for data transmission

Scalability and high performanc

High availability

Globally unified namespace

Elastic volume management

Based on standard protocol

GlusterFS terminology

Brick: storage nod

Volume: volum

FUSE: kernel module, user-side interaction module

VFS: virtual port

Glusterd: servic

Modular stack architecture

Modular, stackable architecture

Realize the responsible function through the combination of modules

GlusterFS working mode

Application: the client or application accesses data through the mount point of GlusterFSync

The kernel of VFS:linux system receives requests and processes them through VFS API.

FUSE: VFS delivers the data to the FUSE kernel file system, while the fuse file system delivers the data to the GlusterFS client side through the / dev/fuse device file

GlusterFS Client; transfers the data to the remote GlusterFS Server over the network and writes it to the server storage device

GlusterFS working principle GlusterFS Workflow Elastic HASH algorithm

Get a 32-bit integer by HASH algorithm

Divided into N contiguous subspaces, each space corresponds to a Brick

Advantages of resilient HASH algorithm

Ensure that the data is evenly distributed in each Brink

It solves the laziness of metadata server, and then solves the single point of failure and access bottleneck.

GlusterFS volumes with four Brick nodes, with an average distribution of range space to the power of 232m

Through the hash algorithm to find the corresponding brick node storage space, to allocate data storage, to call each node data

Volume type of GlusterFS

Distributed volume

Stripe roll

Copy Volum

Distributed stripe volume

Distributed replication Volum

Stripe replication Volum

Distributed stripe replication volume

Distributed volume

The file is not divided into blocks.

Save hash values by extending file properties

Support for underlying file systems such as ext3, ext4, ZFS, XFS, etc.

Distributed volumes have the following characteristics

Files are distributed on different servers. Lack of redundancy

Expand the size of the volume more easily and cheaply

A single point of failure can result in data loss

According to the data protection of lazy bottom layer

Create distributed volumes create a distributed volume file called dis-volume will distribute gluster volume create dis-volume server1:/dir1 server2:/dir2 stripe volumes in server1:/dir1, server2:/dir2, and server3:/dir3 according to HASH

The file is divided into N blocks (N stripe nodes) according to the offset, and the polled is stored in each Brick Server node.

Performance is particularly outstanding when storing large files

No redundancy, similar to Raid0

Improve efficiency by reading files from multiple server at the same time

The data is divided into smaller chunks and distributed to different stripes in the block server farm

Distribution reduces load and smaller files speed up access

No data redundancy

Create a stripe volume create a stripe volume file named Stripe-volume that will be stored in Server1:/dir1 and Server2:dir2 Brick by block polling gluster volume create stripe-volume stripe 2 transport tcp server1:/dir1 server2:/dir2 replication volume

Keep one or more copies of the same document

Replication mode has low disk utilization because the copy is saved.

If the storage space of multiple nodes is inconsistent, the capacity of the lowest node will be taken as the total capacity of the volume according to the bucket effect.

Characteristics

All servers in the volume keep a complete copy

The number of copies of the volume can be determined when the customer creates it.

At least two block servers or more servers

Have redundancy

Create replication volumes create replication volumes named rep-volume, files will store two replicas gluster volume create rep-volume replica 2 transport tcp server1:/dir1 server2:/dir2 distributed stripe volumes at the same time

Take into account the functions of distributed volumes and stripe volumes

Mainly used for large file access processing

At least 4 servers are required

Create a distributed stripe volume create a distributed stripe volume called dis-stripe. When configuring a distributed stripe volume, the number of storage servers contained in Brink in the volume must be a multiple of the stripe number (> = 2) gluster volume create rep-volume stripe 2 transport tcp server1:/dir1 server2:/dir2 server3:/dir1 server4:/dir2 distributed replication volume

Take into account the functions of distributed and replicated volumes

For situations where redundancy is required

Create a distributed replication volume to create a distributed stripe volume called dis-rep. When configuring a replication volume of a distributed stripe volume, the storage server contained in the Brink in the volume must be a multiple of the stripe number (> = 2 times) gluster volume volume create rep-volume replica 2 transport tcp server1:/dir1 server2:/dir2 server3:/dir1 server4:/dir2

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.