I've set up a master slave configuration and it's working great! I know this is the better setup but if I had just one index due to requirements, I'd like to know more about the performance hit of the commit. let's just assume I have a decent size index of a few gig normal sized documents with high traffic. A few questions:
- (main question) When you do a commit on a single index, is there anytime when the reads will not have an index to search on? - With the rebuilding of caches and whatever else happens, is the only downside the fact that the server performance will be degraded due to file copy, cache warming, etc.. or will the index be actually locked at some point? - On a commit, do the files get copied so you need double the space or is that just the optimize? I know a master/slave setup is used to reduce these issues, but if I had only one server I need to know the potential risks. Thanks, Mike
