glusterfs.git/xlators/mgmt, branch v3.4.0qa3

geo-rep / gsyncd,glusterd: do not hardcode socket path

2012-11-29T00:54:07+00:00

... in gsyncd python code. Indeed, use the configuration
mechanism to set it suitably from glusterd.

Change-Id: I9fe2088b14d28588d1e64fe892740cc5755b8365
BUG: 868877
Signed-off-by: Csaba Henk 
Reviewed-on: http://review.gluster.org/4143
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

glusterd, cli: implement gluster system uuid reset command

2012-11-29T00:28:55+00:00

A commonly faced problem among glusterfs users is: after a fresh
installation of glusterfs in a virtual machine, the VM image is
cloned to make multiple instances of the server. This breaks
glusterd because right after glusterfs installation on the first
boot glusterd would have created the node UUID and this gets
inherited into the clone. The result is wierd behavior at the time
of peer probe where glusterd does not (yet) deal with UUID
collisions in a user friendly way.

To handle it gluster peer reset command is implemented which upon
execution changes the uuid of local glusterd.

Change-Id: If207dd2ad93ab94ef1a3253f409c21c442975f87
BUG: 811493
Signed-off-by: Raghavendra Bhat 
Reviewed-on: http://review.gluster.org/3637
Reviewed-by: Pranith Kumar Karampuri 
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

glusterd: Protected conf->xprt_list racy access.

2012-11-29T00:27:01+00:00

- epoll on RPCSVC_EVENT_ACCEPT would add corresponding xprt
  onto the xprt_list. Concurrently, synctask thread (volume op)
  would call into glusterd_fetchspec_notify which iterates on
  the xprt_list. Added a mutex to protect such a racy access of
  the list.

Change-Id: Idc51b4bdb1c814dfab7790e1c899d6977f7640f2
BUG: 878873
Signed-off-by: Krishnan Parthasarathi 
Reviewed-on: http://review.gluster.org/4241
Reviewed-by: Raghavendra G 
Reviewed-by: Jeff Darcy 
Tested-by: Gluster Build System

protocol/client: add an option to filter O_DIRECT flag in open

2012-11-28T11:37:03+00:00

with the option, the idea is all client-side caching will be disabled,
where as on server side process, the fd will be treated as a regular
fd, thus helping the performance better.

"gluster volume set  remote-dio enable" would set
this option in client protocol volumes.

Change-Id: Id2255a167137f8fee20849513e3011274dc829b4
Signed-off-by: Amar Tumballi 
BUG: 845213
Reviewed-on: http://review.gluster.org/4206
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

glusterd: volume-sync shouldn't validate volume-id

2012-11-28T07:28:00+00:00

- volume sync would overwrite volume information on local node
  from the hostname supplied. This warning is provided to the user.

- Also fixed a double free in volume-sync handler.

Change-Id: Icc68d9d563fb50ca58d5880921f063692e1e6882
BUG: 865700
Signed-off-by: Krishnan Parthasarathi 
Reviewed-on: http://review.gluster.org/4188
Reviewed-by: Vijay Bellur 
Tested-by: Gluster Build System

mgmt/glusterd: Implementation of server-side quorum

2012-11-24T07:14:50+00:00

Feature-page:
http://www.gluster.org/community/documentation/index.php/Features/Server-quorum

Change-Id: I747b222519e71022462343d2c1bcd3626e1f9c86
BUG: 839595
Signed-off-by: Pranith Kumar K 
Reviewed-on: http://review.gluster.org/3811
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

glusterd: fix use of undefined realpath(3) result

2012-11-23T10:40:02+00:00

Change-Id: Ic50ae192c99cece25cd63f2277fb440fca5f0b04
BUG: 877522
Signed-off-by: Jeff Darcy 
Reviewed-on: http://review.gluster.org/4201
Reviewed-by: Krishnan Parthasarathi 
Tested-by: Gluster Build System

glusterd: brick path availability check only for local bricks

2012-11-23T10:35:10+00:00

Change-Id: Ica50fb92608f5fd75f8887e0718177faf29d31c4
BUG: 877522
Signed-off-by: Krishnan Parthasarathi 
Reviewed-on: http://review.gluster.org/4203
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

gsyncd / geo-rep: include hostname in status cmd

2012-11-22T00:49:04+00:00

Including hostname of the node where geo-rep start was
initiated from. This helps any consumers of the status
command to identify and possibly issue commands on those
node(s).

Change-Id: I005083878a3a4794da3b7f3f7d2cc9d28f004e3f
BUG: 858218
Signed-off-by: Venky Shankar 
Reviewed-on: http://review.gluster.org/4218
Reviewed-by: Csaba Henk 
Tested-by: Gluster Build System

perf/io-threads: least-rate-limit least priority throttling

2012-11-21T21:49:47+00:00

The 'least-rate-limit' io-threads translator option enables
throttling of least priority operations. This is initially intended
as a debug/diagnostic tool for users who might experience
overloaded servers via background activity (i.e., self-heal).

least-rate-limit defines the maximum number of least priority
operations the io-threads translator will dequeue in one second.
If the specified rate limit is met, the worker threads sleep for
the minimal amount of time before the next least priority operation
becomes available (or until a new request arrives).

The requests/second metric is generic and relative to a variety of
factors involved with a background operation (server, storage,
etc.). The most recent measured rate ("cached least rate") is added
to the io-threads state dump content (kill -USR1) to serve as a
reference point to throttle background activity under particular
conditions.

Change-Id: I80f2282992137d57b1becaa5c6ae3858c066862a
BUG: 853680
Signed-off-by: Brian Foster 
Reviewed-on: http://review.gluster.org/4119
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati