From 1a95fc3036db51b82b6a80952f0908bc2019d24a Mon Sep 17 00:00:00 2001 From: Jeff Darcy Date: Thu, 8 Dec 2016 16:24:15 -0500 Subject: core: run many bricks within one glusterfsd process This patch adds support for multiple brick translator stacks running in a single brick server process. This reduces our per-brick memory usage by approximately 3x, and our appetite for TCP ports even more. It also creates potential to avoid process/thread thrashing, and to improve QoS by scheduling more carefully across the bricks, but realizing that potential will require further work. Multiplexing is controlled by the "cluster.brick-multiplex" global option. By default it's off, and bricks are started in separate processes as before. If multiplexing is enabled, then *compatible* bricks (mostly those with the same transport options) will be started in the same process. Change-Id: I45059454e51d6f4cbb29a4953359c09a408695cb BUG: 1385758 Signed-off-by: Jeff Darcy Reviewed-on: https://review.gluster.org/14763 Smoke: Gluster Build System NetBSD-regression: NetBSD Build System CentOS-regression: Gluster Build System Reviewed-by: Vijay Bellur --- run-tests.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'run-tests.sh') diff --git a/run-tests.sh b/run-tests.sh index 1487f30d832..a922f2e2ad1 100755 --- a/run-tests.sh +++ b/run-tests.sh @@ -5,7 +5,7 @@ export TZ=UTC force="no" head="yes" -retry="no" +retry="yes" tests="" exit_on_failure="yes" skip_bad_tests="yes" -- cgit