Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
Subject: Re: solr blocking and client timeout issue
To: solr-user@lucene.apache.org
References: <55A97B7B.7080800@edgate.com> <55A9808F.4010707@elyograg.org>
 <1437172788348.78092@edgate.com> <55A98C60.3080802@elyograg.org>
 <55A9F56F.10202@edgate.com> <55AA6DC3.7030302@elyograg.org>
 <55AB47C1.1080401@edgate.com> <55AB7281.2080105@elyograg.org>
 <55AD35CF.3090106@edgate.com>
From: Shawn Heisey <apache@elyograg.org>
Message-ID: <55AD419C.9010704@elyograg.org>
Date: Mon, 20 Jul 2015 12:44:44 -0600
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101
 Thunderbird/38.1.0
MIME-Version: 1.0
In-Reply-To: <55AD35CF.3090106@edgate.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

On 7/20/2015 11:54 AM, Jeremy Ashcraft wrote:
> I'm ugrading to the 1.8 JDK on our dev VM now and testing. Hopefully i
> can get production upgraded tonight.
>
> still getting the big GC pauses this morning, even after applying the
> GC tuning options.  Everything was fine throughout the weekend.
>
> My biggest concern is that this instance had been running with no
> issues for almost 2 years, but these GC issues started just last week.

It's very possible that you're simply going to need a larger heap than
you have needed in the past, either because your index has grown, or
because your query patterns have changed and now your queries need more
memory.  It could even be both of these.

At your current index size, assuming that there's nothing else on this
machine, you should have enough memory to raise your heap to 5GB.

If there ARE other software pieces on this machine, then the long GC
pauses (along with other performance issues) could be explained by too
much memory allocation out of the 8GB total memory, resulting in
swapping at the OS level.

Thanks,
Shawn