glusterfs.git/xlators/protocol/server/src, branch v3.2.4qa3

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

protocol/server: logging changes

2011-06-08T16:58:16+00:00

Signed-off-by: Raghavendra Bhat 
Signed-off-by: Anand Avati 

BUG: 2982 ([glusterfs-3.2.1qa2]: logging changes is server protocol)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2982

prevent few excessive logs

2011-04-21T14:38:33+00:00

Signed-off-by: Amar Tumballi 
Signed-off-by: Anand Avati 

BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

remove excessive logs due to log enhancement

2011-04-13T07:38:47+00:00

Signed-off-by: Amar Tumballi 
Signed-off-by: Anand Avati 

BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

protocol/server: prevent unnessary logs in INFO level

2011-04-11T06:52:33+00:00

'op_ret == 0' in readdir() is a valid return code.

Signed-off-by: Amar Tumballi 
Signed-off-by: Anand Avati 

BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

removed reference to GF_LOG_NORMAL

2011-04-07T18:40:25+00:00

instead used GF_LOG_INFO, which is more standard log level.

Signed-off-by: Amar Tumballi 
Signed-off-by: Vijay Bellur 

BUG: 2669 (RuntimeError: cannot recognize log level "normal")
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2669