This sample demonstrates the use of log flushing options
MCO_TRANSLOG_SYNC_TIMER
andMCO_TRANSLOG_SYNC_COUNT
. The application sets up two kinds of flushing strategies: by transactions count and by timer. The latter assumes a user-defined call-back function has been registered. The sample provides output when the timer callback signals to eXtremeDB that the timeout is exceeded, which causes the application to start transaction logging and perform read-write transactions which in turn produces output to the log by the timer and count flushing options.
See instructions here on how to build this and other samples on your development platform. Once built, the sample can be run from the
\target\bin
directory:tlogflushBut it is more instructive to run it in your development environment debugger, stepping through the code.