Perl 6 - the future is here, just unevenly distributed

IRC log for #gluster-dev, 2015-12-08

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

All times shown according to UTC.

Time Nick Message
00:01 Willy joined #gluster-dev
00:03 Guest41282 Hi. I would like to ask whether there is a resource/book about GlusterFS (e.g. LearningCeph about Ceph). I have been looking for it though I only come across introduction about GlusterFS which covers a small part of it. Thanks.
00:04 hagarth Guest41282: not that I know of. gluster.readthedocs.org is the best that is around.
00:04 hagarth are you looking for something specific?
00:08 Guest41282 Yeah actually. I would like how the GlusterFS works when the cluster is added an additional node or lost a node. I am researching it as my final year project.
00:11 hagarth Guest41282: addition & removal of nodes is an online operation in Gluster. Don't think the internals are described well anywhere. If you have specific questions, please send out a note on gluster-devel mailing list and somebody will offer help.
00:24 Guest41282 Okay. Thank you. I will try to learn about GlusterFS from readthedocs and Jeff Darcy's blog first.
00:44 shyam joined #gluster-dev
00:55 EinstCrazy joined #gluster-dev
01:23 rjoseph joined #gluster-dev
02:07 pranithk joined #gluster-dev
02:30 ggarg joined #gluster-dev
03:50 shubhendu joined #gluster-dev
03:57 atinm joined #gluster-dev
04:03 Bhaskarakiran joined #gluster-dev
04:04 vmallika joined #gluster-dev
04:06 nishanth joined #gluster-dev
04:09 itisravi joined #gluster-dev
04:16 kanagaraj joined #gluster-dev
04:23 rafi joined #gluster-dev
04:34 aspandey joined #gluster-dev
04:37 hgowtham joined #gluster-dev
04:44 nbalacha joined #gluster-dev
04:44 kdhananjay joined #gluster-dev
04:56 Apeksha joined #gluster-dev
04:58 hgowtham joined #gluster-dev
04:59 kotreshhr joined #gluster-dev
05:00 ppai joined #gluster-dev
05:06 mchangir joined #gluster-dev
05:07 ndarshan joined #gluster-dev
05:09 ashiq joined #gluster-dev
05:13 poornimag joined #gluster-dev
05:15 Manikandan joined #gluster-dev
05:18 skoduri joined #gluster-dev
05:21 pppp joined #gluster-dev
05:23 vmallika joined #gluster-dev
05:26 overclk joined #gluster-dev
05:34 kdhananjay joined #gluster-dev
05:35 rjoseph joined #gluster-dev
05:41 sakshi joined #gluster-dev
05:55 jiffin joined #gluster-dev
05:59 Bhaskarakiran joined #gluster-dev
06:03 ggarg joined #gluster-dev
06:07 anekkunt joined #gluster-dev
06:10 skoduri joined #gluster-dev
06:15 night joined #gluster-dev
06:16 night left #gluster-dev
06:20 ashiq joined #gluster-dev
06:34 Humble joined #gluster-dev
06:47 hchiramm joined #gluster-dev
06:48 hchiramm_ joined #gluster-dev
07:01 pranithk joined #gluster-dev
07:01 shubhendu joined #gluster-dev
07:02 nishanth joined #gluster-dev
07:03 atalur joined #gluster-dev
07:09 ndarshan joined #gluster-dev
07:20 ggarg joined #gluster-dev
07:50 overclk joined #gluster-dev
07:57 josferna joined #gluster-dev
08:01 ndarshan joined #gluster-dev
08:02 nishanth joined #gluster-dev
08:18 kshlm joined #gluster-dev
08:27 Saravana_ joined #gluster-dev
08:31 obnox don't verification runs get triggered after klicking rebase in gerrit?
08:33 overclk joined #gluster-dev
08:34 kshlm obnox, it should work.
08:42 obnox kshlm: I thought so, too.
08:43 obnox kshlm: how long does it usually take until jobs show up in the lists?
08:44 obnox kshlm: my assumption is, I can seen them pending, with their gerrit review # under, eg. https://build.gluster.org/job/rackspace-regression-2GB-triggered/
08:45 kshlm obnox, You should immediatelly see them in the pending list. If you don't there's a problem.
08:45 aravindavk joined #gluster-dev
08:45 obnox kshlm: there IS a problem.
08:45 obnox here is a patch set that I have submitted. for that one, no build has been triggered automatically at all. just one 2GB build that was triggered manually by "amarts" :
08:45 obnox http://review.gluster.org/#/c/12830/
08:46 kshlm obnox, I'll take a look.
08:46 obnox kshlm: thank you!
08:51 kshlm obnox, I've manually triggered the jobs. I'm not sure why they weren't automatically triggered. I'll investigate that later.
08:51 obnox kshlm: thanks!
08:51 obnox kshlm++
08:51 glusterbot obnox: kshlm's karma is now 44
09:02 rraja joined #gluster-dev
09:10 aravindavk joined #gluster-dev
09:11 aravindavk joined #gluster-dev
09:17 mchangir joined #gluster-dev
09:19 Saravana_ joined #gluster-dev
09:21 Apeksha joined #gluster-dev
09:22 obnox kshlm: if I am not mistaken, this one also was not triggered automatically after rebase by hagarth: http://review.gluster.org/#/c/12826/
09:24 kotreshhr joined #gluster-dev
09:25 ggarg joined #gluster-dev
09:30 Apeksha joined #gluster-dev
09:32 shubhendu joined #gluster-dev
09:34 ashiq joined #gluster-dev
09:54 rjoseph joined #gluster-dev
10:02 rafi1 joined #gluster-dev
10:03 jiffin1 joined #gluster-dev
10:06 josferna joined #gluster-dev
10:08 aravindavk joined #gluster-dev
10:20 Saravana_ joined #gluster-dev
10:21 kotreshhr joined #gluster-dev
10:27 kdhananjay joined #gluster-dev
10:28 ATA joined #gluster-dev
10:37 kdhananjay joined #gluster-dev
10:38 Bhaskarakiran joined #gluster-dev
10:39 Guest71157 hello everybody. Can anyone help me, I want to increase read/write buffer size, is it possible?
10:40 Guest71157 when it reads, the input buffer size is 128KB.
10:42 ggarg joined #gluster-dev
10:43 firemanxbr joined #gluster-dev
10:46 Apeksha joined #gluster-dev
10:48 rafi joined #gluster-dev
10:54 raghu joined #gluster-dev
10:58 Bhaskarakiran joined #gluster-dev
11:06 kkeithley1 joined #gluster-dev
11:10 skoduri joined #gluster-dev
11:10 badone joined #gluster-dev
11:15 jiffin1 joined #gluster-dev
11:24 rafi1 joined #gluster-dev
11:24 EinstCrazy joined #gluster-dev
11:35 Manikandan REMINDER: Gluster Community Bug Triage meeting at 12:00 UTC (~in 30 minutes)
11:35 Manikandan Meeting details: #gluster-meeting on Freenode IRC
11:40 josferna joined #gluster-dev
11:40 skoduri joined #gluster-dev
11:47 mmckeen joined #gluster-dev
11:54 kdhananjay joined #gluster-dev
11:57 kotreshhr joined #gluster-dev
11:59 Manikandan REMINDER: Gluster Community Bug Triage meeting is about to start now in #gluster-meeting
12:00 ppai joined #gluster-dev
12:11 Humble joined #gluster-dev
12:27 Bhaskarakiran joined #gluster-dev
12:28 hchiramm_ joined #gluster-dev
12:30 hchiramm joined #gluster-dev
12:35 EinstCra_ joined #gluster-dev
12:37 Manikandan kkeithley++
12:37 glusterbot Manikandan: kkeithley's karma is now 107
12:55 ppai joined #gluster-dev
12:56 ndk joined #gluster-dev
13:02 Manikandan hchiramm++ hgowtham++ atinm++ jiffin++ skoduri++ kkeithley_++ rafi1++, thank you all for attending bug triage meeting :-)
13:02 glusterbot Manikandan: hchiramm's karma is now 73
13:02 glusterbot Manikandan: hgowtham's karma is now 10
13:02 glusterbot Manikandan: atinm's karma is now 44
13:02 glusterbot Manikandan: jiffin's karma is now 22
13:02 glusterbot Manikandan: skoduri's karma is now 8
13:02 glusterbot Manikandan: kkeithley_'s karma is now 4
13:02 glusterbot Manikandan: rafi1's karma is now 2
13:02 Humble Manikandan++
13:02 glusterbot Humble: Manikandan's karma is now 42
13:03 hgowtham Manikandan++
13:03 glusterbot hgowtham: Manikandan's karma is now 43
13:03 kkeithley_ Manikandan++
13:04 glusterbot kkeithley_: Manikandan's karma is now 44
13:12 Gaurav__ joined #gluster-dev
13:21 kotreshhr joined #gluster-dev
13:48 kshlm Anyone know who's the maintainer for tests/ ? Do we have a maintainer for tests/?
13:50 kkeithley_ everyone?
13:53 kshlm kkeithley_, okay. So maybe you could merge my change https://review.gluster.org/12913 when it passes the regression runs.
13:55 kkeithley_ sure
13:55 atinm kshlm, I'll take a look at it as well
13:56 atinm kkeithley has already +2ed it, so good to go then :)
13:56 kshlm atinm, kkeithley_ , thanks!
13:56 Manikandan kshlm++, thanks for merging :-)
13:56 glusterbot Manikandan: kshlm's karma is now 45
13:56 kkeithley_ nominally the maintainer for the component that the test is testing...
13:57 kshlm kkeithley_, I figured that out later, so I added atinm as well.
13:57 shaunm joined #gluster-dev
13:58 josferna joined #gluster-dev
14:02 ira joined #gluster-dev
14:03 shyam joined #gluster-dev
14:08 kotreshhr left #gluster-dev
14:18 mchangir joined #gluster-dev
14:22 vmallika joined #gluster-dev
14:31 rafi joined #gluster-dev
14:31 zhangjn joined #gluster-dev
14:32 rjoseph joined #gluster-dev
14:32 zhangjn joined #gluster-dev
14:54 kotreshhr joined #gluster-dev
14:55 hagarth joined #gluster-dev
14:57 hagarth is jenkins being restarted?
14:57 csim mhh no
14:57 csim I did restart a few slaves however
14:57 csim because they were not responding to ssh
14:57 csim hagarth: why, what happened ?
14:57 hagarth csim: I see a notification in jenkins web
14:58 hagarth csim: check this - https://build.gluster.org/job/regression-test-burn-in/
14:58 hagarth the red notice at the top made me ask this
14:58 csim hagarth: yeah, I see, but not by me then
14:58 csim (unless I did reboot the wrong server)
14:59 hagarth kshlm: any idea about this? ^^
14:59 kshlm hagarth, I just sent an announcement on gluster-infra
14:59 hagarth kshlm: ah ok
15:00 kshlm gerrit-trigger isn't working again. And nothing in the logs again.
15:00 hagarth kshlm: can I take a look around for a few minutes?
15:01 hagarth kshlm: or go ahead, I have another meeting to run to now
15:01 kshlm hagarth, sure.
15:01 kshlm You should have plenty of time. Some of the running regression jobs show ~2hrs left.
15:03 skoduri joined #gluster-dev
15:06 hagarth kshlm: great
15:06 kotreshhr1 joined #gluster-dev
15:08 kshlm Does anyone have any opinion on removing tests/basic/rpm.t from the regression suite?
15:08 kshlm We have the devrpms jobs which do the same thing.
15:08 kshlm And the rpm.t test doesn't seem to be particularly portable.
15:08 hagarth kshlm: an opinion from ndevos on this would be good
15:09 kshlm It appears pretty specific to the current slave environment
15:09 kshlm hagarth, But he isn't around this week though.
15:10 hagarth kshlm: do drop him a note. I think he plans to check emails sporadically.
15:13 hagarth kshlm: seems to be working again?
15:13 hagarth I just rebased two patches and they seem to be listed in jenkins queue now..
15:13 kshlm hagarth, they shouldn't be!
15:14 kshlm Looks like someone cancelled the restart.
15:14 hagarth kshlm: I did
15:14 kshlm Ah okay.
15:15 josferna joined #gluster-dev
15:16 kshlm hagarth, I see 3 new jobs in the last 5 minutes, but they've been manually triggered by dlambrig
15:16 kshlm Still no auto-triggering.
15:18 obnox no. :-(
15:18 obnox my example: http://review.gluster.org/#/c/12826/
15:21 obnox and this: http://review.gluster.org/#/c/12830/
15:21 obnox (just rebased that. it had verify success before rebase)
15:22 kshlm obnox, You'll need to wait a little while longer. Hopefully hagarth figures out whats wrong.
15:26 obnox kshlm: sure. just giving you more cases to look at.
15:28 hagarth kshlm: is the connectivity between r.g.o & b.g.o stable?
15:29 csim they are on the same VM
15:29 kshlm should be. I'm using b.g.o to tunnel into r.g.o
15:29 kdhananjay joined #gluster-dev
15:29 csim s/VM/virt host/
15:30 kshlm also what csim said.
15:30 hagarth agree, I ran into slave machines not being reachable over the weekend and few of my runs got aborted
15:32 hagarth kshlm, csim: looks like jenkins cannot ssh to gerrit
15:33 csim yeah, same problem as last week
15:33 hagarth kshlm, csim: check here - https://build.gluster.org/gerrit-trigger/server/defaultServer/
15:33 hagarth and click on Test Connection
15:34 kshlm hagarth, I don't know why that happens, but clear out the ssh-password field.
15:34 kshlm For some reason that gets filled.
15:35 hagarth cleared it out and testing now
15:40 hagarth kshlm: maybe we need to install/configure this sometime: Gerrit Missed Events Playback is not supported.  Verify if the connection has the REST API enabled and that the Gerrit  Events-log plugin is installed and configured on the Gerrit Server.
15:41 kshlm hagarth, that requires a newer gerrit version. But not having that gerrit feature shouldn't prevent gerrit-trigger from working.
15:41 csim kshlm: I wonder if that's not a bug fromnew jenkins
15:41 csim ie, it see the empty stuff and fill it with the md5sum of the empty field, something like this
15:42 hagarth kshlm: agree, it was just a note for later.
15:42 kshlm csim, possibly.
15:43 kshlm The gerrit-trigger.xml config file has some encoded value for gerritAuthKeyFilePassword even though we set it to empty.
15:43 kanagaraj joined #gluster-dev
15:44 csim yeah, last time, i did clean the field and restarted
15:44 csim so something fill it back
15:51 wushudoin joined #gluster-dev
15:51 cholcombe joined #gluster-dev
15:54 wushudoin joined #gluster-dev
15:55 kshlm hagarth, csim, good luck with the problem. I'm logging off for the day.
16:06 pranithk joined #gluster-dev
16:20 hagarth csim: was the password appearing the root cause for last week's problem too i.e. regression tests not being triggered on gerrit patches automatically?
16:23 csim hagarth: yes
16:24 csim I tought I posted about it, but maybe not :/
16:26 hagarth csim: np, I am a bit out of sync with my emails right now
16:37 rjoseph joined #gluster-dev
16:52 shubhendu joined #gluster-dev
17:04 Gaurav__ joined #gluster-dev
17:16 _iwc joined #gluster-dev
17:19 pranithk joined #gluster-dev
17:22 pranithk joined #gluster-dev
17:30 pranithk left #gluster-dev
17:34 shyam joined #gluster-dev
19:02 ira joined #gluster-dev
19:30 kotreshhr1 left #gluster-dev
19:32 shyam joined #gluster-dev
20:25 obnox what happens if I retrigger a build that has been done on an older version of a patch in gerrit after a rebase? will it use the new state?
20:50 shyam joined #gluster-dev
20:52 kkeithley_ because the regressions (and other things) didn't run?  Just trigger them with Query and Trigger Gerrit Patches from the top dashboard
20:52 kkeithley_ click the search button.  tick the box for your patch, press Trigger Selected.  Then wait an hour. ;-)
21:03 hagarth joined #gluster-dev
21:32 hagarth joined #gluster-dev
22:02 obnox kkeithley_: I am not sure I get you. top dashboard of jenkins or gerrit?
22:03 obnox kkeithley_: I rebased a patch (or rather, several) and I expected the regression tests to be run. But they were not run.
22:04 kkeithley_ jenkins dashboard
22:04 obnox I can locate the previous regression run in jenkins easily. There I can click "retrigger". My question is: does that use the rebased patch or the old version?
22:04 kkeithley_ yes, they should run. I don't know why they are not
22:05 kkeithley_ I don't think that works the way your want it to work. I could be wrong though
22:05 kkeithley_ s/your/you/
22:05 obnox kk
22:05 obnox kkeithley_: thx
22:06 * obnox looking at the jenkins dashboard now
22:06 kkeithley_ hagarth says in email that he has restarted jenkins and now it seems to be triggering jobs again
22:09 kkeithley_ so all the patches that were submitted up to now didn't get their jobs triggered
22:09 obnox kkeithley_: thanks. found the query and trigger thing and was able to retriggerd

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