glusterfs.git/rpc/rpc-lib, branch v3.3.0qa28

rpc: log in DEBUG when nfs clients try to see if ACL requests are accepted by nfs server

2012-03-14T13:01:22+00:00

Change-Id: I897b48a02ce2150d268a1a8b45163e9e1aee6cff
BUG: 801338
Signed-off-by: krishna 
Reviewed-on: http://review.gluster.com/2901
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

rpc-lib/rpcsvc: nfs auth corrections

2012-03-14T10:10:57+00:00

in comparing ip addresses during authentication,
we need to take only the ip address of the client
instead of the transport endpoint (ip:port).

Change-Id: If48eca37edea1d69deb150720fbaea0ea2443a00
BUG: 771845
Signed-off-by: Rajesh Amaravathi 
Reviewed-on: http://review.gluster.com/2929
Tested-by: Gluster Build System 
Reviewed-by: Amar Tumballi 
Reviewed-by: Vijay Bellur

cli, glusterd, nfs: "volume status|profile|top" for nfs servers

2012-03-14T09:27:42+00:00

Enables usage of volume monitoring operations "volume status", "volume top" and
"volume profile" for nfs servers. These operations can be performed on
nfs-servers  by passing "nfs" as an option in cli. The output is similar to the
normal brick outputs for these commands.

The new syntaxes for the changed commands are as below,
 #gluster volume profile  {start|info|stop} [nfs]
 #gluster volume top  {[open|read|write|opendir|readdir [nfs]]
               |[read-perf|write-perf [nfs|{bs  count }]]}
               [brick ] [list-cnt ]
 #gluster volume status [all |  [nfs|]]
          [detail|clients|mem|inode|fd|callpool]

Change-Id: Ia6eb50c60aecacf9b413d3ea993f4cdd90ec0e07
BUG: 795267
Signed-off-by: Kaushal M 
Reviewed-on: http://review.gluster.com/2820
Tested-by: Gluster Build System 
Reviewed-by: Krishnan Parthasarathi

rpc-clnt: print xid of the saved frames getting unwind

2012-03-05T17:48:29+00:00

so that one can match the corresponding submit failed errors in
brick logs

Change-Id: I4422805a20c251aeffb51d63572c251176b2620c
Signed-off-by: Amar Tumballi 
BUG: 799337
Reviewed-on: http://review.gluster.com/2864
Tested-by: Gluster Build System 
Reviewed-by: M S Vishwanath Bhat 
Reviewed-by: Vijay Bellur

mempool: adjustments in pool sizes

2012-02-22T12:23:48+00:00

* while creating 'rpc_clnt', the caller knows what would be the ideal
  load on it, so an extra argument to set some pool sizes

* while creating 'rpcsvc', the caller knows what would be the ideal
  load of it, so an extra argument to set request pool size

* cli memory footprint is reduced

Change-Id: Ie245216525b450e3373ef55b654b4cd30741347f
Signed-off-by: Amar Tumballi 
BUG: 765336
Reviewed-on: http://review.gluster.com/2784
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

rpc/clnt: handle PARENT_DOWN event appropriately

2012-02-21T09:42:42+00:00

Change-Id: I4644e944bad4d240d16de47786b9fa277333dba4
BUG: 767862
Signed-off-by: Raghavendra G 
Signed-off-by: Amar Tumballi 
Reviewed-on: http://review.gluster.com/2735
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

cluster/afr: Add commands to see self-heald ops

2012-02-21T05:23:37+00:00

Change-Id: Id92d3276e65a6c0fe61ab328b58b3954ae116c74
BUG: 763820
Signed-off-by: Pranith Kumar K 
Reviewed-on: http://review.gluster.com/2775
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

NLM - Network Lock Manger V4

2012-02-20T15:26:51+00:00

Change-Id: Ic31b8bb10a28408da2a623f4ecc0c60af01c64af
BUG: 795421
Signed-off-by: Krishna Srinivas 
Reviewed-on: http://review.gluster.com/2711
Tested-by: Gluster Build System 
Reviewed-by: Amar Tumballi

protocol/client,server: fcntl lock self healing.

2012-02-20T12:45:31+00:00

Currently(with out this patch), on a disconnect the server cleans up
the transport which inturn closes the fd's and releases the locks acquired on
those fd's by that client. On a reconnect, client just reopens the fd's but
doesn't reacquire the locks. The application that had previously acquired
the locks still is under the assumption that it is the owner of those locks
which might have been granted to other clients(if they request) by the server
leading to data corruption.

This patch allows the client to reacquire the fcntl locks (held on the fd's)
during client-server handshake.

* The server identifies the client via process-uuid-xl (which is a combination
  of uuid and client-protocol name, it is assumed to be unique) and lk-version
  number.

* The client maintains a list of process-uuid-xl, lk-version pair for each
  accepted connection. On a connect, the server traverses the list for a
  matching pair, if a matching pair is not found the the server returns
  lk-version with value 0, else it returns the lk-version it has in store.

* On a disconnect, the server and client enter grace period, and on the
  completion of the grace period, the client bumps up its lk-version number
  (which means, it will reacquire the locks the next time) and the server will
  distroy the connection. If reconnection happens within the grace period, the
  server will find the matching (process-uuid-xl, lk-version) pair in its list
  which guarantees that the fd's and there corresponding locks are still valid
  for this client.

Configurable options:
  To set grace-timeout, the following options are
    option server.grace-timeout value
    option client.grace-timeout value

  To enable or disable the lk-heal,
    option lk-heal [on|off]

gluster volume set command can be used to configurable options
Change-Id: Id677ef1087b300d649f278b8b2aa0d94eae85ed2
BUG: 795386
Signed-off-by: Mohammed Junaid 
Reviewed-on: http://review.gluster.com/2766
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

iobuf: use 'iobuf_get2()' to get variable sized buffers

2012-02-20T08:46:27+00:00

added 'TODO' in places where it is missing.

Change-Id: Ia802c94e3bb76930f7c88c990f078525be5459f5
Signed-off-by: Amar Tumballi 
BUG: 765264
Reviewed-on: http://review.gluster.com/388
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur