LiteDB log file persists after program close

[dylanstreb]

Litedb 5 now creates a dbname-log.db file. Hangfire.LiteDB appears to not properly clean up litedb resources, so the log file persists after program termination. I suspect some Dispose call is getting lost at some point. From trying to open the actual db in LiteDB Studio, it looks like the content is never written to the real db, only to the forward log.

This occurs with the console app in the samples folder, as a quick demo of the issue.

[ruslan-mogilevskiy]

That's not a problem of this library. LiteDB's Checkpoint method needs to be called manually, possibly with some schedule or so depending on your application needs.

[bkempinski]

Workaround:

        services.AddHangfire((services, options) =>
        {
            var lifetime = services.GetRequiredService<IHostApplicationLifetime>();
            var liteDb = options.UseLiteDbStorage(jobsDbName, storageOptions.Value);

            lifetime.ApplicationStopping.Register(() => liteDb.Entry.Connection.Database.Dispose());
        });