The LogicalSessionCacheRefresh thread runs in the background and will modify the config.system.sessions collection. This can lead to data inconsistencies being reported between nodes after other manual maintenance operations are performed on mongod in standalone mode (e.g. dropping a conflicting index). Note that drivers and mongosh include a logical session ID in all commands sent to the server.

We can consider expanding the logic to avoid scheduling the jobs when a replica set member is running in standalone mode, very much like the TTL monitor thread is disabled.