ec2baseAmazon EC2 by Robot and Me |
|
http://groups.drupal.org/node/36750
Very similar to setting up an instance with a single EBS drive, you can also fairly easily do a RAID configuration. This leads to better performance usually and higher reliability.
http://mutexlock.blogspot.com/2010/01/resetting-overwriting-etcresolvconf-in.html
For our purposes – we had set up an internal dns server running (bind – process ‘named’ on a particular host).
When we were launching our pool of servers – we wanted to make sure that the new instances fall under the same domain that we specify it to be.
We also wanted to set the nameserver of the newly created instances pointing to the internal DNS server we have to resolve the ambiguity we have.
Before making the change – the file /etc/resolv.conf was looking as follows.
http://monitorcloud.com/monitorcloud
The main monitoring features of Monitis Amazon EC2 (Elastic Compute Cloud) and S3 cloud storage on-demand cloud monitoring service are: external monitoring of launched Amazon virtual servers and generate notifications to users upon breaking the threshold level, dynamically and adaptively monitor web servers, mail servers, databases etc without the need of manually adding each monitor and rules per server, automatically install Monitis agent on new servers and monitor performance metrics plus generate notifications when resources are detected to be low, proactive notification to users if a server is lost in the Amazon cloud.
http://www.lindstromconsulting.com/node/8
In the previous article on the subject of cloud computing using AWS, we setup a simple LAMP application that used a single web server to present data that was queried from a single RDS instance. In this guide we will see how to save the changes we made to the EC2 instance, create more EC2 instances, and setup load balancing across our web servers.
http://www.mysqlperformanceblog.com/2009/10/15/mysql-memcached-or-nosql-tokyo-tyrant-part-1/
A classic example is a simple online game. An online game may only require that an application retrieve a single record from the database. The record may contain all the vital stats for the game, be updated and stuffed back into the database. You would be surprised how many people use this type of system as I run into this type of application frequently. Keeping it simple, ensures that application is generally mean and lean and performs well. The issue is even this simple design can start to have issues as the data size increases and you blow through your available memory. Is there a better architecture? Is there a way to get more scalability out of your database? Is the database even the best place for this data?
percona guys (one of the highest mysql authorities) put some nails in mysql coffin (innocently?)
http://www.umiacs.umd.edu/~jimmylin/cloud9/docs/content/start-EC2.html
This tutorial will get you started with Cloud9 on Amazon’s EC2 (running the simple word count demo). For a gentler introduction to Hadoop, or if you don’t feel like experimenting with EC2, try my tutorial on getting started with Cloud9 in standalone mode. This tutorial assumes you’ve already downloaded Cloud9 and gotten it set up. Otherwise, see my tutorial on that.
http://www.michael-noll.com/wiki/Hadoop
* Writing An Hadoop MapReduce Program In Python
* Running Hadoop On Ubuntu Linux (Single-Node Cluster)
* Running Hadoop On Ubuntu Linux (Multi-Node Cluster)
Teich also said that all of Heroku’s m2.2xlarge instances were running in a single availability zone, which was a mistake. He stressed that Heroku had failover built in already — if 21 instances had failed instead of 22, or if it had spread instances across several zones, “we wouldn’t be talking [about the outage],” he said.
Nevertheless, on Friday, January 2, every m2.2xlarge instance in that availability zone suddenly vanished, despite all other types of EC2 instances running as normal. That’s unheard of in traditional hosting. It would be like every server with a given amount of RAM suddenly shutting down, regardless of operating system, age, brand, hardware or location in the data center, with no effect on its neighbors.
“For us, there’s the stuff you plan for and then there’s the stuff you don’t even know about,” Teich said.
An event like this was an “unknown unknown” that nobody planned for because nobody imagined it. He chalked it up to the learning process and pointed out that everybody in Amazon Web Services was flying by the seat of the pants at least part of the time.
HN thread:
http://news.ycombinator.com/item?id=1046500
A while ago one of the major problems people faced to use Amazon EC2 into production environments was the dynamic state of the instances IPs. Every time one instance was started it was getting a new, dynamic IP. This has been addressed with the introduction of Amazon Elastic IP Addresses, but even when using this, the private IPs are still dynamic and most of the time people will want to communicate between several instances on the private allocated IPs and not on the public ones. This article will show how you can easily automate the process to update DNS hostnames for your EC2 instances, by adding to the AMI’s the logic for this. I will use for this a master DNS server running bind9, but this can be adapted to any other DNS server.
http://bret.appspot.com/entry/how-friendfeed-uses-mysql
We use MySQL for storing all of the data in FriendFeed. Our database has grown a lot as our user base has grown. We now store over 250 million entries and a bunch of other data, from comments and “likes” to friend lists.
As our database has grown, we have tried to iteratively deal with the scaling issues that come with rapid growth. We did the typical things, like using read slaves and memcache to increase read throughput and sharding our database to improve write throughput. However, as we grew, scaling our existing features to accomodate more traffic turned out to be much less of an issue than adding new features.
http://www.powercram.com/2010/01/amazon-ec2-instance-types.html
Amazon EC2 Instance Types.
Standard Instances
Instances of this family are well suited for most applications …
http://blog.reddit.com/2010/01/why-did-we-take-reddit-down-for-71.html
Part of our setup uses what we call a “permacache”, which uses Memcachedb. Memcachedb is Memcached with a built-in permanent storage system using BDB. One of the “features” of this system is that it saves up its disk writes and then bursts them to the disk. Unfortunately, the single EBS volumes they were on could not handle these bursting writes. Memcachedb also has another feature that blocks all reads while it writes to the disk. These two things together would cause the site to go down for about 30 seconds every hour or so lately.
