Perl 6 - the future is here, just unevenly distributed

IRC log for #gluster-dev, 2016-09-01

| Channels | #gluster-dev index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
01:39 EinstCrazy joined #gluster-dev
01:39 EinstCrazy joined #gluster-dev
01:48 ilbot3 joined #gluster-dev
01:48 Topic for #gluster-dev is now Gluster Development Channel - http://gluster.org | For general chat go to #gluster | Patches - http://review.gluster.org/ | Channel Logs - https://botbot.me/freenode/gluster-dev/ & http://irclog.perlgeek.de/gluster-dev/
01:57 dlambrig joined #gluster-dev
02:02 jtc joined #gluster-dev
02:04 EinstCra_ joined #gluster-dev
02:19 spalai joined #gluster-dev
02:32 jtc joined #gluster-dev
02:37 EinstCrazy joined #gluster-dev
02:40 aspandey joined #gluster-dev
02:45 pranithk1 joined #gluster-dev
03:02 spalai left #gluster-dev
03:05 kdhananjay joined #gluster-dev
03:16 poornima joined #gluster-dev
03:17 poornima Can any maintainer merge a patch in io-stats, there are acks and all the comments have been addressed. http://review.gluster.org/#/c/15193/ ? Thanks
03:32 magrawal joined #gluster-dev
03:46 itisravi joined #gluster-dev
03:54 itisravi joined #gluster-dev
03:57 sanoj joined #gluster-dev
04:07 atinm joined #gluster-dev
04:08 kshlm joined #gluster-dev
04:10 nbalacha joined #gluster-dev
04:13 aspandey joined #gluster-dev
04:19 riyas joined #gluster-dev
04:28 shubhendu joined #gluster-dev
04:36 aspandey_ joined #gluster-dev
04:37 glustin joined #gluster-dev
04:38 loadtheacc joined #gluster-dev
04:43 ndk_ joined #gluster-dev
04:45 jiffin joined #gluster-dev
04:46 ashiq joined #gluster-dev
04:55 ppai joined #gluster-dev
05:03 karthik_ joined #gluster-dev
05:04 nbalacha joined #gluster-dev
05:05 ndarshan joined #gluster-dev
05:06 PotatoGim joined #gluster-dev
05:08 ndarshan joined #gluster-dev
05:12 poornima joined #gluster-dev
05:12 poornima pranithk1++
05:12 glusterbot poornima: pranithk1's karma is now 6
05:14 mchangir joined #gluster-dev
05:15 hgowtham joined #gluster-dev
05:22 Bhaskarakiran joined #gluster-dev
05:23 prasanth joined #gluster-dev
05:25 an_ joined #gluster-dev
05:30 bkunal joined #gluster-dev
05:36 an__ joined #gluster-dev
05:38 kshlm joined #gluster-dev
05:42 spalai joined #gluster-dev
05:43 spalai left #gluster-dev
05:43 spalai1 joined #gluster-dev
05:44 skoduri joined #gluster-dev
05:44 an_ joined #gluster-dev
05:48 ankitraj joined #gluster-dev
05:48 jiffin joined #gluster-dev
05:52 aravindavk joined #gluster-dev
05:58 msvbhat joined #gluster-dev
05:59 an_ joined #gluster-dev
06:04 Saravanakmr joined #gluster-dev
06:06 an_ joined #gluster-dev
06:10 spalai joined #gluster-dev
06:10 devyani7 joined #gluster-dev
06:12 kshlm aravindavk, Let's talk here.
06:15 aravindavk kshlm: thanks. will try those steps and get back to you
06:18 pranithk1 joined #gluster-dev
06:19 jiffin joined #gluster-dev
06:22 spalai joined #gluster-dev
06:23 aravindavk kshlm: pranithk1 is trying with the changes
06:27 post-factum pranithk1: around?
06:28 pranithk1 post-factum: yes
06:28 post-factum pranithk1: hello. need some help with valgrind if you have some time for me
06:30 pranithk1 post-factum: Sorry, today is kinda bad because of the branching...
06:30 aspandey joined #gluster-dev
06:30 post-factum pranithk1: oh okay then
06:30 pranithk1 kshlm: what should be done for github in this case?
06:31 pranithk1 kshlm: It will automatically happen?
06:31 kshlm Yup.You don't need to do anything.
06:32 devyani7 joined #gluster-dev
06:35 aravindavk_ joined #gluster-dev
06:35 pranithk1 aravindavk: aravindavk_: I pushed 3.9 branch, could you do git pull
06:36 aravindavk_ pranithk1: checking
06:37 aravindavk_ pranithk1: I am able to pull
06:37 pranithk1 aravindavk_: You are able to see release-3.9?
06:37 aravindavk_ pranithk1++ kshlm++
06:37 glusterbot aravindavk_: pranithk1's karma is now 7
06:37 glusterbot aravindavk_: kshlm's karma is now 110
06:37 Muthu_ joined #gluster-dev
06:37 aravindavk_ pranithk1: yes
06:39 pranithk1 aravindavk_: I think github thing also needs to be done
06:39 pranithk1 aravindavk_: May be niels knows about it
06:40 aravindavk_ pranithk1: release-3.9 is visible in github too https://github.com/gluster/glusterfs/tree/release-3.9
06:40 pranithk1 aravindavk_: oh! really? let me check :-)
06:41 pranithk1 aravindavk_: seems good to me. I guess we are done :-)
06:43 hgowtham joined #gluster-dev
06:43 kshlm pranithk1, You should also tag master with `3.10-dev`
06:45 atinm joined #gluster-dev
06:45 pranithk1 kshlm: didn't get that part
06:45 pranithk1 kshlm: sorry?
06:45 pranithk1 kshlm: You mean from where we branched it off from on master? before the rfc commit
06:45 kshlm Yup.
06:47 pranithk1 kshlm: let me try that
06:48 pranithk1 kshlm: I see that older tags have 'v' in front of it i.e. v3.10-dev may be?
06:50 kshlm pranithk1, Before pushing, could you check if the tag also affects release-3.9?
06:50 pranithk1 kshlm: I didn't push
06:51 kshlm I think that release-3.9 will also get the tag, because it's just master+1 commit now.
06:52 pranithk1 kshlm: hmm... how do we check if the tag affects release-3.9?
06:52 pranithk1 kshlm: I am not sure how to do that
06:53 kshlm git log --tags --oneline release-3.9
06:54 kshlm That doesn't work.
06:55 kshlm `git log --oneline --decorate release-3.9`
06:56 pranithk1 kshlm: checking
06:56 skoduri joined #gluster-dev
06:57 pranithk1 kshlm: But we should have the tag as 'v3.10-dev' right? with the 'v' at the front?
06:57 kshlm Yeah.
06:57 pranithk1 kshlm: cool
06:58 pranithk1 kshlm: there is no '-' either? so may be v3.10dev?
06:58 pranithk1 kshlm: I mean for earlier tags
06:58 kshlm Yup.
06:58 kshlm But hold on pushing the tags.
06:59 pranithk1 kshlm: yeah
06:59 kshlm Okay. So I just checked what ndevos did for 3.8.
07:00 pranithk1 kshlm: 'c544005 (release-3.9) Changed branch to release-3.9
07:00 pranithk1 ee0d8ca (HEAD -> tagging, tag: v3.10dev, origin/master, origin/HEAD) io-stats: Add stats for upcall notifications
07:00 pranithk1 '
07:00 pranithk1 kshlm: it has it
07:00 kshlm He tagged the rfc change script v3.8rc0
07:00 aravindavk joined #gluster-dev
07:00 kshlm s/script/commit/
07:00 pranithk1 kshlm: okay got it, I can do that
07:01 kshlm So you need to the current release-3.9 head v3.9rc0
07:01 ashiq joined #gluster-dev
07:01 kshlm and then tag current head of master v3.10dev
07:01 pranithk1 kshlm: okay, let me do that
07:01 kshlm Remeber to use annotated tags.
07:03 pranithk1 kshlm: I still see them
07:03 pranithk1 kshlm: c544005 (tag: v3.9rc0, release-3.9) Changed branch to release-3.9
07:03 pranithk1 ee0d8ca (HEAD -> tagging, tag: v3.10dev, origin/master, origin/HEAD) io-stats: Add stats for upcall notifications
07:04 pranithk1 kshlm: I didn't use annotated tags, but I can change that, won't be pushing it
07:04 kshlm Now it doesn't matter. The latest tag on release-3.9 is v3.9rc0, which will be picked when building.
07:05 pranithk1 kshlm: ah! got it
07:05 asengupt joined #gluster-dev
07:08 k4n0 joined #gluster-dev
07:09 nigelb pranithk1 / kshlm - If this isn't documented, it's worth writing up.
07:09 kshlm nigelb, Yup.
07:09 kshlm pranithk1, aravindavk, Could one of you document everything you did?
07:10 pranithk1 kshlm: "c544005 (tag: v3.9rc0, release-3.9) Changed branch to release-3.9
07:10 pranithk1 ee0d8ca (HEAD -> tagging, tag: v3.10dev, origin/master, origin/HEAD) io-stats: Add stats for upcall notifications"
07:10 pranithk1 kshlm: 12:40:18 :( ⚡ git show v3.9rc0
07:10 pranithk1 tag v3.9rc0
07:10 pranithk1 Tagger: Pranith Kumar K <pkarampu@redhat.com>
07:10 pranithk1 Date:   Thu Sep 1 12:38:43 2016 +0530
07:10 pranithk1 Release Candidate 0 for GlusterFS 3.9
07:11 pranithk1 kshlm: tag v3.10dev
07:11 pranithk1 Tagger: Pranith Kumar K <pkarampu@redhat.com>
07:11 pranithk1 Date:   Thu Sep 1 12:39:41 2016 +0530
07:11 pranithk1 Work in progress GlusterFS 3.10 (or 4.0)
07:11 pranithk1 kshlm: looks okay right?
07:13 rastar joined #gluster-dev
07:19 pranithk1 kshlm: done
07:19 an_ joined #gluster-dev
07:19 pranithk1 aravindavk: Could you also check these tags once?
07:19 msvbhat joined #gluster-dev
07:19 atinm joined #gluster-dev
07:22 pranithk1 atinm: branching is done
07:23 aravindavk pranithk1: ok
07:27 pranithk1 aravindavk: Have a meeting in 5:30 hours, will sleep now. We need to discuss about the feature patches that didn't make it to the branch tomorrow sometime
07:28 pranithk1 aravindavk: have a nice day cya
07:40 an_ joined #gluster-dev
07:41 aspandey joined #gluster-dev
07:57 msvbhat joined #gluster-dev
08:05 an_ joined #gluster-dev
08:16 an_ joined #gluster-dev
08:18 aspandey xavih, ping
08:18 glusterbot aspandey: Please don't naked ping. http://blogs.gnome.org/markmc/2014/02/20/naked-pings/
08:18 xavih aspandey: hi :)
08:19 aspandey xavih: after long time :)
08:19 aspandey xavih: So I have modified one patch and want to discuss something..
08:20 xavih aspandey: yes, sorry :(. I've been completely disconected these holidays...
08:20 aspandey xavih: That's fine :)
08:20 xavih aspandey: sure. I've seen some changes, but I'm still reading emails...
08:20 xavih aspandey: what do you want to discuss ?
08:21 aspandey xavih: okk. You can review this patch whenever you have time http://review.gluster.org/#/c/13733/
08:21 aspandey xavih: I just want to talk about one point..
08:24 aspandey xavih: So in ec_update_size_version_done, at the end we are checking if fop->parent->id is flush or not...accordingly we are unlocking the lock...
08:24 xavih aspandey: yes
08:25 xavih aspandey: ec_update_size_version() can be called from flush, fsync and some other, but it must not remove any taken locks
08:25 aspandey xavih: right.
08:26 aspandey xavih: Now my point is that can we not just check lock->release flag? if lock->release is true we unlock it else don't...?
08:28 aspandey xavih: there could be diff cases...
08:29 xavih aspandey: I think we cannot. lock->release will be set as soon as a condition is detected like requires immediate release of the lock (like lock contention). However pending operations must be completed before the lock is really released
08:29 xavih aspandey: if one of these operations is a flush and we only check lock->release, the lock will be released but it shouldn't
08:30 xavih aspandey: it should wait until all other pending operations have completed
08:32 aspandey xavih: hmmm ..thinking..
08:33 aspandey xavih: Ok let me tell you what is happening...
08:35 aspandey xavih: As you remember that for update fop's we decided to set dirty flag in get_size_version and UNSET it while unlocking... No when we touch a file, at the time of unlocking a lock on that file ctx->dirty is 1, now it will call update_info which will call update_size_version
08:36 aspandey xavih: but in update_size-version_done, it will not call ec_unlock_lock
08:39 an_ joined #gluster-dev
08:40 aravindavk ping nigelb
08:41 hgowtham joined #gluster-dev
08:41 nigelb aravindavk: hey, what's up?
08:41 aravindavk nigelb: how to add new version in Bugzilla?
08:42 nigelb Email bugzilla-requests@redhat.com (I think)
08:42 nigelb kshlm: ^ Unless you have permissions?
08:42 kshlm Emailing is the way.
08:43 kshlm aravindavk, Just so you know, for 3.9 just ask for a single 3.9 version.
08:43 kshlm Not 3.9.z
08:43 aravindavk kshlm: okay
08:43 aravindavk kshlm, nigelb thanks
08:44 ramky joined #gluster-dev
08:46 xavih aspandey: let me look at the code... the problem arises if the fop that creates the lock is a flush ?
08:47 aspandey xavih: yes..
08:50 aspandey xavih, think about simple "touch file" it is taking lock on parent then creating it and then setting xattr on file and flush....and what I am seeing is that the final unlock call from ec_lock_timer_del is coming with flush fop..
08:59 xavih aspandey: I think I see the problem. What I'm not so sure is what has changed to reveal it now. I think this wasn't happening before...
09:00 aspandey xavih: ok..
09:00 Saravanakmr joined #gluster-dev
09:00 pkalever joined #gluster-dev
09:02 xavih aspandey: anyway, maybe we can write it better
09:03 spalai joined #gluster-dev
09:03 shaunm joined #gluster-dev
09:03 rjoseph joined #gluster-dev
09:03 gvandeweyer joined #gluster-dev
09:04 xavih aspandey: what do you think about adding an additional argument to ec_update_into() and ec_update_size_version() to tell them if the lock should be unlocked ?
09:04 lkoranda joined #gluster-dev
09:05 xavih aspandey: when called from ec_unlock_now(), it will be true. When called from ec_flush_size_version() it will be false
09:05 xavih aspandey: this removes any dependency on the fop id.
09:08 aspandey xavih: I also thought about that...But I was thinking that I just bypassing something.
09:09 aspandey xavih: let me do this and think about it...
09:09 xavih aspandey: I think it's ok. ec_flush_size_version() is only called from flush, fsync and fsyncdir
09:11 xavih aspandey: in these cases, it's called from the DISPATCH state. Later the lock will be released, if needed, at UNLOCK state or when the timeout expires
09:11 xavih aspandey: but this time, the call will go through ec_unlock_now()
09:12 aspandey xavih: hmmmm..
09:12 an_ joined #gluster-dev
09:12 aspandey xavih: okk...
09:13 ankitraj joined #gluster-dev
09:18 aspandey xavih: I will make these changes and will see if it is solving the issue and not creating any new...
09:22 ira joined #gluster-dev
09:26 post-factum kshlm++ for .15
09:26 glusterbot post-factum: kshlm's karma is now 111
09:40 an_ joined #gluster-dev
09:40 decay joined #gluster-dev
09:52 itisravi joined #gluster-dev
09:52 nbalacha poornima, got a minute?
09:56 an_ joined #gluster-dev
09:59 an_ joined #gluster-dev
10:04 k4n0 joined #gluster-dev
10:05 poornima nbalacha, sure tell me
10:05 nbalacha poornima, I would like to close https://bugzilla.redhat.com/show_bug.cgi?id=1087407 as WontFix
10:05 glusterbot Bug 1087407: low, unspecified, ---, rgowdapp, POST , DHT: Setfattr doesn't take rebalance into consideration
10:05 nbalacha is that ok with you?
10:06 poornima nbalacha, sure, go ahead
10:07 nbalacha poornima, thanks
10:07 poornima nbalacha, wc
10:08 hgowtham joined #gluster-dev
10:09 ndarshan joined #gluster-dev
10:09 msvbhat joined #gluster-dev
10:25 misc so, everybody is still ok with the reboot tonight ?
10:26 post-factum ye
10:28 nigelb yep.
10:32 shyam joined #gluster-dev
10:44 hchiramm joined #gluster-dev
11:11 kkeithley @later tell Muthu_ I'm east coast USA (EDT) time zone. I'm hardly ever on-line at 2AM. (I don't want you to think I'm ignoring you)
11:11 glusterbot kkeithley: The operation succeeded.
11:51 an_ joined #gluster-dev
12:04 k4n0 joined #gluster-dev
12:09 ramky joined #gluster-dev
12:37 lpabon joined #gluster-dev
12:39 spalai left #gluster-dev
12:56 jiffin1 joined #gluster-dev
12:58 kdhananjay1 joined #gluster-dev
13:11 ashiq joined #gluster-dev
13:15 rastar joined #gluster-dev
13:29 lkoranda joined #gluster-dev
13:31 baojg joined #gluster-dev
13:37 an_ joined #gluster-dev
13:37 shubhendu joined #gluster-dev
13:39 kshlm joined #gluster-dev
13:42 aravindavk joined #gluster-dev
13:44 ndarshan joined #gluster-dev
13:49 rastar joined #gluster-dev
13:51 msvbhat joined #gluster-dev
13:53 pranithk1 joined #gluster-dev
14:14 an_ joined #gluster-dev
14:16 shyam joined #gluster-dev
14:21 skoduri joined #gluster-dev
14:31 ashiq joined #gluster-dev
14:32 amye joined #gluster-dev
14:33 k4n0 joined #gluster-dev
14:41 [o__o] joined #gluster-dev
14:42 shaunm joined #gluster-dev
14:57 riyas joined #gluster-dev
15:04 k4n0 joined #gluster-dev
15:14 wushudoin joined #gluster-dev
15:39 mchangir joined #gluster-dev
15:42 baojg joined #gluster-dev
15:52 Bhaskarakiran joined #gluster-dev
15:56 glusterbot joined #gluster-dev
15:58 mchangir joined #gluster-dev
16:09 skoduri joined #gluster-dev
16:11 hchiramm joined #gluster-dev
16:11 jiffin joined #gluster-dev
16:26 jiffin joined #gluster-dev
16:27 ndarshan joined #gluster-dev
16:39 jiffin joined #gluster-dev
16:45 glustin joined #gluster-dev
17:04 shyam joined #gluster-dev
17:23 msvbhat joined #gluster-dev
17:38 rafi joined #gluster-dev
18:11 msvbhat joined #gluster-dev
18:22 nigelb misc: all well with the restart?
18:31 misc nigelb: not done yet, was in meeting and then decided to go home and lunch before doing it
18:32 nigelb aha :)
18:32 misc (and sill not home yet, meeting until 20h)
18:33 misc I should have planned that better, as I know that I have a ton of meeting at that timeslot :/
18:34 nigelb misc: If you want to abort and try Monday your time, that works too (it's a holiday in BLR and US I think)
18:34 misc nigelb: nope, I am on PTO on monday
18:34 nigelb hahaha, everyone is away on monday :)
18:34 nigelb I should make sure I don't accidentally work.
18:34 misc well, I am sure I could do it on monday, but I am travelling
18:35 nigelb Don't work on your PTO! :)
18:35 misc I will likely just do ansible stuff, 10h of train is a long time :)
18:35 nigelb Damn, I love train journeys.
18:36 misc come to berlin with a train, you will change your mind :)
18:36 misc 20 days accross Russia
18:37 nigelb there's someone who did London to Singapore on a train.
18:38 misc Fineas Fog ?
18:38 post-factum haha
18:38 misc Phileas Fogg in fact
18:39 misc but if I could be sure to be able to work from the train, I would try it
18:39 spalai joined #gluster-dev
18:39 spalai left #gluster-dev
18:52 misc nigelb: so I put jenkins in "almost about to restart" mode, waiting on last job while I cook
18:59 rafi joined #gluster-dev
19:28 kkeithley joined #gluster-dev
20:02 glustin joined #gluster-dev
20:27 misc so only 3 jobs waiting
20:27 misc (I had time to wash my dishes, cook, eat, and wash again (in theory))
20:36 shyam joined #gluster-dev
20:53 misc 2 jobs :
20:53 misc !
20:55 kkeithley mine? kill them
20:57 post-factum pew-pew
21:01 k4n0 joined #gluster-dev
21:12 shyam joined #gluster-dev
21:49 misc so stopping jenkins and gerrit
21:49 misc for upgrade
21:55 ashiq joined #gluster-dev
21:59 misc and of course, unexpected issue appear
22:21 * misc do not understand why gerrit still boot on xen despites having been xenectomied
22:33 hagarth joined #gluster-dev
22:43 jobewan joined #gluster-dev
22:56 misc so gerrit is back
22:58 misc and for some weird reason, jenkins is not
22:58 misc (but I am on it)
23:03 misc grmblblbl
23:03 misc so jenkins didn't restart because network misbehaved (and didn't put the DNS in resolv.conf)
23:03 misc so this broke both jenkins and httpd
23:04 misc and of course, jenkins did forgot about the jobs in queue
23:04 misc nigelb: we need to discuss this tomorrow, I took some notes :)
23:39 shyam joined #gluster-dev

| Channels | #gluster-dev index | Today | | Search | Google Search | Plain-Text | summary