OK, i might have been a little bit fast on the trigger there 😛
We have actually specified some retention based on time, size, number of buckets and whatNot for our indexes ...
So it seems the input, monitored file, is bigger than at least one if not all of the configure buckets in Hot ...
Any thoughts ? 🙂
39311:07-27-2013 19:41:21.549 +0200 ERROR IndexProcessor - cannot index event because it is larger than mpool size=## source=source::##
39312-07-27-2013 19:41:28.625 +0200 ERROR JournalSlice - Error writing: Success, file="##"
39313-07-27-2013 19:41:28.635 +0200 ERROR databasePartitionPolicy - Unable to write raw: for idx=##, path='##'
39314-07-27-2013 19:41:28.636 +0200 INFO databasePartitionPolicy - idx=## Moving from='hot_v1_96' to warm='write error on hot bucket'
39315-07-27-2013 19:41:38.647 +0200 WARN JournalSlice - Path="##" never got expected file size even after waiting 10000 ms
39316-07-27-2013 19:41:38.647 +0200 ERROR JournalSlice - Forcing immediate bucket roll due to incorrect size of bucket due to inconsistent file size of path="##"
... View more