Re: {soft}Commit and cache flusing

2013-10-10 Thread Dmitry Kan
Tim, my suggestion was very concise, sorry for that. But not at all "rude" or anything. Instead, tried to help you. Dmitry On Wed, Oct 9, 2013 at 9:28 PM, Tim Vaillancourt wrote: > Apologies all. I think the suggestion that I was replying "to get noticed" > is what erked me, otherwise I would

Re: {soft}Commit and cache flusing

2013-10-09 Thread Tim Vaillancourt
Apologies all. I think the suggestion that I was replying "to get noticed" is what erked me, otherwise I would have moved on. I'll follow this advice. Cheers, Tim On 9 October 2013 05:20, Erick Erickson wrote: > Tim: > > I think you're mis-interpreting. By replying to a post with the subject:

Re: {soft}Commit and cache flusing

2013-10-09 Thread Erick Erickson
Tim: I think you're mis-interpreting. By replying to a post with the subject: {soft}Commit and cache flushing but going in a different direction, it's easy for people to think "I'm not interested in that thread, I'll ignore it", thereby missing the fact that you're asking a somewhat different qu

Re: {soft}Commit and cache flusing

2013-10-08 Thread Tim Vaillancourt
I have a genuine question with substance here. If anything this nonconstructive, rude response was "to get noticed". Thanks for contributing to the discussion. Tim On 8 October 2013 05:31, Dmitry Kan wrote: > Tim, > I suggest you open a new thread and not reply to this one to get noticed. > Dm

Re: {soft}Commit and cache flusing

2013-10-08 Thread Dmitry Kan
Tim, I suggest you open a new thread and not reply to this one to get noticed. Dmitry On Mon, Oct 7, 2013 at 9:44 PM, Tim Vaillancourt wrote: > Is there a way to make autoCommit only commit if there are pending changes, > ie: if there are 0 adds pending commit, don't autoCommit (open-a-searcher

Re: {soft}Commit and cache flusing

2013-10-07 Thread Tim Vaillancourt
Is there a way to make autoCommit only commit if there are pending changes, ie: if there are 0 adds pending commit, don't autoCommit (open-a-searcher and wipe the caches)? Cheers, Tim On 2 October 2013 00:52, Dmitry Kan wrote: > right. We've got the autoHard commit configured only atm. The so

Re: {soft}Commit and cache flusing

2013-10-02 Thread Dmitry Kan
right. We've got the autoHard commit configured only atm. The soft-commits are controlled on the client. It was just easier to implement the first version of our internal commit policy that will commit to all solr instances at once. This is where we have noticed the reported behavior. On Wed, Oct

Re: {soft}Commit and cache flusing

2013-10-01 Thread Bram Van Dam
if there are no modifications to an index and a softCommit or hardCommit issued, then solr flushes the cache. Indeed. The easiest way to work around this is by disabling auto commits and only commit when you have to.

Re: {soft}Commit and cache flusing

2013-10-01 Thread Dmitry Kan
Thanks a lot Shawn for an exhaustive reply! Regards, Dmitry On Tue, Oct 1, 2013 at 5:37 PM, Shawn Heisey wrote: > On 10/1/2013 2:48 AM, Dmitry Kan wrote: > > This is a minor thing, perhaps, but thought to ask / share: > > > > if there are no modifications to an index and a softCommit or hardCo

Re: {soft}Commit and cache flusing

2013-10-01 Thread Shawn Heisey
On 10/1/2013 2:48 AM, Dmitry Kan wrote: > This is a minor thing, perhaps, but thought to ask / share: > > if there are no modifications to an index and a softCommit or hardCommit > issued, then solr flushes the cache. Any time you do a commit that opens a new Searcher object (openSearcher=true, w

{soft}Commit and cache flusing

2013-10-01 Thread Dmitry Kan
Hello! This is a minor thing, perhaps, but thought to ask / share: if there are no modifications to an index and a softCommit or hardCommit issued, then solr flushes the cache. Is this designed on purpose? Regards, Dmitry