glusterfs.git/xlators/mgmt/glusterd/src/glusterd-volgen.c, branch v3.7.10

glusterd / afr : Enable auto heal when replica count increases

2016-03-23T10:21:38+00:00

        Backport of http://review.gluster.org/12451

In replicate volumes, when a brick is added to a replicate
group, heal to the new brick should be triggered.
Also, the new brick should not be considered as source for
healing till it is up to date.

Previously, extended attributes had to be set manually on
the bricks for this to happen. This patch is part 1 patch
to automate this process.

        >Change-Id: I29958448618372bfde23bf1dac5dd23dba1ad98f
        >BUG: 1276203
        >Signed-off-by: Anuradha Talur 
        >Reviewed-on: http://review.gluster.org/12451
        >Reviewed-by: Atin Mukherjee 
        >NetBSD-regression: NetBSD Build System 
        >CentOS-regression: Gluster Build System 
        >Reviewed-by: Ravishankar N 
        >Smoke: Gluster Build System 
Signed-off-by: Anuradha Talur 

Conflicts:
	libglusterfs/src/globals.h
	xlators/mgmt/glusterd/src/glusterd-replace-brick.c

Change-Id: Ica83592aab8edbe49e2bb9d8d4824cf5c76324b7
BUG: 1320020
Reviewed-on: http://review.gluster.org/13806
Smoke: Gluster Build System 
Tested-by: Anuradha Talur 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Atin Mukherjee

glusterd: Bug fixes for IPv6 support

2016-03-21T17:52:50+00:00

Backport of http://review.gluster.org/#/c/11988/

Problem:
Glusterd not working using ipv6 transport. The idea is with proper glusterd.vol configuration,
1. glusterd needs to listen on default port (240007) as IPv6 TCP listner.
2. Volume creation/deletion/mounting/add-bricks/delete-bricks/peer-probe
needs to work using ipv6 addresses.
3. Bricks needs to listen on ipv6 addresses.
All the above functionality is needed to say that glusterd supports ipv6 transport and this is broken.

Fix:
When "option transport.address-family inet6" option is present in glusterd.vol
file, it is made sure that glusterd creates listeners using ipv6 sockets only and also the same information is saved
inside brick volume files used by glusterfsd brick process when they are starting.

Tests Run:
Regression tests using ./run-tests.sh
IPv4: Regression tests using ./run-tests.sh for release-3.7 branch verified by comparing with clean repo.
IPv6: (Need to add the above mentioned config and also add an entry for "hostname ::1" in /etc/hosts)
    Started failing at ./tests/basic/glusterd/arbiter-volume-probe.t and ran successfully till here

Change-Id: Idd7513aa2347ce0de2b1f68daeecce1b7a39a7af
BUG: 1310445
Signed-off-by: Nithin D 
Reviewed-on: http://review.gluster.org/13787
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Atin Mukherjee

Revert "glusterd/afr: store afr pending xattrs as a volume option"

2016-02-08T08:18:23+00:00

This reverts commit 486b07dfc33782d27e3458659cdd6090f496ad35.

Change-Id: I2da12ef77fb01c52cae3c3b5547398b6a4d7d17e
BUG: 1293536
Signed-off-by: Pranith Kumar Karampuri 
Reviewed-on: http://review.gluster.org/13339
Smoke: Gluster Build System 
CentOS-regression: Gluster Build System 
NetBSD-regression: NetBSD Build System

all: reduce "inline" usage

2016-01-18T09:02:34+00:00

There are three kinds of inline functions: plain inline, extern inline,
and static inline.  All three have been removed from .c files, except
those in "contrib" which aren't our problem.  Inlines in .h files, which
are overwhelmingly "static inline" already, have generally been left
alone.  Over time we should be able to "lower" these into .c files, but
that has to be done in a case-by-case fashion requiring more manual
effort.  This part was easy to do automatically without (as far as I can
tell) any ill effect.

In the process, several pieces of dead code were flagged by the
compiler, and were removed.

backport of Change-Id: I56a5e614735c9e0a6ee420dab949eac22e25c155,
http://review.gluster.org/11769, BUG: 1245331

Change-Id: Iba1efb0bc578ea4a5e9bf76b7bd93dc1be9eba44
BUG: 1283302
Signed-off-by: Kaleb S KEITHLEY 
Reviewed-on: http://review.gluster.org/12646
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Niels de Vos

glusterd/afr : Readdirp performance improvement

2015-12-21T09:14:24+00:00

        Backport of http://review.gluster.org/#/c/12467/

Add xlator options to index xlator with xattrs that
it needs to keep track of.

Change-Id: If818673be5e626f77e65cc3a340f8cdd624179c2
BUG: 1287531
Signed-off-by: Anuradha Talur 
Reviewed-on: http://review.gluster.org/12467
Tested-by: Gluster Build System 
Reviewed-by: Krutika Dhananjay 
Tested-by: NetBSD Build System 
Reviewed-by: Ravishankar N 
Reviewed-by: Pranith Kumar Karampuri 
Signed-off-by: Anuradha Talur 
Reviewed-on: http://review.gluster.org/12848

