glusterfs-snapshot.git -

diff options

author	Kaushal M <kaushal@redhat.com>	2013-05-23 12:19:33 +0530
committer	Anand Avati <avati@redhat.com>	2013-06-04 13:27:35 -0700
commit	0c1916f3e1eb81aa81dc2d62e97f46880390838c (patch)
tree	e82396844066f43718bddb42f6376adbe8064568 /xlators/protocol
parent	a72e77f7bc5abfa739f19f6d02e7cf94b138c477 (diff)

glusterd-syncop: Fix unlocking and collating errors

* Only those peers which were locked need to be unlocked. * Fix location of collating errors in callbacks. The callback functions could miss collating errors if there was an rpc error. Change-Id: Ie27c2f1ec197da4f5077a4d6e032127954ce87cd BUG: 948686 Signed-off-by: Kaushal M <kaushal@redhat.com> Reviewed-on: http://review.gluster.org/5087 Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com> Tested-by: Gluster Build System <jenkins@build.gluster.com>

Diffstat (limited to 'xlators/protocol')

0 files changed, 0 insertions, 0 deletions

7226e16f'>rfc.sh: Include BUG: header even in first runAnand Avati2013-08-141-2/+2 | | | | | | | | | | Set the commit hook before entiring editor mode. This fixes the error where rfc.sh after first clone does not set BUG: header Change-Id: Ic0e9f2d3f656bc81e29d35556022fbdff2f61225 BUG: 764890 Signed-off-by: Anand Avati <avati@redhat.com> Reviewed-on: http://review.gluster.org/5632 * log: add logger.conf.example fileBala.FA2013-08-143-2/+18 | | | | | | | | | | | | This example file can be safely renamed as logger.conf to enable syslog logging Change-Id: If49dd6002a046915b2eca330b7a539f4fa1f94fa BUG: 928648 Signed-off-by: Bala.FA <barumuga@redhat.com> Reviewed-on: http://review.gluster.org/5622 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Vijay Bellur <vbellur@redhat.com> * log: add comments to rsyslog gluster configuration fileBala.FA2013-08-142-1/+71 | | | | | | | | | | | | Comments are added to rsyslog gluster configuration files to give clear meanings and example email alerting. Change-Id: I23577dc3b39bca89696c46ab6252dc5673d0803f BUG: 928648 Signed-off-by: Bala.FA <barumuga@redhat.com> Reviewed-on: http://review.gluster.org/5621 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Vijay Bellur <vbellur@redhat.com> * cluster/afr: Add largest file is source policyAnand Avati2013-08-142-29/+93 | | | | | | | | | | | | | | For Write Once Read Many times type of work-load choosing largest file to be the source will always resolve fool-fool scenarios correctly. In other cases we fsync() the files and will have a reliable 'wise man'. Change-Id: Ic4dbea8d06db6d578fbcb866fb65ee2d066ac7ba BUG: 958118 Signed-off-by: Anand Avati <avati@redhat.com> Reviewed-on: http://review.gluster.org/5519 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com> * performance/write-behind: invoke request queue processing ifRaghavendra G2013-08-141-19/+30 | | | | | | | | | | | | | | | | | | | | | | we find fd marked bad while trying to fulfill lies. * flush was queued behind some unfulfilled write. * A previously wound write returned an error and hence fd was marked bad with corresponding error. * wb_fulfill_head (invocation probably rooted in wb_flush), before winding checks for failures of previous writes and since there was a failure, calls wb_head_done without even winding one request in head. * wb_head_done unrefs all the requests in list "head". * since flush was last operation on fd (and most likely last operation on inode itself), no one invokes wb_process_queue and flush is stuck in request queue for eternity. Change-Id: I3b5b114a1c401d477dd7ff64fb6119b43fda2d18 BUG: 988642 Signed-off-by: Raghavendra G <rgowdapp@redhat.com> Reviewed-on: http://review.gluster.org/5398 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Anand Avati <avati@redhat.com> * afr: treat appending writes as stable writes.Anand Avati2013-08-135-3/+69 | | | | | | | | | | | | | Durability of appending writes is implicit in the file size. Therefore performing an explicit fsync() is unnecessary in such cases as self-heal can check for the size of file when pending changelog is not unambiguous. Change-Id: I05446180a91d20e0dbee5de5a7085b87d57f178a BUG: 927146 Signed-off-by: Anand Avati <avati@redhat.com> Reviewed-on: http://review.gluster.org/5501 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com> * posix: Default value for `batch-fsync-delay-usec` should be '0'Harshavardhana2013-08-131-3/+3 | | | | | | | | | |


context:
space:
mode: