Perl 6 - the future is here, just unevenly distributed

IRC log for #gluster-dev, 2016-12-20

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

All times shown according to UTC.

Time Nick Message
00:19 hchiramm joined #gluster-dev
00:47 asriram|mtg joined #gluster-dev
01:12 lpabon joined #gluster-dev
02:13 asriram|mtg joined #gluster-dev
02:15 purpleidea kshlm: btw in case you didn't see it: https://github.com/gluster/glusterd2/pull/197
02:48 ilbot3 joined #gluster-dev
02:48 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:55 nishanth joined #gluster-dev
02:58 rafi joined #gluster-dev
03:13 nbalacha joined #gluster-dev
03:19 pranithk1 joined #gluster-dev
03:24 msvbhat joined #gluster-dev
03:30 magrawal joined #gluster-dev
03:31 mchangir joined #gluster-dev
03:34 ankitraj joined #gluster-dev
03:45 pranithk1 joined #gluster-dev
03:49 riyas joined #gluster-dev
03:57 purpleidea pranithk1: yo wazzup?
04:08 mchangir joined #gluster-dev
04:08 kdhananjay joined #gluster-dev
04:11 itisravi joined #gluster-dev
04:12 pranithk1 joined #gluster-dev
04:26 kotreshhr joined #gluster-dev
04:27 mchangir joined #gluster-dev
04:31 Shu6h3ndu joined #gluster-dev
04:34 pranithk1 purpleidea: lots of work :-D
04:34 purpleidea yeah i feel that
04:35 pranithk1 purpleidea: :-)
04:35 purpleidea i'm in your tz again, and fighting with a bug :P
04:36 pranithk1 purpleidea: okay bug smasher!
04:36 purpleidea pranithk1: you going to be around in blr 2nd week of feb?
04:38 pranithk1 purpleidea: If you come to India I will make sure to
04:38 purpleidea there is a certain chance of it
04:38 purpleidea not confirmed yet
04:39 pranithk1 purpleidea: Try to stay and extra week. I stay alone. You can stay an extra week in my house. There are lots of places to see
04:39 pranithk1 purpleidea: If you have anything specific in mind about visting... send me a mail
04:39 purpleidea pranithk1: i appreciate the offer! will keep this all in mind.
04:39 jiffin joined #gluster-dev
04:41 pranithk1 purpleidea: Please make plans and come. There is lot of time :)
04:42 purpleidea pranithk1: if i can i will :) gotta write more code first, the idea is to do a bit of hacking on glusterd with ppai and kshl perhaps!
04:42 purpleidea pranithk1: which subsystem/part have you been working on lately?
04:43 pranithk1 purpleidea: Try staying a bit extra days... You should see mysore, where kshlm is from. You can also visit Kerala and also north India perhaps
04:43 purpleidea pranithk1: although i think it would be pretty awesome if you, et al. came here, we've got lots of snow atm :)
04:43 pranithk1 purpleidea: I have been working on replication/erasure coding
04:43 purpleidea ou, hard things!
04:44 pranithk1 purpleidea: ah! let's see. I don't think folks here have much work in Canada :-P
04:44 purpleidea hehe, did you see this: https://twitter.com/purpleid​ea/status/805838222139990016 ?
04:47 pranithk1 purpleidea: based on that I guess I should say I don't want to come to Canada at this time and die :-P
04:47 pranithk1 purpleidea: okay dude, I need to start for office. Just found a fix for some bug....
04:47 purpleidea pranithk1: cool, i gotta hack too! later!
04:47 pranithk1 purpleidea: Do plan and tell me, I will ping next week or something when things should be in a bit saner state...
04:47 pranithk1 purpleidea: ciao!
05:00 msvbhat joined #gluster-dev
05:01 kdhananjay joined #gluster-dev
05:04 kdhananjay joined #gluster-dev
05:11 nbalacha joined #gluster-dev
05:13 rafi joined #gluster-dev
05:13 skoduri joined #gluster-dev
05:14 susant joined #gluster-dev
05:17 gem joined #gluster-dev
05:23 sanoj joined #gluster-dev
05:24 purpleidea kshlm: we can pair program on it if you want...
05:27 prasanth joined #gluster-dev
05:27 kshlm purpleidea, I'm just trying to get it to compile. Should be easy enough.
05:27 purpleidea cool
05:28 purpleidea kshlm: i think it was due to the stuff using the existing etcdmgmt package.
05:29 ppai joined #gluster-dev
05:30 kshlm Yeah. I had to restore that package, and add mgmt to glide.yaml.
05:31 aravindavk joined #gluster-dev
05:42 kshlm purpleidea, I have a problem. `mgmt/lib` imports basically all the rest of mgmt and I'm failing compilation on `mgmt/resources`
05:43 purpleidea kshlm: error?
05:45 kshlm https://gist.github.com/a86c​e1fb473662232f615737a27ba899
05:46 purpleidea kshlm: your vendor dir is missing something that is currently being tracked in the mgmt dir. most likely it's due to the purpleidea/go-systemd vendored dep.
05:47 kshlm Hmm, glide should have detected the dependency.
05:48 ankitraj joined #gluster-dev
05:49 ankitraj joined #gluster-dev
05:50 purpleidea kshlm: pretty sure that's the issue
05:50 sanoj joined #gluster-dev
05:51 kshlm purpleidea, What vendor tool do you use, if any?
05:51 kshlm If not would you be willing to use one?
05:51 purpleidea kshlm: i hate vendor tools, so i actually just use git submodules in the vendor dir. There are some tools that do this for you.
05:52 mchangir joined #gluster-dev
05:52 purpleidea kshlm: note, only the minimum of what's really required to be vendored is vendored in mgmt. ideally we're using git master and staying fresh.
05:52 purpleidea atm anyways
05:55 kshlm Submodules...they don't appear to be automatically pulled by glide.
05:55 purpleidea :(
05:55 kshlm And I'm not a fan of bundling source code in vendor/.
05:55 purpleidea for our WIP branch, just cp -a * it all into your vendor, but don't commit it.
05:56 kshlm That'll work for now. But we need to find a solution to this sooner or later.
05:56 kshlm BTW, I've never checked, but does `go get` fetch submodules?
05:57 purpleidea kshlm: i agree about not bundling source in vendor/ ... i thought you had zero vendored deps for glusterd2
05:57 purpleidea iirc, no?
05:57 purpleidea git submodule init
05:57 purpleidea git submodule update
05:57 purpleidea should do it
05:57 kshlm purpleidea, We're vendoring using glide (https://glide.sh).
05:58 kshlm Our vendor packages are added to glide.yaml
05:58 purpleidea why are there so many things vendored in there?
05:59 purpleidea (or rather is it only things that have "version" specified that are?)
05:59 kshlm The ones that have version specified are pinned to the version.
06:00 purpleidea why do the others have to be listed then?
06:00 purpleidea (if we're assuming it uses git master for those)
06:00 kshlm The rest are pinned to the git master at the time `glide get` or `glide update` was done.
06:01 kshlm This ensures all devs are at the same versions of all dependencies when developing.
06:01 purpleidea are the other packages that don't specify a version using git master or the specific commit of git master when it was first added?
06:01 kshlm The glide.lock file has the actual pinned versions of all dependencies, including recursive dependecies.
06:01 purpleidea (iow it looks like the lock file mentions specific commits)
06:01 purpleidea yeahg
06:02 hgowtham joined #gluster-dev
06:03 purpleidea kshlm: so maybe it's slightly off-topic for todays discussion, but i am strongly against all this pinning unless it's crucially necessary. Why? This isn't a prod read project atm. So it's better that as each dep git master evolves we have small breakages (if at all) instead of major breakages everytime we want to move everything forwards.
06:03 karthik_us joined #gluster-dev
06:03 purpleidea prod ready*
06:08 skoduri joined #gluster-dev
06:09 kshlm purpleidea, This works better for us from experience.
06:09 kshlm We had a hard time with people fighting with fast changing dependencies like protobuf.
06:10 kshlm This helped avoid those changing targets.
06:12 purpleidea kshlm: as you like, it's your proj, you should run it how you want. I only vendored etcd and protobuf/grpc stuff and things that were broken. The rest should be at git master, IMO. But not vendoring all the other things has saved me a lot.
06:13 kshlm Let's leave this aside for now.
06:13 kshlm I just checked, go-systemd has been correctly detected and added to the vendor directory
06:13 kshlm But the build stil fails.
06:14 purpleidea kshlm: one example: https://github.com/purpleidea/mgmt/commit​/ab73261fd4e98cf7ecb08066ad228a8f559ba16a when they changed the API, it was a simple fix, instead of bumping all deps and having 20 fixes or more at the same time.
06:14 purpleidea kshlm: error | fpaste ?
06:14 purpleidea or gist or whatever
06:14 kshlm Still the same error.
06:15 purpleidea kshlm: probably not vendored correctly. go into your vendor/github.com/purpleidea/go-systemd/ and run git log | head -1
06:16 purpleidea what's the output?
06:16 kshlm Is it purpleidea/go-systemd?
06:16 purpleidea yeah
06:16 kshlm I'm looking at coreos/go-systemd.
06:16 purpleidea we've got a vendored copy of that with some extra patches that JoeJulian never finished getting into their git master...
06:17 kshlm I'm at 48702e0da86bd25e76cfef347e2adeb434a0d0a6
06:17 purpleidea kshlm: if you go into purpleidea/mgmt and type `git submodule` you should see:
06:17 purpleidea 6192533ebb4662c3bc0ce60c1d33dfc6702a1eac vendor/github.com/purpleidea/go-systemd (v13-13-g6192533)
06:17 kshlm Which is the current master.
06:17 purpleidea (and other things)
06:18 purpleidea there's your problem, we're using 6192533ebb4662c3bc0ce60c1d33dfc6702a1eac in our temporary fork
06:22 kshlm Head 6192533ebb4662c3bc0ce60c1d33dfc6702a1eac and branch machine1_support seem to be the same. But the branch has a different head commit-id.
06:22 purpleidea ???
06:22 kshlm https://github.com/purpleidea/go-systemd/comm​its/6192533ebb4662c3bc0ce60c1d33dfc6702a1eac
06:22 kshlm https://github.com/purpleidea/go-​systemd/commits/machine1_support
06:22 apandey joined #gluster-dev
06:22 purpleidea kshlm: if you want to just compile this, `rm resources/nspawn.go`
06:23 kshlm They look the same to me.
06:23 purpleidea kshlm: if they're the same, then it shouldn't matter.
06:23 kshlm brb.
06:23 kshlm But you've set master as the default head. So I'm pulling master.
06:23 kshlm brb again.
06:24 asriram|mtg joined #gluster-dev
06:25 purpleidea kshlm: i don't think so, vendored branch is: https://github.com/purpleid​ea/go-systemd/tree/feat/wip which is that 6192... sha1id
06:27 asengupt joined #gluster-dev
06:28 Saravanakmr joined #gluster-dev
06:29 kshlm purpleidea, Cool. I'm adding purpleidea/go-systemd at feat/wip to glide.yaml.
06:29 kshlm That fixes it.
06:30 purpleidea w00t :)
06:30 purpleidea more interestingly, does everything build and do what you want now?
06:32 kshlm It builds.
06:32 kshlm The other stuff is still todo.
06:32 purpleidea okay
06:32 purpleidea cool
06:32 purpleidea i also had a thought today
06:32 purpleidea got 8 min for a ghangout?
06:33 kshlm let me get my earphones.
06:35 purpleidea bit.ly/purpleidea-ghangout
06:35 purpleidea https://bit.ly/purpleidea-ghangout
06:35 kshlm I'm on
06:35 purpleidea me too
06:35 hgowtham joined #gluster-dev
06:52 hchiramm joined #gluster-dev
06:53 asriram|mtg joined #gluster-dev
06:54 yonex joined #gluster-dev
06:59 penguinRaider joined #gluster-dev
07:01 pranithk1 joined #gluster-dev
07:01 hgowtham joined #gluster-dev
07:07 sanoj joined #gluster-dev
07:11 rastar joined #gluster-dev
07:21 ashiq joined #gluster-dev
07:45 hchiramm joined #gluster-dev
07:57 poornima joined #gluster-dev
08:12 kdhananjay joined #gluster-dev
08:14 nbalacha joined #gluster-dev
08:16 rraja joined #gluster-dev
08:25 mchangir joined #gluster-dev
08:45 rafi yonex: ping rafi here
08:52 gem joined #gluster-dev
08:55 yonex Hi! I joined.
08:58 aravindavk joined #gluster-dev
08:59 nishanth joined #gluster-dev
09:01 yonex found the brick log around disconnecting http://pastebin.com/2TZYgiiU
09:01 yonex rafi: It's enough?
09:05 rafi yonex: hey
09:05 * rafi is going through the logs
09:10 rafi yonex: thanks for the logs, I see the disconnect happened on around 15th dec, what happens after that ?
09:10 rafi yonex: is this consistent issue on your setup ?
09:11 gem joined #gluster-dev
09:15 msvbhat joined #gluster-dev
09:19 yonex rafi: Yes, it's consistent issue on my environment, happening a few times a day. This results in failure to move or copy a file from local storage to glusterfs volume.
09:21 yonex As I described there http://www.gluster.org/pipermail/glu​ster-users/2016-December/029424.html
09:32 rafi yonex: I tried to reproduce the issue in my setup
09:33 rafi yonex: but I was not successful with that
09:33 rafi yonex: I need your help very badly to fix this issue ;) I feel like this is something severe
09:34 rafi yonex: thanks for all your help so far
09:34 rafi yonex: is this your prodcution set up ?
09:40 yonex I appreciate your cooperation on such a severe issue :)
09:41 yonex rafi: Yes, it's on my production
09:43 rafi yonex: so I guess it would be very difficult to add more logs on that, which require upgrade to a custom build
09:43 rafi yonex: right ?
09:44 nbalacha joined #gluster-dev
09:48 yonex Ah.. yes it's difficult, but will it be for client? or server? If for client, it may be possible
09:51 ankitraj joined #gluster-dev
09:56 asriram|mtg joined #gluster-dev
10:13 rafi yonex: okey, so another idea is to use GDB script which will dump rpc content , basically i want to see the headers,
10:13 rafi yonex: which will not cause any downtime or any other effect to the cluster
10:15 rafi yonex: I can write a GDB script, so if you could attach the gdb with that script, then if the point hits it can dump some informations
10:15 rafi yonex: What do you say ? Is it possible ?
10:23 rkavunga joined #gluster-dev
10:26 hgowtham joined #gluster-dev
10:51 rkavunga joined #gluster-dev
10:57 yonex Sounds good. Let me talk about this with my team.
10:57 yonex rafi: How is a workload about that and how large is a additional dump (for example, compared to debug log)? Is it insignificant?
10:57 yonex rafi: I guess the script is for both of client and server, right?
11:02 atinmu joined #gluster-dev
11:02 ankitraj joined #gluster-dev
11:03 hgowtham joined #gluster-dev
11:21 rafi yonex: it is just like we use gdb, we don't want to stop the process when a we catch some code path, we will dump the data when we execute some commands
11:21 rafi yonex: so the plan is let gdb print some specific data values when it execute error path, to figure it out what cause the error case
11:22 rafi yonex: yes we can attach gdb to both client process and bricks
11:23 rafi yonex: only one client is enough and one brick but we should get a disconnect for that brick from the same client where we attach the gdb
11:24 ankit_ joined #gluster-dev
11:35 apandey joined #gluster-dev
11:36 poornima joined #gluster-dev
11:41 gem joined #gluster-dev
11:41 asriram|mtg joined #gluster-dev
11:45 ankit_ #info Bug Traige meeting in 15 min on #gluster-meeting
11:48 yonex rafi: OK, thanks. Though I'm not very familiar with gdb now, I will do it.
11:49 rafi yonex: I can assist you with that, I will write gdb script, then will give to you
11:49 rafi yonex: you can verify it and use it through gdb
11:50 rafi yonex: we can fix a time and can have a call or video chat if you have time
11:59 Muthu joined #gluster-dev
12:02 poornima joined #gluster-dev
12:06 mchangir joined #gluster-dev
12:16 karthik_us joined #gluster-dev
12:25 rafi1 joined #gluster-dev
12:28 rafi1 joined #gluster-dev
12:28 itisravi_ joined #gluster-dev
12:30 kotreshhr left #gluster-dev
12:30 itisravi joined #gluster-dev
12:51 karthik_us joined #gluster-dev
13:03 yonex joined #gluster-dev
13:05 Shu6h3ndu joined #gluster-dev
13:08 yonex joined #gluster-dev
13:10 susant left #gluster-dev
13:14 skoduri_ joined #gluster-dev
13:16 kdhananjay joined #gluster-dev
13:31 mchangir joined #gluster-dev
13:39 asriram|mtg joined #gluster-dev
13:43 atinmu joined #gluster-dev
13:46 rafi joined #gluster-dev
13:50 riyas joined #gluster-dev
13:51 dlambrig_ joined #gluster-dev
14:02 skoduri_ joined #gluster-dev
14:04 skoduri__ joined #gluster-dev
14:05 ira joined #gluster-dev
14:05 shaunm joined #gluster-dev
14:09 lpabon joined #gluster-dev
14:11 ankitraj joined #gluster-dev
14:13 Saravanakmr joined #gluster-dev
14:45 Saravanakmr joined #gluster-dev
15:04 nbalacha joined #gluster-dev
15:45 atinmu joined #gluster-dev
15:45 Shu6h3ndu joined #gluster-dev
15:59 wushudoin joined #gluster-dev
16:08 Acinonyx joined #gluster-dev
16:26 ankitraj joined #gluster-dev
16:33 susant joined #gluster-dev
16:35 gem joined #gluster-dev
16:35 skoduri__ joined #gluster-dev
16:36 shaunm joined #gluster-dev
16:50 dlambrig_ joined #gluster-dev
16:56 gem joined #gluster-dev
17:29 jiffin joined #gluster-dev
17:29 hchiramm joined #gluster-dev
17:29 gem joined #gluster-dev
17:53 jiffin joined #gluster-dev
18:16 JoeJulian purpleidea, kshlm: Right, because it became clear that they were not going to merge it.
18:20 gem joined #gluster-dev
18:28 jiffin joined #gluster-dev
18:34 ashiq joined #gluster-dev
18:42 rastar joined #gluster-dev
18:42 jiffin joined #gluster-dev
18:53 jiffin joined #gluster-dev
18:55 gem joined #gluster-dev
18:57 penguinRaider joined #gluster-dev
18:57 jiffin joined #gluster-dev
18:59 jiffin joined #gluster-dev
19:03 ashiq joined #gluster-dev
19:12 jiffin joined #gluster-dev
19:38 wushudoin joined #gluster-dev
19:39 jiffin joined #gluster-dev
20:09 gem joined #gluster-dev
20:35 gem joined #gluster-dev
21:02 dlambrig_ joined #gluster-dev
21:23 penguinRaider joined #gluster-dev
21:52 purpleidea JoeJulian: i thought with further fixes they would merge it?
22:06 kkeithley merge what?
22:49 JoeJulian purpleidea: They said they would have to give it more thought. Looking through their PR history, that means they'll ignore it forever.
22:49 JoeJulian kkeithley: coreos/go-systemd.
22:50 kkeithley ah
22:51 lpabon joined #gluster-dev
23:10 purpleidea JoeJulian: ack, yeah. Well eventually hopefully someone will take it up and massage it until it's mergeable :)
23:10 purpleidea JoeJulian: btw, did you see: https://github.com/purpleidea/mgmt/​blob/master/docs/resource-guide.md
23:10 purpleidea (comments appreciated!)
23:10 purpleidea patches too of course ;)
23:10 JoeJulian I did. Looks good to me.
23:11 JoeJulian I thought I gave it a :+1:, but maybe I was on my phone.
23:19 susant joined #gluster-dev
23:54 susant left #gluster-dev

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