On Mon, Jul 14, 2014 at 12:06 AM, Kireet Reddy <[email protected]> wrote:
> We did the test with ES still running and indexing data, ES still > running/not indexing, and ES stopped. All three showed the poor i/o rate. > Then after a few minutes, the copy i/o rate somehow increased again. It was > really strange. We still have some digging to do to figure out the problem > there. > Whoa, OK. That's really spooky: boxes are *not* supposed to behave this way (get tired, like humans, after running too hard / too long). Hopefully you get to the bottom of it... Mike McCandless http://blog.mikemccandless.com -- 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/CAD7smRcQYSc7%2BeF%2BiLrU_0FMWciQ4JHihedH12zB%2BADXLz9RSg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
