high_scalability high_scalability-2011 high_scalability-2011-1041 knowledge-graph by maker-knowledge-mining

1041 high scalability-2011-05-15-Building a Database remote availability site


meta infos for this blog

Source: html

Introduction: The AWS East Region outage showed all of us the importance of running our apps and databases across multiple Amazon regions (or multiple cloud providers). In this post, I’ll try to explain how to build a MySQL (or Amazon RDS) redundant site. For simplicity, we create a passive redundant site. This means that the site is not used during normal operation and only comes into action when the primary site crashes. There are many reasons for choosing such an architecture – it’s easy to configure, simple to understand, and minimizes the risk of data collision. The downside is that you have hardware just sitting around doing nothing. Still, it’s a common enough scenario. So what do we need to do to make it work? DATA SYNCHRONIZATION We need to synchronize the database. This is done by means of database replication. Now, there are two options for database replication: synchronous and a-synchronous. Synchronous replication is great; it ensures that the backup database is identical to the


Summary: the most important sentenses genereted by tfidf model

sentIndex sentText sentNum sentScore

1 The AWS East Region outage showed all of us the importance of running our apps and databases across multiple Amazon regions (or multiple cloud providers). [sent-1, score-0.321]

2 In this post, I’ll try to explain how to build a MySQL (or Amazon RDS) redundant site. [sent-2, score-0.192]

3 For simplicity, we create a passive redundant site. [sent-3, score-0.23]

4 This means that the site is not used during normal operation and only comes into action when the primary site crashes. [sent-4, score-0.477]

5 There are many reasons for choosing such an architecture – it’s easy to configure, simple to understand, and minimizes the risk of data collision. [sent-5, score-0.172]

6 The downside is that you have hardware just sitting around doing nothing. [sent-6, score-0.164]

7 DATA SYNCHRONIZATION We need to synchronize the database. [sent-9, score-0.099]

8 Now, there are two options for database replication: synchronous and a-synchronous. [sent-11, score-0.455]

9 Synchronous replication is great; it ensures that the backup database is identical to the primary database. [sent-12, score-1.223]

10 However, it also means that each DML operation on the primary database must be executed on the backup, and the result is sent to the client only after the backup database has completed the operation (at least at commit level). [sent-13, score-1.636]

11 This is very slow when the backup database is located in a remote geographical location (as a good friend of mine once said – sometimes the speed of light is just too slow). [sent-14, score-0.99]

12 A-synchronous replication is better for remote sites, but can result in data loss, depending on the “lag” between the primary database and the backup database. [sent-15, score-1.25]

13 We MySQL customers (RDS customers included) only have a- synchronous replication (and, starting from 5. [sent-16, score-0.783]

14 5, semi- synchronous replication, which on most deployments will behave in the same way as a-synchronous replication). [sent-17, score-0.468]

15 After the replication is configured, the application needs to be updated to make sure that it recognizes database crashes, and will failover to the backup database. [sent-18, score-1.081]

16 DETECTING CRASHES There are several possibilities for crashes and their detection. [sent-19, score-0.276]

17 The first, and simplest, is if the entire region is down, which causes both the application servers and the databases to crash. [sent-20, score-0.22]

18 In this case, the CDN, or a DNS load balancing technique, will failover to the backup region. [sent-21, score-0.513]


similar blogs computed by tfidf model

tfidf for this blog:

wordName wordTfidf (topN-words)

[('backup', 0.387), ('synchronous', 0.313), ('replication', 0.296), ('primary', 0.216), ('crashes', 0.181), ('operation', 0.162), ('rds', 0.157), ('region', 0.151), ('dml', 0.145), ('database', 0.142), ('recognizes', 0.13), ('failover', 0.126), ('remote', 0.122), ('redundant', 0.122), ('passive', 0.108), ('means', 0.099), ('synchronize', 0.099), ('simplest', 0.099), ('minimizes', 0.098), ('identical', 0.096), ('possibilities', 0.095), ('mine', 0.093), ('lag', 0.092), ('slow', 0.089), ('result', 0.087), ('importance', 0.087), ('east', 0.087), ('customers', 0.087), ('ensures', 0.086), ('geographical', 0.084), ('completed', 0.084), ('included', 0.083), ('sitting', 0.082), ('downside', 0.082), ('showed', 0.081), ('commit', 0.079), ('behave', 0.078), ('deployments', 0.077), ('outage', 0.077), ('simplicity', 0.076), ('executed', 0.076), ('regions', 0.076), ('choosing', 0.074), ('friend', 0.073), ('configure', 0.073), ('technique', 0.073), ('loss', 0.071), ('explain', 0.07), ('causes', 0.069), ('providers', 0.069)]

