Perl 6 - the future is here, just unevenly distributed

IRC log for #gluster-dev, 2014-10-01

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

All times shown according to UTC.

Time Nick Message
01:47 ilbot3 joined #gluster-dev
01:47 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/
02:22 jobewan joined #gluster-dev
02:34 kdhananjay joined #gluster-dev
03:08 kdhananjay joined #gluster-dev
03:14 bharata-rao joined #gluster-dev
03:42 spandit joined #gluster-dev
03:48 itisravi joined #gluster-dev
04:08 jobewan joined #gluster-dev
04:29 kanagaraj joined #gluster-dev
04:32 anoopcs joined #gluster-dev
04:39 soumya joined #gluster-dev
04:42 Rafi_kc joined #gluster-dev
04:43 rafi1 joined #gluster-dev
04:45 pranithk joined #gluster-dev
04:52 kshlm joined #gluster-dev
05:19 soumya joined #gluster-dev
05:21 Gaurav_ joined #gluster-dev
05:23 Humble JustinClift, pong.. sorry .. missed ur ping yesterday
05:33 aravindavk joined #gluster-dev
05:36 hagarth joined #gluster-dev
05:47 soumya joined #gluster-dev
06:05 soumya joined #gluster-dev
06:07 raghu joined #gluster-dev
06:09 pranithk ndevos: did you get a chance to check mail about http://review.gluster.com/8757
06:42 nthomas_ joined #gluster-dev
06:42 pranithk joined #gluster-dev
06:47 pranithk ndevos: Sorry got disconnected in the middle. Did you respond to my msg
06:52 hagarth pranithk: no, he hasn't
07:00 pranithk hagarth: :-(
07:01 ws2k3 http://www.gluster.org/docs/index.php/Gluster​FS_1.3.1_-_64_Bricks_Aggregated_I/O_Benchmark is it possible to repair that link ?
07:01 ndevos pranithk: I tend to get online at 9:00 CEST (now), pinging me earlier may work, but not that often :)
07:02 pranithk ndevos: I am waiting for you from morning IST :-). Please take a look at that patch and merge if possible.
07:02 ndevos pranithk: looking at it already :)
07:02 pranithk ndevos: great! thanks a lot
07:02 hagarth pranithk: it is still early in Amsterdam :)
07:02 hagarth ndevos++
07:03 pranithk hagarth: oh!
07:04 hagarth pranithk: most days I would be badly looking for a cup of coffee around this time in Amsterdam ;)
07:04 pranithk hagarth: hehe :-)
07:05 pranithk hagarth: I never understood this coffee business people talk about. I am up and ready to go after a good nights sleep almost any day.
07:06 hagarth ws2k3: checking, if we have a ready link to access that page
07:06 hagarth pranithk: get drinking coffee, then you'll understand :)
07:06 ndevos pranithk: http://review.gluster.org/#/c/8757/2​/xlators/cluster/afr/src/afr-common.c line 4396 - is that if-statement really meant like that?
07:06 pranithk ndevos: checking
07:07 ndevos and yes, this is definitely something for what I need more coffee to understand it...
07:08 pranithk ndevos: I didn't understand the problem...
07:08 pranithk ndevos: what is the doubt in the conditional?
07:08 ndevos pranithk: this one: "if (!priv->child_up[i])"
07:09 ndevos in that case there is a continue, right, otherwise afr_proactive_self_heal() gets called
07:09 lalatenduM joined #gluster-dev
07:09 pranithk ndevos: goal is to call proactive self-heal for the ones where priv->child_up[i] is set
07:09 kdhananjay pranithk: i had a question
07:10 ndevos pranithk: ah, right, yes!
07:10 kdhananjay pranithk: priv->child_up[i] being "TRUE" could mean that it is either 1 or -1?
07:10 ndevos but why the ! in the if, and not just call afr_proactive_self_heal() if priv->child_up[i] is set
07:10 pranithk ndevos: Initially I wrote it as for (...); if (priv->child_up[i]) proactive_self_heal. but since it is exceeding 80 column width I changed it like that...
07:11 pranithk kdhananjay: by that time priv->child_up[i] can never be -1
07:11 ndevos oh no!, use smaller names for your funktions :D
07:11 pranithk ndevos: problem is because of (void*)(long)
07:12 kdhananjay pranithk: Why not? Because it is true that AFR hasn't heard from all of its children yet
07:12 pranithk kdhananjay: it is inside if (have_heard_from_all && priv->shd.iamshd) i.e. it just heard from everybody
07:12 ndevos heard != up ?
07:13 pranithk ndevos: it could be up/down
07:13 kdhananjay Ah yes of course. :D Just panicked for a second. :D. Thanks for the clarification, pranithk. :)
07:13 ndevos ah, ok
07:13 ndevos with that it definitely makes more sense to me
07:14 bharata_ joined #gluster-dev
07:14 ndevos pranithk: done, you can start backporting now
07:15 pranithk ndevos: already backported, just waiting for you to merge. kdhananjay did a fab job finding bugs yesterday for this one
07:15 pranithk ndevos++
07:15 pranithk kdhananjay++
07:15 ndevos pranithk: nice!
07:15 pranithk damn, what happened to bot?
07:15 hagarth unfortunately, glusterbot is MIA
07:15 lalatenduM Humble, are you working on d.g.o for beta3
07:15 ndevos its still early for glusterbot too
07:15 Humble lalatenduM, yes
07:15 pranithk ndevos: oh come on! its a bot :-D
07:16 ndevos pranithk: btw, in the triage/assigning of bugs, would a RSS-feed help to get notifications?
07:16 pranithk ndevos: I'll tell you how it used to work when we were just gluster.
07:16 Humble the dist-git spec was already in .4 version , I think kaleb commited it
07:16 Humble lalatenduM, ^^
07:17 pranithk ndevos: each component had owner. When the bug is raised against some component the corresponding owner used to take care of it.
07:17 Humble so I am tagging .5 for beta3
07:17 ndevos pranithk: okay, that is simple enough
07:17 pranithk ndevos: Now there are multiple people working on same component. So the owner may have to also do the extra job of assigning bugs to others
07:18 ndevos pranithk: yes, and the owner is a SPOF
07:18 lalatenduM Humble, I committed it
07:18 pranithk ndevos: The only extra work is to classify bugs to different components
07:18 pranithk ndevos: SPOF/
07:18 pranithk ndevos: SPOF means?
07:18 ndevos pranithk: Single Point Of Failure
07:19 lalatenduM Humble, .5 'should be ok, actually I had done .4 for beta3
07:19 Humble lalatenduM, the last changelogs are from kaleb wrt psmis
07:19 Humble lalatenduM, that was not needed..
07:19 ndevos pranithk: in those last three (?) years, the gluster sources and all have grown (I think and hope)
07:19 Humble because beta2 had ".3"
07:20 Humble any way it should not harm..
07:20 ndevos pranithk: I doubt we can have a component owner that triages and re-assigns new bugs - there are just too many
07:21 * ndevos has a difficulty to keep up with the NFS bugs, and that seems to be a less active coponent
07:23 lalatenduM Humble, let me know if I can help, I little late for work today so saw your mail sometime back
07:24 Humble I started today morning .. sure..
07:24 pranithk ndevos: I just sent a mail giving the URL to others in the team and one of the bugs Ravi took because he worked on a similar issue. I didn't even look at the bugs completely
07:25 pranithk ndevos: Just by looking at the bug one would get a fair idea is my feeling
07:25 ndevos pranithk: if you have a good bug report yes, sometimes there is just very little info in it :-/
07:27 pranithk ndevos: I agree. But still you need people with expertise in that component looking at them, right?
07:27 pranithk ndevos: more so in those cases
07:28 pranithk ndevos: I think in RHEL they have a mailing list as the assignee instead of person in the beginning then one person takes it.
07:28 pranithk ndevos: I saw it for fs team at least. Some bug bfoster was working on..
07:30 ndevos pranithk: yes, in RHEL it depends on the component - but RHEL does not (very) actively triage/work on bugs that were filed by community members
07:31 hagarth ws2k3: that is a very old page and has been marked for deletion
07:31 pranithk ndevos: okay what do you have in mind?
07:31 hagarth ws2k3: rather has been deleted now - http://gluster.org/community/docume​ntation/index.php/GlusterFS_1.3.1_-​_64_Bricks_Aggregated_I/O_Benchmark
07:32 ndevos pranithk: for RHEL bugs, there is a program manager responsible for approving bugs to get fixed (sets ACKs), that is not done by developers - or rarely
07:32 ws2k3 hagarth ah that to bad
07:33 ndevos pranithk: I hope we can get community members to help us triage bugs, and developers should somehow keep track of triaged bugs and assign them to themselves
07:33 pranithk ndevos: agree.
07:34 hagarth ndevos: I am still working on my AI from yesterday to see if we can get some additional help :)
07:34 ndevos pranithk: so, lets assume we get bugs triaged - what would be most suitable for developers to watch out for new triaged bugs they can fix?
07:34 ndevos hagarth: yeah, that would help :)
07:35 ndevos pranithk: email is one option, an RSS-feed would be an other - anything else?
07:35 hagarth Humble++ for beta3 RPMs
07:49 pranithk ndevos: email is good enough IMO. just reminder mails saying these are the ones every week per component
07:52 ndevos pranithk: okay, and should those emails with triaged bugs get sent to gluster-devel, or rather an other list, or opt-in for developers?
07:52 hagarth ndevos: gluster-devel might be a good target
07:52 * ndevos just added some RSS feeds to feedly.com
07:53 ndevos hagarth: and once a week would be sufficient?
07:53 hagarth ndevos: sounds like a good frequency to begin with
07:54 pranithk ndevos: opt-in for devs. Let people from redhat do it as a must...
07:56 ndevos hagarth, pranithk: I think we need a poll or something like that :)
07:57 pranithk ndevos: for?
07:57 ndevos pranithk: you and hagarth seem to prefer different things, and I doubt you are alone
07:58 pranithk ndevos: ask in gluster-devel itself
07:58 ndevos pranithk: yeah, I plan doing that, and give some (tested) options too
07:59 ndevos two RSS feeds now added to http://www.gluster.org/community/documentatio​n/index.php/Bugzilla_Notifications#RSS_Feeds
07:59 ndevos Humble, lalatenduM: do you think Bug Triagers would like RSS feeds?
07:59 Humble it would be a good addon
08:00 lalatenduM ndevos, yeah I would like that
08:03 ndevos lalatenduM, Humble: care to check - http://goo.gl/llNxe9 -> NEW Gluster Bugs to Triage
08:04 nthomas_ joined #gluster-dev
08:04 Humble ndevos, checking
08:05 Humble ndevos++
08:07 lalatenduM ndevos, checking
08:08 ndevos Humble: that ++ means you like it?
08:12 lalatenduM ndevos, The only issue is the list looks long as of now
08:12 lalatenduM as we have so many bugs
08:12 Humble ndevos, why u doubt ?  :)
08:12 ndevos lalatenduM: well, yes, that is what we need to fix :)
08:13 Humble lalatenduM, hopefully it will be less in future
08:13 Humble :)
08:13 lalatenduM yeah
08:13 lalatenduM ndevos++ for the innovative idea :)
08:13 ndevos Humble, lalatenduM: what other RSS feeds should we add to http://www.gluster.org/community/documentatio​n/index.php/Bugzilla_Notifications#RSS_Feeds ?
08:14 Humble ndevos, may be version specific bug listing ?
08:16 ndevos Humble: sure, like untriaged 3.5 bugs?
08:17 Humble yep , that would help
08:17 lalatenduM ndevos, I like the idea of "untriaged or not fixed bug for supported branched "
08:18 lalatenduM ndevos, that would give us idea of how much bugs pending for a particular release
08:20 ndevos lalatenduM: you mean a list with all open bugs, one list for 3.4, one for 3.5 and one for 3.6?
08:20 ndevos so, 3 lists?
08:22 Humble ndevos, defintely having different lists for version will help
08:22 lalatenduM ndevos, yeah
08:25 ndevos Humble, lalatenduM: okay, I'll look into that after my next call
08:36 soumya joined #gluster-dev
08:42 soumya joined #gluster-dev
09:10 vimal joined #gluster-dev
09:18 deepakcs joined #gluster-dev
09:29 nthomas joined #gluster-dev
09:29 Humble nthomas, ping
09:36 lalatenduM joined #gluster-dev
09:37 Humble lalatenduM, hi
09:40 Humble hagarth++  for 3.6 beta3 release
09:40 Humble may be you could put a blog post :)
09:40 hagarth xavih: ping, running arequal-checksum with a sufficiently large directory seems to trigger the memory leak in bricks
09:41 hagarth Humble: still waiting for the one release candidate that might be the last :)
09:41 Humble ok.. cool .. make sense  :)
09:53 lalatenduM Humble, pm
09:55 xavih hagarth: I'll try to reproduce this. Thanks :)
09:55 soumya_ joined #gluster-dev
09:57 Humble lalatenduM++
09:57 nthomas_ joined #gluster-dev
10:20 lalatenduM joined #gluster-dev
10:31 pranithk_lunch hagarth: http://review.gluster.org/#/c/8537/ needs to be taken in for the release IMO
10:39 pranithk ndevos: Could you take a look at http://review.gluster.org/8595  for 3.5.3?
10:39 ndevos pranithk: http://review.gluster.org/8873 needs your review :)
10:43 pranithk ndevos: Patch looks fine except your comment man
10:45 ndevos pranithk: your patch looks good, but it took me a while to figure out what changed compared to the mainline version - comments are everything!
10:48 ndevos pranithk: my comment is wrong? I'm pointing out the brace indention - see page 5 in <glusterfs>/doc/coding-standard.pdf
10:49 pranithk ndevos: No no, it is correct
10:50 ndevos pranithk: ah, right
10:50 ndevos pranithk: enough of an issue to -1 it? or you want to +2 it and let me merge it?
10:50 pranithk ndevos: lets merge
10:50 pranithk ndevos: shall I give +1
10:51 ndevos pranithk: yeah, +1 or +2
10:52 pranithk gave _1
10:53 pranithk gave +1
10:53 Humble JustinClift, there ?
10:53 ndevos pranithk: thanks!
11:11 lalatenduM joined #gluster-dev
11:18 hagarth xavih: let me know if you find something .. the client memory usage is also on the higher side
11:19 hagarth pranithk: yes, I will review 8537 later today
11:19 xavih hagarth: yes, I'm currently testing it. I'll tell you something as soon as I identify the problem
11:39 kkeithley meghanam, soumya_: are we having a phone call today?
11:39 kkeithley oops, wrong channel
11:40 JustinClift hagarth: Want to reply to this? https://twitter.com/x4blue​/status/517275597760757761
11:40 * JustinClift isn't sure of the answer
11:40 JustinClift Humble: Kinda.  probably going to crawl back into bed and get more sleep soon.  Not properly awake atm.
11:40 JustinClift Humble: What's up?
11:41 Humble oh ..ok .. small thing . about the project you approved
11:41 Humble planning to keep the fedora gluster package maintainer tasks inside the same
11:42 JustinClift Ahhhh
11:42 JustinClift Cool. :)
11:42 Humble so that its publicly available for everyone :)
11:42 Humble thanks :)
11:42 kkeithley good idea. Humble++
11:42 JustinClift Yep, it makes sense.
11:42 Humble kkeithley, thanks.
11:43 kkeithley hchiramal++
11:44 kkeithley no glusterbot, and no karmabot.
11:44 * Humble : looks like glusterbot is on PTO
11:44 Humble :)
11:44 JustinClift glusterbot-- ;)
11:44 Humble :)
11:45 kkeithley Is the BLR office closed on Monday and Tuesday next week?
11:46 Humble yep..
11:46 kkeithley Humble: ^^^
11:46 kkeithley ah, okay.
11:46 kkeithley Happy Holidays then.
11:46 * kkeithley wonders why you're still in the office then. ;-)
11:46 Humble kkeithley, thanks :)
11:48 hagarth JustinClift: thinking of an appropriate answer :)
11:51 pranithk hagarth: Nobody reviewed heal info for afrv2 either :-(.
11:51 pranithk hagarth: I think itisravi is available on Monday so we can ask him
12:08 aravindavk joined #gluster-dev
12:12 hagarth joined #gluster-dev
12:14 lalatenduM Humble, pm
12:15 Humble lalatenduM, sure
12:23 Humble lalatenduM++ Thanks !!
12:24 lalatenduM Humble, I am missing glusterbot
12:24 Humble indeed I missed 4 times today j/k
12:24 Humble but I will remember it once he is back from pto
12:25 JustinClift hagarth: "Appropriate answer" reminder. ;)
12:26 hagarth JustinClift: right :)
12:32 hagarth JustinClift: done
12:35 JustinClift hagarth: Thanks. :)
12:44 aravindavk joined #gluster-dev
13:09 JustinClift Is it just me, or does Gerrit feel like it's operating faster these days?
13:09 JustinClift Maybe the nightly restart helps it... ;)
13:09 shyam joined #gluster-dev
13:16 ppai joined #gluster-dev
13:28 pranithk joined #gluster-dev
13:32 pranithk left #gluster-dev
13:56 Humble lalatenduM, pm
14:01 tdasilva joined #gluster-dev
14:04 Humble ppai++
14:17 aravindavk joined #gluster-dev
14:54 hagarth joined #gluster-dev
15:18 lpabon joined #gluster-dev
15:27 Gaurav_ joined #gluster-dev
15:56 lalatenduM joined #gluster-dev
15:59 xavih hagarth: I've identified the bug (filed as #1148520). Now working on a solution.
16:00 hagarth xavih: cool!
16:02 lpabon joined #gluster-dev
16:02 ira joined #gluster-dev
16:10 MacWinner joined #gluster-dev
16:15 msvbhat_ joined #gluster-dev
16:56 JustinClift hagarth: Have you noticed any difference in Gerrit speed over the last few days?
16:56 * JustinClift is wondering if the nightly restarts have changed anything with that
16:56 hagarth JustinClift: nothing perceivable
16:56 hagarth JustinClift: have you noticed any?
16:57 JustinClift Wasn't sure.  It feels a bit faster to me, but it's possible it's because I've had stuff downloading in the background for a few days which finished.
16:58 JustinClift So completely possible it's my imagination. :D
16:58 hagarth JustinClift: at least, I haven't noticed any degradation :) .. will keep a tab on performance over the next few days
16:59 JustinClift No biggie.  Just an idle curiosity thing. ;)
17:03 aravindavk joined #gluster-dev
17:12 aravindavk joined #gluster-dev
17:27 kanagaraj joined #gluster-dev
17:28 jobewan joined #gluster-dev
17:55 RaSTar joined #gluster-dev
17:58 _Bryan_ joined #gluster-dev
18:14 anoopcs joined #gluster-dev
18:30 soumya_ joined #gluster-dev
18:33 jobewan joined #gluster-dev
18:58 lpabon joined #gluster-dev
19:57 charta joined #gluster-dev
20:06 shyam joined #gluster-dev
20:30 glusterbot joined #gluster-dev
22:38 MacWinner joined #gluster-dev
23:05 jcastillo joined #gluster-dev

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