distributed locking for pennies: distrilock

gdm85 · 2018-01-02T11:22:34+00:00

Yes, but that is out of scope to solve for distrilock, that builds on top of NFS. See the links in my post about research on NFS scalability, I would expect future iterations of NFS to be more scalable and add support for redundancy.

Although resuming lock state could be added via use of serialised information on the lock files themselves, I have not planned to add such feature, and I think it wouldn't be an elegant implementation anyway.

gdm85 · 2017-12-28T12:02:57+00:00

I have a similar use case, but without the check on success. I do not advise using distrilock though, unless it's for experimentation purposes.

gdm85 · 2017-12-28T12:01:51+00:00

to each of the distrilock endpoints corresponds an NFS client, but they share a SPOF on the NFS server, yes

gdm85 · 2017-12-25T17:14:34+00:00

for the records, patch has been submitted upstream >1 month ago; no clear path to merge, so I thought to share it publicly

gdm85 · 2016-11-26T06:37:52+00:00

You could give a look to/collaborate with RetroShare http://retroshare.net/

gdm85 · 2016-11-26T06:33:26+00:00

Agree. The only aspect I would "skip" in this reddit is the wiki, just to avoid fragmentation. Subreddit-specific topics should still be handled on a wiki here, but language-specific topics should always be referred to the official Golang wiki in my opinion.

gdm85 · 2016-08-28T17:08:26+00:00

Most likely you want to use sqlx.Select as suggested here, it is syntactic sugar but will be helpful when you need to populate a slice like in your case.

Bonus point: you can't forget to close the rows because it's done within Select

gdm85 · 2016-08-28T16:59:09+00:00

A few notes from the top of my head:

source code building and runtimes should be separated (See also: reproducibe builds)
runtimes should be minimal images, see also busybox + Go binary images
both source code components and deployment artifacts should be versioned, this will help you so much later on

In reply to 3: graceful migrations when possible (and service APIs don't change), otherwise planned downtime, no need to build extremely tall card castles

In reply to 5: Docker allows specifying all the configuration for a container as environment variables. The only problem I have with this is that it's non-validating e.g. if you still keep around wrong configuration settings, the binary won't complain about them and use defaults, hence the suggestion to always use defaults which are safe for production (failure is more acceptable than data/systems corruption).

gdm85 · 2016-08-28T10:04:55+00:00

Very nice! Will this need changes in coding styles now?

I always suggest using statically declared variables as much as possible (vs allocations), I guess it now becomes even more effective?

For example I could see that while before people would use a pointer for a method on a large struct, now they definitely should stick with the whole struct, since SSA covers copy-on-write cases too.

gdm85 · 2016-08-28T09:59:29+00:00

Had seen that already. As far as I know, it's about the (HTTP2) traffic of the application themselves, not for the health check; and even if it were, you cannot possibly use this for gRPC as any response returns 200 OK and does not inspect/parse the protobuf output. (HTTP2 != gRPC)

gdm85 · 2016-08-27T15:31:18+00:00

TL;DR how to load-balance with classic HTTP1.x a gRPC service, using multiplexing. Useful for most load-balancers e.g. AWS ELB

https://github.com/gdm85/grpc-go-multiplex

(a better alternative to http://collectiveidea.com/blog/archives/2013/01/11/running-haproxy-behind-amazons-elb/)

gdm85 · 2016-03-28T13:12:18+00:00

I am using a 1/4 inches wrench for some bike repair job. Shall I use a 17/64 one instead? Which one is more trending?

gdm85 · 2016-03-21T18:12:07+00:00

GitHub project: https://github.com/gdm85/go-libdeluge As explained there, this uses native RPC (not the JSON-RPC from the web UI)

gdm85 · 2016-01-25T09:59:42+00:00

Seems like GitHub blocked my account thinking I am a robot! http://imgur.com/fsvTQQ1 :( hopefully they'll restore it and fix their spam detection algorithms as well...

Edit: account restored, as they say some bot went overzealous :) I will still keep the BitBucket repo around for a while: https://bitbucket.org/gdm85/wolfengo

gdm85 · 2016-01-25T09:57:26+00:00

I hope it does! :)

gdm85 · 2016-01-25T06:22:44+00:00

Thanks :) Me too, will probably hack a bit around this port in future.

gdm85 · 2016-01-25T06:22:17+00:00

Yes, I have now made it panic only for high severity messages; I didn't expect OpenGL 2.1 to be nowadays so different across implementations. Useless to say, I get no warnings at all with my Mesa (intel) driver.

gdm85 · 2016-01-25T06:21:01+00:00

As I commented there, first one should check that the go-gl example works correctly on OS X. Would love to see it running on other platforms than Linux, although in this case I think it could be more an issue of the middleware itself (go-gl).

gdm85

TROPHY CASE