chucky_z

I believe those are the direct rottentomatoes.com "User" scores. So aggregated from a large population of users for rottentomatoes.com; I would consider that to be a pretty good representation of the average American population who uses the internet.

When I was fresh with Gluster, I was blindly following tutorials for how to fix a split-brain. Backstory: I inherited this, so I had to fix it as quickly as possible.

Basically, you can mount individual bricks in /tmp and run a 'forcefully fix this split brain.'

I left this running to let things get happy overnight in a screen. The following morning every single file was gone.

I had left a tmpwatch on /tmp to remove all files in /tmp after a certain point in time. We had a backup, but it was a few days old. That was a fun weekend.

It is the worst feeling in the world, and one that I'll never make again... at least like that.

What's the best way to deal with this problem, and what's the correct way to deal with this problem?

The C-Max is a very utilitarian vehicle. It's more Mazda 5 than Volt/Prius.

That being said, they sure do have a nice interior for that style of car!

Was the ElastiCache service around when you migrated Redis to Dynamo? This is another alternative I'm considering.

I think in this case I could have interchanged "terrible" with "enterprise" and it would've had a more ""correct"" meaning (seriously I wish I could keep adding quotes to all of that...). I had to fight and argue with the previous host (Rackspace) to get them to lower our prices. It also took weeks to deploy a server. Now it takes 5-25 seconds with a prebuilt AMI that I've cooked together, deployed on exactly the hardware that I want, with the network configuration that I setup, and the security rules (bi-directional! Rackspace firewall only offers inbound at the level we had) that I want/need. On top of this, to get lower prices, I open a ticket and say "Hello, I'll be needing this server for 1 year, lower prices please." No phone calls involved. I'm not trying to diss Rackspace, they seem to be doing a lot of cool things... I simply had a permanantly sour taste left in my mouth. AWS is a big juicy BBQ sandwich in comparison.

On your points about AWS itself I'm not going to argue with as they certainly are valid, however in my specific setup (everything production is c4/r3 types, 1tb gp2 volumes as all volumes, and running network benchmarks to ensure everything is properly sized) I've actually had a pretty big performance gain over dedicated servers in a DMZ behind a hardware firewall.

With regards to the bandwidth, it seems a common issue is when you have very chatty services (Apache Kafka) deployed across multiple AZ's the bill gets real big real fast. Thus far, we're not even cracking 3-digits in bandwidth monthly. Maybe we're simply not at a scale to notice these problems yet.

Have you looked at Terraform? I have everything defined (unless it doesn't work very well... which still happens as it's still under heavy development), and if it needs to be dealt with care (e.g.: core EC2 instances) I'm slowly filtering it into a separate set of units/variables, and setting the "static" infrastructure (VPC) as a downstream group, and slurping the statefile upstream as to not potentially damage anything when playing nice with deploying/redeploying EC2 instances.

I simply don't believe the $250 - $20,000 month comparison. Could you please provide some real-world numbers/hardware/stack information?

I just did this migration (non-AWS -> AWS), and we saw a ~20% reduction in monthly prices with 1-year contract at AWS vs. physical hosting (admittedly we were getting terrible pricing with our physical hosts, but still). This will be reduced with the addition of t2.nano servers as we run enough t2.micro instances for little odds and ends that it will put a dent in the bill.

What about as a kind of Redis stand-in? I'm curious about the DynamoDB PHP session driver.

It sounds like you have a lot of experience with Dynamo. All the use-cases I seem to keep coming up with are more for storing global environment keys outside of the environment itself and using a large number of IAM roles to access individual keys, and as a kind of throwaway 'I need to store this somewhere, but it doesn't really fit in the main DB, and I still need it to persist for at least awhile' case.

This looks interesting, and I'd like to read the article more, but the graphs are so eye-drawing and completely unreadable that I'm unable to make sense of them. Please make your x/y readable (font roughly 200% larger...) and actually label which line is which.

