Perl 6 - the future is here, just unevenly distributed

IRC log for #gluster, 2017-02-12

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

All times shown according to UTC.

Time Nick Message
00:45 Wizek joined #gluster
00:51 farhorizon joined #gluster
01:09 FiveBroDeepBook joined #gluster
01:09 FiveBroDeepBook left #gluster
01:31 alvinstarr joined #gluster
01:56 arpu joined #gluster
02:05 phileas joined #gluster
02:08 pjrebollo joined #gluster
02:19 derjohn_mob joined #gluster
02:55 farhorizon joined #gluster
03:10 phileas joined #gluster
03:11 MadPsy left #gluster
03:28 bluenemo joined #gluster
03:29 cacasmacas_ joined #gluster
03:31 cacasmacas joined #gluster
03:32 nirokato joined #gluster
03:37 riyas joined #gluster
04:56 farhorizon joined #gluster
05:06 shutupsquare joined #gluster
05:08 BitByteNybble110 joined #gluster
05:56 FiveBroDeepBook joined #gluster
05:56 FiveBroDeepBook left #gluster
06:00 susant joined #gluster
06:20 susant left #gluster
06:57 Guest28184 joined #gluster
06:58 farhorizon joined #gluster
06:58 cacasmacas joined #gluster
06:58 cacasmacas joined #gluster
07:04 cacasmacas joined #gluster
07:07 pjrebollo joined #gluster
07:27 susant joined #gluster
07:56 Gnomethrower joined #gluster
07:59 musa22 joined #gluster
08:10 cacasmacas joined #gluster
08:11 niknakpaddywak joined #gluster
08:13 cacasmacas joined #gluster
08:14 jiffin joined #gluster
08:22 shutupsquare joined #gluster
08:28 jiffin joined #gluster
08:33 riyas joined #gluster
08:35 susant joined #gluster
08:36 Wizek joined #gluster
08:44 Wizek joined #gluster
08:57 jiffin joined #gluster
08:59 jiffin1 joined #gluster
08:59 farhorizon joined #gluster
09:00 cacasmacas joined #gluster
09:12 jiffin1 joined #gluster
09:14 susant left #gluster
09:32 Gnomethrower joined #gluster
09:42 Wizek joined #gluster
09:47 susant1 joined #gluster
09:59 nthomas joined #gluster
10:05 k4n0 joined #gluster
10:32 rjoseph joined #gluster
10:37 cacasmacas joined #gluster
10:41 shutupsquare joined #gluster
10:54 susant joined #gluster
11:01 farhorizon joined #gluster
11:02 arif-ali joined #gluster
11:05 shutupsquare joined #gluster
11:39 susant joined #gluster
11:47 pulli joined #gluster
11:47 k4n0 joined #gluster
11:55 mannol joined #gluster
11:56 mannol hello
11:56 glusterbot mannol: Despite the fact that friendly greetings are nice, please ask your question. Carefully identify your problem in such a way that when a volunteer has a few minutes, they can offer you a potential solution. These are volunteers, so be patient. Answers may come in a few minutes, or may take hours. If you're still in the channel, someone will eventually offer an an
11:59 mannol quick question: when using POSIX read() on a file which is served in a distributed FS is it going to block until some data is available or is it going to return with an error (assuming FD is created as a blocking FD)?
11:59 mannol i'm new to distributed FS and i consider using gluster for our product
12:00 yoavz joined #gluster
12:03 jwd joined #gluster
12:04 FiveBroDeepBook joined #gluster
12:04 FiveBroDeepBook left #gluster
12:05 pjrebollo joined #gluster
12:15 Gnomethrower joined #gluster
12:24 sbulage joined #gluster
12:30 pulli joined #gluster
12:50 shutupsquare joined #gluster
13:25 mhulsman joined #gluster
14:06 ndevos mannol: yes, it will block, similar as how things happen on 'normal' network filesystems
14:08 mannol ndevos, so i should treat read() and write() as i would normally treat a socket read&write ?
14:11 gyadav joined #gluster
14:53 ndevos mannol: treat it as a (slow) filesystem
14:54 mannol thanks
14:54 ndevos mannol: also make sure you catch any errors as you would do for read/write on NFS
15:02 gyadav joined #gluster
15:50 riyas joined #gluster
15:55 siel joined #gluster
16:02 jwd joined #gluster
16:23 sona joined #gluster
16:24 FiveBroDeepBook joined #gluster
16:24 FiveBroDeepBook left #gluster
16:43 cacasmacas joined #gluster
16:44 shutupsquare joined #gluster
16:46 jkroon joined #gluster
16:52 FiveBroDeepBook joined #gluster
16:53 FiveBroDeepBook left #gluster
17:25 nh2 joined #gluster
17:26 cacasmacas joined #gluster
17:33 musa22 joined #gluster
17:45 nh2 I noticed that glusterfsd seems to use only 6 OS threads to make open() syscalls, and am suspecting that this might be the bottleneck for me when writing small files. Does anybody have insight how many treads gluster should use?
17:46 Humble joined #gluster
17:56 sona joined #gluster
18:03 bluenemo joined #gluster
18:03 jkroon joined #gluster
18:08 mhulsman joined #gluster
18:09 jkroon joined #gluster
18:12 cacasmacas joined #gluster
18:16 musa22 joined #gluster
18:17 musa22 joined #gluster
18:39 ahino joined #gluster
18:45 mhulsman joined #gluster
18:46 jwd joined #gluster
19:02 yoavz joined #gluster
19:10 zakharovvi[m] joined #gluster
19:40 f0rpaxe joined #gluster
20:29 derjohn_mob joined #gluster
20:31 mannol joined #gluster
21:01 DV joined #gluster
21:04 musa22 joined #gluster
21:34 i64 joined #gluster
21:44 i64 joined #gluster
21:46 i64 Hello, I have a quick question. Is glusterfs write intensive on the nodes system disks? (apart from logs). And is the system disks preformance a bottleneck for the cluster speed?
21:47 i64 The point being, can I run glusterfs nodes with SD cards as system disks?
21:52 k4n0 joined #gluster
22:02 Vapez joined #gluster
22:02 Vapez joined #gluster
22:12 bbooth joined #gluster
22:14 gem joined #gluster
22:24 Limebyte WAAAAAAA
22:24 akay_ joined #gluster
22:26 cacasmacas joined #gluster
22:57 vbellur joined #gluster
23:03 cacasmacas joined #gluster
23:06 nh2 joined #gluster
23:55 nh2 i64: I'm no expert, but from a quick strace on my glusterfsd it seems like all writes that show up there go to your brick disk, not to the system disk

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