Bug #44448 ndb_mgmd declares FragmentLogFileSize=2G invalid by "1" and adjusts
Submitted: 23 Apr 2009 22:32 Modified: 8 Oct 2009 13:59
Reporter: Jonathan Miller Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:mysql-5.1-telco-7.0 OS:Linux
Assigned to: Magnus Blåudd CPU Architecture:Any
Tags: mysql-5.1-telco-7.0.5
Triage: Triaged: D4 (Minor) / R1 (None/Negligible) / E1 (None/Negligible)

[23 Apr 2009 22:32] Jonathan Miller
Description:
2009-04-24 02:07:03 [MgmSrvr] INFO     -- Reading cluster configuration using my.cnf
2009-04-24 02:07:03 [MgmSrvr] Warning: option 'FragmentLogFileSize': signed value 2147483648 adjusted to 2147483647

How to repeat:
Set FragmentLogFileSize=2G and start cluster

Suggested fix:
A file size of 2 gigabytes can also be expressed as
17179869184 bits
2147483648 bytes
2097152 kilobytes (abbreviated as KB or Kb*)
2048 megabytes (abbreviated as M or MB)
2 gigabytes (abbreviated as G or GB)
0.001953 terabytes
0.0000019 petabytes
[6 Oct 2009 13:56] Magnus Blåudd
FragmentLogFileSize has been limited to 1G, but still possible to get this with for example DiskSyncSize

Warning: option 'DiskSyncSize': signed value 4294967296 adjusted to 2147483647

It's my_getopt that parse the value as signed and "truncates" it accordingly.
[6 Oct 2009 14:24] Bugs System
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/85922
[8 Oct 2009 12:36] Magnus Blåudd
Pushed to 7.0
[8 Oct 2009 13:31] Bugs System
Pushed into 5.1.39-ndb-7.1.0 (revid:frazer@mysql.com-20091008132902-a4xc1mn6m82i4ix4) (version source revid:frazer@mysql.com-20091008132902-a4xc1mn6m82i4ix4) (merge vers: 5.1.39-ndb-7.1.0) (pib:11)
[8 Oct 2009 13:59] Jon Stephens
Documented fix in the NDB-7.0.9 changelog as follows:

        Numeric configuration parameters set in my.cnf were interpreted
        as signed rather than unsigned values. The effect of this was
        that values of 2G or more were truncated with the warning
        "[MgmSrvr] Warning: option '*option_name*': signed value 
        *option_value* adjusted to 2147483647". Now such parameter values 
        are treated as unsigned, so that this truncation does not take 
        place.

        This issue did not effect parameters set in config.ini.

Closed.