On Thu, May 29, 2014 at 8:16 PM, Edward Sargisson <[email protected]> wrote: > > Our fix was to configure VMWare to reserve the entire configured memory. > This means that the host doesn't try to take the memory back. It seemed > sensible to reserve all of the configured memory as we want elasticsearch > to keep its buffers and memory maps in place just as it would be on a > hardware instance in production. If placed under memory pressure, the OS > would start to reclaim these things. > > After making the change, we've been running for a few weeks with no > further failures. >
That's great to hear! Memory ballooning is mostly fine for application servers or job servers but is the kiss of death to databases and database like things. You may want to take an inventory of what has memory ballooning on and make sure they can handle it.... Nik -- 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/CAPmjWd1fOyW3bkJ1w78OJ_XvJHNLJDzNXGz4RBGHeiDZSgQ3Bw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
