Perl 6 - the future is here, just unevenly distributed

IRC log for #gluster-dev, 2016-06-02

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

All times shown according to UTC.

Time Nick Message
00:38 pranithk1 left #gluster-dev
00:47 luizcpg joined #gluster-dev
01:09 hagarth joined #gluster-dev
01:30 hagarth joined #gluster-dev
01:33 shyam joined #gluster-dev
02:01 kdhananjay joined #gluster-dev
02:02 shyam left #gluster-dev
02:08 pranithk1 joined #gluster-dev
02:36 lpabon joined #gluster-dev
03:10 luizcpg joined #gluster-dev
03:34 jiffin joined #gluster-dev
03:44 vimal joined #gluster-dev
03:46 penguinRaider joined #gluster-dev
03:53 nbalacha joined #gluster-dev
03:53 mchangir joined #gluster-dev
03:56 shubhendu joined #gluster-dev
03:56 atinm joined #gluster-dev
03:59 itisravi joined #gluster-dev
04:01 josferna joined #gluster-dev
04:02 rafi joined #gluster-dev
04:08 kotreshhr joined #gluster-dev
04:25 JoeJulian joined #gluster-dev
04:28 aspandey joined #gluster-dev
04:32 josferna joined #gluster-dev
04:43 vimal joined #gluster-dev
04:45 kotreshhr left #gluster-dev
04:46 gem joined #gluster-dev
04:52 jiffin joined #gluster-dev
04:54 josferna joined #gluster-dev
05:09 vimal joined #gluster-dev
05:12 atalur joined #gluster-dev
05:14 ndarshan joined #gluster-dev
05:16 vimal joined #gluster-dev
05:18 pur__ joined #gluster-dev
05:24 aravindavk joined #gluster-dev
05:26 rastar joined #gluster-dev
05:26 ppai joined #gluster-dev
05:27 sakshi joined #gluster-dev
05:29 Apeksha joined #gluster-dev
05:30 kdhananjay joined #gluster-dev
05:32 hgowtham joined #gluster-dev
05:34 karthik___ joined #gluster-dev
05:39 rafi joined #gluster-dev
05:39 vimal joined #gluster-dev
05:41 overclk joined #gluster-dev
05:41 Manikandan joined #gluster-dev
05:42 kotreshhr joined #gluster-dev
05:44 nigelb Manikandan: Could you please email gluster-infra with what you need access to, why you need access, and what you're trying to accomplish?
05:44 nigelb I won't get around to it soon, but it's good to know what you need.
05:44 Manikandan nigelb, sure, we will send today
05:45 itisravi joined #gluster-dev
05:48 aspandey joined #gluster-dev
05:52 rraja joined #gluster-dev
06:09 poornimag joined #gluster-dev
06:11 Acinonyx joined #gluster-dev
06:15 spalai joined #gluster-dev
06:15 Bhaskarakiran joined #gluster-dev
06:18 Bhaskarakiran joined #gluster-dev
06:18 post-factum ndevos: http://review.gluster.org/#/c/14564/ what is the issue with netbsd?
06:20 pkalever joined #gluster-dev
06:20 anoopcs post-factum, spurious failure  :-)
06:26 anoopcs post-factum, You can try re-triggering NetBSD regression by commenting "recheck netbsd".
06:26 post-factum lets try...
06:28 ashiq joined #gluster-dev
06:28 nishanth joined #gluster-dev
06:28 pranithk1 joined #gluster-dev
06:30 josferna joined #gluster-dev
06:33 poornimag pranithk1++
06:33 glusterbot poornimag: pranithk1's karma is now 4
07:04 spalai joined #gluster-dev
07:06 spalai1 joined #gluster-dev
07:07 ppai nigelb++
07:07 glusterbot ppai: nigelb's karma is now 4
07:07 spalai left #gluster-dev
07:08 claude_ joined #gluster-dev
07:15 jiffin nigelb++
07:15 glusterbot jiffin: nigelb's karma is now 5
07:17 prasanth joined #gluster-dev
07:25 Saravanakmr joined #gluster-dev
07:52 post-factum trying to mount 3.7.11 volume with 3.9dev client, and still getting "Unable to fetch afr pending changelogs. Is op-version >= 30707?" error
07:56 karthik___ joined #gluster-dev
07:57 post-factum what am i missing?
08:01 ndevos itisravi: I thought that ^ should have been fixed?
08:03 post-factum ndevos: http://review.gluster.org/#/c/14414/
08:03 post-factum ndevos: i guess it is not present in master
08:25 itisravi post-factum: Haven't reverted the patch in master because we want to have what the patch does. But I'll send another patch to fall back to regular changelogs if "afr pending changelogs" is not present in the volfile.
08:26 post-factum itisravi: nice, thanks
08:29 sabansal_ joined #gluster-dev
08:36 purpleidea joined #gluster-dev
08:36 purpleidea joined #gluster-dev
08:41 claude_ joined #gluster-dev
08:49 nbalacha joined #gluster-dev
08:55 penguinRaider joined #gluster-dev
09:17 itisravi joined #gluster-dev
09:30 jiffin1 joined #gluster-dev
09:33 moka111 joined #gluster-dev
09:36 moka111 Hello, is there someone who could help me with a memory leak problem in glusterd (as described in #gluster) ?
09:43 Jules- joined #gluster-dev
09:48 atinm moka111, go ahead
09:53 moka111 thx. did you read the problem in #gluster?
09:54 atinm moka111, I did
09:54 atinm moka111, it does seem like some of the numbers are too high
09:55 atinm moka111, I need few additional information
09:55 atinm moka111, how many nodes in the cluster, how many volumes, glusterd log file along with cmd_history.log from all the nodes
09:56 atinm moka111, do you have some scripts which run gluster commands very frequently?
09:58 moka111 there is munin with glusterfs plugins installed, but the problem was also before installing munin.
10:00 moka111 the server with the problem is 1 of 2 nodes, mounting the node itself and another glusterfs of a 3 node cluster with the dynamic web content
10:04 nbalacha joined #gluster-dev
10:04 kotreshhr joined #gluster-dev
10:04 moka111 is etc-glusterfs-glusterd.vol.log the glusterd log file?
10:05 atinm|brb yes
10:06 hgowtham joined #gluster-dev
10:07 luizcpg joined #gluster-dev
10:08 moka111 ok, I'll collect the data. It will need some time. is it maybe a general problem, that the node mount the volume itself and also another volume and vice versa?
10:13 jiffin1 joined #gluster-dev
10:15 purpleidea joined #gluster-dev
10:33 jiffin1 joined #gluster-dev
10:39 hgowtham joined #gluster-dev
10:44 atinm|brb joined #gluster-dev
10:46 kotreshhr joined #gluster-dev
10:49 atalur nigelb, https://build.gluster.org/job/smoke/28275/console I see this error on slave29 too many times
10:49 atalur nigelb, is there something you can do about it?
10:53 kkeithley atalur,nigelb,ndevos:  maybe related to http://review.gluster.org/#/c/14340/
10:55 kkeithley or http://review.gluster.org/14338
10:57 moka111 @atinm|brb I collected the data into one tgz file http://expirebox.com/download/8aacc180bea1443af1a2e0ffde5f14f5.html
10:57 atinm|brb moka111, Could you just mail this to gluster-users@gluster.org?
10:58 atinm|brb moka111, I will take a look at it tomorrow
10:58 atinm|brb moka111, for now does restarting glusterd service solve your problem?
10:59 atalur guess will just have to keep retriggering smoke till those patches get merged. Thanks kkeithley :)
11:04 moka111 ok, I'll sent it per email. the restart reduces the memory to about 20% of the ram
11:05 ira joined #gluster-dev
11:08 post-factum moka111: 20% seems to be too much as well
11:08 atinm|brb moka111, glusterd consumes 20% memory ?
11:15 pranithk1 joined #gluster-dev
11:15 post-factum itisravi: btw, any possibility to get that afr-related patch soon? i need to test master branch but have little desire to setup separate cluster :(
11:17 itisravi post-factum: just curious, why are you testing a client based off master while the server is 3.7.11?
11:17 moka111 after restart it is about 20% slowly increasing. before restart it was about 96%
11:17 itisravi post-factum: generally newer clients and older servers are not supported.
11:25 claude__ joined #gluster-dev
11:29 kkeithley amye: linuxcon europe is October 4-6, and Gluster Summit is October 6-7.  (Both at Intercontinental, Berlin)  So we have one day overlap?
11:30 kkeithley @later tell amye linuxcon europe is October 4-6, and Gluster Summit is October 6-7.  (Both at Intercontinental, Berlin)  So we have one day overlap?
11:30 glusterbot kkeithley: The operation succeeded.
11:31 post-factum itisravi: because i already have 3.7 server set up and running
11:32 post-factum itisravi: i believe newer clients and older servers should be supported, otherwise, how one would make rolling upgrade?
11:32 itisravi post-factum: no it is the other way around. Servers can be at a newer version while clients can be at the same version or older.
11:33 itisravi post-factum: In rolling upgrade, you always need to update the servers first.
11:34 post-factum itisravi: hmm, at least within 3.7 minor updates my strategy worked well...
11:34 post-factum itisravi: okay, let it be
11:35 itisravi post-factum: hmm. I'll send the afr fix in a day or two, but what I'm saying is there in no guarantee that other things might not break if client==new and servers==old.
11:37 * itisravi wonders if there is upstream doucmentation to the effect that new client+ old servers are not supported.
11:37 * itisravi or rather not 'officially' supported :)
11:37 nigelb atalur: that looks like a good bug that kkeithley pointed out.
11:38 nigelb I will most probably not be able to anything about it until I've sorted out our gerrit issues post-upgrade.
11:43 itisravi hagarth: Do we explicitly support/not support newer clients and older servers?
11:44 alghost joined #gluster-dev
11:48 kkeithley new client needs/wants a new feature that the old server can't provide?
11:49 penguinRaider joined #gluster-dev
12:12 atinm|brb joined #gluster-dev
12:14 luizcpg joined #gluster-dev
12:19 itisravi_ joined #gluster-dev
12:39 kdhananjay joined #gluster-dev
12:52 nbalacha joined #gluster-dev
12:57 shyam joined #gluster-dev
13:27 pranithk1 joined #gluster-dev
13:27 hagarth post-factum, itisravi: new(er) clients are expected to work with old servers. Even if you ignore external fuse clients, we can have older clients (through gNFS, glustershd etc.) in the trusted storage pool with new servers during an online/rolling upgrade.
13:28 pranithk1 hagarth: It is not possible to get new clients to work with old servers because some of the things new clients do, older servers won't understand right?
13:28 hagarth pranithk1: the clients would need to negotiate capabilities and tune accordingly (based on who they are talking to)
13:28 pranithk1 hagarth: newer servers and older clients is fine.
13:29 pranithk1 hagarth: Ah! you are saying older op-version
13:29 pranithk1 hagarth: that seems fine I guess..
13:29 hagarth pranithk1: yes, capabilities should be tied to op-version(s).
13:30 pranithk1 hagarth: Do you know why http://review.gluster.org/#/c/14454 smoke is not given +1 even after successful smoke run? :-/
13:32 hagarth pranithk1: no idea, isn't the rpm building issue sorted out yet?
13:33 kdhananjay pranithk1: do a recheck smoke now. worked for me.
13:33 pranithk1 kdhananjay: thanks!
13:33 pranithk1 hagarth: will do what kdhananjay is suggesting
13:34 kdhananjay pranithk1: i already did
13:34 pranithk1 kdhananjay: sorry :-/
14:05 mchangir joined #gluster-dev
14:06 ndevos hi nigelb, do you have an eta for when the login issues with gerrit are resolved?
14:06 ndevos hagarth: I've not had a fsx segfault yet... although some other error
14:06 hagarth ndevos: am able to hit it consistently
14:07 hagarth ndevos: do you know of any problems for not being able to upload attachments to bugzilla?
14:07 nigelb ndevos: I have a fix now that I'm having the affected people test on review.nigelb.me
14:07 hagarth ndevos: are you running with fuse or nfs?
14:07 nigelb I'll ping you in a bit about that.
14:07 ndevos hagarth: testing with nfs, I thought you did that too?
14:08 hagarth ndevos: yes, am also running fsx with nfs
14:08 ndevos nigelb: ok, thanks, its rather annoying to be unable to leave inline comments on code reviews
14:08 nigelb ndevos: I know! I'm sorry about this. I'm specifically moving slowly so we don't break it *again*.
14:09 nigelb hagarth: Do you still have the Anonymous Coward issue?
14:09 nigelb If you do, please check if you can reproduce it in a private browsing window.
14:10 hagarth nigelb: checking
14:11 hagarth nigelb: i seem to hit it randomly .. will keep monitoring in a private browsing window
14:11 nigelb hagarth: Pretty sure it'll go away once I flush the server cache.
14:11 hagarth nigelb: cool
14:11 nigelb I'm trying not to touch the production server and cause any new issues.
14:12 ndevos nigelb: ok, thanks!
14:13 nigelb ndevos: You'll have to do two rounds of testing, I'm afraid :)
14:13 nigelb One round now and one round later today.
14:13 nigelb (with fresher data from production)
14:13 nigelb to confirm that we won't hit any issues.
14:19 ndevos nigelb: hmm, I've seen a list of "Anonymous Coward #..." patches yesterday too, but a refresh resolved it
14:21 nigelb oh, ok.
14:22 nigelb I'll need to track it down after we solve the issue that a few people can't login.
14:23 shyam joined #gluster-dev
14:25 shyam joined #gluster-dev
14:27 mchangir joined #gluster-dev
14:29 gem joined #gluster-dev
14:31 kdhananjay pranithk++
14:31 glusterbot kdhananjay: pranithk's karma is now 54
14:36 wushudoin joined #gluster-dev
14:56 nigelb ndevos: see PM.
14:59 vimal joined #gluster-dev
15:01 dlambrig1 joined #gluster-dev
15:06 shubhendu joined #gluster-dev
15:07 PotatoGim joined #gluster-dev
15:36 jiffin joined #gluster-dev
15:37 hagarth joined #gluster-dev
15:52 jiffin joined #gluster-dev
16:12 deangiberson joined #gluster-dev
16:20 rafi1 joined #gluster-dev
16:21 gem joined #gluster-dev
16:31 anoopcs pranithk1, Can you please edit the topic of https://review.gluster.org/#/c/14596/ ?
16:32 pranithk1 anoopcs: is it giving problems?
16:32 anoopcs pranithk1, It won't take away the reviews
16:32 pranithk1 anoopcs: By default it gave this topic
16:32 anoopcs (unless you are afraid of reviews and regression results)
16:33 pranithk1 anoopcs: I am just curious to know why it should be changed...
16:33 anoopcs pranithk1, It's supposed to be like bug-<bug number>
16:34 pranithk1 anoopcs: I think new version makes it this way...
16:34 pranithk1 anoopcs: new version of gerrit
16:34 pranithk1 anoopcs: it is assigned like this..
16:34 anoopcs pranithk1, Is it?
16:34 pranithk1 anoopcs: yeah
16:34 anoopcs You cherry-picked using Gerrit Web UI, right?
16:35 pranithk1 anoopcs: I did one more cherry-pick, which got both release-3.8-release-3.7
16:35 pranithk1 anoopcs: yes
16:35 anoopcs Interesting...
16:35 pranithk1 anoopcs: I thought this is how it will be going forward...
16:35 pranithk1 anoopcs: it is not?
16:35 pranithk1 anoopcs: Or may be we should change default
16:36 pranithk1 anoopcs: I mean default way of assigning topic
16:36 anoopcs pranithk1, With older Gerrit, after cherry-picking via web-ui topic used to be empty.
16:36 pranithk1 anoopcs: yeah
16:36 pranithk1 anoopcs: Now it changed
16:36 anoopcs and I remember adding it manually
16:36 pranithk1 anoopcs: Anyways, I changed it
16:36 pranithk1 anoopcs: yeah, I didn't touch it then either :-)
16:38 anoopcs nigelb, Do you have any idea on this new behavior?
16:39 anoopcs pranithk1, Thanks. You can change http://review.gluster.org/#/c/14598/ too..
16:40 anoopcs pranithk++
16:40 glusterbot anoopcs: pranithk's karma is now 55
16:42 nigelb anoopcs: I don't off the top of my head.
16:42 nigelb I've been deep in the login issue.
16:43 anoopcs nigelb, np. We can take it later.
16:45 atalur joined #gluster-dev
16:48 atalur nigelb, need your help. http://review.gluster.org/#/c/14454/ has smoke test passed successfully twice but has not marked it with a +1 :-/
16:48 atalur nigelb, looks like an infra issue. could you please help ? :)
17:09 rafi joined #gluster-dev
17:59 luizcpg joined #gluster-dev
18:18 nishanth joined #gluster-dev
18:58 shyam1 joined #gluster-dev
19:00 shyam joined #gluster-dev
20:05 shyam joined #gluster-dev
21:10 penguinRaider joined #gluster-dev
22:06 shyam joined #gluster-dev
22:08 pranithk1 joined #gluster-dev
22:09 luizcpg joined #gluster-dev
23:31 moka111 joined #gluster-dev
23:34 suliba joined #gluster-dev

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