Glad to hear it's solved! The suggester stuff is
way cool, but can surprise you!
Erick
On Thu, Dec 17, 2015 at 2:54 AM, Vincenzo D'Amore wrote:
> Great!!! Great Erick! It was a buildOnCommit.
>
> Many thanks for your help.
>
>
>
> On Wed, Dec 16, 2015 at 6:30 PM, Erick Erickson
> wrote:
>
>
Great!!! Great Erick! It was a buildOnCommit.
Many thanks for your help.
On Wed, Dec 16, 2015 at 6:30 PM, Erick Erickson
wrote:
> Quick scan, but probably this:
> INFO
> o.a.solr.spelling.suggest.Suggester - build()
>
> The suggester build process can easily take many minutes, there's some
Quick scan, but probably this:
INFO
o.a.solr.spelling.suggest.Suggester - build()
The suggester build process can easily take many minutes, there's some
explanation here:
https://lucidworks.com/blog/2015/03/04/solr-suggester/
the short form is that depending on how it's defined, it may have to
Hi,
an update. Hope you can help me.
I have stopped all the other working collections, in order to have a clean
log file.
at 11:01:16 an hard commit has been issued
2015-12-16 11:01:49,839 [http-bio-8080-exec-824] INFO
org.apache.solr.update.UpdateHandler - start
commit{,optimize=false,openSea
Autowarm times will only happen when the commit has openSearcher=true
or on a soft commit. But maybe your log levels aren't at INFO for the right
code...
That said, your autowarm counts at 0 probably means that you're not seeing
any autowarming really, so that might be a red herring. Your newSearc
Hi All,
an update, I have switched logging from WARN to INFO for all except for
those two:
- org.apache.solr.core
- org.apache.solr.handler.component.SpellCheckComponent
Well, looking at log file I'm unable to find any autowarm log line, even
after few updates and commits.
Looking at solrconfig
Thanks Erick, Mark,
I'll raise maxTime asap.
Just to be sure understand, given that I have openSearcher=false, I suppose
it shouldn't trigger autowarming at least until a commit is executed,
shouldn't it?
Anyway, I don't understand, given that maxTime is very aggressive, why hard
commit takes so
He has waitSearcher as false it looks, so all the time should be in the
commit. So that amount of time does sound odd.
I would certainly change those commit settings though. I would not use
maxDocs, that is an ugly way to control this. And one second is much too
aggressive as Erick says.
If you w
First of all, your autocommit settings are _very_ aggressive. Committing
every second is far to frequent IMO.
As an aside, I generally prefer to omit the maxDocs as it's not all
that predictable,
but that's a personal preference and really doesn't bear on your problem..
My _guess_ is that you are
Hi all,
I have a SolrCloud cluster with a collection (2.5M docs) with 3 shards and
15 replicas.
There is a solrj application that feeds the collection, updating few
documents every hour, I don't understand why, at end of process, the hard
commit takes about 8/10 minutes.
Even if there are only fe
10 matches
Mail list logo
