Thanks Eric. Its super helpful! So here's my understanding so far:
1. On update, write the doc to tlog(which will be used only for recovery) 2. As soon as the docs size becomes greater than ramBufferSize, flush it to the latest segment inside the index directory. 3. Upto this point, even though the index directory size will grow, but the docs are neither searchable not durable. 4. As soon as I issue a soft commit, the documents inside the latest segment becomes searchable, but they are still not merged with main index. Hence they are still not durable. 5. At this point if a node goes down, the docs will still needs to be replayed from the tlog, before they are searchable. If someone deletes tlogs before starting that node, then the documents are lost. They can't be recovered from unclosed segments inside index directory. 6. As soon as I issue a hard commit, the docs becomes durable. So that means if I increase maxRamBufferSize, then there will be less file system access, but more load on memory. Please let me know if I get it right so far before I ask further questions? -- View this message in context: http://lucene.472066.n3.nabble.com/Solr-tlog-and-soft-commit-tp4193105p4193126.html Sent from the Solr - User mailing list archive at Nabble.com.
