SumoLogic Collector file locking Question
We are wondering about how/if Sumo locks files while reading them. How might processes writing to log files be affected by Sumo collectors reading from the log files at the same time? The only thing I've found is this document: https://support.sumologic.com/entries/23758636-Collector-locking-log-files-on-Windows-servers. We are using the 64bit version of the 64 bit collector, but this article isn't clear if the problem that was corrected by the 64bit version was that Sumo was actually locking the file in the first place or that Sumo "may not close the file for up to a couple of minutes". Can anyone point me to more specific information about how or if SumoLogic Collectors locks files?
Thanks,
Scott Edwards
-
Hi Scott,
The locking issue was only a problem with the 32bit version of the Collector and was only a problem on Windows.This was an issue with how the 32bit Windows libraries handled the sessions to the files.
Sumo Logic tries to be as unobtrusive as possible and does not specifically place any locks on files. The Collector will live tail a log file and will not drop the session for a few minutes, this is to ensure it has collected everything from the file, however during the time the Collector is reading from the file any other process should continue to be able to access, update, rename, or delete the file.If you are seeing some sort of locking on files please let us know as this would be unexpected behavior.
Please sign in to leave a comment.
Comments
1 comment