glusterfs.git/xlators/protocol, branch v3.2.2

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

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

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

protocol/client: Change log level of error to GF_LOG_ERROR

2011-06-08T10:03:08+00:00

Signed-off-by: Pranith Kumar K 
Signed-off-by: Anand Avati 

BUG: 2986 (Failed operations should should be logged `E' or `W')
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2986

Introduce client-allow-insecure xlator-option.

2011-05-31T16:13:20+00:00

Allows glusterfs clients to bind to any port and does not restrict it
to 1024.

This is a xlator-option only, and is not supported in volume set cmd.
The reason is, few clients may choose this, and few may not. Hence
only supported as a xlator-option during mount time.

For this to work with glusterfs, server.allow-insecure should be set
to on

Signed-off-by: shishir gowda 
Signed-off-by: Anand Avati 

BUG: 2868 (Add xlator-option to support insecure-bind for clients)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2868

gf_auth also needs to handle server.allow-insecure

2011-05-31T16:13:15+00:00

When server.allow-insecure option is set, the connection from client
can be from any port. gf_auth also needs to check for this option

Signed-off-by: shishir gowda 
Signed-off-by: Anand Avati 

BUG: 2868 (Add xlator-option to support insecure-bind for clients)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2868

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