glusterd/afr: store afr pending xattrs as a volume option

2015-12-17T06:02:55+00:00

Backport of http://review.gluster.org/#/c/12738/

Problem:
When AFR xlator initialises, it uses the name of the client xlators
below it for storing the pending changelogs (xattrs). This can be
problem when some other xlator is loaded in between AFR and the client.
Though that is a trivial 'traverse-graph-till-the-client-and-use-the-name'
fix in AFR's init(), there are other issues like when there's no client
xlator at all when, say, AFR is moved to the server side.

Fix:
The client xlator names are currenly unique and stored as
brickinfo->brick_ids. So persist these ids as comma separated values in
AFR's volume_options and use them as xattr values during init().

Change-Id: Ie761ffeb3373a4c4d85ad05c84a768c4188aa90d
BUG: 1291985
Signed-off-by: Ravishankar N 
Reviewed-on: http://review.gluster.org/12977
Tested-by: NetBSD Build System 
Reviewed-by: Pranith Kumar Karampuri 
Tested-by: Gluster Build System

mgmt/gluster: Handle tier brick volgen

2015-12-10T12:34:52+00:00

        Backport of http://review.gluster.org/#/c/12595/

Index xlator watches only some xattrs based on type of volume. i.e.
disperse/afr. When the volume becomes tiered then index is not adding these
options in the volfile leading to no maintenance of indices. Thus no
proactive self-heals. With this fix, we write brick volfiles considering
the type of volume they belong to.

Change-Id: Ibe8f2d4ad5cb350306ab7ca0753e0f9a40b96a26
BUG: 1283756
Signed-off-by: Pranith Kumar K 
Reviewed-on: http://review.gluster.org/12595
Tested-by: NetBSD Build System 
Tested-by: Gluster Build System 
Reviewed-by: Kaushal M 
Signed-off-by: Anuradha Talur 
Reviewed-on: http://review.gluster.org/12847

glusterd/quota: quota-version conflict in export/import volinfo

2015-12-09T07:25:25+00:00

This is a backport of http://review.gluster.org/#/c/12865/

When exporting/importing voinfo during handshake,
quota conf and quota xattr version were using same key
'quota-version' and updated wrong values when importing
quota version values.

> Change-Id: If939d6f5bc4851d4114963877be72dda21834f0f
> BUG: 1287996
> Signed-off-by: vmallika 

Change-Id: Ic234d9e496f1372789112a0b82ba5cf34014de64
BUG: 1288052
Signed-off-by: vmallika 
Reviewed-on: http://review.gluster.org/12872
Tested-by: NetBSD Build System 
Tested-by: Gluster Build System 
Reviewed-by: Atin Mukherjee

tier/glusterd : Validation for frequency thresholds and record-counters

2015-12-02T19:47:17+00:00

1) if record-counters is set to off
   check if both the frequency thresholds are non-zero, then pop
   an error message, with volume set failed.
2) if record-counters is set to on
   check if both the frequency thresholds are zero, then pop
   an note, but volume set is not failed.
3) If any of the frequency thresholds are set to a non-zero value,
   switch record-counters on, if not already on
4) If both the frequency thresholds are set to zero,
   switch record-counters off, if not already off

NOTE: In this fix we have
1) removed unnecessary ctr vol set options.
2) changed  ctr_hardlink_heal_expire_period to ctr_lookupheal_link_timeout

Backport of  http://review.gluster.org/12780

> Change-Id: Ie7ccfd3f6e021056905a79de5a3d8f199312f315
> BUG: 1286346
> Signed-off-by: Joseph Fernandes 
> Signed-off-by: Dan Lambright 
> Reviewed-on: http://review.gluster.org/12780
> Tested-by: Gluster Build System 
> Tested-by: NetBSD Build System 
> Signed-off-by: Joseph Fernandes 

Change-Id: I35621ed3cc1ad20a75ef16e0b95453b8c6120852
BUG: 1287560
Signed-off-by: Joseph Fernandes 
Reviewed-on: http://review.gluster.org/12849
Tested-by: NetBSD Build System 
Tested-by: Gluster Build System 
Reviewed-by: Dan Lambright 
Tested-by: Dan Lambright

afr/glusterd: Fix naming issue in tier related changes

2015-12-02T08:49:21+00:00

changing some of the function names added recently as
part of the tiering changes.

Back port of>
>Change-Id: I238831128ee00cdf83f8a80be937d3528d133099
>BUG: 1275489
>Signed-off-by: Mohammed Rafi KC 
>Reviewed-on: http://review.gluster.org/12431
>Reviewed-by: Pranith Kumar Karampuri 
>Tested-by: Gluster Build System 
>Reviewed-by: Dan Lambright 
>Tested-by: Dan Lambright 

Change-Id: Id2125e20690e697948a7e48529d853626e345879
BUG: 1285978
Signed-off-by: Mohammed Rafi KC 
Reviewed-on: http://review.gluster.org/12774
Tested-by: NetBSD Build System 
Tested-by: Gluster Build System 
Reviewed-by: Atin Mukherjee