+22
−0
Loading
When the "save_config" RPC command is called in SPDK, the current environment is saved. However, the environment created by "iscsi_enable_histogram" is not included in the saved configuration. In a production environment, it is crucial to monitor various IO indicators, and IO latency is one of the important metrics. Fortunately, SPDK provides an RPC method called "iscsi_get_histogram" to obtain the IO latency histogram of an iscsi target device. However, before using this RPC method, it is necessary to first call the "iscsi_enable_histogram" command. In a production environment, SPDK is typically configured to automatically restart using the saved configuration file (by using the "save_config" command in rpc.py). However, since the "iscsi_enable_histogram" configuration is missing from the saved configuration, the IO latency monitoring will fail once SPDK restarts. Change-Id: I3fe79debc337ae42f99cd23856a2cee405dbb3cd Signed-off-by:Changqi Lu <luchangqi.123@bytedance.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/23486 Community-CI: Mellanox Build Bot Tested-by:
SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by:
Jim Harris <jim.harris@samsung.com> Reviewed-by:
Tomasz Zawadzki <tomasz.zawadzki@intel.com>