Hi All, This is a bit off topic, but we only see this on some of our elastic search hosts, and it is also the only place where we enable mlockall for java which is our understanding is a strongly recommended best practice.
Basically we from time to time see kswapd run away at 100% on a single core. It seems to hit our master nodes more frequently, and they also have the least amount of memory. masters are: CentOS 6.4 4GB RAM 4GB swap ES_HEAP_SIZE=2908m Does anybody know much about this and how to prevent it? We have hunted google groups, but have not really found the magic bullet. We have considered turning off swap and seeing what happens in the lab but prefer not to do that unless it is well known as the correct solution. Thanks, - Mike -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/57F0E223-ACBE-4819-A37C-4D935E2D71AF%40deman.com. For more options, visit https://groups.google.com/d/optout.