similar blogs list:

simIndex simValue blogId blogTitle

same-blog 1 1.0000004 1041 high scalability-2011-05-15-Building a Database remote availability site

Introduction: The AWS East Region outage showed all of us the importance of running our apps and databases across multiple Amazon regions (or multiple cloud providers). In this post, I’ll try to explain how to build a MySQL (or Amazon RDS) redundant site. For simplicity, we create a passive redundant site. This means that the site is not used during normal operation and only comes into action when the primary site crashes. There are many reasons for choosing such an architecture – it’s easy to configure, simple to understand, and minimizes the risk of data collision. The downside is that you have hardware just sitting around doing nothing. Still, it’s a common enough scenario. So what do we need to do to make it work? DATA SYNCHRONIZATION We need to synchronize the database. This is done by means of database replication. Now, there are two options for database replication: synchronous and a-synchronous. Synchronous replication is great; it ensures that the backup database is identical to the

2 0.19191298 1386 high scalability-2013-01-14-MongoDB and GridFS for Inter and Intra Datacenter Data Replication

Introduction: This is a guest post by Jeff Behl , VP Ops @ LogicMonitor.  Jeff has been a bit herder for the last 20 years, architecting and overseeing the infrastructure for a number of SaaS based companies.   Data Replication for Disaster Recovery An inevitable part of disaster recovery planning is making sure customer data exists in multiple locations.  In the case of LogicMonitor, a SaaS-based monitoring solution for physical, virtual, and cloud environments, we wanted copies of customer data files both within a data center and outside of it.  The former was to protect against the loss of individual servers within a facility, and the latter for recovery in the event of the complete loss of a data center. Where we were:  Rsync Like most everyone who starts off in a Linux environment, we used our trusty friend rsync to copy data around.   Rsync is tried, true and tested, and works well when the number of servers, the amount of data, and the number of files is not horrendous.

3 0.14450173 1557 high scalability-2013-12-02-Evolution of Bazaarvoice’s Architecture to 500M Unique Users Per Month

Introduction: This is a guest post written by Victor Trac , Cloud Architect at Bazaarvoice . Bazaarvoice is a company that people interact with on a regular basis but have probably never heard of. If you read customer reviews on sites like bestbuy.com, nike.com, or walmart.com, you are using Bazaarvoice services. These sites, along with thousands of others, rely on Bazaarvoice to supply the software and technology to collect and display user conversations about products and services. All of this means that Bazaarvoice processes a lot of sentiment data on most of the products we all use daily. Bazaarvoice helps our clients make better products by using a combination of machine learning and natural language processing to extract useful information and user sentiments from the millions of free-text reviews that go through our platform. This data gets boiled down into reports that clients can use to improve their products and services. We are also starting to look at how to show per

4 0.1388111 151 high scalability-2007-11-12-a8cjdbc - Database Clustering via JDBC

Introduction: Practically any software project nowadays could not survive without a database (DBMS) backend storing all the business data that is vital to you and/or your customers. When projects grow larger, the amount of data usually grows larger exponentially. So you start moving the DBMS to a separate server to gain more speed and capacity. Which is all good and healthy but you do not gain any extra safety for this business data. You might be backing up your database once a day so in case the database server crashes you don't lose EVERYTHING, but how much can you really afford to lose?  Well clearly this depends on what kind of data you are storing. In our case the users of our solutions use our software products to do their everyday (all day) work. They have "everything" they need for their business stored in the database we are providing. So is 24 hours of data loss acceptable? No, not really. One hour? Maybe. But what we really want is a second database running with the EXACT same data. We

5 0.13639967 308 high scalability-2008-04-22-Simple NFS failover solution with symbolic link?

