From d6978803395fb1d1635dd454894e26d9feb806d9 Mon Sep 17 00:00:00 2001 From: Anand Avati Date: Mon, 11 Oct 2010 07:30:55 +0000 Subject: dht: change behaviour CHILD_UP/DOWN/CONNECTING event propagation The first CHILD_UP/DOWN/CONNECTING event to pass dht upwards should be only after all subvols have reported their status atleast once. Signed-off-by: Anand V. Avati Signed-off-by: Vijay Bellur BUG: 1643 (Initial requests after mount ESTALE if DHT subvolumes connect after nfs startup) URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1643 --- xlators/cluster/dht/src/dht-common.h | 1 + 1 file changed, 1 insertion(+) (limited to 'xlators/cluster/dht/src/dht-common.h') diff --git a/xlators/cluster/dht/src/dht-common.h b/xlators/cluster/dht/src/dht-common.h index 32e5cf566..f0510f868 100644 --- a/xlators/cluster/dht/src/dht-common.h +++ b/xlators/cluster/dht/src/dht-common.h @@ -144,6 +144,7 @@ struct dht_conf { int subvolume_cnt; xlator_t **subvolumes; char *subvolume_status; + int *last_event; dht_layout_t **file_layouts; dht_layout_t **dir_layouts; dht_layout_t *default_dir_layout; -- cgit