Hacker Newsnew | comments | show | ask | jobs | submit | fjordan's comments login

Goagain by Richard Crowley is a great package that we are using for graceful restarts: https://github.com/rcrowley/goagain

EDIT: added author

-----


I found that it corrupts the FD by using this call:

https://github.com/rcrowley/goagain/blob/master/goagain.go#L...

Not sure why it happens though, but it led to all sorts of strange intermittent issues with broken connections.

Once I replaced this logic with passing files using GetFile().Fd() instead it started working fine, so beware of this. I still wonder why it happens though.

-----


Thanks for this.

Were you able to publish your changes either on a fork or in a PR?

-----


I ended up using different library:

https://github.com/gwatts/manners

But the code that extracts the fd without using reflection and access to the private properties is here:

https://github.com/mailgun/manners/blob/master/listener.go#L...

I think it should be fairly easy to port it to Richard's implementation

-----


CVE-2014-6271 was posted on the AWS Security Bulletin earlier today:

http://aws.amazon.com/security/security-bulletins/CVE_2014_6...

My guess is that they cannot rely on all users to perform these updates.

-----


can someone explain the downvotes?

-----


Already confirmed by AWS its not related. Confirmed in this thread its not related. That issue is an OS level problem, AWS won't touch your OS.

-----


On a related note, this book (http://www.treesmapsandtheorems.com/) is excellent.

The author approaches communication from the principle of Gestalt psychology and really helps one understand how our minds communicate.

-----


From the description it sounds as if this provides synchronous replication. How does this work in a WAN environment?

-----


Well, "synchronous replication" is used in a couple of ways here.

Tables can be designated as replicated or distributed (sharded). Replicated tables are typically fairly static. These are handled synchronously in the cluster on every datanode where the table resides. Actually, it first applies to a designated "primary" node, and upon completion, it will execute on the other nodes. The reason for this is to reduce the chance for deadlocks; if it succeeds on the primary, it has obtained all of the needed locks and we can be sure we can then get the locks on the other nodes.

In addition, the term synchronous replication is also used as in PostgreSQL's replication, but in Postgres-XL for a datanode having a standby replica, synchronously. It is a warm, non-queryable standby.

With regards to a WAN environment, Postgres-XL is not designed for that because of the latency, and for handling long network outages. If there is enough interest, that could be an area to enhance in the future, but consistency may be compromised.

-----


I didn't get replication out of the description. It sounded more like distributed storage and load. Notice they say "warm-standby" for data nodes. I can only think of one reason anybody would resort to STONITH for something like this.

-----


If not UML, what do you recommend for most effective communication?

ERDs? Documentation tools? Or do you simply tell the engineer to read the code?

-----


Yes, just read the code (and whatever textual documentation comes along with it). The best I can hope for is a set of OO interfaces that is really well-described in their comments. And some oral presentation/walkthrough. And some small tasks to get me acquainted with a new codebase. If there's a large library, some HTML-based documentation, perhaps even with examples, is very fine.

-----


rewardStyle, Full-time - Dallas, TX - (https://www.rewardstyle.com/)

Engineers in rewardStyle's product development team are responsible for developing key features for rewardStyle's state-of-the-art web and mobile applications and services. Developers on any part of the stack are encouraged to apply (front-end, back-end, middleware).

rewardStyle's international platform presents a number of challenges that require intimate understanding of distributed web architectures and load balancing, synchronous and asynchronous database clustering and replication, algorithms, data structures, JavaScript development and libraries, DOM layout and styling, as well as network security protocols and intrusion detection.

To qualify for this position, please present an example of your work that would demonstrate your engineering skills to dev.jobs@rewardstyle.com

-----


rewardStyle, Full-time - Dallas, TX - (https://www.rewardstyle.com/)

Engineers in rewardStyle's product development team are responsible for developing key features for rewardStyle's state-of-the-art web and mobile applications and services. Developers on any part of the stack are encouraged to apply (front-end, back-end, middleware).

rewardStyle's international platform presents a number of challenges that require intimate understanding of distributed web architectures and load balancing, synchronous and asynchronous database clustering and replication, algorithms, data structures, JavaScript development and libraries, DOM layout and styling, as well as network security protocols and intrusion detection.

To qualify for this position, please present an example of your work that would demonstrate your engineering skills to dev.jobs@rewardstyle.com

-----


This, in addition to the increase in traffic we detected directly before, smells of DOS. Also, it is Friday the 13th.

-----


We are able to reach some servers but not all in our us-east AZ and notice it seems to be random.

-----


Maybe someone from GitHub can tell us.

I'm having a difficult time reasoning as to the motivation behind all the DDOS attacks. Why would anyone want to disrupt a tool for open, public collaboration used by many free and open-source technologies.

Anyone have any insight?

-----


Github.com is a profitable entity that makes a fairly large amount of money. Additionally, Github.com hosts a lot of content. Content that other people may not like.

Possibilities are: 1) Extortion of some sort i.e. We want your money, or we'll DDoS you every week 2) Content i.e. Remove repositories a, b, and c with content we don't like, or we'll DDoS you every week 3) Weapons demonstration i.e. We want to show off what l33t hax0rs we are, so we'll DDoS Github.com every week

-----


Do they not have the bandwidth or resources to stop or mitigate something like this from happening? I would've thought they'd have better resources in place in case of something like this.

-----


Just a theory, but perhaps some hackers trying to flex their muscles and stroke their ego's by taking down GitHub.

-----


Would make sense. Saw a bunch of that at the Rio during defcon. Print my boarding pass? Nope. Somebody broke all of the machines. Order a movie or checkout on the TV from my room? Nope. Someone broke the outdated system.

Tools gonna tool.

-----


To a degree this is pretty funny. Are you sure the hotel didn't do it on purpose just to remove the opportunity for hackers to get over on the hotel?

-----


Yes. These systems weren't disabled, they were broken.

Not trying to be a buzkill, but I fail to see how it's funny. So you can break an old - undoubtedly unpatched - win xp box that people use to print boarding passes. Congrats.

-----


> Why would anyone want to disrupt a tool for open, public collaboration used by many free and open-source technologies

and a lot of closed source commercial projects.

-----

More

Guidelines | FAQ | Support | API | Lists | Bookmarklet | DMCA | Y Combinator | Apply | Contact

Search: