We used to wait until the discovery service could connect to the discovery subsystem before calling the callback function provided by the caller (mainly the start_discovery RPC). Moving forward, we will be handling the case where the discovery subsystem is unavailable temporarily. For now, let's not fail the bdev_nvme_start_discovery call if we cannot connect to the discovery subsystem. This will keep the initial service start path the same as the path where the discovery subsystem is temporarily unavailable. In the future, we can consider adding functionality to the start_discovery RPC that waits up to X number of seconds to see if we were able to connect and fail otherwise. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: Icb05523b9d59f508bfbc0233595c8bf58c10488f Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/11768 Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com> Community-CI: Mellanox Build Bot Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Shuhei Matsumoto <smatsumoto@nvidia.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Aleksey Marchuk <alexeymar@mellanox.com> |
||
---|---|---|
.. | ||
accel | ||
bdev | ||
blob | ||
blobfs | ||
env_dpdk | ||
event | ||
scheduler | ||
sock | ||
Makefile |