Bug 47844

Bug: 47844

Impact:

Product:

GemStone/S 64 Bit

Versions:

3.4.3, 3.4.2, 3.4.1, 3.4, 3.3.9, 3.3.8, 3.3.7, 3.3.6, 3.3.5, 3.3.4, 3.3.3, 3.3.2, 3.3.1, 3.3, 3.2.17, 3.2.16, 3.2.15, 3.2.14, 3.2.13, 3.2.12, 3.2.11, 3.2.10, 3.2.9, 3.2.8.1, 3.2.8, 3.2.7, 3.2.6, 3.2.5, 3.2.4, 3.2.3, 3.2.2, 3.2.1, 3.2, 3.1.0.6, 3.1.0.5, 3.1.x

Platform:

All Platforms

Fixed In:

3.5, 3.4.4

Logreceiver race condition can cause slave stone tranlog read failure

There is a race condition in the logreceiver logic that can cause the slave stone to attempt to read from a newly transferred tranlog before any data has been permanently flushed to disk.  This will generate errors that look like this (for tranlog ID XXXXX)

    WARNING: for fileId XXXXX,
       filename = <tranlog_directory>/tranlogXXXXX.dbf
    This file is not a GemStone transaction log file:
    error in read() , <tranlog_directory>/tranlogXXXXX.dbf failed with errno=9,EBADF, Bad file number (file is not open, or cannot be read/written)

Workaround

You will need to restart the "SystemRepository continuousRestoreFromArchiveLogs:*" command on the slave stone.