Also to provide some article-related input, in some NoSQL style databases latency makes a very surprising difference in speed. Redis is especially affected. When network latency is introduced on even the 50ms level GET/SET operations drop to double digit (vs. 15k+/s in normal operation even on small servers)

I can only compare Ansible to Puppet, but I've had great success with rewriting a ton of hacky bash stuff directly in Ansible and having it feel much more 'maintainable.'

Perhaps if you're already using puppet/chef/salt it's not completely worth it to just suddenly switch to it, but it does feel "simple" to use; in my opinion it's worth use over Puppet solely due to the fact that you can really crank up the errors and get good messages.

Actually, one of my friends on Facebook saw that I was job hunting and offered me an interview. :/

I've gotten all of my best (and last few) jobs through connections, fortunately for me, and maybe unfortunately for me giving advice on how to get a job.

I'm specifically in the sysadmin/dba (and a little devops-y) side of things, and less in programming.

I was going to mention this exact same thing. The last time I had to go job hunting I submitted my resume to 40-50 companies each week or so, and unless I heard anything back ever, I did zero research outside of seeing if what they were looking for matched what I wanted to apply for.

Please refer to the #postgresql channel on irc.freenode.net for any postgres inquiries, you will receive an answer from experts and core developers on the correct processes within minutes for almost any question. It is a very active channel full of knowledgeable folks.

I think his hostility comes from the fact that if you google just "postgresql json" the second hit is the official documentation that goes over jsonb right in the second paragraph.

http://www.postgresql.org/docs/9.4/static/datatype-json.html

You can also see that the very first link outside of the official documentation:

https://www.compose.io/articles/is-postgresql-your-next-json...

Explains the benefits of jsonb and how to use indexes.

If you're going to include a database, at the very least do 20 minutes of research on it. If that can't be given, then just don't include something.

That's like saying "I've just installed MongoDB and read the intro documentation page, I'm now going to benchmark it against a MySQL cluster, which I have years of experience with, and that I helped develop." (E.g.: they developed ArangoDB, so they should be experts in at least that, right?)

I think I'd argue against Sharepoint simply because of the investment and vendor lock-in required. You do have an extremely solid point about Google Apps at the bottom end because of this exact reason though.

I only wish the O365 platform was more stable. I had endless issues when I tried to setup a paltry 50 accounts from a different managed Exchange platform. We ended up with using the Office products using the O365 license (cost of 2013/2015 products was far too high to justify individual licenses), but switching Exchange back to the previous provider.

Also, when it comes to high availability, there isn't much that can beat the ease of SQL Server's HA solutions. I personally greatly prefer PostgreSQL over everything, but there is no doubt in my mind that MSSQL is a solid platform.

Unless every single employee actually follows this clause, just one bad apple can ruin every security procedure in the world. Layer 8 is awfully vulnerable...

I do as well, and while looking around for laws about it I stumbled across this:

http://www.wsj.com/articles/SB100014240527023038478045794799...

and a few articles like it. It seems the laws aren't well enforced though (probably for the better).

Perhaps the author is dyslexic, and wanted an easy to read font? As far as I know, Comic Sans is the only font that is easy to read for dyslexic folk that works in about every graphical web browser.

I would say you can park in Palo Alto in an RV for free... but it looks like that's changed in recent history. Kind of sad! :(

I had written a large chunk but removed it after reading most of the article. I will go out on a limb and simply comment that I felt the interview where I'm currently at was done correctly, and addressed most of the issues that this article raises. As a note, I was hired as a sysadmin/dba/devops for a smallish startup.

They brought me in for a total of ~20 hours of interview, and in that time I discussed work-related topics with every single C-level. I went through a standard interview with questions, and then a longer skill test that included every current engineer at the company.

For the last few hours they paired me up with a current engineer to work on some database issues they'd been having.

I've been very happily employed here now for around 7 months, and after adding this company to my resume I've had quite a lot of offers on LinkedIn. I feel nothing other than "Oh, this company has offered me an interview, that's really cool!" towards these offers.

