{"push_id":599730557,"size":1000,"distinct_size":0,"ref":"refs/heads/master","head":"02d42a5e80f3e2624eba2d00acff0aaebb20b12f","before":"006328b81b2dd3416c20b0f19b438c614c1932cc","commits":[{"sha":"eeb4434d6196735323fa28cfd19b5f7b36e1f664","author":{"email":"648737a4d5e8e7f3005f086c2dbed7bf1e0319c8@harshavardhana.net","name":"Harshavardhana"},"message":"glusterd: NFS server wrongly started with `DEBUG` log-level\n\nDisable DEBUG\n\nChange-Id: I011231ba3df4a42f892f1305867bfc74bb101269\nBUG: 1089172\nSigned-off-by: Harshavardhana <harsha@harshavardhana.net>\nReviewed-on: http://review.gluster.org/7654\nReviewed-by: Niels de Vos <ndevos@redhat.com>\nReviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>\nTested-by: Gluster Build System <jenkins@build.gluster.com>\nReviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>\nTested-by: Krishnan Parthasarathi <kparthas@redhat.com>","distinct":false,"url":"https://api.github.com/repos/anoopcs9/glusterfs/commits/eeb4434d6196735323fa28cfd19b5f7b36e1f664"},{"sha":"b47b46d98a5e1d3e6e9eb9bde4f81b745f2ac09d","author":{"email":"ca630918676f465396be6c88fe8166e4d3e6bea8@redhat.com","name":"Raghavendra Bhat"},"message":"mgmt/glusterd: quorum check before taking the snapshot\n\nwithout force option:\nquorum fails if glusterds are not in quorum. If glusterd are in quorum, then\nvolume quorum (i.e quorum of the bricks) is checked. volume quorum fails even if\none of the bricks are down.\n\nwith force option:\neven though the glusterds are not in quorum, and some bricks are down, the\nquorum check of the volume (i.e bricks) is done and if the volume quorum is\nmet, snapshot is taken.\n\nChange-Id: I06971e45d5cf09880032ef038bfe011e6c244268\nBUG: 1061685\nSigned-off-by: Raghavendra Bhat <raghavendra@redhat.com>\nReviewed-on: http://review.gluster.org/7463\nTested-by: Gluster Build System <jenkins@build.gluster.com>\nReviewed-by: Rajesh Joseph <rjoseph@redhat.com>\nReviewed-by: Kaushal M <kaushal@redhat.com>","distinct":false,"url":"https://api.github.com/repos/anoopcs9/glusterfs/commits/b47b46d98a5e1d3e6e9eb9bde4f81b745f2ac09d"},{"sha":"e80daecc3dd3023f010c785ff0e238fc92214477","author":{"email":"9e157012ae67f4ec8906b0ba0acc39e7756f1e97@redhat.com","name":"Avra Sengupta"},"message":"glusterd: Use a calloc-ed copy of txn_id for glusterd_do_replace_brick\n\nAs glusterd_do_replace_brick() is spawned through gf_timer_call_after(),\nby the time it's called the event is freed, and the txn_id is lost.\nHence using a calloc-ed copy, which will be freed as a part of rb_ctx\ndict.\n\nChange-Id: I3e309fe1a7ba96ad1d1ce01f4d2aa18178f59244\nBUG: 1095097\nSigned-off-by: Avra Sengupta <asengupt@redhat.com>\nReviewed-on: http://review.gluster.org/7686\nReviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>\nTested-by: Gluster Build System <jenkins@build.gluster.com>\nReviewed-by: Kaushal M <kaushal@redhat.com>","distinct":false,"url":"https://api.github.com/repos/anoopcs9/glusterfs/commits/e80daecc3dd3023f010c785ff0e238fc92214477"},{"sha":"a4b622e0bd60a5e19e73f415a6a64aa6661a971a","author":{"email":"3d98f31eab06971051372b88e77259b2119ee764@redhat.com","name":"Pranith Kumar K"},"message":"mgmt/glusterd: Perform Pending quorum actions after Op\n\nChange-Id: I2bb67b5fb4a6f6dac892ef3206e7a79706018a6e\nBUG: 959986\nSigned-off-by: Pranith Kumar K <pkarampu@redhat.com>\nReviewed-on: http://review.gluster.org/4955\nTested-by: Gluster Build System <jenkins@build.gluster.com>\nReviewed-by: Kaushal M <kaushal@redhat.com>","distinct":false,"url":"https://api.github.com/repos/anoopcs9/glusterfs/commits/a4b622e0bd60a5e19e73f415a6a64aa6661a971a"},{"sha":"281d95cb7d53069158eae99392e9e7863c8850fd","author":{"email":"3d98f31eab06971051372b88e77259b2119ee764@redhat.com","name":"Pranith Kumar K"},"message":"mgmt/glusterd: Prevent spurious brick restarts\n\nChange-Id: I7ee5d18b926d6c31e3e4ea2f5fbe9050c8e1dee8\nBUG: 959986\nSigned-off-by: Pranith Kumar K <pkarampu@redhat.com>\nReviewed-on: http://review.gluster.org/4954\nTested-by: Gluster Build System <jenkins@build.gluster.com>\nReviewed-by: Kaushal M <kaushal@redhat.com>","distinct":false,"url":"https://api.github.com/repos/anoopcs9/glusterfs/commits/281d95cb7d53069158eae99392e9e7863c8850fd"},{"sha":"933f60796d69686a153659c7b178dbd1475f9cb6","author":{"email":"78a921d2249fa39da59d1342df10fbdfc586e02b@redhat.com","name":"Venky Shankar"},"message":"libgfchangelog: memory accounting intialization\n\nNeeded as memory accounting turned ON by default now.\nWithout this, GF_{CALLOC,MALLOC} calls assert.\n\nChange-Id: Ie54a6efb61871e70d4f7c796d9c86a867051e2e0\nBUG: 1094708\nSigned-off-by: Venky Shankar <vshankar@redhat.com>\nReviewed-on: http://review.gluster.org/7698\nReviewed-by: Kotresh HR <khiremat@redhat.com>","distinct":false,"url":"https://api.github.com/repos/anoopcs9/glusterfs/commits/933f60796d69686a153659c7b178dbd1475f9cb6"},{"sha":"1b042296ddc65f5eab9d6e5f1e30e353413d9bbb","author":{"email":"3d98f31eab06971051372b88e77259b2119ee764@redhat.com","name":"Pranith Kumar K"},"message":"cluster/afr: Remove stale index in self-heal codepath\n\nChange-Id: I635fc0fa955b33590f1c5b4dfec22d591ea8575c\nBUG: 1032894\nSigned-off-by: Pranith Kumar K <pkarampu@redhat.com>\nReviewed-on: http://review.gluster.org/6592\nTested-by: Gluster Build System <jenkins@build.gluster.com>\nReviewed-by: Anand Avati <avati@redhat.com>","distinct":false,"url":"https://api.github.com/repos/anoopcs9/glusterfs/commits/1b042296ddc65f5eab9d6e5f1e30e353413d9bbb"},{"sha":"75baf16c01b7cc09fbf14e3c9ecf447c3c793c5b","author":{"email":"ca019b8b0be1f5b5438ff00722db4c4ccf7beb28@redhat.com","name":"Vijay Bellur"},"message":"Update Maintainers to reflect recent changes\n\nChange-Id: I8dc3347d88942473810c2b4c9d52a69ecb6129e8\nBUG: 1040351\nSigned-off-by: Vijay Bellur <vbellur@redhat.com>\nReviewed-on: http://review.gluster.org/7689\nReviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>\nTested-by: Humble Devassy Chirammal <humble.devassy@gmail.com>","distinct":false,"url":"https://api.github.com/repos/anoopcs9/glusterfs/commits/75baf16c01b7cc09fbf14e3c9ecf447c3c793c5b"},{"sha":"4f8c7cc34dad6a963f70dfcf11e737fd44c31a42","author":{"email":"648737a4d5e8e7f3005f086c2dbed7bf1e0319c8@harshavardhana.net","name":"Harshavardhana"},"message":"runtime: Disable optimization for OSX versions < 10.9\n\nOptimization flags has led to segfaults at wrong locations\nthroughout gluster code for versions < 10.9\n\nAssuming this to be a compiler bug, disable optimization\nflags\n\nChange-Id: Ia2dc983dc5bb06935f03b68c07688ce41255d7da\nBUG: 1089172\nSigned-off-by: Harshavardhana <harsha@harshavardhana.net>\nReviewed-on: http://review.gluster.org/7656\nReviewed-by: Justin Clift <justin@gluster.org>\nTested-by: Justin Clift <justin@gluster.org>","distinct":false,"url":"https://api.github.com/repos/anoopcs9/glusterfs/commits/4f8c7cc34dad6a963f70dfcf11e737fd44c31a42"},{"sha":"065b91b4993f1ab0abc8b1db4d5745a6b58545b0","author":{"email":"36ab91862badf129e22a0765506a8b181227d4e1@redhat.com","name":"Vijaikumar M"},"message":"glusterd/snapshot: Add brick-count suffix for the LVM snapshot\n\nWhen there are more than one brick created from the same LVM volume\ngroup, there will be a conflict with the LVM snapshot name we use.\n\nSolution is to add a brick-count suffix to the LVM snapshot name\n\nChange-Id: I7258e69fe0b50e86b81c66ab1db523ab3c7cbae0\nBUG: 1091934\nSigned-off-by: Vijaikumar M <vmallika@redhat.com>\nReviewed-on: http://review.gluster.org/7581\nTested-by: Gluster Build System <jenkins@build.gluster.com>\nReviewed-by: Rajesh Joseph <rjoseph@redhat.com>\nReviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>\nTested-by: Krishnan Parthasarathi <kparthas@redhat.com>","distinct":false,"url":"https://api.github.com/repos/anoopcs9/glusterfs/commits/065b91b4993f1ab0abc8b1db4d5745a6b58545b0"},{"sha":"5dda1d4e00b8235656b7e4e8de35f599bf033148","author":{"email":"36ab91862badf129e22a0765506a8b181227d4e1@redhat.com","name":"Vijaikumar M"},"message":"glusterd/snapshot: Execute lvm snapshots in parallel\n\nBack-end LVM Snapshot is executed parallely as synop task\nThis helps is gaining performance when there are more bricks in a\nnode.\n\nThis patch also removes unwanted logs printed in snapshot cleanup\n\nChange-Id: I3174cb4547ebb670eca37a98eb9d75ecb0672a90\nBUG: 1061685\nSigned-off-by: Vijaikumar M <vmallika@redhat.com>\nReviewed-on: http://review.gluster.org/7461\nTested-by: Gluster Build System <jenkins@build.gluster.com>\nReviewed-by: Rajesh Joseph <rjoseph@redhat.com>\nReviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>\nTested-by: Krishnan Parthasarathi <kparthas@redhat.com>","distinct":false,"url":"https://api.github.com/repos/anoopcs9/glusterfs/commits/5dda1d4e00b8235656b7e4e8de35f599bf033148"},{"sha":"26043d1f8ed6892aca47abcb75cedfdc51e86a0a","author":{"email":"36ab91862badf129e22a0765506a8b181227d4e1@redhat.com","name":"Vijaikumar M"},"message":"glusterd/snapshot: Don't release big_lock before completing snapshot creation\n\nReleasing the big-lock can cause problem like deadlock or memory\ncorruption.\n\nSame happened with bug 1091926 where glusterd on node-2 entered a commit\nphase and released a big-lock.\n\nThe originator node received timeout for the commit phase and\ntriggered a post-validate cleanup to the node-2.\n\nNow node-2 continued to work with the object that are alreday cleaned-up\nand resulted in a crash.\n\nSolution is to not to release big-lock in the commit phase of snapshot\ncreation.\n\nChange-Id: I571194fdb0b0ecc91bd13f2a9fc92fe4338d14dc\nBUG: 1091926\nSigned-off-by: Vijaikumar M <vmallika@redhat.com>\nReviewed-on: http://review.gluster.org/7579\nTested-by: Gluster Build System <jenkins@build.gluster.com>\nReviewed-by: Rajesh Joseph <rjoseph@redhat.com>\nReviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>\nTested-by: Krishnan Parthasarathi <kparthas@redhat.com>","distinct":false,"url":"https://api.github.com/repos/anoopcs9/glusterfs/commits/26043d1f8ed6892aca47abcb75cedfdc51e86a0a"},{"sha":"d74c10603196a57c5fa033aaeb55f93f7ef7b4be","author":{"email":"b1fc68e1c6d4e38f3ef87e9c9d68c44de38b0c16@redhat.com","name":"Rajesh Joseph"},"message":"glusterd/snapshot: volume gets deleted if restore fails\n\nIf the restore command fails in pre-validate phase\nthen main volume gets deleted.\n\nFix: Perform cleanup only when pre-validate passes.\n\nChange-Id: I7128c8582c3dd166a5683babb7e136ad0b56f0ac\nBUG: 1061685\nSigned-off-by: Rajesh Joseph <rjoseph@redhat.com>\nReviewed-on: http://review.gluster.org/7665\nTested-by: Gluster Build System <jenkins@build.gluster.com>\nReviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>\nTested-by: Krishnan Parthasarathi <kparthas@redhat.com>","distinct":false,"url":"https://api.github.com/repos/anoopcs9/glusterfs/commits/d74c10603196a57c5fa033aaeb55f93f7ef7b4be"},{"sha":"26a4b5c98e9e50ace28a9bed97f04ecea262e11d","author":{"email":"ca630918676f465396be6c88fe8166e4d3e6bea8@redhat.com","name":"Raghavendra Bhat"},"message":"mgmt/glusterd: delete oldest snapshot upon exceeding soft-limit\n\nChange-Id: I2d6ebae3ced1910f2dee43eeb9fc430e9f31073f\nBUG: 1061685\nSigned-off-by: Raghavendra Bhat <raghavendra@redhat.com>\nReviewed-on: http://review.gluster.org/7587\nReviewed-by: Rajesh Joseph <rjoseph@redhat.com>\nReviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>\nTested-by: Krishnan Parthasarathi <kparthas@redhat.com>","distinct":false,"url":"https://api.github.com/repos/anoopcs9/glusterfs/commits/26a4b5c98e9e50ace28a9bed97f04ecea262e11d"},{"sha":"93129e862a2dde291ddbf22fe30d955b25da6059","author":{"email":"8c581b930d4e467db7caf29db13010a40a93b692@redhat.com","name":"Aravinda VK"},"message":"geo-rep: Loading libgfchangelog.so only while running geo-rep\n\nIn source install, libgfchangelog is installed in /usr/local/lib\nWhen glusterd runs /usr/local/libexec/glusterfs/python/gsyncd --version\nit fails to find library without LD_LIBRARY_PATH.\n\nThis patch avoids loading library when it is run from glusterd\nduring start.\n\nBUG: 1096026\nChange-Id: I59912227ac27ff4877d947a7c8f1fe2e8c5be06e\nSigned-off-by: Aravinda VK <avishwan@redhat.com>\nReviewed-on: http://review.gluster.org/7713\nReviewed-by: Kotresh HR <khiremat@redhat.com>\nReviewed-by: Venky Shankar <vshankar@redhat.com>\nTested-by: Venky Shankar <vshankar@redhat.com>","distinct":false,"url":"https://api.github.com/repos/anoopcs9/glusterfs/commits/93129e862a2dde291ddbf22fe30d955b25da6059"},{"sha":"65757e0f57f93103d87fdf9534c5ca25b66d14b7","author":{"email":"8c581b930d4e467db7caf29db13010a40a93b692@redhat.com","name":"Aravinda VK"},"message":"geo-rep: Changelog History consumption more fixes\n\nNumber of parallel threads to process changelog history\nis made configurable via sync_jobs\n\nChange-Id: Idcd8e655d9df540cfa48648b9e98af941f95e9d0\nSigned-off-by: Aravinda VK <avishwan@redhat.com>\nReviewed-on: http://review.gluster.org/7660\nReviewed-by: Venky Shankar <vshankar@redhat.com>\nTested-by: Venky Shankar <vshankar@redhat.com>","distinct":false,"url":"https://api.github.com/repos/anoopcs9/glusterfs/commits/65757e0f57f93103d87fdf9534c5ca25b66d14b7"},{"sha":"c7b0396f680863528248e6f5a162de47184b6c88","author":{"email":"8c581b930d4e467db7caf29db13010a40a93b692@redhat.com","name":"Aravinda VK"},"message":"geo-rep: Pause and Resume feature for geo-replication\n\nChangelog consumption/processing now happens in seperate process\ngroup than monitor. When monitor process group gets SIGSTOP all\nworker process, ssh, rsync will be paused except the changelog\nprocessing. When it gets SIGCONT it resumes its operation.\n\nChangelog agent runs as RepceServer, geo-rep worker communicates\nwith changelog agent using RepceClient.\n\nChange-Id: I35c333e4d8b13d03a7808aed601960eef23cfa04\nBUG: 1093602\nSigned-off-by: Venky Shankar <vshankar@redhat.com>\nSigned-off-by: Aravinda VK <avishwan@redhat.com>\nReviewed-on: http://review.gluster.org/7322","distinct":false,"url":"https://api.github.com/repos/anoopcs9/glusterfs/commits/c7b0396f680863528248e6f5a162de47184b6c88"},{"sha":"47c33dd27150039a6e5e3295eacd8d2d5a7e0ce0","author":{"email":"648737a4d5e8e7f3005f086c2dbed7bf1e0319c8@harshavardhana.net","name":"Harshavardhana"},"message":"tests: min-free-disk test was incomplete\n\n- use '%' when we mean it for clarity\n- in bash we need to evaluate counter decrements\n\nChange-Id: Ibd17126945e8a335fa2671d658a2e0c71049fd1e\nBUG: 874554\nSigned-off-by: Harshavardhana <harsha@harshavardhana.net>\nReviewed-on: http://review.gluster.org/7687\nTested-by: Gluster Build System <jenkins@build.gluster.com>\nReviewed-by: Raghavendra Talur <rtalur@redhat.com>\nReviewed-by: Vijay Bellur <vbellur@redhat.com>","distinct":false,"url":"https://api.github.com/repos/anoopcs9/glusterfs/commits/47c33dd27150039a6e5e3295eacd8d2d5a7e0ce0"},{"sha":"2fd499d148fc8865c77de8b2c73fe0b7e1737882","author":{"email":"7bda0c0ee7f47171cc808e9e60292cbc5d8140dd@redhat.com","name":"Niels de Vos"},"message":"rpc: implement server.manage-gids for group resolving on the bricks\n\nThe new volume option 'server.manage-gids' can be enabled in\nenvironments where a user belongs to more than the current absolute\nmaximum of 93 groups. This option triggers the following behavior:\n\n1. The AUTH_GLUSTERFS structure sent by GlusterFS clients (fuse, nfs or\n   libgfapi) will contain only one (1) auxiliary group, instead of\n   a full list. This reduces network usage and prevents problems in\n   encoding the AUTH_GLUSTERFS structure which should fit in 400 bytes.\n2. The single group in the RPC Calls received by the server is replaced\n   by resolving the groups server-side. Permission checks and similar in\n   lower xlators are applied against the full list of groups where the\n   user belongs to, and not the single auxiliary group that the client\n   sent.\n\nChange-Id: I9e540de13e3022f8b63ff893ecba511129a47b91\nBUG: 1053579\nSigned-off-by: Niels de Vos <ndevos@redhat.com>\nReviewed-on: http://review.gluster.org/7501\nTested-by: Gluster Build System <jenkins@build.gluster.com>\nReviewed-by: Santosh Pradhan <spradhan@redhat.com>\nReviewed-by: Harshavardhana <harsha@harshavardhana.net>\nReviewed-by: Anand Avati <avati@redhat.com>","distinct":false,"url":"https://api.github.com/repos/anoopcs9/glusterfs/commits/2fd499d148fc8865c77de8b2c73fe0b7e1737882"},{"sha":"5adb10b9ac1c634334f29732e062b12d747ae8c5","author":{"email":"d83894965d597d87a548ff845500589a4a6a54e9@redhat.com","name":"Soumya Koduri"},"message":"libgfapi:  Added support to fetch volume info from glusterd and store in glfs object.\n\nDefined new APIs in the libgfapi module, given a glfs object,\n * to send handshake RPC call to glusterd process to fetch UUID of the volume\n * store it in the glusterfs_context linked to the glfs object.\n * to parse UUID from its cannonical string format into 16-byte array\n   before sending it to the libgfapi users.\n\nDefined a RPC call in glusterd which can be used to query volume related\ninfo by other processes using 'clnt_handshake_procs'.\n\nNote - Currently this RPC call to glusterd process is used only to fetch UUID.\nBut it can be extended to get other volume related structures as well.\n\nIn addition to the above, defined a new variable to keep track of such handshake\nRPCs still in progress to make sure all the corresponding RPC callbacks have been\nprocessed before libgfapi returns the glfs object initialized.\n\nAlso bumping up the GFAPI current version number since there is a new API\n\"glfs_get_volume_id\" defined and exposed by libgfapi as part of these changes.\n\nChange-Id: I303f76d7177d32d25bdb301b1dbcf5cd73f42807\nBUG: 1090363\nSigned-off-by: Soumya Koduri <skoduri@redhat.com>\nReviewed-on: http://review.gluster.org/7218\nReviewed-by: Anand Avati <avati@redhat.com>\nReviewed-by: Harshavardhana <harsha@harshavardhana.net>\nTested-by: Gluster Build System <jenkins@build.gluster.com>\nReviewed-by: Vijay Bellur <vbellur@redhat.com>","distinct":false,"url":"https://api.github.com/repos/anoopcs9/glusterfs/commits/5adb10b9ac1c634334f29732e062b12d747ae8c5"}]}