Perl 6 - the future is here, just unevenly distributed

IRC log for #gluster-dev, 2017-10-12

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

All times shown according to UTC.

Time Nick Message
01:56 ilbot3 joined #gluster-dev
01:56 Topic for #gluster-dev is now Gluster Development Channel - https://www.gluster.org | For general chat go to #gluster | Patches - https://review.gluster.org/ | Channel Logs - https://botbot.me/freenode/gluster-dev/ & http://irclog.perlgeek.de/gluster-dev/
02:22 pkalever joined #gluster-dev
02:30 susant joined #gluster-dev
02:34 susant left #gluster-dev
03:04 nbalacha joined #gluster-dev
03:19 PotatoGim Hi all! I had heard for gluster summit 2017 :) Do you have a plan to make and upload videos for that?
03:36 psony joined #gluster-dev
03:37 apandey joined #gluster-dev
03:41 nbalacha joined #gluster-dev
04:09 itisravi joined #gluster-dev
04:19 skoduri joined #gluster-dev
04:22 susant joined #gluster-dev
04:34 skumar joined #gluster-dev
04:46 atinm joined #gluster-dev
04:58 ndarshan joined #gluster-dev
05:07 Shu6h3ndu joined #gluster-dev
05:13 msvbhat joined #gluster-dev
05:13 msvbhat_ joined #gluster-dev
05:16 Humble joined #gluster-dev
05:23 gobindadas joined #gluster-dev
05:29 amarts joined #gluster-dev
05:31 dkhandel__ joined #gluster-dev
05:31 xavih joined #gluster-dev
05:33 jiffin joined #gluster-dev
05:34 nishanth joined #gluster-dev
05:35 Saravanakmr joined #gluster-dev
05:37 karthik_us joined #gluster-dev
05:46 msvbhat joined #gluster-dev
05:46 msvbhat_ joined #gluster-dev
05:47 ppai joined #gluster-dev
05:48 kotreshhr joined #gluster-dev
05:52 hgowtham joined #gluster-dev
05:53 rafi joined #gluster-dev
05:55 poornima_ joined #gluster-dev
05:59 atinm joined #gluster-dev
06:15 sanoj joined #gluster-dev
06:20 karthik_us joined #gluster-dev
06:22 BlackoutWNCT Hey guys, I'm seeing a pretty major mem usage issue with the gluster FUSE client, I've got 2 machines who are currently running OOM due to this, one has 24G the other has 32G. the glusterfs proc seems to just be eating what it can and not releasing anything.
06:22 BlackoutWNCT FUSE client is v3.11.3
06:22 BlackoutWNCT server version is 3.10.3
06:24 Venkata joined #gluster-dev
06:24 BlackoutWNCT I've also got a client on v3.10.3 which is doing the same
06:25 nbalacha BlackoutWNCT, can you take statedumps of the Fuse client at intervals when you see the mem rising?
06:26 BlackoutWNCT nbalacha, No worries, can do
06:26 nbalacha BlackoutWNCT, thanks - that should give us some clues as to what is happening
06:27 BlackoutWNCT nbalacha, just so I'm on the right page, is this done on the client side? or on the server side?
06:28 BlackoutWNCT I'm following the guide on generating a statedump, but running gluster --print-statedumpdir returns a prompt to install the glusterfs-server package
06:28 BlackoutWNCT I've currently got the glusterfs-client package installed
06:29 nbalacha BlackoutWNCT, try kill -SIGUSR1 <pid of mount process>
06:29 nbalacha and can you point me to the guide you are using?
06:29 BlackoutWNCT https://gluster.readthedocs.io/en/latest/Troubleshooting/statedump/#generate-a-statedump
06:30 nbalacha ok, we will make that a little cleare
06:30 BlackoutWNCT I ran the command, and it appears to have completed without error.
06:30 nbalacha also we have migrated the docs to docs.gluster.org :)
06:30 BlackoutWNCT Where would I find the statedump?
06:30 nbalacha BlackoutWNCT, you should see statedumps in /var/run/gluster
06:31 BlackoutWNCT nbalacha, I don't have that path, is it different on ubuntu?
06:31 nbalacha hmm, I have not tried
06:31 nbalacha can you try creating it and then run the statedump again?
06:32 itisravi joined #gluster-dev
06:32 BlackoutWNCT nbalacha, cool, that did it :)
06:33 BlackoutWNCT But it created an empty file.
06:33 BlackoutWNCT well, not quite empty
06:33 BlackoutWNCT This is the only line...
06:33 BlackoutWNCT DUMP-START-TIME: 2017-10-12 06:32:16.070050
06:33 BlackoutWNCT Or will this run for a bit?
06:35 nbalacha hmm
06:35 nbalacha that is strange
06:37 nbalacha can you try it again?
06:38 BlackoutWNCT It created nothing this time
06:38 BlackoutWNCT And nothing new has been added to the previous file.
06:38 BlackoutWNCT I'll test on another client, gimme a sec.
06:38 nbalacha sure
06:40 BlackoutWNCT ok, so it worked on a client running 3.10.3
06:40 BlackoutWNCT But didn't on the 3.11 client
06:40 BlackoutWNCT Both of these are experiencing similar issues though
06:42 foster joined #gluster-dev
06:43 nbalacha ok, can you file a BZ for this and attach the statedumps?
06:46 BlackoutWNCT nbalacha, I can do, is there a guide somewhere for filing a bugzilla report? I've not done one before :S
06:48 BlackoutWNCT Actually, I think I've worked it out.
06:48 nbalacha BlackoutWNCT, http://docs.gluster.org/en/latest/Contributors-Guide/Bug-reporting-template/
06:48 nbalacha :)
06:49 BlackoutWNCT Thank you :)
06:49 nbalacha BlackoutWNCT, you are welcome
07:05 pkalever joined #gluster-dev
07:15 msvbhat_ joined #gluster-dev
07:15 msvbhat joined #gluster-dev
07:16 BlackoutWNCT nbalacha, https://bugzilla.redhat.com/show_bug.cgi?id=1501146
07:16 glusterbot Bug 1501146: high, unspecified, ---, bugs, NEW , FUSE client Memory usage issue
07:24 atinm joined #gluster-dev
07:55 nbalacha BlackoutWNCT, will take a look.
08:00 nbalacha joined #gluster-dev
08:11 BlackoutWNCT nbalacha, no worries, I should have some extra state dumps for you in the morning. I"ve created a cron job to create one every 4 hours.
08:11 BlackoutWNCT I'll update the BZ in the morning with them :)
08:22 skoduri joined #gluster-dev
08:24 itisravi joined #gluster-dev
08:50 karthik_us joined #gluster-dev
08:56 rafi anoopcs++
08:56 glusterbot rafi: anoopcs's karma is now 51
09:17 pkalever joined #gluster-dev
09:19 karthik_us joined #gluster-dev
09:23 gobindadas joined #gluster-dev
09:24 nbalacha jiffin, ping
09:43 jiffin nbalacha: pong
09:45 nbalacha jiffin, can https://review.gluster.org/18480 be taken for 3.12 if the centos regressions complete in time
09:46 jiffin nbalacha: yes
09:46 nbalacha jiffin, thanks
10:00 atinm joined #gluster-dev
10:10 xavih joined #gluster-dev
10:16 pkalever joined #gluster-dev
10:40 rraja joined #gluster-dev
10:41 skumar_ joined #gluster-dev
10:44 kotreshhr left #gluster-dev
10:59 pkalever joined #gluster-dev
11:14 pkalever joined #gluster-dev
11:15 hgowtham joined #gluster-dev
11:18 pkalever joined #gluster-dev
11:33 nh2 joined #gluster-dev
11:37 msvbhat joined #gluster-dev
11:38 msvbhat_ joined #gluster-dev
11:59 csaba joined #gluster-dev
12:04 susant left #gluster-dev
12:19 sanju joined #gluster-dev
12:27 sanju_ joined #gluster-dev
12:27 sanju joined #gluster-dev
12:28 shyam joined #gluster-dev
12:37 skumar__ joined #gluster-dev
12:50 atinm joined #gluster-dev
13:07 atinm joined #gluster-dev
13:22 shyam joined #gluster-dev
14:01 uebera|| joined #gluster-dev
14:01 uebera|| joined #gluster-dev
14:07 shyam joined #gluster-dev
14:43 uebera|| joined #gluster-dev
14:47 ndevos kkeithley: I need an explanation for 0x3ff in the commit message of https://review.gluster.org/18287 :)
14:53 skumar_ joined #gluster-dev
14:57 kkeithley fits in three chars
14:59 kkeithley decimal 1023 (max number of threads) is hex 3ff
15:00 skumar_ joined #gluster-dev
15:01 kkeithley max threads in some cases is 1000 or 1024. since it's printing hex it could be masked/clamped to 0xfff too as far as that goes, but 0x3ff is more precise.
15:02 kkeithley for some definition of precise.
15:02 kkeithley and I know you're really asking for this in the commit message
15:03 kkeithley I don't believe there are that many epoll threads possible, I'd need to double check
15:05 kkeithley but mainly it's a hint to the compiler that the printed value will fit in the available space, i.e. three chars
15:19 atinm joined #gluster-dev
16:58 msvbhat joined #gluster-dev
17:02 msvbhat_ joined #gluster-dev
17:26 atinm joined #gluster-dev
17:36 msvbhat joined #gluster-dev
17:37 msvbhat_ joined #gluster-dev
17:48 jiffin joined #gluster-dev
18:41 vbellur1 joined #gluster-dev
18:42 vbellur joined #gluster-dev
18:43 vbellur joined #gluster-dev
18:55 vbellur joined #gluster-dev
18:56 vbellur joined #gluster-dev
18:56 vbellur joined #gluster-dev
19:00 vbellur joined #gluster-dev
19:01 vbellur joined #gluster-dev
19:02 vbellur joined #gluster-dev
19:02 vbellur1 joined #gluster-dev
19:04 vbellur joined #gluster-dev
19:05 vbellur joined #gluster-dev
19:06 vbellur joined #gluster-dev
19:34 msvbhat joined #gluster-dev
19:35 msvbhat_ joined #gluster-dev
19:46 vbellur joined #gluster-dev
19:47 vbellur joined #gluster-dev
19:47 vbellur1 joined #gluster-dev
19:48 vbellur joined #gluster-dev
19:49 vbellur joined #gluster-dev
19:50 vbellur joined #gluster-dev
19:50 vbellur joined #gluster-dev
19:51 vbellur joined #gluster-dev
19:52 vbellur joined #gluster-dev
19:53 vbellur1 joined #gluster-dev
19:54 vbellur joined #gluster-dev
20:23 vbellur joined #gluster-dev
20:27 vbellur1 joined #gluster-dev
20:51 msvbhat joined #gluster-dev
20:52 msvbhat_ joined #gluster-dev
21:16 vbellur joined #gluster-dev
21:44 msvbhat_ joined #gluster-dev
21:44 msvbhat joined #gluster-dev
22:08 glusterbot joined #gluster-dev
22:28 devyani7 joined #gluster-dev
22:45 msvbhat joined #gluster-dev
22:46 msvbhat_ joined #gluster-dev

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