glusterfs.git/rpc, branch v3.3.0qa12

build: Solaris build fixes

2011-09-27T12:44:41+00:00

Change-Id: Ic47d07a199ecbc42a141e391bbc75096e270e404
BUG: 3446
Reviewed-on: http://review.gluster.com/503
Tested-by: Gluster Build System 
Reviewed-by: Amar Tumballi

rpc: fix wrong wiping of state machine's state

2011-09-25T13:15:12+00:00

The macro __socket_proto_read() is used to read one sub-header in a fragment
after another. It also has to 'get out' of the state machine's
switch/case construct in two situations -

a) finished reading the full header

b) after a partial read, (and return in the same state at next pollin)

The 'reset' of the state should happen only after a full read of the header
and not if there was a partial read of the header.

Change-Id: I3650a83e1fae0f317cfd1b549835c72e39dc5253

rpc: No timeouts for lock fops.

2011-09-23T13:11:32+00:00

As of today, all fops bail out after 30 mins by default. This is not desirable
with lock fops since it could be 'rightfully blocked' for a really long time.
But the client would assume that the lock fop has 'expired' after 30 mins and
clean up its references to the locks.  Later when the locks xlator decides to
grant it, we are left with an orphan (stale) lock .

This fix exempts lock fops from timeouts. Only on network disruptions both
client and server decide to 'clean up' the locks held.

Change-Id: If1d74ba21113650b976728e9b764c551a0a49e59
BUG: 3617
Reviewed-on: http://review.gluster.com/478
Tested-by: Gluster Build System 
Reviewed-by: Amar Tumballi

glusterd: Implemented cmd to trigger self-heal on a replicate volume.

2011-09-22T16:43:25+00:00

This cmd is used in the context of proactive self-heal for replicated
volumes. User invokes the following cmd when (s)he suspects that self-heal
needs to be done on a particular volume,
        gluster volume heal .

Change-Id: I3954353b53488c28b70406e261808239b44997f3
BUG: 3602
Reviewed-on: http://review.gluster.com/454
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

NFS : Posix compliance fixes.

2011-09-22T11:51:22+00:00

Change-Id: I4f1d8883a3eedee20557e306815674a6dc062bfe
BUG: 1337
Reviewed-on: http://review.gluster.com/487
Tested-by: Gluster Build System 
Reviewed-by: Amar Tumballi 
Reviewed-by: Vijay Bellur

rpc:memcpy data of right size to auth params

2011-09-20T05:00:08+00:00

Change-Id: I6999e0a1463ee3475f7607990337326b3f008538
BUG: 3587
Reviewed-on: http://review.gluster.com/464
Tested-by: Gluster Build System 
Reviewed-by: Amar Tumballi

rpc: Use correct variable for volume-specific insecure ports check

2011-09-19T05:17:26+00:00

Change-Id: Ica59a3154c4e7d980d3477dd3879c7cebe92ad87
BUG: 3515
Reviewed-on: http://review.gluster.com/418
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

rpc: fix up mountbroker xdr defs and regenerate headers

2011-09-16T04:56:12+00:00

Change-Id: I8a88d2b9228c3614ee7cbaf48782a419e6aee0f6
BUG: 3482
Reported-by: Krishnan Parthasarathi 
Reviewed-on: http://review.gluster.com/432
Tested-by: Gluster Build System 
Reviewed-by: Krishnan Parthasarathi 
Reviewed-by: Vijay Bellur

support for de-commissioning a node using 'remove-brick'

2011-09-13T09:10:12+00:00

to achieve this, we now create volume-file with
'decommissioned-nodes' option in distribute volume, then just
perform the rebalance set of operations (with 'force' flag set).

now onwards, the 'remove-brick' (with 'start' option) operation tries
to migrate data from removed bricks to existing bricks.

'remove-brick' also supports similar options as of replace-brick.

* (no options) -> works as 'force', will have the current behavior
         of remove-brick, ie., no data-migration, volume changes.

* start  (starts remove-brick with data-migration/draining process,
          which takes care of migrating data and once complete, will
          commit the changes to volume file)
* pause  (stop data migration, but keep the volume file intact with
          extra options whatever is set)
* abort  (stop data-migration, and fall back to old configuration)
* commit (if volume is stopped, commits the changes to volumefile)
* force  (stops the data-migration and commits the changes to
          volume file)

Change-Id: I3952bcfbe604a0952e68b6accace7014d5e401d3
BUG: 1952
Reviewed-on: http://review.gluster.com/118
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

socket: provide proper arguments to getaddrinfo

2011-09-13T07:04:33+00:00

-----
from 'man getaddrinfo' :

If hints.ai_flags includes the AI_ADDRCONFIG flag, then IPv4 addresses
are returned in the list pointed to by res only if the local system has
at least one IPv4 address  configured, and IPv6 addresses are only
returned if the local system has at least one IPv6 address configured.
-----

Change-Id: Ie30344daf1bb9d41ac58741b38e83af35cd8b5e9
BUG: 2456
Reviewed-on: http://review.gluster.com/405
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur