Another issue might be that your dumping the cache tables too causing significantly more overhead than needed.
On Friday, May 15, 2015, Larry Silverman <[email protected]> wrote: > Something to try: pipe the dump through gzip. If you have more CPU oomph > than disk speed, the whole operation might finish faster and you might > avoid getting kicked by whatever timeout is killing your process. > > Here's the mysqldump command I use: > mysqldump --databases devmediawiki --single-transaction --add-drop-database > --triggers --routines --events --user=root --password | gzip > > /tmp/devmediawiki-sql.gz > > Larry Silverman > Chief Technology Officer > TrackAbout, Inc. > > On Fri, May 15, 2015 at 3:56 PM, John Foster <[email protected] > <javascript:;>> wrote: > > > This is the dump command I use: > > > > mysqldump --verbose -u root -p my_wiki > my_wiki.sql > > > > This is the error I get: > > mysqldump: Error 2013: Lost connection to MySQL server during query when > > dumping table `transcache` at row: 12 > > > > This is the relevant part of etc/mysql/my.cnf: > > # * Fine Tuning > > # > > key_buffer = 64M > > max_allowed_packet = 64M > > thread_stack = 192K > > 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 = 8M > > query_cache_size = 64M > > # > > # * Logging and Replication > > # > > # Both location gets rotated by the cronjob. > > # Be aware that this log type is a performance killer. > > # As of 5.1 you can enable the log at runtime! > > #general_log_file = /var/log/mysql/mysql.log > > #general_log = 1 > > # > > # Error logging goes to syslog due to > > /etc/mysql/conf.d/mysqld_safe_syslog.cnf. > > # > > # Here you can see queries with especially long duration > > #log_slow_queries = /var/log/mysql/mysql-slow.log > > #long_query_time = 2 > > #log-queries-not-using-indexes > > # > > # The following can be used as easy to replay backup logs or for > > replication. > > # note: if you are setting up a replication slave, see README.Debian > about > > # other settings you may need to change. > > #server-id = 1 > > #log_bin = /var/log/mysql/mysql-bin.log > > expire_logs_days = 10 > > max_binlog_size = 100M > > #binlog_do_db = include_database_name > > #binlog_ignore_db = include_database_name > > # > > # * InnoDB > > # > > # InnoDB is enabled by default with a 10MB datafile in /var/lib/mysql/. > > # Read the manual for more InnoDB related options. There are many! > > # > > net_write_timeout = 360 > > > > > > > > > > On 05/15/2015 08:24 AM, Dave Humphrey wrote: > > > >> Exactly what is the error message you are getting? If it is something > like > >> "Mysql Server has gone away" it may be due to a too small > >> "max_allowed_packet" setting. See > >> > >> > http://stackoverflow.com/questions/19214572/can-not-import-large-sql-dump-into-mysql-5-6 > >> > >> > > -- > > John Foster > > JW Foster & Associates > > > > > > _______________________________________________ > > MediaWiki-l mailing list > > To unsubscribe, go to: > > https://lists.wikimedia.org/mailman/listinfo/mediawiki-l > > > _______________________________________________ > MediaWiki-l mailing list > To unsubscribe, go to: > https://lists.wikimedia.org/mailman/listinfo/mediawiki-l > _______________________________________________ MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
