Hi,
My ndb_1_fs keeps growing to unexpected size. I have two nodes in my cluster.
I have recently rebuilt one node and re-synchronized data. On the newly rebuilt server, the ndb file system is 10-fold smaller than on the older node. The older node recently bombed out on me filling up all of its disk.
How can I estimate total disk space required for a given ndb cluster? I need to know the upper bound on the disk requirements.
Thanks!
Here is a snippet of the related cluster.ini config file:
[NDBD DEFAULT]
NoOfReplicas=2
Datadir=/var/lib/mysql-cluster
FileSystemPathDD=/var/lib/mysql-cluster
DataMemory=11000M
IndexMemory=1024M
LockPagesInMainMemory=1
MaxNoOfConcurrentOperations=1000000
StringMemory=25
MaxNoOfTables=4096
MaxNoOfOrderedIndexes=2048
MaxNoOfUniqueHashIndexes=512
MaxNoOfAttributes=24576
MaxNoOfTriggers=14336
DiskCheckpointSpeedInRestart=100M
FragmentLogFileSize=256M
InitFragmentLogFiles=SPARSE
NoOfFragmentLogFiles=72
RedoBuffer=48M
TimeBetweenLocalCheckpoints=20
TimeBetweenGlobalCheckpoints=1000
TimeBetweenEpochs=100
#MemReportFrequency=30
#BackupReportFrequency=10
### Params for setting logging
LogLevelStartup=15
LogLevelShutdown=15
LogLevelCheckpoint=8
LogLevelNodeRestart=15
### Params for increasing Disk throughput
BackupMaxWriteSize=1M
BackupDataBufferSize=16M
BackupLogBufferSize=4M
BackupMemory=20M
#Reports indicates that odirect=1 can cause io errors (os err code 5) on some systems. You must test.
#ODirect=1
### Watchdog
TimeBetweenWatchdogCheckInitial=60000
### TransactionInactiveTimeout - should be enabled in Production
TransactionInactiveTimeout=60000
### CGE 6.3 - REALTIME EXTENSIONS
#RealTimeScheduler=1
#SchedulerExecutionTimer=80
#SchedulerSpinTimer=40
### DISK DATA
SharedGlobalMemory=20M
DiskPageBufferMemory=64M
### Multithreading
MaxNoOfExecutionThreads=4
### Increasing the LongMessageBuffer b/c of a bug (20090903)
LongMessageBuffer=32M
BatchSizePerLocalScan=512
My ndb_1_fs keeps growing to unexpected size. I have two nodes in my cluster.
I have recently rebuilt one node and re-synchronized data. On the newly rebuilt server, the ndb file system is 10-fold smaller than on the older node. The older node recently bombed out on me filling up all of its disk.
How can I estimate total disk space required for a given ndb cluster? I need to know the upper bound on the disk requirements.
Thanks!
Here is a snippet of the related cluster.ini config file:
[NDBD DEFAULT]
NoOfReplicas=2
Datadir=/var/lib/mysql-cluster
FileSystemPathDD=/var/lib/mysql-cluster
DataMemory=11000M
IndexMemory=1024M
LockPagesInMainMemory=1
MaxNoOfConcurrentOperations=1000000
StringMemory=25
MaxNoOfTables=4096
MaxNoOfOrderedIndexes=2048
MaxNoOfUniqueHashIndexes=512
MaxNoOfAttributes=24576
MaxNoOfTriggers=14336
DiskCheckpointSpeedInRestart=100M
FragmentLogFileSize=256M
InitFragmentLogFiles=SPARSE
NoOfFragmentLogFiles=72
RedoBuffer=48M
TimeBetweenLocalCheckpoints=20
TimeBetweenGlobalCheckpoints=1000
TimeBetweenEpochs=100
#MemReportFrequency=30
#BackupReportFrequency=10
### Params for setting logging
LogLevelStartup=15
LogLevelShutdown=15
LogLevelCheckpoint=8
LogLevelNodeRestart=15
### Params for increasing Disk throughput
BackupMaxWriteSize=1M
BackupDataBufferSize=16M
BackupLogBufferSize=4M
BackupMemory=20M
#Reports indicates that odirect=1 can cause io errors (os err code 5) on some systems. You must test.
#ODirect=1
### Watchdog
TimeBetweenWatchdogCheckInitial=60000
### TransactionInactiveTimeout - should be enabled in Production
TransactionInactiveTimeout=60000
### CGE 6.3 - REALTIME EXTENSIONS
#RealTimeScheduler=1
#SchedulerExecutionTimer=80
#SchedulerSpinTimer=40
### DISK DATA
SharedGlobalMemory=20M
DiskPageBufferMemory=64M
### Multithreading
MaxNoOfExecutionThreads=4
### Increasing the LongMessageBuffer b/c of a bug (20090903)
LongMessageBuffer=32M
BatchSizePerLocalScan=512