glusterfs-afrv1.git/xlators/protocol, branch v3.2.6qa5

protocol/client: writev(): don't unwind if rpc_submit failed

2012-02-20T08:48:44+00:00

because rpc_submit does call 'cbk()' from inside if sending fails.
no need to unwind in higher layers

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

Move some of the messages to log level `TRACE'.

2011-10-31T05:43:10+00:00

Change-Id: I41e6f39c5d0621942a310f550250034fd520ec76
BUG: 3761
Reviewed-on: http://review.gluster.com/644
Tested-by: Gluster Build System 
Reviewed-by: Amar Tumballi

protocol/client: print remote operation failure logs in error mode instead if info

2011-10-28T12:00:18+00:00

Change-Id: Ic4cd16618925656a12049f28f9b30bcac2242d4b
BUG: 2346
Reviewed-on: http://review.gluster.com/621
Tested-by: Gluster Build System 
Reviewed-by: Amar Tumballi 
Reviewed-by: Vijay Bellur

check the return value of inode_path for less than or equal to zero

2011-10-28T11:14:56+00:00

Change-Id: I9bbdfe79664c1339b66819a6c7ea4b7698beb5c6
BUG: 3757
Reviewed-on: http://review.gluster.com/640
Tested-by: Gluster Build System 
Reviewed-by: Amar Tumballi

libglusterfs/iobuf: increase the iobref's iobuf array size

2011-10-10T10:58:28+00:00

earlier it was hardcoded to 8, now increased the size to 16.
also return the exact error code in client_submit_vec_request(),
so there will be no missing frames in case of errors.

Change-Id: I82a6ee681a543b673a7cf1a0b9c5ade2a7175ebe
BUG: 3679
Reviewed-on: http://review.gluster.com/570
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

glusterfs protocol: handshake to log the version of the peer

2011-09-20T08:48:35+00:00

* As RPC program's name is just used for logging, we now have
  'PACKAGE_VERSION' part of the string, which gets logged in client
  side.
* From client, we send the PACKAGE_VERSION in handshake dictionary,
  which gets logged on serverside handshake.

The change doesn't break any compatibility between client or server
as it would only enhance the logging part of handshake.

Change-Id: Ie7f498af2f5d3f97be37c8d982061cb6021883ce
BUG: 3589
Reviewed-on: http://review.gluster.com/468
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

mgmt/Glusterd: Implementation volume set help/help-xml

2011-08-19T05:42:48+00:00

Change-Id: I0c54fd1c15550e5e5551e95ed32adb14d8029fab
Reviewed-on: http://review.gluster.com/238
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

Change Copyright current year

2011-08-10T17:57:44+00:00

Change-Id: Id1f1a91cf15d933d5621a0073ddaebe02df0f159
BUG: 3348
Reviewed-on: http://review.gluster.com/198
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

LICENSE: s/GNU Affero General Public/GNU General Public/

2011-08-06T13:40:14+00:00

Change-Id: Ibf5f45431d7a55b70d7304649af652d6f25bb688
BUG: 3348
Reviewed-on: http://review.gluster.com/183
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

server: Reassociating 'old' conn can lead to chaos.

2011-07-12T12:38:10+00:00

Since we moved to a single socket connection b/w client and server,
inherting connection state is unnecessary and can sometimes be
dangerous when clients reconnect even before the server detects
a socket error on the old connection.

Dirty detail: This reassociation results in 'ref count' not decreasing
in tandem with the connection disconnects. This results in a resource
leak.

Signed-off-by: Krishnan Parthasarathi 
Signed-off-by: Anand Avati 

BUG: 3104 (Self-heal does not work in dis-rep!)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3104