maxHotSpanSecs determines how long a hot bucket is open before it rolls over to warm.
However, both hot and warm buckets consume disk space. This is the data roll progression:
Hot(lives at the specified hot/warm mount point, is able to be written to)------/after maxHotSpanSecs or other config/-->
Warm(lives at the specified hot/warm mount point, is read only)----/after maxWarmDBCount/--->
Cold(lives at the specified cold path which could be on the same disk as hot/warm or a different one, is read only)-/(maxTotalDataSizeMB)->
Frozen (deleted by default but could be archived somewhere or sent into Hadoop)
It sounds like you want to do is hard footprint taken up on disk so I would suggest setting maxTotalDataSizeMB to the maximum amount of space you want that index to take up on disk.
... View more