Why is coldPath.maxDataSizeMB taking precedence and growing until parameter is reached?

[srteclesmayer]

I have the following configuration for an index extracted by using btool:

/opt/splunk/etc/system/local/indexes.conf   coldPath.maxDataSizeMB = 1843200
/opt/splunk/etc/system/local/indexes.conf   maxTotalDataSizeMB = 500000

But the coldPath doesn't care about maxTotalDataSizeMB parameter and it gets bigger and bigger:

950G    ./colddb
36G     ./frozendb
74M     ./datamodel_summary
4.0K    ./thaweddb
985G    .

So I checked how other indexes in my production environment were configured. For other indexes, I have the following configuration:

/opt/splunk/etc/system/local/indexes.conf   coldPath.maxDataSizeMB = 0
/opt/splunk/etc/system/local/indexes.conf   maxTotalDataSizeMB = 500000

And for these cases the rotation works propertly.

So my opinion is that coldPath.maxDataSizeMB has precedence over maxTotalDataSizeMB and even when maxTotalDataSizeMB is reached it keeps growing until coldPath.maxDataSizeMB parameter is reached.

I hope someone can help me to understand this situation because I'm suffering a huge problem in my environment.

Thank you in advance.