{"push_id":1515567976,"size":2,"distinct_size":2,"ref":"refs/heads/release-3.9","head":"bc1ce55a7c83c7f5394b26a65bd4a3a669b5962a","before":"72a768610a438aa43184d840beb532af87aa2217","commits":[{"sha":"0f63bda0df91ee7ff42e3262c74220178ef87a21","author":{"name":"Ashish Pandey","email":"c91949672c9e337b6992fc0032bafd6df3335bb3@redhat.com"},"message":"cluster/disperse: Do not log fop failed for lockless fops\n\nProblem: Operation failed messages are getting logged\nbased on the callbacks of lockless fop's. If a fop does\nnot take a lock, it is possible that it will get some\nout of sync xattr, iatts. We can not depend on these\ncallback to psay that the fop has failed.\n\nSolution: Print failed messages only for locked fops.\nHowever, heal would still be triggered.\n\n>Change-Id: I4427402c8c944c23f16073613caa03ea788bead3\n>BUG: 1414287\n>Signed-off-by: Ashish Pandey <aspandey@redhat.com>\n>Reviewed-on: http://review.gluster.org/16435\n>Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>\n>Smoke: Gluster Build System <jenkins@build.gluster.org>\n>NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>\n>CentOS-regression: Gluster Build System <jenkins@build.gluster.org>\n>Signed-off-by: Ashish Pandey <aspandey@redhat.com>\n\nChange-Id: I4427402c8c944c23f16073613caa03ea788bead3\nBUG: 1415082\nSigned-off-by: Ashish Pandey <aspandey@redhat.com>\nReviewed-on: https://review.gluster.org/16439\nReviewed-by: Xavier Hernandez <xhernandez@datalab.es>\nSmoke: Gluster Build System <jenkins@build.gluster.org>\nNetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>\nCentOS-regression: Gluster Build System <jenkins@build.gluster.org>","distinct":true,"url":"https://api.github.com/repos/anoopcs9/glusterfs/commits/0f63bda0df91ee7ff42e3262c74220178ef87a21"},{"sha":"bc1ce55a7c83c7f5394b26a65bd4a3a669b5962a","author":{"name":"Ashish Pandey","email":"c91949672c9e337b6992fc0032bafd6df3335bb3@redhat.com"},"message":"cluster/ec: Do not start heal on good file while IO is going on\n\nProblem:\nWrite on a file has been slowed down significantly after\nhttp://review.gluster.org/#/c/13733/\n\nRC : When update fop starts on a file, it sets dirty flag at\nthe start and remove it at the end which make an index entry\nin indices/xattrop. During IO, SHD scans this and finds out\nan index and starts heal even if all the fragments are healthy\nand up tp date. This heal takes inodelk for different types of\nheal. If the IO is for long time this will happen in every 60 seconds.\nDue to this extra, unneccessary locking, IO gets slowed down.\n\nSolution:\nBefore starting  any  type of heal check if file needs heal or not.\n\n>Change-Id: Ib9519a43e7e4b2565d3f3153f9ca0fb92174fe51\n>BUG: 1409191\n>Signed-off-by: Ashish Pandey <aspandey@redhat.com>\n>Reviewed-on: http://review.gluster.org/16377\n>NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>\n>CentOS-regression: Gluster Build System <jenkins@build.gluster.org>\n>Smoke: Gluster Build System <jenkins@build.gluster.org>\n>Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>\n>Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>\n>Signed-off-by: Ashish Pandey <aspandey@redhat.com>\n\nChange-Id: Ib9519a43e7e4b2565d3f3153f9ca0fb92174fe51\nBUG: 1415160\nSigned-off-by: Ashish Pandey <aspandey@redhat.com>\nReviewed-on: https://review.gluster.org/16444\nSmoke: Gluster Build System <jenkins@build.gluster.org>\nNetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>\nCentOS-regression: Gluster Build System <jenkins@build.gluster.org>\nReviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>","distinct":true,"url":"https://api.github.com/repos/anoopcs9/glusterfs/commits/bc1ce55a7c83c7f5394b26a65bd4a3a669b5962a"}]}
{"actor":{"display_login":"anoopcs9"}}