Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
Received-SPF: pass (athena.apache.org: domain of erickerickson@gmail.com
 designates 209.85.223.174 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <549546434.810191424976011710.JavaMail.httpd@webmail-51.iol.local>
References: <549546434.810191424976011710.JavaMail.httpd@webmail-51.iol.local>
Date: Thu, 26 Feb 2015 10:53:00 -0800
Message-ID: 
 <CAN4YXvds78+JT6RwwnTiwquP81swd4kpOaRB075SY7MCSVQXRA@mail.gmail.com>
Subject: Re: Solr collection unavailable after reload
From: Erick Erickson <erickerickson@gmail.com>
To: solr-user@lucene.apache.org, "akirapix@libero.it" <akirapix@libero.it>
Content-Type: text/plain; charset=UTF-8

This is very, very strange. How are you indexing the docs? SolrJ? XML? DIH?

What happens if you _only_ index the doc?

You say nothing comes out in the log file indicating an error, but
what _does_ come out? Particularly at the end?

And in general note that attachments don't come through the Apache
mailing lists, to show them you usually have to post it somewhere and
provide a link.

You _might_ be hitting the problem where the suggester takes a long
time to build on startup, in which case you'll be seeing a message at
the end of your log when you can't start things about building. If you
wait _very_ patiently it'll eventually complete. This was commented
out of solrconfig.xml stock distros in 4.10.3, see:
https://issues.apache.org/jira/browse/SOLR-6679. And if your suggester
is configured with anything like "build on commit", it'll happen
whenever you index.

Anyway, this is consistent with the problems you've reported, so at
least there's a chance it's the issue.

Best,
Erick

On Thu, Feb 26, 2015 at 10:40 AM, akirapix@libero.it <akirapix@libero.it> wrote:
> Hi everybody,
>
> hi have a very strange issue in my solr (version 4.10.2) installation (on a
> windows server 2008 java jdk 1.7).
>
> I am sure nobody met this problem before (at least googling around i found
> nothing). I have a simple configuration with a base "text_general"  field.
> I was able to index any kind of text without any problem. After some days i
> got a strange behavior. After restarting my server i was not able to load my
> collection
> My server started without error messages in my log but, trying to select my
> collection, web app hangs (as in picture)
>
> I googled around to find a way to debug such situation, or a way to "fix"
> collection itself (but found nothing).
>
> I am able to produce such error trying to index word "wasting" in my
> text_general field ( i know that problem is not related to this word....but
> is the only way to produce such behavior).
> The only thing i can do is stop solr, delete "index" folder content and
> restart solr. Then i try again to index a document with "wasting" word,
> reload collection, and the problem is there again.
>
> Please someone could at least tell me a way to investigate????
>