From 8d4d8088c73f2ffc60b8e5c23a33e6b996fb5053 Mon Sep 17 00:00:00 2001 From: Kaushal M Date: Tue, 6 Sep 2011 17:18:20 +0530 Subject: glusterd: run 'volume top read-perf/write-perf' in different thread Runs the 'volume top read-perf/write-perf' operations in a different thread without blocking glusterd. Prvents glusterd from being unresponsive when large values of 'bs' and 'count' are given. Also increase cli timeout for top/profile commands , from 120s to 300s to allow large i/o top read-perf and write-perf to return result. Change-Id: I4b7de1d735f33643d836772db7f25133f112b75a BUG: 2720 Reviewed-on: http://review.gluster.com/375 Tested-by: Gluster Build System Reviewed-by: Shishir Gowda --- cli/src/cli.h | 1 + 1 file changed, 1 insertion(+) (limited to 'cli/src/cli.h') diff --git a/cli/src/cli.h b/cli/src/cli.h index 1e0d69cd8a2..bf3437827ec 100644 --- a/cli/src/cli.h +++ b/cli/src/cli.h @@ -33,6 +33,7 @@ #define CLI_GLUSTERD_PORT 24007 #define CLI_DEFAULT_CONN_TIMEOUT 120 #define CLI_DEFAULT_CMD_TIMEOUT 120 +#define CLI_TOP_CMD_TIMEOUT 300 //Longer timeout for volume top #define DEFAULT_CLI_LOG_FILE_DIRECTORY DATADIR "/log/glusterfs" #define CLI_VOL_STATUS_BRICK_LEN 55 #define CLI_TAB_LENGTH 8 -- cgit