percona-discussion team mailing list archive
-
percona-discussion team
-
Mailing list archive
-
Message #00553
[Bug 369913] [NEW] Feature Request: more verbose output during initial table scan
Public bug reported:
We ran innobackupex-1.5.1 to test it on our development system, 125
total databases, consisting of 23768 tables in innodb format
(innodb_table_per_file *.idb) and 937 tables in myisam format (*.MYD).
The total dataset is around 13 GB.
When doing the initial table scan, there is a long pause where nothing
is printed out. On our system with a lot of db's and tables, I
initially though that long period of inactivity might be a lock-up. An
strace showed that it was in fact reading in massive amounts of database
info, so outputting a "Generating db/table list" type of message would
be a helpful message to people with large numbers of tables.
On the opposite end, there could possibly also be a --quiet option that
will suppress the "Copying $FILE to $DESTFILE" messages when it is
copying all of the messages. If you think that &>/dev/null is a
sufficient synonym for --quiet, then I am quite happy with that too.
** Affects: percona-xtrabackup
Importance: Undecided
Status: New
** Tags: feature-request
--
Feature Request: more verbose output during initial table scan
https://bugs.launchpad.net/bugs/369913
You received this bug notification because you are a member of Percona
developers, which is the registrant for Percona-XtraBackup.
Status in Open source backup tool for InnoDB and XtraDB: New
Bug description:
We ran innobackupex-1.5.1 to test it on our development system, 125 total databases, consisting of 23768 tables in innodb format (innodb_table_per_file *.idb) and 937 tables in myisam format (*.MYD). The total dataset is around 13 GB.
When doing the initial table scan, there is a long pause where nothing is printed out. On our system with a lot of db's and tables, I initially though that long period of inactivity might be a lock-up. An strace showed that it was in fact reading in massive amounts of database info, so outputting a "Generating db/table list" type of message would be a helpful message to people with large numbers of tables.
On the opposite end, there could possibly also be a --quiet option that will suppress the "Copying $FILE to $DESTFILE" messages when it is copying all of the messages. If you think that &>/dev/null is a sufficient synonym for --quiet, then I am quite happy with that too.
Follow ups
References