If you read the source code it calls a method called get_all_keys. Please realize, this does NOT get all the keys in the bucket. Passed to it is the maxkeys=0 argument which means no keys are returned and a single list call is made.
Yes, it is still a waste of money, but just make sure you understand that it's not actually listing your entire bucket.
> Use random strings at the start of your keys.
> This seems like a strange idea, but one of the implementation details
> of S3 is that Amazon use the object key to determine where a file is physically
> placed in S3. So files with the same prefix might end up on the same hard disk
> for example. By randomising your key prefixes, you end up with a better distribution
> of your object files. (Source: S3 Performance Tips & Tricks)
This is great advice, but just a small conceptual correction. The prefix doesn't control where the file contents will be stored it just controls where the index to that file's contents is stored.
I'd also like to point out that it was placed there by local criminals, not the conference attendees. It was however discovered by the attendees and the hotel was notified and the offending ATM was turned over to police.
I would have to say in the majority of cases the answer is still no. Let's face it, when a group of people head out to the bars after conference hours there is plenty of networking going on. People form business relationships and friendships that continue after the conference. A female shouldn't have to choose to tolerate unwanted sexual advances simply to participate in these bonding experiences.
Thanks match, and I agree. You're still not just out at a bar with buddies, you're there with people you've met at a professional event and the professional context should still apply. I think match says it well:
>when a group of people head out to the bars after conference hours there is plenty of networking going on. People form business relationships and friendships that continue after the conference. A female shouldn't have to choose to tolerate unwanted sexual advances simply to participate in these bonding experiences.
Interesting question, let's try to compare the two events. The 2011 event involved roughly 13% of ebs volumes in the affected zone, including multi-az control plane impact, the 2012 event involved 7% of EC2 instances in the affected zone. These two events are different, since one was a power event and the other a network event, but let's see how they compare in number of impacted volumes. It's not exactly clear how to compare these numbers, but if you assume nearly all EC2 instances (7% were affected, were any EBS servers affected? possibly the same % or none or in between) have at least the boot volume and possible more attached then maybe that's roughly 7-10+% of the volumes in the affected zone. Assuming a respectable growth rate (http://huanliu.wordpress.com/2012/03/13/amazon-data-center-s...) these events may have been around the same size (I'd be curious to hear other arguments for/against this guess).
If you compare the recovery time (ballpark, feel free to break down the timelines in your copious amounts of free time):
2011:
12:47AM, Apr 21 - Event started, API impaired across all availability zones
12:00PM, Apr 21 - API recovered in non-affected zones
"Customers also experienced elevated error rates until Noon
PDT on April 21st when attempting to launch new EBS-backed
EC2 instances in Availability Zones other than the affected
zone."
12:30PM, Apr 22 - Nearly all volumes in affected zone restored
"all but about 2.2% of the volumes in the affected
Availability Zone were restored by 12:30PM PDT on
April 22nd"
18:15PM, Apr 23 - API restored for affected zone
"At 6:15 PM PDT on April 23rd, API access to EBS resources
was restored in the affected Availability Zone."
2012:
20:04, July 2 - Some number of racks lose power due to drained UPSs
21:10, July 2 - API restore
"8:04pm PDT to 9:10pm PDT, customers were not able to launch
new EC2 instances, create EBS volumes, or attach volumes in
any Availability Zone in the US-East-1 Region. At 9:10pm PDT,
control plane functionality was restored for the Region."
02:45, July 3 - Vast majority of volumes restored to customers
"By 2:45am PDT, 90% of outstanding volumes had been turned
over to customers."
Yes I'm painting with broad strokes here, and feel free to argue the details (we always do). But I do think this at least shows some improvement to answer the previous poster's question.
[edits to try to fix the formatting, fixed mis-paste]
This is an awesome answer, thanks so much for doing the research here. So although the time of outage was much shorter this time, what I'm concerned about was that they seem to have violated their "AZs are totally separate" claim again, which would point to a still-lurking fundamental problem. Happy to be corrected here if I'm wrong.
This is why I never make a judgment based on the answer of a single trivia-like question. I will jump all over the map and ask about as many different aspects of a topic as I can, hoping to map out where the depth of knowledge is for a candidate. If I am getting mostly blank stares I then give them the opportunity to decide what to tell me about the subject, in case they can surprise me. Unfortunately the vast majority of the time candidates are unable to convince me that they have deep knowledge on a subject. I want to find qualified people as much as these people would like to be considered qualified. But sometimes I feel like I throw a bunch of stuff at the candidate and NOTHING sticks.
I am beginning to believe that the majority of people who consider themselves experts or experienced are really just novice or intermediate and don't realize how deep the rabbit hole goes.
Then apparently we're the only company that has crazy number of openings and I personally talk to people every week that aren't what we're looking for.
As a developer looking for work, I am curious what you are looking for in your future employees. Looking at your profile and comment history gives me no hints.
Perhaps you have enough people to weed through that you don't want to post here and get a few more, but I know that I am not the only developer on HN that is looking for work. I'm also certain that other people would also appreciate knowing where to look for employers who have "crazy number of openings".
What hyper specialized positions are you hiring for that none of those you've interviewed can possibly fill? Did your job listing requesting a developer get answered by waves of auto mechanics?
To echo what others have said : are you sure you're not raising the bar to imaginary and unrealistic heights? You wouldn't be the first would-be employer to sigh woefully just because you couldn't find a mythical wizard-rockstar hybrid.
Maybe the problem is what you're looking for? All of these people you're interviewing aren't capable of being trained to do the job? They're just not smart enough for that or something?
I agree with you that these companies are probably turning away qualified developers. However at my current job it is the prevailing feeling, and I mostly agree, that it's better to turn away a few qualified candidates in order to prevent a mis-hire.
I generally agree with that sentiment too -- having seen what a bad hire can do first-hand. However, I feel like the industry has gone too far in that direction, and may in fact be selecting for a different kind of mis-hire.
When you spend an entire interview doing college computer science quiz type questions, and none of it on process, code review, coding style, development philosophy, approach to testing, etc.... you end up selecting for people who are good test-takers, but may not be any good at writing maintainable code. Or debugging. Or troubleshooting production issues. etc... etc...
I actually agree with you. This is why I never make a hiring decision based on a single trivia question, but I do ask trivia questions that are all over the map on a topic in order to find something the candidate is good at. Honestly, if you can answer any of my trivia questions in a deep and meaningful way that demonstrates insight into the topic then I'm satisfied.
