| Bug #23733 | INFORMATION_SCHEMA.FILES shows unknown null file after LOGFILE GROUP created | ||
|---|---|---|---|
| Submitted: | 27 Oct 2006 18:30 | Modified: | 2 Feb 2007 8:51 |
| Reporter: | Jonathan Miller | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Cluster: Disk Data | Severity: | S3 (Non-critical) |
| Version: | 5.1.13 | OS: | Linux (Linux 32 Bit) |
| Assigned to: | Jon Stephens | CPU Architecture: | Any |
[29 Oct 2006 2:47]
Stewart Smith
This is an intended behaviour change from a patch to a previous bug (free space for undofiles). The NULL file for the LFG would report the free space for that LFG as no individual file really had "free space", just the LFG. It was also decided that this was a lot easier to get implemented quickly and correctly. (so we could get onto other bugs :) maybe this hasn't hit the manual yet, or perhaps need clarification..
[26 Nov 2006 9:27]
Jon Stephens
Stewart, What was the original bug number? In what version was the patch applied producing the behaviour noted by JMiller?
[2 Feb 2007 8:51]
Jon Stephens
Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products. Updated 5.1 Manual: Added info/examples to FILES Table section in I_S chapter, added note/pointer to Disk Data section of Cluster chapter. See also: Bug #18051, Bug #17844.
Description: + INITIAL_SIZE as Int_Size FROM INFORMATION_SCHEMA.FILES; + Name Free Total Size Int_Size + undofile.dat NULL 4194304 4 16777216 + undofile02.dat NULL 1048576 4 4194304 + NULL 5223944 NULL 4 NULL Not sure what NULL 5223944 NULL 4 NULL is suppose to be showing us. How to repeat: CREATE LOGFILE GROUP lg1 ADD UNDOFILE 'undofile.dat' INITIAL_SIZE 16M UNDO_BUFFER_SIZE = 1M ENGINE=NDB; ALTER LOGFILE GROUP lg1 ADD UNDOFILE 'undofile02.dat' INITIAL_SIZE = 4M ENGINE=NDB; SELECT DISTINCT FILE_NAME as Name, FREE_EXTENTS as Free, TOTAL_EXTENTS as Total, EXTENT_SIZE as Size, INITIAL_SIZE as Int_Size FROM INFORMATION_SCHEMA.FILES; Suggested fix: Not sure what to do with it, or why it is there.