*2) Though *not* recommended - kill -9 should not result in data loss. If > so it's a bug and should be reported.* > > It *should* not, but it *may*. A kill -9 ends a process without allowing it to flush any unwritten buffers to disk, close any open files, or even finish writing what it started. No process can detect or capture it; therefore no process can perform any cleanup, shutdown, or completion.
So file all the bugs you wish, but there is no code change that can be made to detect or handle a kill -9. Nothing in the Java code, and nothing in the underlying JVM that is the process itself. Unless ES is redesigned so that any given disk block can be written or not and the entire index remains fully consistent. Because while the process cannot detect a kill -9, the OS waits until it returns from any kernel call before ripping the rug out from under it. Kill -9 just dangerous. No, it's not a guarantee of disaster. But the same could be said about walking blindfolded across the Autobahn. Brian -- 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 elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/be116ad2-61b2-482b-97e2-0557c92c78f5%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
