Gluster Cloud Night in Tokyo 2013 -- Tips for getting started

Copyright （C） 2013, NTTPC Communications, Inc. All Rights Reserved.

1

Agenda

!
!
!
!
!

 About me
 Tips 1: Installation
 Tips 2: NFS Workloads
 Tips 3: Logging
 Conclusion


2

About
Me

3

About me

!  Work at
!  Programmer
! 

as a ...

(Most recently)

! Also Interested in

!  Software Engineer
! Cloud Computing
! Big Data
! Something new technologies
! Supporting GlusterFS/Red Hat Storage Introduction
with Red Hat K.K.

4

About me

! GlusterFS since 2007 (v1.3.7)
!  for my internet crawler at first.

!  Love Gluster because of the ...
!  Potential
!  Performance
!  Code
!  Community

!  Introduced or introducing it into ...
!  Printer and scanner solution (field trial)
!  Email services
!  File storage services (WebDAV, NFS)
!  Backup services
!  Shared storage platform

!  A board member of the Gluster
Community

5

Getting started today!

See http://www.gluster.org/community/documentation/index.php/QuickStart

6

Tips 1
Installation

7

Tips 1: Installation
!   Question 1: Have you installed GlusterFS?


8

!   Question 2: Did you find it easy?


9

!   Question 2: Did you find it easy?
!   Question 3: Did you do it on each single node?


10

!
!
!
!

 
 
 
 

Question 1: Have you installed GlusterFS?
Question 2: Did you find it easy?
Question 3: Did you do it on each single node?
Question 4: Don't you think you should take easier way?


11

!
!
!
!
!

 
 
 
 
 

Question 1: Have you installed GlusterFS?
Question 2: Did you find it easy?
Question 3: Did you do it on each single node?
Question 4: Don't you think you should take easier way?
Question 5: Do you use deployment automation tools?


12


Development team says that hand-to-hand construction of systems is inefficient so they want to
show an installation way with a deployment tool in the documents for installation.

13


Operational team says that they never want to learn the usage of deployment tools and never
trust them so they don't accept such a document and they will install the system by hand work.

14


My offer is that what development team should do is only copy the commands that the
deployment tool write on your stdout and paste them into the documents for operational team.
https://twitter.com/keithseahus/status/398453753352691714


15


Deployment
Automation
Tools

16

A node for automated deployment
deployment
automation
tool

peer 1

peer 2

sshd

sshd

shell

3

4

N

shell
...


17

deployment
automation
tool

peer 1

peer 2

sshd

sshd

shell

3

4

N

shell
...


18

deployment
automation
tool

peer 1

peer 2

sshd

sshd

shell

3

4

N

shell
...

glusterfs

glusterfs


19

deployment
automation
tool

peer 1

peer 2

sshd

sshd

shell

3

4

N

shell
...

glusterfs

glusterfs


20

deployment
automation
tool

peer 1

peer 2

sshd

sshd

shell

3

4

N

shell
...

glusterfs

glusterfs


21



22


I use this mainly in my projects
written in Ruby so am used to it.


23

Capistrano


24

Capistrano
$ gem install capistrano
$ cap install
mkdir -p config/deploy
create config/deploy.rb
create config/deploy/staging.rb
create config/deploy/production.rb
mkdir -p lib/capistrano/tasks
Capified
$ tree .
.
├── Capfile
├── config
│   ├── deploy
│   │   ├── production.rb
│   │   └── staging.rb
│   └── deploy.rb
└── lib
└── capistrano
└── tasks


25

capistrano-glusterfs


26

$ tree capistrano-glusterfs
├── Capfile
├── Gemfile
├── Gemfile.lock
├── LICENSE
├── README.md
├── config
│   │   ├── production.rb
│   │   ├── production.rb.example
│   │   ├── staging.rb
│   │   └── staging.rb.example
│   ├── deploy.rb
│   └── deploy.rb.example
└── lib
└── tasks
├── gluster.cap
├── glusterd.cap
└── glusterfs.cap


27

$ tree capistrano-glusterfs
├── Capfile
├── Gemfile
├── Gemfile.lock
├── LICENSE
├── README.md
├── config
│   │   ├── production.rb ... settings for production environment
│   │   ├── production.rb.example
│   │   ├── staging.rb ... settings for staging environment
│   │   └── staging.rb.example
│   ├── deploy.rb ... global settings and main sequences
│   └── deploy.rb.example
└── lib
└── tasks
├── gluster.cap ... tasks to execute gluster command remotely
├── glusterd.cap ... tasks to start/stop all remote glusterd
└── glusterfs.cap ... tasks for deploying GlusterFS


