MySQL Database Scale-out and Replication for High Growth Businesses


 
Thread Tools Search this Thread
Operating Systems Solaris Solaris BigAdmin RSS MySQL Database Scale-out and Replication for High Growth Businesses
# 1  
Old 11-11-2008
MySQL Database Scale-out and Replication for High Growth Businesses

This Sun BluePrints paper addresses the primary ways MySQL installations can scale to meet increasing user demands, while still providing the flexibility and ease of use that single installations offer.

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

3 More Discussions You Might Find Interesting

1. HP-UX

Database replication process stopped in server

Hi, A database (Oracle) replication process was executed by the DBA team in one server (serverX). However, this replication process gets terminated, and there are no errors in the replication log. But there is error in the OS log files (syslog.log) : Aug 8 16:51:47 L28dre02 sshd: subsystem... (1 Reply)
Discussion started by: anaigini45
1 Replies

2. Linux

Mysql replication

Need to recover a replication broken error on the mysql slave server. I want to force it to resend the binlog file from the begining. What is the correct value for the: MASTER_LOG_POS ? 0, 1 or 107 ? (2 Replies)
Discussion started by: andriesh
2 Replies

3. Shell Programming and Scripting

Strategical Shell Scripting For MySql Replication

Hi to all guyz , As i'm new to Shell scripting i was been working out to write a shell script for mysql Replication for multiple slave master architecture.i have done the process up with a script of 200 lines but still there are some things which can make my script more effective so i want your... (5 Replies)
Discussion started by: kgrvamsi
5 Replies
Login or Register to Ask a Question
Apache::Session::Lock::MySQL(3pm)			User Contributed Perl Documentation			 Apache::Session::Lock::MySQL(3pm)

NAME
Apache::Session::Lock::MySQL - Provides mutual exclusion using MySQL SYNOPSIS
use Apache::Session::Lock::MySQL; my $locker = Apache::Session::Lock::MySQL->new(); $locker->acquire_read_lock($ref); $locker->acquire_write_lock($ref); $locker->release_read_lock($ref); $locker->release_write_lock($ref); $locker->release_all_locks($ref); DESCRIPTION
Apache::Session::Lock::MySQL fulfills the locking interface of Apache::Session. Mutual exclusion is achieved through the use of MySQL's GET_LOCK and RELEASE_LOCK functions. MySQL does not support the notion of read and write locks, so this module only supports exclusive locks. When you request a shared read lock, it is instead promoted to an exclusive write lock. CONFIGURATION
The module must know how to connect to your MySQL database to acquire locks. You must provide a datasource name, a user name, and a password. These options are passed in the usual Apache::Session style, and are very similar to the options for Apache::Session::Store::MySQL. Example: tie %hash, 'Apache::Session::MySQL', $id, { LockDataSource => 'dbi:mysql:database', LockUserName => 'database_user', LockPassword => 'K00l' }; Instead, you may pass in an already opened DBI handle to your database. tie %hash, 'Apache::Session::MySQL', $id, { LockHandle => $dbh }; AUTHOR
This module was written by Jeffrey William Baker <jwbaker@acm.org>. SEE ALSO
Apache::Session perl v5.10.1 2010-10-18 Apache::Session::Lock::MySQL(3pm)