Versions (relevant - OpenSearch/Dashboard/Server OS/Browser):
2.16
Describe the issue:
I have an opensearch cluster with one node dedicated for the search role (searchable snapshots). I have stored several indices of around each 50GB in a S3 repository and I realize that when I restore one snapshot as a searchable snapshot, the cache directory in the node with search role (inside the path.data variable) grows around 1GB for every index I restore as searchable snapshot, in a initial state, without doing any search. So if I have 100 indices restored as searchable snapshots I would need initially 100GB in the cache directory without even doing any search. Is there any parameter to tune the initial cache?, thanks.