28

$ cat capistrano-glusterfs/config/deploy/staging.rb
set :stage, :staging
set :branch, "master"
server
server
server
server
server
server
server
server
server
server

'192.168.200.100',
'192.168.200.101',
'192.168.200.102',
'192.168.200.103',
'192.168.200.104',
'192.168.200.105',
'192.168.200.106',
'192.168.200.107',
'192.168.200.108',
'192.168.200.109',

roles:
roles:
roles:
roles:
roles:
roles:
roles:
roles:
roles:
roles:

%w(glusterfs
%w(glusterfs
%w(glusterfs
%w(glusterfs
%w(glusterfs
%w(glusterfs
%w(glusterfs
%w(glusterfs
%w(glusterfs
%w(glusterfs

glusterd gluster), user: 'deploy'
glusterd), user: 'deploy'


29

$ bundle exec cap -vT | grep -i "glusterfs:"
cap glusterfs:build
# Starting installation
cap glusterfs:compile
# Compile GlusterFS
cap glusterfs:configuration
# GlusterFS related configurations
cap glusterfs:dependancies
# Install GlusterFS dependancies
cap glusterfs:make_install
# Install GlusterFS
cap glusterfs:preparation
# Prepare installing GlusterFS
$ bundle exec cap -vT | grep -i "glusterd:"
cap glusterd:restart
# Restart glusterd
cap glusterd:start
# Start glusterd
cap glusterd:status
# Get the status of glusterd
cap glusterd:stop
# Stop glusterd
$ bundle exec cap -vT | grep -i "gluster:"
cap gluster:peer:help
# Help command for peer
cap gluster:peer:status
# list status of peers
cap gluster:pool:list
# list all the nodes in the pool
cap gluster:volume:help
# display help for the volume command
cap gluster:volume:info
# list information of all volumes
cap gluster:volume:list
# list all volumes in cluster
cap gluster:volume:status
# display status of all volume(s)/brick


30


http://www.capistranorb.com/documentation/getting-started/flow/


31


prepare and install
dependancies
before starting

build GlusterFS from
source and install it
after published
http://www.capistranorb.com/documentation/getting-started/flow/


32

task :preparation do
....
execute "sudo -i yum install -y wget git yum-priorities"
....
end


33

task :dependancies do
....
dependancies = %w[
openssh-clients
make
rpm-build
bison
flex
automake
libtool
ncurses-devel
readline-devel
openssl-devel
libxml2-devel
libibverbs-devel
libacl-devel
libattr-devel
python-devel
python-setuptools
lvm2-devel
systemtap-sdt-devel
libaio-devel
xfsprogs
]

34

task :compile do
on roles(:glusterfs), in: :sequence, wait: 5 do
execute "cd #{DIR}; sh ./autogen.sh"
execute "cd #{DIR}; sh ./configure
--prefix=#{INSTALL_PATH}
--enable-bd-xlator
--enable-fusermount
--enable-systemtap
--enable-debug"
execute "cd #{DIR}; make"
end
end


35

task :make_install do
on roles(:glusterfs), in: :sequence, wait: 5 do
execute "cd #{DIR}; sudo make install"
symlink = "/usr/local/glusterfs"
execute "sudo -i rm -f #{symlink}" if test("[ -L #{symlink} ]")
execute "sudo -i ln -snf #{INSTALL_PATH} #{symlink}"
end
end


36

$ git clone git@github.com:keithseahus/capistrano-glusterfs.git
$ cd capistrano-glusterfs
$ bundle exec cap staging deploy


37

$ git clone git@github.com:keithseahus/capistrano-glusterfs.git
$ cd capistrano-glusterfs
$ bundle exec cap staging deploy
DEBUG [e5bdd4a7] Running /usr/bin/env /bin/egrep '/bin' ~/.bashrc > /dev/null;
exit $? on 192.168.200.101
DEBUG [e5bdd4a7] Command: /bin/egrep '/bin' ~/.bashrc > /dev/null; exit $?
DEBUG [e5bdd4a7] Finished in 0.096 seconds with exit status 0 (successful).
INFO [a54cf65d] Running /usr/bin/env sudo -i yum install -y wget git yumpriorities on 192.168.200.101
DEBUG [a54cf65d] Command: sudo -i yum install -y wget git yum-priorities
DEBUG [a54cf65d] Loaded plugins: fastestmirror, priorities
DEBUG [a54cf65d] Loading mirror speeds from cached hostfile
epel/metalink
| 6.4 kB
00:00
DEBUG [a54cf65d]
* base: ftp.tsukuba.wide.ad.jp
DEBUG [a54cf65d]
* epel: ftp.kddilabs.jp
DEBUG [a54cf65d]
* extras: ftp.tsukuba.wide.ad.jp
DEBUG [a54cf65d]
* remi: rpms.famillecollet.com
DEBUG [a54cf65d]
* remi-php55: rpms.famillecollet.com
DEBUG [a54cf65d]
* remi-test: rpms.famillecollet.com
DEBUG [a54cf65d]
* rpmforge: ftp.kddilabs.jp
DEBUG [a54cf65d]
* updates: mirrors.tuna.tsinghua.edu.cn
...


38

...
DEBUG
DEBUG
DEBUG
DEBUG
DEBUG
DEBUG
DEBUG
DEBUG
DEBUG
DEBUG
DEBUG
DEBUG
DEBUG
DEBUG
DEBUG
DEBUG
DEBUG
...
INFO

[80062be9]
[80062be9]
[80062be9]
[80062be9]
[80062be9]
[80062be9]
[80062be9]
[80062be9]
[80062be9]
[80062be9]
[80062be9]
[80062be9]
[80062be9]
[80062be9]
[80062be9]
[80062be9]
[80062be9]

GlusterFS configure summary
===========================
FUSE client
: yes
Infiniband verbs
: no
epoll IO multiplex
: yes
argp-standalone
: no
fusermount
: yes
readline
: yes
georeplication
: yes
Linux-AIO
: yes
Enable Debug
: yes
systemtap
: yes
Block Device backend : yes
glupy
: yes
Use syslog
: yes
XML output
: yes
QEMU Block formats
: no

[a9e8de7e] Finished in 0.015 seconds with exit status 0 (successful).


39

$ bundle exec cap staging gluster:pool:list
INFO [201946fe] Running /usr/bin/env sudo -i gluster pool list on
192.168.200.101
DEBUG [201946fe] Command: sudo -i gluster pool list
DEBUG [201946fe] UUID
Hostname State
DEBUG [201946fe] d185fa19-d1a1-489c-a653-4510122f5278 localhostConnected
INFO [201946fe] Finished in 0.294 seconds with exit status 0 (successful).
$ bundle exec cap staging glusterd:status
INFO [cb482772] Running /usr/bin/env sudo -i /sbin/service glusterd status on
192.168.200.101
DEBUG [cb482772] Command: sudo -i /sbin/service glusterd status
INFO [cb482772] Finished in 0.151 seconds with exit status 0 (successful).
DEBUG [cb482772] glusterd (pid 25855) is running...
INFO [cb482772] Finished in 0.151 seconds with exit status 0 (successful).


40

$ bundle exec cap staging gluster:volume:help
INFO [4628fd38] Running /usr/bin/env sudo -i gluster volume help on
192.168.200.101
DEBUG [4628fd38] Command: sudo -i gluster volume help
DEBUG [4628fd38] volume info [all|<VOLNAME>] - list information of all volumes
DEBUG [4628fd38] volume create <NEW-VOLNAME> [stripe <COUNT>] [replica <COUNT>]
[device vg] [transport <tcp|rdma|tcp,rdma>] <NEW-BRICK> ... [force] - create a
new volume of specified type with mentioned bricks
DEBUG [4628fd38] volume delete <VOLNAME> - delete volume specified by <VOLNAME>
DEBUG [4628fd38] volume start <VOLNAME> [force] - start volume specified by
<VOLNAME>
DEBUG [4628fd38] volume stop <VOLNAME> [force] - stop volume specified by
<VOLNAME>
DEBUG [4628fd38] volume add-brick <VOLNAME> [<stripe|replica> <COUNT>] <NEWBRICK> ... [force] - add brick to volume <VOLNAME>
DEBUG [4628fd38] volume remove-brick <VOLNAME> [replica <COUNT>] <BRICK> ...
{start|stop|status|commit|force} - remove brick from volume <VOLNAME>
DEBUG [4628fd38] volume rebalance <VOLNAME> [fix-layout] {start|stop|status}
[force] - rebalance operations
DEBUG [4628fd38] volume replace-brick <VOLNAME> <BRICK> <NEW-BRICK> {start
[force]|pause|abort|status|commit [force]} - replace-brick operations
DEBUG [4628fd38] volume set <VOLNAME> <KEY> <VALUE> - set options for volume
<VOLNAME>
...

41


capistrano-glusterfs is available here:
https://github.com/keithseahus/capistrano-glusterfs


42

Tips 2
NFS Workloads


43

Tips 2: NFS Workloads
!   Question 1: Do you mount GlusterFS in NFS?


44

!   Question 1: Do you mount GlusterFS in NFS?
!   Question 2: Which is your main workload, write or read?


45


peer 1
glusterd

glustershd

peer 2
glusterfs

d

shd

3

4

N

fs

...
glusterfsd
brick

brick

brick

fsd
brick

b

b

b

b


46


TCP connection
in gluster protocol
peer 1
glusterd

glustershd

peer 2
glusterfs

d

shd

3

4

N

fs

...
glusterfsd
brick

brick

brick

fsd
brick

b

b

b

b


47

NFS Client
user app
/mnt/nfs
vfs

page
cache
kernel

peer 1
glusterd

glustershd

peer 2
glusterfs

d

shd

3

4

N

fs

...
glusterfsd
brick

brick

brick

fsd
brick

b

b

b

b


48

NFS Client
user app
/mnt/nfs
vfs

page
cache

TCP connection
in NFS v3

kernel

peer 1
glusterd

glustershd

peer 2
glusterfs

d

shd

3

4

N

fs

...
glusterfsd
brick

brick

brick

fsd
brick

b

b

b

b


49

NFS Client
read access
to a file

user app
/mnt/nfs
vfs

page
cache
kernel

peer 1
glusterd

glustershd

peer 2
glusterfs

d

shd

3

4

N

fs

...
glusterfsd
brick

brick

brick

fsd
brick

b

b

b

b


50

NFS Client
user app
/mnt/nfs
vfs

page
cache
kernel

performance/io-cache

peer 1
glusterd

glustershd

peer 2
glusterfs

d

shd

3

4

N

fs

...
glusterfsd
brick

brick

brick

fsd
brick

b

b

b

b


51

NFS Client
user app
/mnt/nfs
vfs

activate cachefilesd
/var/cache/fscache

page
cache

cachefilesd

kernel

peer 1
glusterd

glustershd

peer 2
glusterfs

d

shd

3

4

N

fs

...
glusterfsd
brick

brick

brick

fsd
brick

b

b

b

b


52

NFS Client
user app
/mnt/nfs
vfs

read files from its own RAM!

/var/cache/fscache

page
cache

cachefilesd

kernel

peer 1
glusterd

glustershd

peer 2
glusterfs

d

shd

3

4

N

fs

...
glusterfsd
brick

brick

brick

fsd
brick

b

b

b

b


53

# NFS_SERVER=192.168.200.101
# MOUNT_POINT=/mnt/nfs


54

# NFS_SERVER=192.168.200.101
# yum install -y cachefilesd


55

# NFS_SERVER=192.168.200.101
# if test `grep 'SELINUX=disabled' /etc/selinux/config > /dev/null; echo $?` -ne
0; then
sed -i 's/^secctx/#secctx/g' /etc/cachefilesd.conf
fi


56

# NFS_SERVER=192.168.200.101
0; then
fi
# chkconfig cachefilesd on
# service cachefilesd start


57

# NFS_SERVER=192.168.200.101
0; then
fi
# chkconfig cachefilesd on
# service cachefilesd start
# mount -t nfs -o fsc,vers=3 $NFS_SERVER $MOUNT_POINT


58

# free -m
root@dev-centos:/root
total
Mem:
996
-/+ buffers/cache:
Swap:
2015

used
926
314
0

free
69
682
2015

shared
0

buffers
32

cached
579

# ls /var/cache/fscache/cache/@4a/I03nfs/@7f/Jc0000000000000cG0I00/@8d/
J1100000000000QFi24tY1EH900000000000M000000g00000100Kb000wFe000jt000oG3000000040
000g000000000/
@01 @0d @13 @1b @22 @35 @40 @50 @58 @61 @6e @78 @87 @a7 @b3 @b9
@d1 @d7 @e6
@06 @10 @17 @1e @25 @3c @4d @52 @5d @63 @6f @81 @97 @a9 @b6 @c1
@d3 @dc @f1
@0a @11 @1a @21 @2b @3d @4f @57 @5f @66 @73 @82 @9a @ae @b7 @cc
@d4 @de @fe
# du -h /var/cache/fscache/cache/@4a/I03nfs/@7f/Jc0000000000000cG0I00/@8d/
000g000000000/
186M /var/cache/fscache/cache/@4a/I03nfs/@7f/Jc0000000000000cG0I00/@8d/
000g000000000/

59

nodes:
VirtualBox
CentOS 6.4 x86_64
4 vCPUs, Core i7 2.4GHz
2GB RAM
Striped SSDs


60

nodes:
VirtualBox
CentOS 6.4 x86_64
2GB RAM
Striped SSDs
postmark 1.51
set size 1048576 10485760
set number 500
set transactions 1000
set location /mnt/nfs/rep2
set subdirectories 100
set read 8192
set write 8192
set buffering true


61

nodes:
VirtualBox
CentOS 6.4 x86_64
2GB RAM
Striped SSDs
MB/sec (read)
postmark 1.51
set size 1048576 10485760
set number 500
set transactions 1000
set location /mnt/nfs/rep2
set subdirectories 100
set read 8192
set write 8192
set buffering true

↓Oops...

62


Okay... but this is still a hypothesis.
We need your feedback!


63

Tips 3
Logging


64

Tips 3: Logging
!   Question 1: Do you monitor GlusterFS logs?


65

Tips 3: Logging
!   Question 2: Do you utilize the logs?


66

Tips 3: Logging
!   Question 2: Do you utilize the logs?
!   Question 3: Do you use a log collector or aggregator?


67

Tips 3: Logging


68

Tips 3: Logging

I pick it up because:
•  easy to install
•  easy to configure
•  make unstructured logs structured
•  collect logs from multiple resources
•  output aggregated and structured
logs into a target as you prefer
•  easy to create a module
•  high performance
•  well maintained

69

Tips 3: Logging
NFS Client
user app
/mnt/nfs
vfs

/var/cache/fscache

page
cache

cachefilesd

kernel

peer 1
glusterd

glustershd

peer 2
glusterfs

d

shd

3

4

N

fs

...
glusterfsd
brick

brick

brick

fsd
brick

b

b

b

b


70

Tips 3: Logging
NFS Client

Log server

user app
/mnt/nfs
vfs

/var/cache/fscache

page
cache

cachefilesd

kernel

peer 1
glusterd

glustershd

peer 2
glusterfs

d

shd

3

4

N

fs

...
glusterfsd
brick

brick

brick

fsd
brick

b

b

b

b


71

Tips 3: Logging
NFS Client

Log server

user app
/mnt/nfs
vfs

/var/cache/fscache

page
cache

cachefilesd

kernel

peer 1
glusterd

glustershd

peer 2
glusterfs

d

shd

3

4

N

fs

...
glusterfsd
brick

brick

brick

fsd
brick

b

b

b

b


72

Tips 3: Logging
NFS Client

Log server

user app
/mnt/nfs
vfs

/var/cache/fscache

page
cache

cachefilesd

kernel

peer 1
glusterd

glustershd

peer 2
glusterfs

d

shd

3

4

N

fs

...
glusterfsd
brick

brick

brick

fsd
brick

b

b

b

b


73

Tips 3: Logging
NFS Client

Log server

user app
/mnt/nfs
vfs

/var/cache/fscache

page
cache

cachefilesd

kernel

peer 1
glusterd

glustershd

peer 2
glusterfs

d

shd

3

4

N

fs

...
glusterfsd
brick

brick

brick

fsd
brick

b

b

b

b


74

Tips 3: Logging
NFS Client

Log server

user app
/mnt/nfs
vfs

/var/cache/fscache

page
cache

cachefilesd

kernel

peer 1
glusterd

glustershd

peer 2
glusterfs

d

shd

3

4

N

fs

...
glusterfsd
brick

brick

brick

fsd
brick

b

b

b

b


75

Tips 3: Logging
/etc/td-agent/td-agent.conf (on the log server)
<source>
type forward
port 24224
bind 0.0.0.0
</source>
<match filtered.glusterd.**>
type file
path /home/keith/var/log/fluent/glusterd
</match>

Today I will get the td-agent
output the logs into a file.


76

Tips 3: Logging
/etc/td-agent/td-agent.conf (on the GlusterFS peers)
<source>
type tail
path /var/log/glusterfs/usr-local-glusterfs-3.4.0beta2-etc-glusterfs-glusterd.vol.log
pos_file /var/log/td-agent/usr-local-glusterfs-3.4.0beta2-etc-glusterfs-glusterd.vol.log.pos
tag glusterd
format /^(?:[(?<date_ymd>[0-9]{4}-[01][0-9]-[0-3][0-9]) (?<time_hms>[0-2][0-9]:[0-5][0-9]:[0-6]
[0-9]).(?<time_usec>[0-9]{6})]) (?<log_level>[TDINWECA]) (?:[(?<source_file_name>[^[]:/ ]*):(?
<source_line>[0-9]*):(?<function_name>[^[]:/ ]*)]) (?<component>[^[]:/ ]*): *(?<message>.*)$/
rotate_wait 5
</source>
<match glusterd.**>
type hostname
key_name host
add_prefix filtered
</match>

Too complex to input
and maintain!

<match filtered.glusterd.**>
type forward
send_timeout 60s
recover_wait 10s
heartbeat_interval 1s
phi_threshold 8
hard_timeout 60s
<server>
…


77

Tips 3: Logging


78

Tips 3: Logging

You can specify log levels
to forward.


79

Tips 3: Logging

You can specify each field
name to output in JSON.

Comment out if you don't
need the fields.


80

Tips 3: Logging

Parse error should be
treated as a failure of
fluent-plugin-glusterfs.


81

Tips 3: Logging
It makes the logs structured in JSON.
[root@glusterfs-unstable-01 plugin]# tail -3 /var/log/glusterfs/usr-local-glusterfs-3.4.0beta2-etcglusterfs-glusterd.vol.log
[2013-07-07 15:52:43.778961] I [socket.c:3495:socket_init] 0-management: using system polling thread
[2013-07-07 15:52:43.779397] W [socket.c:514:__socket_rwv] 0-management: readv failed (No data
available)
[2013-07-07 15:52:43.779668] I [socket.c:2236:socket_event_handler] 0-transport: disconnecting now

[root@dev-centos ~]# grep glusterfs-unstable-01 /home/keith/var/log/fluent/glusterd.
20130708.b4e0ed6e32655d35f | tail -3
2013-07-08T00:52:43+09:00
filtered.glusterd
{"date_ymd":"2013-07-07","time_hms":"15:52:43","time_usec":"778961","log_level":"I","source_file_name":
"socket.c","source_line":"3495","function_name":"socket_init","component":"0management","message":"using system polling thread","host":"glusterfs-unstable-01.localdomain"}
2013-07-08T00:52:43+09:00
filtered.glusterd
{"date_ymd":"2013-07-07","time_hms":"15:52:43","time_usec":"779397","log_level":"W","source_file_name":
"socket.c","source_line":"514","function_name":"__socket_rwv","component":"0management","message":"readv failed (No data available)","host":"glusterfs-unstable-01.localdomain"}
2013-07-08T00:52:43+09:00
filtered.glusterd
"socket.c","source_line":"2236","function_name":"socket_event_handler","component":"0transport","message":"disconnecting now","host":"glusterfs-unstable-01.localdomain"}

82

Tips 3: Logging
The logs on each peer could be output in a single log file.
20130708.b4e0ed6e32655d35f | tail -3
2013-07-08T00:52:43+09:00
filtered.glusterd
2013-07-08T00:52:43+09:00
filtered.glusterd
2013-07-08T00:52:43+09:00
filtered.glusterd
20130708.b4e0ed6e32655d35f | tail -3
2013-07-08T00:52:43+09:00
filtered.glusterd
2013-07-08T00:52:43+09:00
filtered.glusterd
2013-07-08T00:52:43+09:00
filtered.glusterd

83

Tips 3: Logging

Also available on Gluster Forge:
https://forge.gluster.org/fluent-plugin-glusterfs


84

Tips 3: Logging

More detailed explanation in Japanese is here!:
http://www.nttpc.co.jp/company/r_and_d/technology/gluster_fs_fluentd.html

85

Conclusion


86

Conclusion

!  Deployment automation tools are
useful to install and operate
GlusterFS on multiple nodes.
!  With cachefilesd, NFS can might
be more efficient under heavy
read workload.
!  Aggregating GlusterFS logs is easy
enough and you can utilize them.


87

Gluster Cloud Night in Tokyo 2013 -- Tips for getting started

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Gluster Cloud Night in Tokyo 2013 -- Tips for getting started

Similar to Gluster Cloud Night in Tokyo 2013 -- Tips for getting started (20)

More from Keisuke Takahashi

More from Keisuke Takahashi (13)

Recently uploaded

Recently uploaded (20)

Gluster Cloud Night in Tokyo 2013 -- Tips for getting started