Auto-resizing of the ib_logfile* files

Bug #653302 reported by m00dawg
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Drizzle
Triaged
Wishlist
Stewart Smith
HailDB
Triaged
Wishlist
Stewart Smith

Bug Description

This is a feature request (not a bug)

Currently, to change the size of the InnoDB log_files, the server must be shutdown properly, logs removed, config changes, and the server started back up. It seems like InnoDB (or Drizzle) could handle this automatically because the steps are actually quite mundane.

My thought is that InnoDB/Drizzle could check the innodb.log-file-size variable and, if different than the size of the ib_logfile* files, simply copy the existing files elsewhere, generate the new logs, populate the new logs with the contents of the old files, then drop the old files. BOOM!

While Drizzle improves on MySQL by having the server die when there is a mismatch, the above would totally make the issue moot. Same holds true for the log-files-in-group setting.

Just a thought :)

Revision history for this message
m00dawg (tim-moocowproductions) wrote :

Logged a bug with MySQL for this as well:

http://bugs.mysql.com/bug.php?id=57190

Revision history for this message
Monty Taylor (mordred) wrote : Re: [Bug 653302] [NEW] Auto-resizing of the ib_logfile* files

This sounds like an excellent idea to me!

On 10/01/2010 03:05 PM, m00dawg wrote:
> Public bug reported:
>
> This is a feature request (not a bug)
>
> Currently, to change the size of the InnoDB log_files, the server must
> be shutdown properly, logs removed, config changes, and the server
> started back up. It seems like InnoDB (or Drizzle) could handle this
> automatically because the steps are actually quite mundane.
>
> My thought is that InnoDB/Drizzle could check the innodb.log-file-size
> variable and, if different than the size of the ib_logfile* files,
> simply copy the existing files elsewhere, generate the new logs,
> populate the new logs with the contents of the old files, then drop the
> old files. BOOM!
>
> While Drizzle improves on MySQL by having the server die when there is a
> mismatch, the above would totally make the issue moot. Same holds true
> for the log-files-in-group setting.
>
> Just a thought :)
>
> ** Affects: drizzle
> Importance: Undecided
> Status: New
>
> ** Bug watch added: MySQL Bug System #57190
> http://bugs.mysql.com/bug.php?id=57190
>

Revision history for this message
Stewart Smith (stewart) wrote :

This could be done with HailDB relatively easily if we get an ADMIN style command... shut down haildb, change setting, start it up again.

firm WontFix for innobase plugin though.

Changed in haildb:
importance: Undecided → Wishlist
status: New → Triaged
Changed in drizzle:
importance: Undecided → Wishlist
status: New → Triaged
Changed in haildb:
assignee: nobody → Stewart Smith (stewart)
Changed in drizzle:
assignee: nobody → Stewart Smith (stewart)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.