Bug #40724 | Entire Cluster Crashes When A LG With Large Undo Log >150M Is Created | ||
---|---|---|---|
Submitted: | 14 Nov 2008 2:08 | Modified: | 19 Feb 2009 10:48 |
Reporter: | Mikiya Okuno | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Cluster: Disk Data | Severity: | S1 (Critical) |
Version: | 6.3.18 | OS: | Linux (Ubuntu 8.10) |
Assigned to: | Assigned Account | CPU Architecture: | Any |
[14 Nov 2008 2:08]
Mikiya Okuno
[14 Nov 2008 3:42]
MySQL Verification Team
I did the test using the following settings. [NDBD DEFAULT] NoOfReplicas=2 DataMemory=1024M IndexMemory=64M LockPagesInMainMemory=1 MaxNoOfTables=256 MaxNoOfOrderedIndexes=512 MaxNoOfUniqueHashIndexes=256 MaxNoOfAttributes=8192 MaxNoOfConcurrentOperations=250000 FragmentLogFileSize=64M NoOfFragmentLogFiles=4 RedoBuffer=64M ODirect=1 ### Disk data related DiskPageBufferMemory=2000M SharedGlobalMemory=1500M
[19 Feb 2009 10:48]
Jonas Oreland
duplicate of bug#34102 (which I just fixed)