如何监视glusterfs音量

Glusterfs虽然是一个不错的分布式文件系统，但几乎无法提供监视其完整性的方法。服务器可以来来去去，砖块可能会陈旧或发生故障，并且我怕在为时已晚时才知道这一点。

最近，当一切似乎都正常运行时，我们遇到了一个奇怪的失败，但是一堆砖从体积中掉了下来（纯粹出于巧合）。

是否有一种简单可靠的方法（cron脚本？）可以让我知道我的GlusterFS 3.2卷的运行状况？

一段时间以来，这一直是对GlusterFS开发人员的要求，您没有可以使用的即用型解决方案。但是，使用一些脚本并不是没有可能。

几乎整个Gluster系统都由一个gluster命令管理，并且有几个选项，您可以编写自己的健康监控脚本。有关砖块和体积的列表信息，请参见此处-http://gluster.org/community/documentation/index.php/Gluster_3.2: _Displaying_Volume_Information

要监视性能，请查看此链接-http://gluster.org/community/documentation/index.php/Gluster_3.2:_Monitoring_your_GlusterFS_Workload

更新：请考虑升级到http://gluster.org/community/documentation/index.php/About_GlusterFS_3.3

始终使用最新版本会更好，因为它们似乎具有更多的错误修复且受到良好的支持。当然，在升级到新版本之前，请运行您自己的测试-http : //vbellur.wordpress.com/2012/05/31/upgrading-to-glusterfs-3-3/ :)

有一个管理指南与特定部分用于监视GlusterFS在第10章3.3安装- http://www.gluster.org/wp-content/uploads/2012/05/Gluster_File_System-3.3.0-Administration_Guide-en-US .pdf

请参阅此处以获取其他nagios脚本-http: //code.google.com/p/glusterfs-status/

有一个nagios插件可用于监视。不过，您可能需要为您的版本进行编辑。

请检查https://www.gluster.org/pipermail/gluster-users/2012-June/010709.html随附的脚本，以获取gluster 3.3；它可能很容易适应gluster 3.2。

#!/bin/bash

# This Nagios script was written against version 3.3 of Gluster.  Older
# versions will most likely not work at all with this monitoring script.
#
# Gluster currently requires elevated permissions to do anything.  In order to
# accommodate this, you need to allow your Nagios user some additional
# permissions via sudo.  The line you want to add will look something like the
# following in /etc/sudoers (or something equivalent):
#
# Defaults:nagios !requiretty
# nagios ALL=(root) NOPASSWD:/usr/sbin/gluster peer status,/usr/sbin/gluster volume list,/usr/sbin/gluster volume heal [[\:graph\:]]* info
#
# That should give us all the access we need to check the status of any
# currently defined peers and volumes.

# define some variables
ME=$(basename -- $0)
SUDO="/usr/bin/sudo"
PIDOF="/sbin/pidof"
GLUSTER="/usr/sbin/gluster"
PEERSTATUS="peer status"
VOLLIST="volume list"
VOLHEAL1="volume heal"
VOLHEAL2="info"
peererror=
volerror=

# check for commands
for cmd in $SUDO $PIDOF $GLUSTER; do
    if [ ! -x "$cmd" ]; then
        echo "$ME UNKNOWN - $cmd not found"
        exit 3
    fi
done

# check for glusterd (management daemon)
if ! $PIDOF glusterd &>/dev/null; then
    echo "$ME CRITICAL - glusterd management daemon not running"
    exit 2
fi

# check for glusterfsd (brick daemon)
if ! $PIDOF glusterfsd &>/dev/null; then
    echo "$ME CRITICAL - glusterfsd brick daemon not running"
    exit 2
fi

# get peer status
peerstatus="peers: "
for peer in $(sudo $GLUSTER $PEERSTATUS | grep '^Hostname: ' | awk '{print $2}'); do
    state=
    state=$(sudo $GLUSTER $PEERSTATUS | grep -A 2 "^Hostname: $peer$" | grep '^State: ' | sed -nre 's/.* \(([[:graph:]]+)\)$/\1/p')
    if [ "$state" != "Connected" ]; then
        peererror=1
    fi
    peerstatus+="$peer/$state "
done

# get volume status
volstatus="volumes: "
for vol in $(sudo $GLUSTER $VOLLIST); do
    thisvolerror=0
    entries=
    for entries in $(sudo $GLUSTER $VOLHEAL1 $vol $VOLHEAL2 | grep '^Number of entries: ' | awk '{print $4}'); do
        if [ "$entries" -gt 0 ]; then
            volerror=1
            let $((thisvolerror+=entries))
        fi
    done
    volstatus+="$vol/$thisvolerror unsynchronized entries "
done

# drop extra space
peerstatus=${peerstatus:0:${#peerstatus}-1}
volstatus=${volstatus:0:${#volstatus}-1}

# set status according to whether any errors occurred
if [ "$peererror" ] || [ "$volerror" ]; then
    status="CRITICAL"
else
    status="OK"
fi

# actual Nagios output
echo "$ME $status $peerstatus $volstatus"

# exit with appropriate value
if [ "$peererror" ] || [ "$volerror" ]; then
    exit 2
else
    exit 0
fi

我能够为glusterfs配置nagios监视，如下所述：

http://gopukrish.wordpress.com/2014/11/16/monitor-glusterfs-using-nagios-plugin/

@Arie Skliarouk，您check_gluster.sh有错字-在最后一行，您使用grep exitst代替exist。我继续进行了改写，使其更加紧凑，并删除了对临时文件的要求。

#!/bin/bash

# Ensure that all peers are connected
gluster peer status | grep -q Disconnected && echo "Peer disconnected." && exit 1

# Ensure that all bricks have a running log file (i.e., are sending/receiving)
for vol in $(gluster volume list); do
  for brick in $(gluster volume info "$vol" | awk '/^Brick[0-9]*:/ {print $2}'); do
    gluster volume log locate "$vol" "$brick";
  done;
done |
 grep -qE "does not (exist|exitst)" &&
 echo "Log file missing - $vol/$brick ." &&
 exit 1