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 container, but that
shouldn't be a problem, it usually never is.


On Wed, Nov 20, 2019 at 10:42 AM Jörn Franke <jornfra...@gmail.com> wrote:

> 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 <
> koen.degro...@limecraft.com>:
> >
> > 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 find the cores.
> > 3. Fix the install, meaning create new data folders, which are empty at
> > this point.
> > 4. Restart the container again, to pick up the empty folders and not be
> in
> > error anymore.
> > 5. Perform the restore
> > 6. Check if everything is available again
> >
> > The problem is between step 4 and 5. After step 4, it takes several
> minutes
> > before solr actually responds to curl commands.
> >
> > Once responsive, the restore happened just fine. But it's very stressful
> in
> > a situation where you have to restore a production environment and the
> > process just doesn't respond for 5-10 minutes.
> >
> > We're talking about 20GB of data here, so not very much, but not little
> > either.
> >
> > Is it normal that it takes so long before solr responds? If not, what
> > should I look at in order to find the cause?
> >
> > I have asked this before recently, though the wording was confusing. This
> > should be clearer.
> >
> > Kind regards,
> > Koen De Groote
>

Reply via email to