You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by anil lakineni <an...@gmail.com> on 2016/04/25 12:28:10 UTC
mysql-bin log files eating more space and DB server root fs filling
up now at 98%
Hi All,
In Cloud DB server, the root file system reached to 98% and found that
*/var/lib/mysql/* is consumed with more space.
Inside that specified directory i found that " *mysql bin logs* " are
eating more space and files are there since one year.
My environment has enabled with DB replication.
Is it safe to purge the older mysql bin logs ? if yes, Could you please
paste the working steps here which wouldn't affect replication as some
blogs are saying that replication will be affected if we purge.
*Please recommend best solution that was already worked on production
environment*
So please suggest me the process to free up some space and clean up mysql
bin logs.
P.S. I have verified other directories and logs, they are consuming very
little space except this bin logs directory (not *ibdata1* file).
Cloud version is 4.5 and MySQL version is " 5.1.73-log "
My MySQL configuration file is,
#cat /etc/my.cnf
*[mysqld]*
*datadir=/var/lib/mysql*
*socket=/var/lib/mysql/mysql.sock*
*user=mysql*
*# Disabling symbolic-links is recommended to prevent assorted security
risks*
*symbolic-links=0*
*innodb_rollback_on_timeout=1*
*innodb_lock_wait_timeout=600*
*max_connections=1400*
*log-bin=mysql-bin*
*binlog-format = 'ROW'*
*innodb_buffer_pool_size=5500m*
*default-character-set=utf8*
*default-collation=utf8_unicode_ci*
*character-set-server=utf8*
*collation-server=utf8_unicode_ci*
*default-time-zone='+03:00'*
*# for Master / Slave*
*server-id = 1*
*[mysqld_safe]*
*log-error=/var/log/mysqld.log*
*pid-file=/var/run/mysqld/mysqld.pid*
Please let me know if any other information needed and please suggest the
process that would cleanup old logs automatically by mysql.
Hope will get some help here..
Regards,
Anil.
Re: mysql-bin log files eating more space and DB server root fs
filling up now at 98%
Posted by Wido den Hollander <wi...@widodh.nl>.
> Op 25 april 2016 om 12:28 schreef anil lakineni <an...@gmail.com>:
>
>
> Hi All,
>
> In Cloud DB server, the root file system reached to 98% and found that
> */var/lib/mysql/* is consumed with more space.
>
> Inside that specified directory i found that " *mysql bin logs* " are
> eating more space and files are there since one year.
>
> My environment has enabled with DB replication.
>
> Is it safe to purge the older mysql bin logs ? if yes, Could you please
> paste the working steps here which wouldn't affect replication as some
> blogs are saying that replication will be affected if we purge.
>
Yes, you can remove them. Just use 'rm' to remove the old logs.
> *Please recommend best solution that was already worked on production
> environment*
>
> So please suggest me the process to free up some space and clean up mysql
> bin logs.
>
I recommend you search a bit on this topic. It is not CloudStack-specific, the MySQL documentation will tell you how to do this.
> P.S. I have verified other directories and logs, they are consuming very
> little space except this bin logs directory (not *ibdata1* file).
>
> Cloud version is 4.5 and MySQL version is " 5.1.73-log "
>
> My MySQL configuration file is,
>
> #cat /etc/my.cnf
> *[mysqld]*
> *datadir=/var/lib/mysql*
> *socket=/var/lib/mysql/mysql.sock*
> *user=mysql*
> *# Disabling symbolic-links is recommended to prevent assorted security
> risks*
> *symbolic-links=0*
>
> *innodb_rollback_on_timeout=1*
> *innodb_lock_wait_timeout=600*
> *max_connections=1400*
> *log-bin=mysql-bin*
> *binlog-format = 'ROW'*
> *innodb_buffer_pool_size=5500m*
>
> *default-character-set=utf8*
> *default-collation=utf8_unicode_ci*
> *character-set-server=utf8*
> *collation-server=utf8_unicode_ci*
> *default-time-zone='+03:00'*
>
> *# for Master / Slave*
> *server-id = 1*
>
> *[mysqld_safe]*
> *log-error=/var/log/mysqld.log*
> *pid-file=/var/run/mysqld/mysqld.pid*
>
>
> Please let me know if any other information needed and please suggest the
> process that would cleanup old logs automatically by mysql.
>
> Hope will get some help here..
>
> Regards,
> Anil.
Re: mysql-bin log files eating more space and DB server root fs
filling up now at 98%
Posted by Wido den Hollander <wi...@widodh.nl>.
> Op 25 april 2016 om 12:28 schreef anil lakineni <an...@gmail.com>:
>
>
> Hi All,
>
> In Cloud DB server, the root file system reached to 98% and found that
> */var/lib/mysql/* is consumed with more space.
>
> Inside that specified directory i found that " *mysql bin logs* " are
> eating more space and files are there since one year.
>
> My environment has enabled with DB replication.
>
> Is it safe to purge the older mysql bin logs ? if yes, Could you please
> paste the working steps here which wouldn't affect replication as some
> blogs are saying that replication will be affected if we purge.
>
Yes, you can remove them. Just use 'rm' to remove the old logs.
> *Please recommend best solution that was already worked on production
> environment*
>
> So please suggest me the process to free up some space and clean up mysql
> bin logs.
>
I recommend you search a bit on this topic. It is not CloudStack-specific, the MySQL documentation will tell you how to do this.
> P.S. I have verified other directories and logs, they are consuming very
> little space except this bin logs directory (not *ibdata1* file).
>
> Cloud version is 4.5 and MySQL version is " 5.1.73-log "
>
> My MySQL configuration file is,
>
> #cat /etc/my.cnf
> *[mysqld]*
> *datadir=/var/lib/mysql*
> *socket=/var/lib/mysql/mysql.sock*
> *user=mysql*
> *# Disabling symbolic-links is recommended to prevent assorted security
> risks*
> *symbolic-links=0*
>
> *innodb_rollback_on_timeout=1*
> *innodb_lock_wait_timeout=600*
> *max_connections=1400*
> *log-bin=mysql-bin*
> *binlog-format = 'ROW'*
> *innodb_buffer_pool_size=5500m*
>
> *default-character-set=utf8*
> *default-collation=utf8_unicode_ci*
> *character-set-server=utf8*
> *collation-server=utf8_unicode_ci*
> *default-time-zone='+03:00'*
>
> *# for Master / Slave*
> *server-id = 1*
>
> *[mysqld_safe]*
> *log-error=/var/log/mysqld.log*
> *pid-file=/var/run/mysqld/mysqld.pid*
>
>
> Please let me know if any other information needed and please suggest the
> process that would cleanup old logs automatically by mysql.
>
> Hope will get some help here..
>
> Regards,
> Anil.