Whamcloud - gitweb
LU-5020 llite: don't reconnect MGC if connecting 81/30581/2
authorHongchao Zhang <hongchao.zhang@intel.com>
Fri, 13 Oct 2017 22:57:28 +0000 (06:57 +0800)
committerJohn L. Hammond <john.hammond@intel.com>
Thu, 4 Jan 2018 17:21:47 +0000 (17:21 +0000)
commit7c04a652f85c53f732bbcf4e70b01202360a34c8
treeb4c7edb7e40b95ea7e7bcfb43af1ab3dc3972764
parent2c2f42ccd55601b410e35f76d89b2691f11250b1
LU-5020 llite: don't reconnect MGC if connecting

1. In mgc_set_info_async(KEY=KEY_INIT_RECOV_BACKUP "init_recov_bk"),
   the MGC import should be reconnected only if its state is
   LUSTRE_IMP_DISCON

2. in mgc_target_register, if the target will regenerate the config,
   we should use some longer delay limit to wait the MGC to connect
   to MGS for the target (server) will fail to exit if the request
   expired due to delay limit.

3. In case of parallel mount, the async cleanup of OSS will affects
   the following mount for the OSS can't be setup again, then there
   should be some barrier to sync with the OSS cleanup.

Lustre-change: https://review.whamcloud.com/10229
Lustre-commit: 1a7ff02c1fbb8e85ac2e8fa458ba3fb810a76ea4

Change-Id: I805b84cf12100ec2cc68f95bb65a9c396e0fbc1b
Signed-off-by: Hongchao Zhang <hongchao.zhang@intel.com>
Reviewed-by: Fan Yong <fan.yong@intel.com>
Reviewed-by: Andreas Dilger <andreas.dilger@intel.com>
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/30581
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
lustre/mgc/mgc_request.c
lustre/obdclass/genops.c