nfs: treat GF_EVENT_CHILD_CONNECTING as subvolume up statusv3.1.1qa9

GF_EVENT_CHILD_CONNECTING is sent as a status from underlying subvolumes
after a sufficient margin of time (tcp connect() timeout) if the subvolumes
are not reachable.

This should avoid the problem of NFS not being reachable if any volume
is down

Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

BUG: 2093 (volumes cannot start when one node in a replicated setup is down)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2093

1 files changed, 1 insertions, 0 deletions

diff --git a/xlators/nfs/server/src/nfs.c b/xlators/nfs/server/src/nfs.c
index ec939a55e48..5f116a3b76d 100644
--- a/xlators/nfs/server/src/nfs.c
+++ b/xlators/nfs/server/src/nfs.c
@@ -662,6 +662,7 @@ notify (xlator_t *this, int32_t event, void *data, ...)
                 event);
         switch (event)
         {
+                case GF_EVENT_CHILD_CONNECTING:
                 case GF_EVENT_CHILD_UP:
                 {
                         nfs_startup_subvolume (this, subvol);