Re: Next v3.6 maint release suggested commits

[Humble Devassy Chirammal <humble.devassy@xxxxxxxxx>]

Thanks !!
Ccing 3.6.X release maintainer to make sure he is not missing this mail.

--Humble

On Fri, Sep 11, 2015 at 1:30 AM, Richard Wareing <rwareing@xxxxxx> wrote:

Greetings,

Just a heads up, there's a very nasty deadlock bug w/ multi-core e-poll in v3.6.x (latest branch) which appear to be due to DHT doing naughty things (like racing among other things).  So to fix these issues we had to pull in these (trivial cherry-pick) commits from master:

565ef0d826b356d188028410575da1f0fa9416b7

5a0aced9802d12f45cebf1b318e20676395570f9

b387c485c069c201ddabebe00c7176f960f4be32

2691a650f94ed9f82ecb8dda5d9b12f52147dc51

532566802b58d847d1ff1818ea857b583049ee76

50a92b2d72a43a940b0e38340d161fa7687a7104

df83769d4c6c6bb13df70751640b2a90af0064d7

9f8b4c2ef3523f91213a00edec863f322e92a6d5

68dfe137c7dfa08fb601257309f3db7e3ce6e4e8

e57a5eef4ea0da579986e9b61fec47a50ddf2b8a

2a3b7086957b095a5bbb5325aab0f765496e8491

393de0d7fd4309f4262a8747183f164e8f6d23c1

48aa51d49800bafbad5825165d4798cbbe592f5a

4fcf231aac51668742114320068b1570cee75667

8ac26cf2302dc452d7448a769b6b117dbdaaf05c

40da6554acabedebc2259a8c867159e41e1079c2

39bbf0ed97c3a1e8bf2966b2561f964013cde606

20a014332504efbc0204a591cad257abb167fce7

83b65187148e1dd145752c61660b8e5902e9a94f

83b65187148e1dd145752c61660b8e5902e9a94f

d60943ff2f6d58c129a66308f29986b471762210

6588d8f2a8975f032cb1567eef5ed35e5f992357

4ac9399be4f620abdaeee1054a48458c8238b907

a7e30beef3ab41985e7435dc1a90cde30e07dc47

(yes this is a lot of commits...but it fixes a lot of brokenness :) ).

So for the next maintenance release it might be wise to include these fixes to better the experience for v3.6.x users out there who do not maintain their own builds.  Without these multi-core epoll under high load prone to deadlocks (repro'able by rsync'ing [rsync -avR --inplace] a 100k or so small files from one tmpfs mount to another tmpfs backed GFS cluster on a development/test machine).  Not sure if it's worth filing a bug report since the issue has clearly been fixed in newer releases.

Richard

_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-devel

_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-devel