From c0d4081cf4b90a4316b786cc53263a7c56fdb344 Mon Sep 17 00:00:00 2001 From: Krutika Dhananjay Date: Mon, 12 Jun 2017 11:17:01 +0530 Subject: Revert "glusterd: disallow rebalance & remove-brick on a sharded volume" This reverts commit 8375b3d70d5c6268c6770b42a18b2e1bc09e411e. Now that some of the users have confirmed rebalance works fine without causing corruption of VMs, time to revert the CLI restriction. Change-Id: I45493fcbb1f25fd0fff27b2b3526c42642ccb464 BUG: 1460585 Signed-off-by: Krutika Dhananjay Reviewed-on: https://review.gluster.org/17506 Reviewed-by: Atin Mukherjee Smoke: Gluster Build System NetBSD-regression: NetBSD Build System Reviewed-by: Raghavendra G CentOS-regression: Gluster Build System --- xlators/mgmt/glusterd/src/glusterd-brick-ops.c | 10 ---------- 1 file changed, 10 deletions(-) (limited to 'xlators/mgmt/glusterd/src/glusterd-brick-ops.c') diff --git a/xlators/mgmt/glusterd/src/glusterd-brick-ops.c b/xlators/mgmt/glusterd/src/glusterd-brick-ops.c index 21e3377b631..8d4ea13af95 100644 --- a/xlators/mgmt/glusterd/src/glusterd-brick-ops.c +++ b/xlators/mgmt/glusterd/src/glusterd-brick-ops.c @@ -2180,16 +2180,6 @@ glusterd_op_stage_remove_brick (dict_t *dict, char **op_errstr) case GF_OP_CMD_START: { - if (dict_get_str_boolean (volinfo->dict, "features.shard", - _gf_false)) { - ret = -1; - snprintf (msg, sizeof (msg), "remove-brick operation is" - " not allowed on a sharded volume as it may" - " lead to a data loss situation."); - errstr = gf_strdup (msg); - goto out; - } - if ((volinfo->type == GF_CLUSTER_TYPE_REPLICATE) && dict_get (dict, "replica-count")) { snprintf (msg, sizeof(msg), "Migration of data is not " -- cgit