From: Xavier Cardil
Date: June 15 2009 8:24am
Subject: mysql restore on a slave for cluster replication takes forever
List-Archive: http://lists.mysql.com/replication/1639
Message-Id: <50c2d0150906150124r4944c44aq55866084e1db8ddc@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary=001636458d30e34b89046c5ec891

--001636458d30e34b89046c5ec891
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Hi, I am on the process of make a replication slave for a cluster, and now
I'm uploading the cluster dump. It is about 4 gb of data and I'm using the
following my.cnf :

[mysqld]
#
# * Basic Settings
#
user            = mysql
pid-file        = /var/run/mysqld/mysqld.pid
socket          = /var/run/mysqld/mysqld.sock
port            = 3306
basedir         = /usr
datadir         = /var/lib/mysql
tmpdir          = /tmp
language        = /usr/share/mysql/english
skip-external-locking
thread_concurrency = 2
skip_name_resolve
ndb-log-updates-as-writes=O


# * Fine Tuning
#
key_buffer              = 16M
max_allowed_packet      = 16M
thread_stack            = 128K
thread_cache_size       = 8
# This replaces the startup script and checks MyISAM tables if needed
# the first time they are touched
myisam-recover         = BACKUP
#max_connections        = 100
#table_cache            = 64
#thread_concurrency     = 10
#
# * Query Cache Configuration
#
query_cache_limit       = 1M
query_cache_size        = 16M


[mysqldump]
quick
quote-names
max_allowed_packet      = 16M

[mysql]
#no-auto-rehash # faster start of mysql but no tab completition

[isamchk]
key_buffer              = 16M

The problem is that 5 days have passed and the restore process still
running. I don't know if this is normal, as It never happened to me.  Do I
have to tune some param to speed it up ? Thank you.

--001636458d30e34b89046c5ec891--