Introduction: I've been trying to find a high availability file storage solution without success. I tried GlusterFS which looks very promising but experienced problems with stability and don't want something I can't easily control and rely on. Other solutions are too complicated or have a SPOF. So I'm thinking of the following setup: Two NFS servers, a primary and a warm backup. The primary server will be rsynced with the warm backup every minute or two. I can do it so frequently as a PHP script will know which directories have changed recently from a database and only rsync those. Both servers will be NFS mounted on a cluster of web servers as /mnt/nfs-primary (sym linked as /home/websites) and /mnt/nfs-backup. I'll then use Ucarp (http://www.ucarp.org/project/ucarp) to monitor both NFS servers availability every couple of seconds and when one goes down, the Ucarp up script will be set to change the symbolic link on all web servers for the /home/websites dir from /mnt/nfs-primary to /mn

6 0.13473412 1029 high scalability-2011-04-25-The Big List of Articles on the Amazon Outage

7 0.13257959 692 high scalability-2009-09-01-Cheap storage: how backblaze takes matters in hand

8 0.12393268 367 high scalability-2008-08-17-Strategy: Drop Memcached, Add More MySQL Servers

9 0.12165171 1604 high scalability-2014-03-03-The “Four Hamiltons” Framework for Mitigating Faults in the Cloud: Avoid it, Mask it, Bound it, Fix it Fast

10 0.12097166 1033 high scalability-2011-05-02-The Updated Big List of Articles on the Amazon Outage

11 0.12062012 1606 high scalability-2014-03-05-10 Things You Should Know About Running MongoDB at Scale

12 0.11901404 1508 high scalability-2013-08-28-Sean Hull's 20 Biggest Bottlenecks that Reduce and Slow Down Scalability

13 0.11872523 1631 high scalability-2014-04-14-How do you even do anything without using EBS?

14 0.11657801 1347 high scalability-2012-10-25-Not All Regions are Created Equal - South America Es Bueno

15 0.11517843 1221 high scalability-2012-04-03-Hazelcast 2.0: Big Data In-Memory

16 0.11503372 457 high scalability-2008-12-01-Sun FireTM X4540 Server as Backup Server for Zmanda's Amanda Enterprise 2.6 Software

17 0.11444061 736 high scalability-2009-11-04-Damn, Which Database do I Use Now?

18 0.11376993 1589 high scalability-2014-02-03-How Google Backs Up the Internet Along With Exabytes of Other Data

19 0.11250859 1133 high scalability-2011-10-27-Strategy: Survive a Comet Strike in the East With Reserved Instances in the West

20 0.11075656 16 high scalability-2007-07-16-Book: High Performance MySQL


similar blogs computed by lsi model

lsi for this blog:

topicId topicWeight

[(0, 0.17), (1, 0.064), (2, -0.075), (3, -0.032), (4, -0.02), (5, 0.024), (6, 0.047), (7, -0.155), (8, 0.04), (9, -0.089), (10, -0.037), (11, -0.002), (12, -0.059), (13, -0.02), (14, 0.021), (15, 0.046), (16, 0.053), (17, 0.011), (18, 0.026), (19, 0.031), (20, 0.039), (21, 0.041), (22, 0.011), (23, 0.027), (24, -0.048), (25, 0.063), (26, 0.004), (27, -0.016), (28, 0.057), (29, -0.026), (30, 0.001), (31, -0.008), (32, 0.017), (33, -0.049), (34, -0.019), (35, 0.006), (36, 0.042), (37, 0.023), (38, -0.034), (39, 0.036), (40, 0.053), (41, -0.087), (42, -0.043), (43, 0.051), (44, 0.015), (45, -0.036), (46, 0.019), (47, -0.011), (48, 0.006), (49, -0.069)]

similar blogs list:

simIndex simValue blogId blogTitle

same-blog 1 0.95064473 1041 high scalability-2011-05-15-Building a Database remote availability site

Introduction: The AWS East Region outage showed all of us the importance of running our apps and databases across multiple Amazon regions (or multiple cloud providers). In this post, I’ll try to explain how to build a MySQL (or Amazon RDS) redundant site. For simplicity, we create a passive redundant site. This means that the site is not used during normal operation and only comes into action when the primary site crashes. There are many reasons for choosing such an architecture – it’s easy to configure, simple to understand, and minimizes the risk of data collision. The downside is that you have hardware just sitting around doing nothing. Still, it’s a common enough scenario. So what do we need to do to make it work? DATA SYNCHRONIZATION We need to synchronize the database. This is done by means of database replication. Now, there are two options for database replication: synchronous and a-synchronous. Synchronous replication is great; it ensures that the backup database is identical to the

