Give the administrator a possibility to set oom_score_adj for glusterfs process. Applies to Linux only. Change-Id: Iff13c2f4cb28457871c6ebeff6130bce4a8bf543 BUG: 1336818 Signed-off-by: Oleksandr Natalenko <oleksandr@natalenko.name> Reviewed-on: http://review.gluster.org/14399 Smoke: Gluster Build System <jenkins@build.gluster.com> NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org> CentOS-regression: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
53 lines
1.3 KiB
Bash
53 lines
1.3 KiB
Bash
#!/bin/bash
|
|
|
|
#Test case: OOM score adjust
|
|
|
|
. $(dirname $0)/../../include.rc
|
|
. $(dirname $0)/../../volume.rc
|
|
|
|
cleanup;
|
|
|
|
# Prepare
|
|
TEST glusterd
|
|
TEST pidof glusterd
|
|
TEST $CLI volume info;
|
|
|
|
TEST $CLI volume create $V0 $H0:$B0/brick1;
|
|
EXPECT 'Created' volinfo_field $V0 'Status';
|
|
|
|
TEST $CLI volume start $V0;
|
|
EXPECT 'Started' volinfo_field $V0 'Status';
|
|
|
|
# Basic check
|
|
TEST glusterfs -s $H0 --volfile-id $V0 $M0
|
|
TEST umount $M0
|
|
|
|
# Check valid value (< 0)
|
|
TEST glusterfs --oom-score-adj=-1000 -s $H0 --volfile-id $V0 $M0
|
|
TEST umount $M0
|
|
|
|
# Check valid value (> 0)
|
|
TEST glusterfs --oom-score-adj=1000 -s $H0 --volfile-id $V0 $M0
|
|
TEST umount $M0
|
|
|
|
# Check valid value (= 0)
|
|
TEST glusterfs --oom-score-adj=0 -s $H0 --volfile-id $V0 $M0
|
|
TEST umount $M0
|
|
|
|
# Check invalid value (no value given)
|
|
TEST ! glusterfs --oom-score-adj -s $H0 --volfile-id $V0 $M0
|
|
|
|
# Check invalid value (< OOM_SCORE_ADJ_MIN)
|
|
TEST ! glusterfs --oom-score-adj=-1001 -s $H0 --volfile-id $V0 $M0
|
|
|
|
# Check invalid value (> OOM_SCORE_ADJ_MAX)
|
|
TEST ! glusterfs --oom-score-adj=1001 -s $H0 --volfile-id $V0 $M0
|
|
|
|
# Check invalid value (float)
|
|
TEST ! glusterfs --oom-score-adj=12.34 -s $H0 --volfile-id $V0 $M0
|
|
|
|
# Check invalid value (non-integer string)
|
|
TEST ! glusterfs --oom-score-adj=qwerty -s $H0 --volfile-id $V0 $M0
|
|
|
|
cleanup;
|