Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
Date: Tue, 19 Sep 2017 01:11:48 -0700 (MST)
From: shamik <shamikb@gmail.com>
To: solr-user@lucene.apache.org
Message-ID: <1505808708630-0.post@n3.nabble.com>
In-Reply-To: <1505805507.11509.33.camel@kb.dk>
References: <CAG+u80spdpmfeDnJXPc_eprp7mawBRqoYjMSceue+BixPKB+9A@mail.gmail.com> <4440F0C3-659D-4B2D-B2E1-B35AE00BE99D@wunderwood.org> <1505746530208-0.post@n3.nabble.com> <B8BFF1A8-BDDD-41AD-9699-925CA40EF3CE@wunderwood.org> <1505750627860-0.post@n3.nabble.com> <CAN4YXvfqEDryzWDZv45026Yrk9Y50UiXF2DWAVaknyawN-55XA@mail.gmail.com> <1505792836254-0.post@n3.nabble.com> <1505805507.11509.33.camel@kb.dk>
Subject: Re: Solr nodes crashing (OOM) after 6.6 upgrade
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
archived-at: Tue, 19 Sep 2017 08:12:00 -0000

Thanks, the change seemed to have addressed the memory issue (so far), but on
the contrary, the GC chocked the CPUs stalling everything. The CPU
utilization across the cluster clocked close to 400%, literally stalling
everything.On a first look, the G1-Old generation looks to be the culprit
that took up 80% of the CPU. Not sure what triggered really triggered it as
the GC seemed to have stable till then. The other thing I noticed was the
mlt queries (I'm using mlt query parser for cloud support) took a huge
amount of time to respond (10 sec+) during the CPU spike compared to the
rest. Again, that might just due to the CPU.

The index might not be a large one to merit a couple of shards, but it has
never been an issue for past couple of years on 5.5. We never had a single
outage related to memory or CPU. The query/indexing load has increased over
time, but it has been linear. I'm little baffled why would 6.6 behave so
differently. Perhaps the hardware is not adequate enough? I'm running on 8
core / 30gb machine with SSD.


--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html