2 0.7040453 1557 high scalability-2013-12-02-Evolution of Bazaarvoice’s Architecture to 500M Unique Users Per Month

Introduction: This is a guest post written by Victor Trac , Cloud Architect at Bazaarvoice . Bazaarvoice is a company that people interact with on a regular basis but have probably never heard of. If you read customer reviews on sites like bestbuy.com, nike.com, or walmart.com, you are using Bazaarvoice services. These sites, along with thousands of others, rely on Bazaarvoice to supply the software and technology to collect and display user conversations about products and services. All of this means that Bazaarvoice processes a lot of sentiment data on most of the products we all use daily. Bazaarvoice helps our clients make better products by using a combination of machine learning and natural language processing to extract useful information and user sentiments from the millions of free-text reviews that go through our platform. This data gets boiled down into reports that clients can use to improve their products and services. We are also starting to look at how to show per

3 0.69578224 1604 high scalability-2014-03-03-The “Four Hamiltons” Framework for Mitigating Faults in the Cloud: Avoid it, Mask it, Bound it, Fix it Fast

Introduction: This is a guest post by Patrick Eaton , Software Engineer and Distributed Systems Architect at Stackdriver. Stackdriver provides intelligent monitoring-as-a-service for cloud hosted applications.  Behind this easy-to-use service is a large distributed system for collecting and storing metrics and events, monitoring and alerting on them, analyzing them, and serving up all the results in a web UI.  Because we ourselves run in the cloud (mostly on AWS), we spend a lot of time thinking about how to deal with faults in the cloud.  We have developed a framework for thinking about fault mitigation for large, cloud-hosted systems.  We endearingly call this framework the “Four Hamiltons” because it is inspired by an article from James Hamilton, the Vice President and Distinguished Engineer at Amazon Web Services. The article that led to this framework is called “ The Power Failure Seen Around the World ” .  Hamilton analyzes the causes of the power outage that affected Super Bowl XL

4 0.68513763 925 high scalability-2010-10-22-Paper: Netflix’s Transition to High-Availability Storage Systems

Introduction: In an audacious move for such an established property, Netflix is moving their website out of the comfort of their own datacenter and into the wilds of the Amazon cloud. This paper by Netflix's Siddharth “Sid” Anand, Netflix’s Transition to High-Availability Storage Systems , gives a detailed look at this transition and does a deep dive on SimpleDB best practices, focussing especially on techniques useful to those who are making the move from a RDBMS. Sid is going to give a talk at QCon based on this paper and he would appreciate your feedback. So if you have any comments or thoughts please comment here or email Sid at r39132@hotmail.com  or Twitter at @r39132 Here's the introduction from the paper: Circa late 2008, Netflix had a single data center. This single data center raised a few concerns. As a single-point-of-failure (a.k.a. SPOF), it represented a liability – data center outages meant interruptions to service and negative customer impact. Additionally, with growth in both

5 0.67542726 1098 high scalability-2011-08-15-Should any cloud be considered one availability zone? The Amazon experience says yes.

Introduction: Amazon has a very will written account of their 8/8/2011 downtime: Summary of the Amazon EC2, Amazon EBS, and Amazon RDS Service Event in the EU West Region . Power failed, backup generators failed to kick in, there weren't enough resources for EBS volumes to recover, API servers where overwhelmed, a DNS failure caused failovers to alternate availability zones to fail, a double fault occurred as the power event interrupted the repair of a different bug. All kind of typical stuff that just seems to happen. Considering the  previous outage , the big question for programmers is: what does this mean? What does it mean for how systems should be structured? Have we learned something that can't be unlearned? The Amazon post has lots of good insights into how EBS and RDS work, plus lessons learned. The short of the problem is large + complex = high probability of failure. The immediate fixes are adding more resources, more redundancy, more isolation between components, more automation, re

