On 10/15/2012 3:37 PM, Shawn Heisey wrote:
On 10/15/2012 2:51 PM, Chris Hostetter wrote:
For your usecase and upgrade: don't add the updateLog to your
configs, and
don't add autocommit to your configs, and things should work fine.
if you
decide you wnat to start using something that requires the updateLog,
you
should probably add a short autoCommit with openSearcher=false.
Thank you for your answer. Using updateLog seems to have another
downside -- a huge hit to performance. It wouldn't be terrible on
incremental updates. These happen once a minute and normally complete
extremely quickly - less than a second, followed by a commit that may
take 2-3 seconds. If it took 5-10 seconds instead of 3, that's not
too bad. But when you are expecting a process to take three hours and
it actually takes 8-10 hours, it's another story.
Could we create an option that would allow turning updateLog off for an
update request? To be useful to me, it would have to be something that
could also be specified in a dataimporthandler request. That way I
could do a full import with no log (for performance), but then when
SolrJ maintains the index, logging would be enabled.
Thanks,
Shawn