I think it's one of the best things in the world to have that feeling, and I wish everyone who was hired in an engineer position felt the same way.

This test 'cheats' in favor of HTTP 2.0. The problem is that there are ways around the HTTP 1.1 limitation of 'one connection, one thing,' and this test uses absolutely none of those ways. It makes a connection, receives an image, closes a connection, opens a connection, receives an image,... 200 times.

The HTTP/2 test does exactly what it's designed to do: opens a lot of connections and receives the images pretty much all at once.

This isn't to downplay HTTP/2, but it's something that should be noted for _this_ test.

As an interesting perspective, I don't know a single person who pirates any JetBrains software. All the programmers I know use their software exclusively and pay for it.

I can name many people who pirate all sorts of video production, 3d, and 2d art programs.

As for myself, maybe I'm a curmudgeon, but I try to avoid paid software at all costs. I used Sublime Text briefly, but switched back to vim when I found a good combination of plugins (caveat: I do little programming).

server-side as in... shell scripts/daemons?

or server-side as in... cgi/fastcgi serving to a client?

because I would say 'yes' to cgi/fastcgi, but 'no' to shell scripts/daemons.

There are a handful of really cool newish Perl frameworks, but unfortunately I think Perl 5's stigma is so far out there it will never gain any real traction. It seems that Perl 6 has a lot of the same stigma attached to it. I almost wish they would name it something other than Perl so that a fresh perspective could be used, it seems like it's going to be quite nice!

I'm going to restrict myself to official documentation here as much as possible....

How to dump things to any file the correct way using the postgres COPY command: http://www.postgresql.org/docs/9.4/static/sql-copy.html

Stored procedures: http://www.postgresql.org/docs/9.4/static/plpgsql.html (ok, this one is a bit big... but PL/pgSQL is damn powerful)

Clustering is a topic that lives outside PostgreSQL, there are some helpful posts on the wiki though: https://wiki.postgresql.org/wiki/Replication,_Clustering,_an...

https://wiki.postgresql.org/wiki/Clustering

Failover: http://www.postgresql.org/docs/9.4/static/warm-standby-failo... ( You should really read all of this though: http://www.postgresql.org/docs/9.4/static/high-availability.... )

Recovering from a crash: This is a difficult topic. There isn't a great single page in the documentation, but essentially it just replays x-logs (from what I remember last, this may have changed), and if you lose them, there are a number of options. pg_restore from a backup, use this: http://www.postgresql.org/docs/9.2/static/runtime-config-dev.... the list is pretty long for options.

Thanks for pointing me to Racker (https://github.com/aspring/racker). I'm currently building Packer and Terraform images with chunked together Python scripts that work, but I wouldn't call them a great solution. I'm actually using Packer specifically so I can start with regular EC2, and then move to a more Docker-based infrastructure.

I believe Docker's biggest feature is it's speed of building. It's a trade-off of portability vs. temporary-ness.

I currently use it for MySQL DB restoration and remote bug-checking by having a handful of xtrabackup instances that I can quickly attach a docker to, hand an IP to a developer, and he can then debug the problem with production data _at that exact point in time._

When they're done, I simply throw that docker away.

It's a tool that (in my mind) doesn't solve any existing problems better than a lot of tools out there. It instead should be thought of like a better hammer for the same nail. Think of it like... would you rather have a giant set of wrenches, or a single ratchet with a set of sockets? They both accomplish the same thing, but both are better for certain jobs.

For those curious... click through the entire thread with thread-next>.

You'll be rewarded with some really great discussion!

Check out the pie chart...

https://wiki.postgresql.org/wiki/Category:Fun_Snippets

The Mandelbrot is awesome, but the pie chart is some next level stuff. You can even make it colored.

Interesting. I got around this by just recreating the users file for pgbouncer and issuing a reload every 15 minutes or so. This was only needed for one setup as the rest were just static, or the user was very low volume so I asked them to connect directly. pgbouncer handled reloads very well (on-par with nginx) so it worked for me. Thanks for the great insight with your answer.