6 0.6662218 816 high scalability-2010-04-28-Elasticity for the Enterprise -- Ensuring Continuous High Availability in a Disaster Failure Scenario

7 0.66041541 1508 high scalability-2013-08-28-Sean Hull's 20 Biggest Bottlenecks that Reduce and Slow Down Scalability

8 0.64224333 1631 high scalability-2014-04-14-How do you even do anything without using EBS?

9 0.64136904 1070 high scalability-2011-06-29-Second Hand Seizure : A New Cause of Site Death

10 0.63630694 1367 high scalability-2012-12-05-5 Ways to Make Cloud Failure Not an Option

11 0.63610542 793 high scalability-2010-03-10-Saying Yes to NoSQL; Going Steady with Cassandra at Digg

12 0.63273364 23 high scalability-2007-07-24-Major Websites Down: Or Why You Want to Run in Two or More Data Centers.

13 0.62717652 1386 high scalability-2013-01-14-MongoDB and GridFS for Inter and Intra Datacenter Data Replication

14 0.62265319 798 high scalability-2010-03-22-7 Secrets to Successfully Scaling with Scalr (on Amazon) by Sebastian Stadil

15 0.61233437 68 high scalability-2007-08-20-TypePad Architecture

16 0.60721004 187 high scalability-2007-12-14-The Current Pros and Cons List for SimpleDB

17 0.6050455 736 high scalability-2009-11-04-Damn, Which Database do I Use Now?

18 0.60456806 28 high scalability-2007-07-25-Product: NetApp MetroCluster Software

19 0.60441935 139 high scalability-2007-10-30-Paper: Dynamo: Amazon’s Highly Available Key-value Store

20 0.60379755 302 high scalability-2008-04-10-Mysql scalability and failover...


similar blogs computed by lda model

lda for this blog:

topicId topicWeight

[(1, 0.182), (2, 0.229), (10, 0.122), (38, 0.038), (61, 0.069), (79, 0.174), (85, 0.055), (94, 0.038)]

similar blogs list:

simIndex simValue blogId blogTitle

same-blog 1 0.9886657 1041 high scalability-2011-05-15-Building a Database remote availability site

Introduction: The AWS East Region outage showed all of us the importance of running our apps and databases across multiple Amazon regions (or multiple cloud providers). In this post, I’ll try to explain how to build a MySQL (or Amazon RDS) redundant site. For simplicity, we create a passive redundant site. This means that the site is not used during normal operation and only comes into action when the primary site crashes. There are many reasons for choosing such an architecture – it’s easy to configure, simple to understand, and minimizes the risk of data collision. The downside is that you have hardware just sitting around doing nothing. Still, it’s a common enough scenario. So what do we need to do to make it work? DATA SYNCHRONIZATION We need to synchronize the database. This is done by means of database replication. Now, there are two options for database replication: synchronous and a-synchronous. Synchronous replication is great; it ensures that the backup database is identical to the

2 0.98275483 716 high scalability-2009-10-06-Building a Unique Data Warehouse

Introduction: There are many reasons to roll your own  data  storage solution on top of existing technologies. We've seen stories on HighScalability about custom databases for very large sets of individual  data (like Twitter) and large amounts of binary  data  (like Facebook pictures). However, I recently ran into a  unique  type of problem. I was tasked with recording and storing bandwidth information for more than 20,000 servers and their associated networking equipment. This  data  needed to be accessed in real-time, with less than a 5 minute delay between the  data  being recorded and the  data showing up on customer bandwidth graphs on our customer portal. After numerous false starts with off the shelf components and existing database clustering technology, we decided we must roll our own system. The real key to our problem (literally) was the ratio of the size of the key to the size of the actual  data . Because the tracked metric was so small (a 64-bit counter) compared to the  unique  ide

3 0.97689962 1553 high scalability-2013-11-25-How To Make an Infinitely Scalable Relational Database Management System (RDBMS)

