1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
|
<?xml version='1.0' encoding='UTF-8'?>
<!-- This document was created with Syntext Serna Free. --><!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "docbookV4.5/docbookx.dtd" []>
<chapter id="chap-Administration_Guide-Monitor_Workload">
<title>Monitoring your GlusterFS Workload</title>
<para>You can monitor the GlusterFS volumes on different parameters. Monitoring volumes helps in capacity planning and performance tuning tasks of the GlusterFS volume. Using these information, you can identify and troubleshoot issues. </para>
<para>You can use Volume Top and Profile commands to view the performance and identify bottlenecks/hotspots of each brick of a volume. This helps system administrators to get vital performance information whenever performance needs to be probed. </para>
<para>You can also perform statedump of the brick processes and nfs server process of a volume, and also view volume status and volume information. </para>
<section id="chap-Administration_Guide-Monitor_Workload-Profile">
<title>Running GlusterFS Volume Profile Command</title>
<para>GlusterFS Volume Profile command provides an interface to get the per-brick I/O information for each File Operation (FOP) of a volume. The per brick information helps in identifying bottlenecks in the storage system.
</para>
<para>This section describes how to run GlusterFS Volume Profile command by performing the following operations:
</para>
<itemizedlist>
<listitem>
<para><xref linkend="chap-Administration_Guide-Monitor_Workload-Profile-Start"/></para>
</listitem>
<listitem>
<para><xref linkend="chap-Administration_Guide-Monitor_Workload-Profile-Display"/></para>
</listitem>
<listitem>
<para><xref linkend="chap-Administration_Guide-Monitor_Workload-Profile-Stop"/></para>
</listitem>
</itemizedlist>
<section id="chap-Administration_Guide-Monitor_Workload-Profile-Start">
<title>Start Profiling</title>
<para>You must start the Profiling to view the File Operation information for each brick.
</para>
<para><emphasis role="bold">To start profiling: </emphasis></para>
<itemizedlist>
<listitem>
<para>Start profiling using the following command:
</para>
</listitem>
</itemizedlist>
<para><command># gluster volume profile <replaceable>VOLNAME</replaceable> start </command></para>
<para>For example, to start profiling on test-volume:
</para>
<para><programlisting># gluster volume profile test-volume start
Profiling started on test-volume</programlisting></para>
<para>When profiling on the volume is started, the following additional options are displayed in the Volume Info:
</para>
<para><programlisting>diagnostics.count-fop-hits: on
diagnostics.latency-measurement: on</programlisting></para>
</section>
<section id="chap-Administration_Guide-Monitor_Workload-Profile-Display">
<title>Displaying the I/0 Information</title>
<para>You can view the I/O information of each brick.
</para>
<para>To display I/O information:
</para>
<itemizedlist>
<listitem>
<para>Display the I/O information using the following command:
</para>
</listitem>
</itemizedlist>
<para><command># gluster volume profile <replaceable>VOLNAME</replaceable> info</command>
</para>
<para>For example, to see the I/O information on test-volume:
</para>
<para><programlisting># gluster volume profile test-volume info
Brick: Test:/export/2
Cumulative Stats:
Block 1b+ 32b+ 64b+
Size:
Read: 0 0 0
Write: 908 28 8
Block 128b+ 256b+ 512b+
Size:
Read: 0 6 4
Write: 5 23 16
Block 1024b+ 2048b+ 4096b+
Size:
Read: 0 52 17
Write: 15 120 846
Block 8192b+ 16384b+ 32768b+
Size:
Read: 52 8 34
Write: 234 134 286
Block 65536b+ 131072b+
Size:
Read: 118 622
Write: 1341 594
%-latency Avg- Min- Max- calls Fop
latency Latency Latency
___________________________________________________________
4.82 1132.28 21.00 800970.00 4575 WRITE
5.70 156.47 9.00 665085.00 39163 READDIRP
11.35 315.02 9.00 1433947.00 38698 LOOKUP
11.88 1729.34 21.00 2569638.00 7382 FXATTROP
47.35 104235.02 2485.00 7789367.00 488 FSYNC
------------------
------------------
Duration : 335
BytesRead : 94505058
BytesWritten : 195571980</programlisting></para>
</section>
<section id="chap-Administration_Guide-Monitor_Workload-Profile-Stop">
<title>Stop Profiling</title>
<para>You can stop profiling the volume, if you do not need profiling information anymore.
</para>
<para><emphasis role="bold">To stop profiling</emphasis>
</para>
<itemizedlist>
<listitem>
<para>Stop profiling using the following command:
</para>
<para><command># gluster volume profile <replaceable>VOLNAME</replaceable> stop</command>
</para>
<para>For example, to stop profiling on test-volume:</para>
<para><command># gluster volume profile <replaceable>test-volume</replaceable> stop</command> </para>
<para><computeroutput>Profiling stopped on test-volume</computeroutput></para>
</listitem>
</itemizedlist>
</section>
</section>
<section id="chap-Administration_Guide-Monitor_Workload-Top">
<title> Running GlusterFS Volume TOP Command </title>
<para>GlusterFS Volume Top command allows you to view the glusterfs bricks’ performance metrics like
read, write, file open calls, file read calls, file write calls, directory open calls, and directory real
calls. The top command displays up to 100 results.
</para>
<para>This section describes how to run and view the results for the following GlusterFS Top commands:
</para>
<itemizedlist>
<listitem>
<para><xref linkend="chap-Administration_Guide-Monitor_Workload-Top-Open_FD_Count"/></para>
</listitem>
<listitem>
<para><xref linkend="chap-Administration_Guide-Monitor_Workload-Top-File_Read"/></para>
</listitem>
<listitem>
<para><xref linkend="chap-Administration_Guide-Monitor_Workload-Top-File_Write"/></para>
</listitem>
<listitem>
<para><xref linkend="chap-Administration_Guide-Monitor_Workload-Top-Open_Calls"/></para>
</listitem>
<listitem>
<para><xref linkend="chap-Administration_Guide-Monitor_Workload-Top-Read_Calls"/></para>
</listitem>
<listitem>
<para><xref linkend="chap-Administration_Guide-Monitor_Workload-Top-Read_Perf"/></para>
</listitem>
<listitem>
<para><xref linkend="chap-Administration_Guide-Monitor_Workload-Top-Write_Perf"/></para>
</listitem>
</itemizedlist>
<section id="chap-Administration_Guide-Monitor_Workload-Top-Open_FD_Count">
<title>Viewing Open fd Count and Maximum fd Count </title>
<para>You can view both current open fd count (list of files that are currently the most opened and the
count) on the brick and the maximum open fd count (count of files that are the currently open and
the count of maximum number of files opened at any given point of time, since the servers are up
and running). If the brick name is not specified, then open fd metrics of all the bricks belonging to
the volume will be displayed.
</para>
<para><emphasis role="bold">To view open fd count and maximum fd count: </emphasis></para>
<itemizedlist>
<listitem>
<para>View open fd count and maximum fd count using the following command:</para>
<para><command># gluster volume top <replaceable>VOLNAME</replaceable> open [brick <replaceable>BRICK-NAME</replaceable>] [list-cnt <replaceable>cnt</replaceable>]</command>
</para>
<para>For example, to view open fd count and maximum fd count on brick <replaceable>server:/export</replaceable> of <replaceable>test-volume</replaceable> and list top 10 open calls:
</para>
<para><command># gluster volume top <replaceable>test-volume</replaceable> open brick <replaceable>server:/export/</replaceable> list-cnt <replaceable>10</replaceable></command></para>
<para><computeroutput>Brick: server:/export/dir1 </computeroutput></para>
<para><computeroutput>Current open fd's: 34 Max open fd's: 209 </computeroutput><programlisting> ==========Open file stats========
open file name
call count
2 /clients/client0/~dmtmp/PARADOX/
COURSES.DB
11 /clients/client0/~dmtmp/PARADOX/
ENROLL.DB
11 /clients/client0/~dmtmp/PARADOX/
STUDENTS.DB
10 /clients/client0/~dmtmp/PWRPNT/
TIPS.PPT
10 /clients/client0/~dmtmp/PWRPNT/
PCBENCHM.PPT
9 /clients/client7/~dmtmp/PARADOX/
STUDENTS.DB
9 /clients/client1/~dmtmp/PARADOX/
STUDENTS.DB
9 /clients/client2/~dmtmp/PARADOX/
STUDENTS.DB
9 /clients/client0/~dmtmp/PARADOX/
STUDENTS.DB
9 /clients/client8/~dmtmp/PARADOX/
STUDENTS.DB</programlisting></para>
</listitem>
</itemizedlist>
</section>
<section id="chap-Administration_Guide-Monitor_Workload-Top-File_Read">
<title>Viewing Highest File Read Calls </title>
<para>You can view highest read calls on each brick. If brick name is not specified, then by default, list of
100 files will be displayed.
</para>
<para><emphasis role="bold">To view highest file Read calls:</emphasis>
</para>
<itemizedlist>
<listitem>
<para>View highest file Read calls using the following command:
</para>
<para><command># gluster volume top <replaceable>VOLNAME</replaceable> read [brick <replaceable>BRICK-NAME</replaceable>] [list-cnt <replaceable>cnt</replaceable>] </command></para>
<para>For example, to view highest Read calls on brick server:/export of test-volume:
</para>
<para><command># gluster volume top <replaceable>test-volume</replaceable> read brick <replaceable>server:/export</replaceable> list-cnt <replaceable>10</replaceable></command></para>
<para><computeroutput>Brick:</computeroutput> <replaceable>server:/export/dir1</replaceable><programlisting> ==========Read file stats========
read filename
call count
116 /clients/client0/~dmtmp/SEED/LARGE.FIL
64 /clients/client0/~dmtmp/SEED/MEDIUM.FIL
54 /clients/client2/~dmtmp/SEED/LARGE.FIL
54 /clients/client6/~dmtmp/SEED/LARGE.FIL
54 /clients/client5/~dmtmp/SEED/LARGE.FIL
54 /clients/client0/~dmtmp/SEED/LARGE.FIL
54 /clients/client3/~dmtmp/SEED/LARGE.FIL
54 /clients/client4/~dmtmp/SEED/LARGE.FIL
54 /clients/client9/~dmtmp/SEED/LARGE.FIL
54 /clients/client8/~dmtmp/SEED/LARGE.FIL</programlisting> </para>
</listitem>
</itemizedlist>
</section>
<section id="chap-Administration_Guide-Monitor_Workload-Top-File_Write">
<title>Viewing Highest File Write Calls </title>
<para>You can view list of files which has highest file write calls on each brick. If brick name is not
specified, then by default, list of 100 files will be displayed.
</para>
<para><emphasis role="bold">To view highest file Write calls:</emphasis>
</para>
<itemizedlist>
<listitem>
<para>View highest file Write calls using the following command:
</para>
<para><command># gluster volume top <replaceable>VOLNAME</replaceable> write [brick <replaceable>BRICK-NAME</replaceable>] [list-cnt <replaceable>cnt</replaceable>] </command></para>
<para>For example, to view highest Write calls on brick <replaceable>server:/export</replaceable> of <replaceable>test-volume</replaceable>:
</para>
<para><command># gluster volume top <replaceable>test-volume</replaceable> write brick <replaceable>server:/export</replaceable> list-cnt <replaceable>10</replaceable></command></para>
<para><code>Brick: server:/export/dir1 </code><programlisting> ==========Write file stats========
write call count filename
83 /clients/client0/~dmtmp/SEED/LARGE.FIL
59 /clients/client7/~dmtmp/SEED/LARGE.FIL
59 /clients/client1/~dmtmp/SEED/LARGE.FIL
59 /clients/client2/~dmtmp/SEED/LARGE.FIL
59 /clients/client0/~dmtmp/SEED/LARGE.FIL
59 /clients/client8/~dmtmp/SEED/LARGE.FIL
59 /clients/client5/~dmtmp/SEED/LARGE.FIL
59 /clients/client4/~dmtmp/SEED/LARGE.FIL
59 /clients/client6/~dmtmp/SEED/LARGE.FIL
59 /clients/client3/~dmtmp/SEED/LARGE.FIL</programlisting></para>
</listitem>
</itemizedlist>
</section>
<section id="chap-Administration_Guide-Monitor_Workload-Top-Open_Calls">
<title>Viewing Highest Open Calls on Directories </title>
<para>You can view list of files which has highest open calls on directories of each brick. If brick name is
not specified, then the metrics of all the bricks belonging to that volume will be displayed.
</para>
<para>To view list of open calls on each directory</para>
<itemizedlist>
<listitem>
<para>View list of open calls on each directory using the following command:
</para>
<para><command># gluster volume top <replaceable>VOLNAME</replaceable> opendir [brick <replaceable>BRICK-NAME</replaceable>] [list-cnt <replaceable>cnt</replaceable>] </command></para>
<para>For example, to view open calls on brick server:/export/ of test-volume:
</para>
<para><command># gluster volume top <replaceable>test-volume</replaceable> opendir brick <replaceable>server:/export</replaceable> list-cnt <replaceable>10</replaceable></command></para>
<para><code>Brick: server:/export/dir1 </code><programlisting> ==========Directory open stats========
Opendir count directory name
1001 /clients/client0/~dmtmp
454 /clients/client8/~dmtmp
454 /clients/client2/~dmtmp
454 /clients/client6/~dmtmp
454 /clients/client5/~dmtmp
454 /clients/client9/~dmtmp
443 /clients/client0/~dmtmp/PARADOX
408 /clients/client1/~dmtmp
408 /clients/client7/~dmtmp
402 /clients/client4/~dmtmp</programlisting></para>
</listitem>
</itemizedlist>
</section>
<section id="chap-Administration_Guide-Monitor_Workload-Top-Read_Calls">
<title>Viewing Highest Read Calls on Directory </title>
<para>You can view list of files which has highest directory read calls on each brick. If brick name is not
specified, then the metrics of all the bricks belonging to that volume will be displayed.
</para>
<para><emphasis role="bold">To view list of highest directory read calls on each brick</emphasis>
</para>
<itemizedlist>
<listitem>
<para>View list of highest directory read calls on each brick using the following command:
</para>
<para><command># gluster volume top <replaceable>VOLNAME</replaceable> readdir [brick <replaceable>BRICK-NAME</replaceable>] [list-cnt <replaceable>cnt</replaceable>] </command></para>
<para>For example, to view highest directory read calls on brick <replaceable>server:/export</replaceable> of <replaceable>test-volume</replaceable>:</para>
<para><command># gluster volume top <replaceable>test-volume</replaceable> readdir brick <replaceable>server:/export</replaceable> list-cnt <replaceable>10</replaceable></command> </para>
<para><code>Brick: <replaceable>server:/export/dir1</replaceable></code><programlisting>==========Directory readdirp stats========
readdirp count directory name
1996 /clients/client0/~dmtmp
1083 /clients/client0/~dmtmp/PARADOX
904 /clients/client8/~dmtmp
904 /clients/client2/~dmtmp
904 /clients/client6/~dmtmp
904 /clients/client5/~dmtmp
904 /clients/client9/~dmtmp
812 /clients/client1/~dmtmp
812 /clients/client7/~dmtmp
800 /clients/client4/~dmtmp</programlisting>
</para>
</listitem>
</itemizedlist>
</section>
<section id="chap-Administration_Guide-Monitor_Workload-Top-Read_Perf">
<title>Viewing List of Read Performance on each Brick </title>
<para>You can view the read throughput of files on each brick. If brick name is not specified, then the
metrics of all the bricks belonging to that volume will be displayed. The output will be the read
throughput.
</para>
<para><programlisting> ==========Read throughput file stats========
read filename Time
through
put(MBp
s)
2570.00 /clients/client0/~dmtmp/PWRPNT/ -2011-01-31
TRIDOTS.POT 15:38:36.894610
2570.00 /clients/client0/~dmtmp/PWRPNT/ -2011-01-31
PCBENCHM.PPT 15:38:39.815310
2383.00 /clients/client2/~dmtmp/SEED/ -2011-01-31
MEDIUM.FIL 15:52:53.631499
2340.00 /clients/client0/~dmtmp/SEED/ -2011-01-31
MEDIUM.FIL 15:38:36.926198
2299.00 /clients/client0/~dmtmp/SEED/ -2011-01-31
LARGE.FIL 15:38:36.930445
2259.00 /clients/client0/~dmtmp/PARADOX/ -2011-01-31
COURSES.X04 15:38:40.549919
2221.00 /clients/client0/~dmtmp/PARADOX/ -2011-01-31
STUDENTS.VAL 15:52:53.298766
2221.00 /clients/client3/~dmtmp/SEED/ -2011-01-31
COURSES.DB 15:39:11.776780
2184.00 /clients/client3/~dmtmp/SEED/ -2011-01-31
MEDIUM.FIL 15:39:10.251764
2184.00 /clients/client5/~dmtmp/WORD/ -2011-01-31
BASEMACH.DOC 15:39:09.336572 </programlisting>This command will initiate a dd for the specified count and block size and measures the
corresponding throughput.
</para>
<para><emphasis role="bold">To view list of read performance on each brick</emphasis>
</para>
<itemizedlist>
<listitem>
<para>View list of read performance on each brick using the following command:
</para>
<para><command># gluster volume top <replaceable>VOLNAME</replaceable> read-perf [bs <replaceable>blk-size</replaceable> count <replaceable>count</replaceable>] [brick <replaceable>BRICK-NAME</replaceable>] [list-cnt <replaceable>cnt</replaceable>]</command>
</para>
<para>For example, to view read performance on brick server:/export/ of test-volume, 256 block size
of count 1, and list count 10:
</para>
<para><command># gluster volume top <replaceable>test-volume</replaceable> read-perf bs 256 count 1 brick <replaceable>server:/export/ </replaceable>list-cnt <replaceable>10</replaceable></command></para>
<para><computeroutput>Brick: server:/export/dir1 256 bytes (256 B) copied, Throughput: 4.1 MB/s </computeroutput></para>
<programlisting> ==========Read throughput file stats========
read filename Time
through
put(MBp
s)
2912.00 /clients/client0/~dmtmp/PWRPNT/ -2011-01-31
TRIDOTS.POT 15:38:36.896486
2570.00 /clients/client0/~dmtmp/PWRPNT/ -2011-01-31
PCBENCHM.PPT 15:38:39.815310
2383.00 /clients/client2/~dmtmp/SEED/ -2011-01-31
MEDIUM.FIL 15:52:53.631499
2340.00 /clients/client0/~dmtmp/SEED/ -2011-01-31
MEDIUM.FIL 15:38:36.926198
2299.00 /clients/client0/~dmtmp/SEED/ -2011-01-31
LARGE.FIL 15:38:36.930445
2259.00 /clients/client0/~dmtmp/PARADOX/ -2011-01-31
COURSES.X04 15:38:40.549919
2221.00 /clients/client9/~dmtmp/PARADOX/ -2011-01-31
STUDENTS.VAL 15:52:53.298766
2221.00 /clients/client8/~dmtmp/PARADOX/ -2011-01-31
COURSES.DB 15:39:11.776780
2184.00 /clients/client3/~dmtmp/SEED/ -2011-01-31
MEDIUM.FIL 15:39:10.251764
2184.00 /clients/client5/~dmtmp/WORD/ -2011-01-31
BASEMACH.DOC 15:39:09.336572
</programlisting>
</listitem>
</itemizedlist>
</section>
<section id="chap-Administration_Guide-Monitor_Workload-Top-Write_Perf">
<title>Viewing List of Write Performance on each Brick </title>
<para>You can view list of write throughput of files on each brick. If brick name is not specified, then the
metrics of all the bricks belonging to that volume will be displayed. The output will be the write
throughput.
</para>
<para>This command will initiate a dd for the specified count and block size and measures the
corresponding throughput.
To view list of write performance on each brick:
</para>
<itemizedlist>
<listitem>
<para>View list of write performance on each brick using the following command:
</para>
<para><command># gluster volume top <replaceable>VOLNAME</replaceable> write-perf [bs <replaceable>blk-size</replaceable> count <replaceable>count</replaceable>] [brick <replaceable>BRICK-NAME</replaceable>] [list-cnt <replaceable>cnt</replaceable>] </command></para>
<para>For example, to view write performance on brick <replaceable>server:/export/</replaceable> of <replaceable>test-volume</replaceable>, 256 block size
of count 1, and list count 10:
</para>
<para><command># gluster volume top <replaceable>test-volume</replaceable> write-perf bs 256 count 1 brick <replaceable>server:/export/ </replaceable>list-cnt <replaceable>10</replaceable></command></para>
<para><code>Brick</code>: <replaceable>server:/export/dir1</replaceable>
</para>
<para><code>256 bytes (256 B) copied, Throughput: 2.8 MB/s </code><programlisting> ==========Write throughput file stats========
write filename Time
throughput
(MBps)
1170.00 /clients/client0/~dmtmp/SEED/ -2011-01-31
SMALL.FIL 15:39:09.171494
1008.00 /clients/client6/~dmtmp/SEED/ -2011-01-31
LARGE.FIL 15:39:09.73189
949.00 /clients/client0/~dmtmp/SEED/ -2011-01-31
MEDIUM.FIL 15:38:36.927426
936.00 /clients/client0/~dmtmp/SEED/ -2011-01-31
LARGE.FIL 15:38:36.933177
897.00 /clients/client5/~dmtmp/SEED/ -2011-01-31
MEDIUM.FIL 15:39:09.33628
897.00 /clients/client6/~dmtmp/SEED/ -2011-01-31
MEDIUM.FIL 15:39:09.27713
885.00 /clients/client0/~dmtmp/SEED/ -2011-01-31
SMALL.FIL 15:38:36.924271
528.00 /clients/client5/~dmtmp/SEED/ -2011-01-31
LARGE.FIL 15:39:09.81893
516.00 /clients/client6/~dmtmp/ACCESS/ -2011-01-31
FASTENER.MDB 15:39:01.797317
</programlisting></para>
</listitem>
</itemizedlist>
</section>
</section>
<section id="sect-Administration_Guide-Monitor_Workload-Displaying_Volume_Information">
<title>Displaying Volume Information </title>
<para>You can display information about a specific volume, or all volumes, as needed.</para>
<para><emphasis role="bold">To display volume information </emphasis></para>
<itemizedlist>
<listitem>
<para>Display information about a specific volume using the following command:</para>
<para><command># gluster volume info </command><varname>VOLNAME</varname></para>
<para>For example, to display information about test-volume:</para>
<para><programlisting># gluster volume info test-volume
Volume Name: test-volume
Type: Distribute
Status: Created
Number of Bricks: 4
Bricks:
Brick1: server1:/exp1
Brick2: server2:/exp2
Brick3: server3:/exp3
Brick4: server4:/exp4</programlisting></para>
</listitem>
<listitem>
<para>Display information about all volumes using the following command:</para>
<para><command># gluster volume info all</command></para>
<para><programlisting># gluster volume info all
Volume Name: test-volume
Type: Distribute
Status: Created
Number of Bricks: 4
Bricks:
Brick1: server1:/exp1
Brick2: server2:/exp2
Brick3: server3:/exp3
Brick4: server4:/exp4
Volume Name: mirror
Type: Distributed-Replicate
Status: Started
Number of Bricks: 2 X 2 = 4
Bricks:
Brick1: server1:/brick1
Brick2: server2:/brick2
Brick3: server3:/brick3
Brick4: server4:/brick4
Volume Name: Vol
Type: Distribute
Status: Started
Number of Bricks: 1
Bricks:
Brick: server:/brick6
</programlisting></para>
</listitem>
</itemizedlist>
</section>
<section id="sect-Administration_Guide-Monitor_Workload-Performing_Statedump">
<title>Performing Statedump on a Volume </title>
<para>Statedump is a mechanism through which you can get details of all internal variables and state of the glusterfs process at the time of issuing the command.You can perform statedumps of the brick processes and nfs server process of a volume using the statedump command. The following options can be used to determine what information is to be dumped:</para>
<itemizedlist>
<listitem>
<para><emphasis role="bold">mem</emphasis> - Dumps the memory usage and memory pool details of the bricks.</para>
</listitem>
<listitem>
<para><emphasis role="bold">iobuf</emphasis> - Dumps iobuf details of the bricks.</para>
</listitem>
<listitem>
<para><emphasis role="bold">priv</emphasis> - Dumps private information of loaded translators.</para>
</listitem>
<listitem>
<para><emphasis role="bold">callpool</emphasis> - Dumps the pending calls of the volume.</para>
</listitem>
<listitem>
<para><emphasis role="bold">fd</emphasis> - Dumps the open fd tables of the volume.</para>
</listitem>
<listitem>
<para><emphasis role="bold">inode</emphasis> - Dumps the inode tables of the volume.</para>
</listitem>
</itemizedlist>
<para><emphasis role="bold">To display volume statedump </emphasis></para>
<itemizedlist>
<listitem>
<para>Display statedump of a volume or NFS server using the following command:</para>
<para> <command># gluster volume statedump <replaceable>VOLNAME</replaceable> [nfs] [all|mem|iobuf|callpool|priv|fd|inode]</command></para>
<para>For example, to display statedump of test-volume:</para>
<para><programlisting># gluster volume statedump test-volume
Volume statedump successful</programlisting></para>
<para>The statedump files are created on the brick servers in the<filename> /tmp</filename> directory or in the directory set using <command>server.statedump-path</command> volume option. The naming convention of the dump file is <filename><brick-path>.<brick-pid>.dump</filename>.</para>
</listitem>
<listitem>
<para>By defult, the output of the statedump is stored at <filename> /tmp/<brickname.PID.dump></filename> file on that particular server. Change the directory of the statedump file using the following command:</para>
<para><command># gluster volume set <replaceable>VOLNAME</replaceable> server.statedump-path <replaceable>path</replaceable></command></para>
<para>For example, to change the location of the statedump file of test-volume:</para>
<para><programlisting># gluster volume set test-volume server.statedump-path /usr/local/var/log/glusterfs/dumps/
Set volume successful</programlisting></para>
<para>You can view the changed path of the statedump file using the following command:</para>
<para><command># gluster volume info <replaceable>VOLNAME</replaceable></command></para>
</listitem>
</itemizedlist>
</section>
<section id="sect-Administration_Guide-Monitor_Workload-Displaying_Volume_Status">
<title>Displaying Volume Status </title>
<para>You can display the status information about a specific volume, brick or all volumes, as needed. Status information can be used to understand the current status of the brick, nfs processes, and overall file system. Status information can also be used to monitor and debug the volume information. You can view status of the volume along with the following details:</para>
<itemizedlist>
<listitem>
<para><emphasis role="bold">detail</emphasis> - Displays additional information about the bricks.</para>
</listitem>
<listitem>
<para><emphasis role="bold">clients</emphasis> - Displays the list of clients connected to the volume.</para>
</listitem>
<listitem>
<para><emphasis role="bold">mem</emphasis> - Displays the memory usage and memory pool details of the bricks.</para>
</listitem>
<listitem>
<para><emphasis role="bold">inode</emphasis> - Displays the inode tables of the volume.</para>
</listitem>
<listitem>
<para><emphasis role="bold">fd</emphasis> - Displays the open fd (file descriptors) tables of the volume.</para>
</listitem>
<listitem>
<para><emphasis role="bold">callpool</emphasis> - Displays the pending calls of the volume.</para>
</listitem>
</itemizedlist>
<para><emphasis role="bold">To display volume status </emphasis></para>
<itemizedlist>
<listitem>
<para>Display information about a specific volume using the following command:</para>
<para><command># gluster volume status [all|<replaceable>VOLNAME</replaceable> [<replaceable>BRICKNAME</replaceable>]] [detail|clients|mem|inode|fd|callpool]</command> </para>
<para>For example, to display information about test-volume:</para>
<para><programlisting># gluster volume status test-volume
STATUS OF VOLUME: test-volume
BRICK PORT ONLINE PID
--------------------------------------------------------
arch:/export/1 24009 Y 22445
--------------------------------------------------------
arch:/export/2 24010 Y 22450</programlisting></para>
</listitem>
<listitem>
<para>Display information about all volumes using the following command:</para>
<para><command># gluster volume status all</command>
</para>
<para><programlisting># gluster volume status all
STATUS OF VOLUME: volume-test
BRICK PORT ONLINE PID
--------------------------------------------------------
arch:/export/4 24010 Y 22455
STATUS OF VOLUME: test-volume
BRICK PORT ONLINE PID
--------------------------------------------------------
arch:/export/1 24009 Y 22445
--------------------------------------------------------
arch:/export/2 24010 Y 22450</programlisting></para>
</listitem>
<listitem>
<para>Display additional information about the bricks using the following command:</para>
<para><command># gluster volume status <replaceable>VOLNAME</replaceable> detail</command>
</para>
<para>For example, to display additional information about the bricks of test-volume:</para>
<para><programlisting># gluster volume status test-volume details
STATUS OF VOLUME: test-volume
-------------------------------------------
Brick : arch:/export/1
Port : 24009
Online : Y
Pid : 16977
File System : rootfs
Device : rootfs
Mount Options : rw
Disk Space Free : 13.8GB
Total Disk Space : 46.5GB
Inode Size : N/A
Inode Count : N/A
Free Inodes : N/A
Number of Bricks: 1
Bricks:
Brick: server:/brick6</programlisting></para>
</listitem>
<listitem>
<para>Display the list of clients accessing the volumes using the following command:</para>
<para><command># gluster volume status <replaceable>VOLNAME</replaceable> clients</command>
</para>
<para>For example, to display the list of clients connected to test-volume:</para>
<para><programlisting># gluster volume status test-volume clients
Brick : arch:/export/1
Clients connected : 2
Hostname Bytes Read BytesWritten
-------- --------- ------------
127.0.0.1:1013 776 676
127.0.0.1:1012 50440 51200</programlisting></para>
</listitem>
<listitem>
<para>Display the memory usage and memory pool details of the bricks using the following command:</para>
<para><command># gluster volume status <replaceable>VOLNAME</replaceable> mem</command>
</para>
<para>For example, to display the memory usage and memory pool details of the bricks of test-volume:</para>
<screen>Memory status for volume : test-volume
----------------------------------------------
Brick : arch:/export/1
Mallinfo
--------
Arena : 434176
Ordblks : 2
Smblks : 0
Hblks : 12
Hblkhd : 40861696
Usmblks : 0
Fsmblks : 0
Uordblks : 332416
Fordblks : 101760
Keepcost : 100400
Mempool Stats
-------------
Name HotCount ColdCount PaddedSizeof AllocCount MaxAlloc
---- -------- --------- ------------ ---------- --------
test-volume-server:fd_t 0 16384 92 57 5
test-volume-server:dentry_t 59 965 84 59 59
test-volume-server:inode_t 60 964 148 60 60
test-volume-server:rpcsvc_request_t 0 525 6372 351 2
glusterfs:struct saved_frame 0 4096 124 2 2
glusterfs:struct rpc_req 0 4096 2236 2 2
glusterfs:rpcsvc_request_t 1 524 6372 2 1
glusterfs:call_stub_t 0 1024 1220 288 1
glusterfs:call_stack_t 0 8192 2084 290 2
glusterfs:call_frame_t 0 16384 172 1728 6</screen>
</listitem>
<listitem>
<para>Display the inode tables of the volume using the following command:</para>
<para><command># gluster volume status <replaceable>VOLNAME</replaceable> inode</command>
</para>
<para>For example, to display the inode tables of the test-volume:</para>
<para><programlisting># gluster volume status test-volume inode
inode tables for volume test-volume
----------------------------------------------
Brick : arch:/export/1
Active inodes:
GFID Lookups Ref IA type
---- ------- --- -------
6f3fe173-e07a-4209-abb6-484091d75499 1 9 2
370d35d7-657e-44dc-bac4-d6dd800ec3d3 1 1 2
LRU inodes:
GFID Lookups Ref IA type
---- ------- --- -------
80f98abe-cdcf-4c1d-b917-ae564cf55763 1 0 1
3a58973d-d549-4ea6-9977-9aa218f233de 1 0 1
2ce0197d-87a9-451b-9094-9baa38121155 1 0 2</programlisting></para>
</listitem>
<listitem>
<para>Display the open fd tables of the volume using the following command:</para>
<para><command># gluster volume status <replaceable>VOLNAME</replaceable> fd</command>
</para>
<para>For example, to display the open fd tables of the test-volume:</para>
<para><screen># gluster volume status test-volume fd
FD tables for volume test-volume
----------------------------------------------
Brick : arch:/export/1
Connection 1:
RefCount = 0 MaxFDs = 128 FirstFree = 4
FD Entry PID RefCount Flags
-------- --- -------- -----
0 26311 1 2
1 26310 3 2
2 26310 1 2
3 26311 3 2
Connection 2:
RefCount = 0 MaxFDs = 128 FirstFree = 0
No open fds
Connection 3:
RefCount = 0 MaxFDs = 128 FirstFree = 0
No open fds</screen></para>
</listitem>
<listitem>
<para>Display the pending calls of the volume using the following command:</para>
<para><command># gluster volume status <replaceable>VOLNAME</replaceable> callpool</command>
</para>
<para>Each call has a call stack containing call frames.</para>
<para>For example, to display the pending calls of test-volume:</para>
<para><programlisting># gluster volume status test-volume
Pending calls for volume test-volume
----------------------------------------------
Brick : arch:/export/1
Pending calls: 2
Call Stack1
UID : 0
GID : 0
PID : 26338
Unique : 192138
Frames : 7
Frame 1
Ref Count = 1
Translator = test-volume-server
Completed = No
Frame 2
Ref Count = 0
Translator = test-volume-posix
Completed = No
Parent = test-volume-access-control
Wind From = default_fsync
Wind To = FIRST_CHILD(this)->fops->fsync
Frame 3
Ref Count = 1
Translator = test-volume-access-control
Completed = No
Parent = repl-locks
Wind From = default_fsync
Wind To = FIRST_CHILD(this)->fops->fsync
Frame 4
Ref Count = 1
Translator = test-volume-locks
Completed = No
Parent = test-volume-io-threads
Wind From = iot_fsync_wrapper
Wind To = FIRST_CHILD (this)->fops->fsync
Frame 5
Ref Count = 1
Translator = test-volume-io-threads
Completed = No
Parent = test-volume-marker
Wind From = default_fsync
Wind To = FIRST_CHILD(this)->fops->fsync
Frame 6
Ref Count = 1
Translator = test-volume-marker
Completed = No
Parent = /export/1
Wind From = io_stats_fsync
Wind To = FIRST_CHILD(this)->fops->fsync
Frame 7
Ref Count = 1
Translator = /export/1
Completed = No
Parent = test-volume-server
Wind From = server_fsync_resume
Wind To = bound_xl->fops->fsync</programlisting></para>
</listitem>
</itemizedlist>
</section>
</chapter>
|
