We have a splunk light forwarder monitoring a file that grows in excess of 5GB a day before rolling over. The roll over threshold cannot be changed. Splunk is having issues indexing this file and often time misses data, completely stops indexing data for this source (although other sources on the box seem fine) or indexes data on a different date than when the log was written. (for instance, an event will be written to the log on the 17th, but it will show up on our search head as the 14th or 15th). Unfortunately, there is only a time in the log and not a date.
Does anyone know if there is a maximum size a log can be for Splunk to still successfully monitor and forward that log? Is there an easy work around to the issue of the date not being present in the log?