Introduction: This is a guest post by  Mark Travis , Founder of InfiniSQL . InfiniSQL is the specific "Infinitely Scalable RDBMS" to which the title refers. It is free software, and instructions for getting, building, running and testing it are available in the guide . Benchmarking shows that an InfiniSQL cluster can handle over 500,000 complex transactions per second with over 100,000 simultaneous connections, all on twelve small servers. The methods used to test are documented, and the code is all available so that any practitioner can achieve similar results. There are two main characteristics which make InfiniSQL extraordinary: It performs transactions with records on multiple nodes better than any clustered/distributed RDBMS It is free, open source. Not just a teaser "community" version with the good stuff proprietary. The community version of InfiniSQL will also be the enterprise version, when it is ready. InfiniSQL is still in early stages of development--it already has m

4 0.97627974 1452 high scalability-2013-05-06-7 Not So Sexy Tips for Saving Money On Amazon

Introduction: Harish Ganesan  CTO of 8KMiles  has a very helpful blog,  Cloud, Big Data and Mobile , where he shows a nice analytical bent which leads to a lot of practical advice and cost saving tips: Use SQS Batch Requests  to reduce the number of requests hitting SQS which saves costs. Sending 10 messages in a single batch request which in the example save $30/month. Use SQS Long Polling  to reduce extra polling requests, cutting down empty receives, which in the example saves ~$600 in empty receive leakage costs. Choose the right search technology choice to save costs in AWS  by matching your activity pattern to the technology. For a small application with constant load or a heavily utilized search tier or seasonal loads Amazon Cloud Search looks like the cost efficient play.  Use Amazon CloudFront Price Class to minimize costs  by selecting the right Price Class for your audience to potentially reduce delivery costs by excluding Amazon CloudFront’s more expensive edge locatio

5 0.97572607 1186 high scalability-2012-02-02-The Data-Scope Project - 6PB storage, 500GBytes-sec sequential IO, 20M IOPS, 130TFlops

Introduction: “ Data is everywhere, never be at a single location. Not scalable, not maintainable. ” –Alex Szalay While Galileo played life and death doctrinal games over the mysteries revealed by the telescope, another revolution went unnoticed, the microscope gave up mystery after mystery and nobody yet understood how subversive would be what it revealed. For the first time these new tools of perceptual augmentation allowed humans to peek behind the veil of appearance. A new new eye driving human invention and discovery for hundreds of years. Data is another material that hides, revealing itself only when we look at different scales and investigate its underlying patterns. If the universe is truly made of information , then we are looking into truly primal stuff. A new eye is needed for Data and an ambitious project called Data-scope aims to be the lens. A detailed paper on the Data-Scope tells more about what it is: The Data-Scope is a new scientific instrum

6 0.97137445 498 high scalability-2009-01-20-Product: Amazon's SimpleDB

7 0.96961814 1654 high scalability-2014-06-05-Cloud Architecture Revolution

8 0.96767068 1626 high scalability-2014-04-04-Stuff The Internet Says On Scalability For April 4th, 2014

9 0.96749246 1075 high scalability-2011-07-07-Myth: Google Uses Server Farms So You Should Too - Resurrection of the Big-Ass Machines

10 0.96693361 857 high scalability-2010-07-13-DbShards Part Deux - The Internals

11 0.9662261 853 high scalability-2010-07-08-Cloud AWS Infrastructure vs. Physical Infrastructure

12 0.96348912 572 high scalability-2009-04-16-Paper: The End of an Architectural Era (It’s Time for a Complete Rewrite)

13 0.96312708 450 high scalability-2008-11-24-Scalability Perspectives #3: Marc Andreessen – Internet Platforms

14 0.96284646 1369 high scalability-2012-12-10-Switch your databases to Flash storage. Now. Or you're doing it wrong.

15 0.96228993 1275 high scalability-2012-07-02-C is for Compute - Google Compute Engine (GCE)

16 0.96220922 1479 high scalability-2013-06-21-Stuff The Internet Says On Scalability For June 21, 2013

17 0.96218723 1068 high scalability-2011-06-27-TripAdvisor Architecture - 40M Visitors, 200M Dynamic Page Views, 30TB Data

18 0.96208239 1353 high scalability-2012-11-01-Cost Analysis: TripAdvisor and Pinterest costs on the AWS cloud

19 0.96183634 1371 high scalability-2012-12-12-Pinterest Cut Costs from $54 to $20 Per Hour by Automatically Shutting Down Systems

20 0.96183282 1647 high scalability-2014-05-14-Google Says Cloud Prices Will Follow Moore’s Law: Are We All Renters Now?