View Issue Details

IDProjectCategoryView StatusLast Update
0001259IB LogManagerIBLMPumppublic2015-07-10 15:47
ReporterVitalij Assigned To 
PriorityhighSeveritycrashReproducibilityalways
Status newResolutionopen 
OSWindowsOS Version7 
Product Version2.12.5 
Summary0001259: Background pumping killing disks
DescriptionWhen using IBLMPump in background pumping mode, abnormal amount of IO operations are generated on disks where transaction log database is located.
When normally we have about 50 I/O operations per second (IOPS) on the disks with IBLMPump running there is around 30 000 I/O operations per seconds on the disks. As a result replication crashes.
Is there a way to tweak application so it won't kill disks?
Steps To Reproduceconfig:

[Source]
Path=ra.fdb
Charset=UNICODE_FSS
Username=sysadm
Password=xxx
Dialect=3
IBLM_MetadataTable=IBLM$METADATA
LogCurrentGeneratorValues=1
LogCurrentGeneratorValuesEachRun=1
UseEncryptedPassword=1

[Destination]
Path=a-log.fdb
Charset=UNICODE_FSS
Username=sysadm
Password=xxx
Dialect=3
IBLM_MetadataTable=IBLM$METADATA
UseEncryptedPassword=1
CommitInterval=100

[General]
SMTP_Host=smtp.iblogmanager.com
SMTP_Port=25
SMTP_UseAuthentication=0
SMTP_Username=XXX
SMTP_Password=yyy
SMTP_UseEncryptedPassword=0
EmailFrom_Name=IBLMPump Utility
EmailTo_Address=
EmailCc_Address=
EmailBcc_Address=

command: iblmpump.exe -i iblmpump.ini -b -v
Additional InformationIBLMPump is running on Windows 7.
Transaction log database is located on a server running CentOS.
TagsNo tags attached.

Activities

Vitalij

2015-07-10 15:47

reporter   ~0000382

In the same time when IBLMPump is running all free amount of disk space is getting used. As a result DB is crashing.

Issue History

Date Modified Username Field Change
2015-07-10 15:36 Vitalij New Issue
2015-07-10 15:47 Vitalij Note Added: 0000382