diff options
author | Mohit Agrawal <moagrawal@redhat.com> | 2018-12-20 16:41:37 +0530 |
---|---|---|
committer | Amar Tumballi <amarts@redhat.com> | 2018-12-21 07:41:33 +0000 |
commit | 730ab84586b73e8677537ed90b78fabf5dde3b48 (patch) | |
tree | 5f16e8a7ce10de8964eb88c1ed587a8ebfe12a00 /tests | |
parent | 0c7425d431b90c9c5c087511b34150e30dbe028a (diff) |
tests: Brick is getting OOM in ./tests/bugs/core/bug-1432542-mpx-restart-crash.t
This test "tests/bugs/core/bug-1432542-mpx-restart-crash.t" case creates 20 2x3
volumes after enabling brick_mux.At the time of creating last volume brick is getting
OOM because brick consumption has increased from previous consumption due to these patches
https://review.gluster.org/#/c/glusterfs/+/19997/,
https://review.gluster.org/#/c/glusterfs/+/20362/
To avoid OOM reduce NUM_VOLS to 15 so that brick consumption has reduced
Change-Id: Ib98b47a3db6b990ff22c7e57396d51e7fef5c7e8
fixes: bz#1661214
Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>
Diffstat (limited to 'tests')
-rw-r--r-- | tests/bugs/core/bug-1432542-mpx-restart-crash.t | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/tests/bugs/core/bug-1432542-mpx-restart-crash.t b/tests/bugs/core/bug-1432542-mpx-restart-crash.t index 2cc5109f0c0..ecffcfa4fb7 100644 --- a/tests/bugs/core/bug-1432542-mpx-restart-crash.t +++ b/tests/bugs/core/bug-1432542-mpx-restart-crash.t @@ -8,7 +8,7 @@ SCRIPT_TIMEOUT=800 cleanup; -NUM_VOLS=20 +NUM_VOLS=15 MOUNT_BASE=$(dirname $M0) # GlusterD reports that bricks are started when in fact their attach requests @@ -79,13 +79,14 @@ TEST $CLI volume set all cluster.brick-multiplex on # Our infrastructure can't handle an arithmetic expression here. The formula # is (NUM_VOLS-1)*5 because it sees each TEST/EXPECT once but needs the other # NUM_VOLS-1 and there are 5 such statements in each iteration. -TESTS_EXPECTED_IN_LOOP=114 +TESTS_EXPECTED_IN_LOOP=84 for i in $(seq 1 $NUM_VOLS); do create_volume $i TEST dd if=/dev/zero of=$(get_mount_point $i)/a_file bs=4k count=1 # Unmounting to reduce memory footprint on regression hosts mnt_point=$(get_mount_point $i) EXPECT_WITHIN $UMOUNT_TIMEOUT "Y" force_umount $mnt_point + pmap -x `pgrep glusterfsd` | grep total done # Kill glusterd, and wait a bit for all traces to disappear. |