right, doesn’t sound likely that it’s rebuilding suggesters/spellcheckers.
Throwing a profiler at it to see where it’s spending the time might be easiest.
> On Nov 22, 2019, at 3:45 AM, Koen De Groote
> wrote:
>
> Thanks for the link, that's some nice documentation and guidelines.
>
> I'll pr
Thanks for the link, that's some nice documentation and guidelines.
I'll probably have time to test again next week, but in the meantime, it
does make me scratch my head.
I deleted the root folder and re-instrumented the environment.
So, there's nothing there. Nothing.
The text says:
"Do you r
https://doc.sitecore.com/developers/90/platform-administration-and-architecture/en/using-solr-auto-suggest.html
If you need more references. Set all parameters yourself, don’t rely on
defaults.
> On Nov 21, 2019, at 3:41 PM, Dave wrote:
>
> https://lucidworks.com/post/solr-suggester/
>
> Yo
https://lucidworks.com/post/solr-suggester/
You must set buildonstartup to false, the default is true. Try it
> On Nov 21, 2019, at 3:21 PM, Koen De Groote
> wrote:
>
> Erick:
>
> No suggesters. There is 1 spellchecker for
>
> text_general
>
> But no buildOnCommit or buildOnStartup setting
Erick:
No suggesters. There is 1 spellchecker for
text_general
But no buildOnCommit or buildOnStartup setting mentioned anywhere.
That being said, the point in time at which this occurs, the database is
guaranteed to be empty, as the data folders had previously been deleted and
recreated empty.
Koen:
Do you have any spellcheckers or suggesters defined with buildOnCommit or
buildOnStartup set to “true”? Depending on the implementation, this may have to
read the stored data for the field used in the suggester/spellchecker from
_every_ document in your collection, which can take many min
The logs files showed a startup, printing of all the config options that
had been set, 1 or 2 commands that got executed and then nothing.
Sending the curl did not get shown in the logs files until after that
period where Solr became unresponsive.
Service mesh, I don't think so? It's in a docker
Have you checked the log files of Solr?
Do you have a service mesh in-between? Could it be something at the network
layer/container orchestration that is blocking requests for some minutes?
> Am 20.11.2019 um 10:32 schrieb Koen De Groote :
>
> Hello
>
> I was testing some backup/restore sce
Hello
I was testing some backup/restore scenarios.
1 of them is Solr7.6 in a docker container(7.6.0-slim), set up as
SolrCloud, with zookeeper.
The steps are as follows:
1. Manually delete the data folder.
2. Restart the container. The process is now in error mode, complaining
that it cannot fi
