What is: ERROR BucketMover - sizeBytes=xxx candidateBytes=yyy

[rune_hellem]

Got a lot of logged events in the _internal-index for one of our indexers. First we always see an event like this

02-24-2014 13:43:42.850 +0100 INFO  BucketMover - will attempt to freeze: candidate='e:\splunk\indexes\test\db\db_1389020646_1383541534_0' because frozenTimePeriodInSecs=2592000 exceeds difference between now=1393245822 and latest=1389020646

Then immediately we get an error event like this

02-24-2014 13:43:42.850 +0100 ERROR BucketMover - sizeBytes=176128 candidateBytes=253952

24 events the last 15 minutes, and they keep coming.

Searchhead and indexers on Windows 2012, Splunk 6.0.1 (build 189883)

[jdastmalchi_spl · Accepted solution]

This looks like a known issue fixed in 6.1.4. SPL-86189
http://docs.splunk.com/Documentation/Splunk/6.1.3/ReleaseNotes/KnownIssues

[rune_hellem]

Did update on 1'st of October to 6.1.4, no errors seen since then.

[rune_hellem]

2,018 events (08/09/2014 00:00:00.000 to 08/09/2014 21:41:16.000)

So...no, still an issue

Now using Splunk 6.1.3 build 220630

[jonathan_cooper]

Still no help on this? I am seeing this same issue, also getting authentication errors/timeouts on search peers periodically. Thought it had to do with too many search jobs, but ruled that out when I disabled everything.

[rune_hellem]

93 events last 60 minutes, so sorry - still an issue here as well.

[theouhuios]

Any update on this? Seeing it on linux too

[rune_hellem]

Now running Splunk 6.1.1 build 207789, still same issue

[rune_hellem]

Checked just now, 1048 events so far today, 5 on one of the indexers, the rest shared on the searchhead and the second indexer, so still an issue

[jerinabeham]

We have also got a ton of this error.
Could anyone please throw some light on this error?