From f44eb2a4838742a29c6e7399e15d4d21f2308032 Mon Sep 17 00:00:00 2001 From: Joseph Gmitter Date: Wed, 2 Aug 2017 14:01:18 -0400 Subject: [PATCH] LUDOC-387 rpc: fix typo in max_rpcs_in_flight This is a trivial patch that fixes the following two lctl set_param examples: client$ lctl set_param mdc.*.max_rpcs_in_flight=16 client$ lctl set_param mdc.*.max_mod_rpcs_in_flight=12 Signed-off-by: Joseph Gmitter Change-Id: If0ac0b1a99be8f13a702d1f7f2a8e28b48ea223b Reviewed-on: https://review.whamcloud.com/28327 Tested-by: Jenkins --- LustreProc.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/LustreProc.xml b/LustreProc.xml index a5916a0..e52b1f6 100644 --- a/LustreProc.xml +++ b/LustreProc.xml @@ -1544,7 +1544,7 @@ obdfilter.lol-OST0001.sync_on_lock_cancel=never minimum setting is 1 and maximum setting is 256. To set the max_rpcs_in_flight parameter, run the following command on the Lustre client: - client$ lctl set_param mdc.*.max_rcps_in_flight=16 + client$ lctl set_param mdc.*.max_rpcs_in_flight=16 The MDC max_mod_rpcs_in_flight parameter defines the maximum number of file system modifying RPCs that can be sent in parallel by a client to a MDT target. For example, the Lustre @@ -1554,7 +1554,7 @@ obdfilter.lol-OST0001.sync_on_lock_cancel=never 256. To set the max_mod_rpcs_in_flight parameter, run the following command on the Lustre client: - client$ lctl set_param mdc.*.max_mod_rcps_in_flight=12 + client$ lctl set_param mdc.*.max_mod_rpcs_in_flight=12 The max_mod_rpcs_in_flight value must be strictly less than the max_rpcs_in_flight value. It must also be less or equal to the MDT -- 1.8.3.1