-
Improvement
-
Resolution: Unresolved
-
Medium
-
None
-
None
-
None
-
3
-
9223372036854775807
Writing SERVICE.threads_min (e.g. ost.OSS.ost_io.threads_min) to a running service only sets srv_nthrs_cpt_init, which is read when the service is set up (ptlrpc_start_threads()). A running service adds threads only when one of its threads wakes up and finds the others busy (ptlrpc_threads_need_create() in ptlrpc_main()), so a raised threads_min has no effect until the service is restarted.
This was seen in sanity-ec test_54n (https://review.whamcloud.com/69709): a zfs OSS that had just restarted ran 3 ost_io threads per CPU partition, and since a service with a high-priority handler keeps up to two of them free (ptlrpc_server_allow_normal()), two delayed reads of the same OSS were served one after the other. Raising threads_min did not help.
Writing threads_min should start the missing threads in each CPU partition at once, up to threads_max. The threads_min, threads_max and threads_started parameters also have no man4 pages.