What are the pros and cons of increasing vm.max_map_count from 64k to 256k?
Does 64k vm.max_map_count imply --> 64k addresses * 64kb page size = upto 4GB of lucene index data can be referenced by ES which is actually residing on FS cache?
And if i exceed 4GB - the adressable space due to the max_map_count limit, will OS need to page out some of the older accessed index data?
Maybe my above undertsanding is not correct as FS cache can use up remaining memory of say 16GB to store lucene data. So i am not sure what exactly the vm.max_map_count limit does
How does this limit result in OOM?
I also read http://blog.thetaphi.de/2012/07/use-lucenes-mmapdirectory-on-64bit.html which had good explanation but still could not fully understand the full role and impact of increasing vm.max_map_count