glusterfs.git/xlators/protocol/client/src/client-handshake.c, branch v3.2.3qa5

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

client-handshake: skip CHILD_DOWN notifications when client is querying port using different volume names in the presence of rdma.

2011-07-07T13:03:57+00:00

Signed-off-by: Raghavendra G 
Signed-off-by: Vijay Bellur 

BUG: 3091 (rebalance fails with "transport endpoint not connected" in 3.2.1 rdma set-up)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3091

loc_t: add 'gfid' and 'pargfid' fields

2011-06-14T07:13:51+00:00

these fields are used mainly in case of selfheal path, where
'inode->gfid'||'parent->gfid' is not yet set.

These fields in 'loc' will have lower precedence than 'inode->gfid'
in client protocol.

also contains 'Pranith 's patch to set proper
loc->gfid during afr selfheal

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

fix multiple transport related portmap issues in client handshake

2011-06-08T18:19:17+00:00

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

BUG: 2294 (Currently there is no way through cli to make a volume listen on both the transports (socket/rdma))
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2294

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/client: fix the fd_count decrement logic

2011-04-13T04:49:56+00:00

the error creeped in during some code cleanup and logging enhancement

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

BUG: 1761 (incorrect self-heal behaviour when files are deleted)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1761

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

protocol/client: make sure to send only genuine events up to parent

2011-04-06T17:51:52+00:00

that way parent notify logic is fine.

also, remove 'xlator_notify()' call in code, instead use 'default_notify()'

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

BUG: 2584 (Inode number changes on a directory when one of subvolumes is down in replicate)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2584

protocol/client: log enhancement

2011-03-17T18:59:17+00:00

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

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