Success with OpenSolaris + ZFS + MySQL in production!

Tags

mysql, production, rss, solaris

Operating Systems Solaris Solaris BigAdmin RSS Success with OpenSolaris + ZFS + MySQL in production!

10-21-2008

Registered User

26,240, 27

Join Date: Sep 2000

Last Activity: 1 August 2008, 3:09 PM EDT

Posts: 26,240

Thanks Given: 0

Thanked 27 Times in 26 Posts

Success with OpenSolaris + ZFS + MySQL in production!

This tip provides information about using ZFS on a MySQL database box and OpenSolaris. The author explores two questions: Can a MySQL slave on OpenSolaris with ZFS keep up with the write load with no readers, and if yes, can the slave shoulder its fair share of the reads, too?

More...

Linux Bot

View Public Profile for Linux Bot

Find all posts by Linux Bot

Previous Thread | Next Thread

1 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

production issue - shell sqlplus processing sometime success sometime fail

Hi Expert, Below is a real production environment issue: we are using shell script to FTP to a remote server and fetch around 150 files every day, for each file we need to keep a entry inside ORACLE DB table, before insert into table, each file has a associated logid, which need to be...

LEARN ABOUT DEBIAN

apache::session::lock::mysql

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)

Solaris BigAdmin RSS