each core has its memory overhead. For instance, caches are
> based on cores, so you're having 36 individual caches per type.
>
> Best,
> Michael
>
> Am 14.02.2017 um 16:39 schrieb Leon STRINGER:
> >> On 14 February 2017 at 14:44 Michael Kuhlmann <
>
> On 14 February 2017 at 15:49 Walter Underwood
> wrote:
>
>
> Yes, 512 MB is far too small. I’m surprised it even starts. We run with 8
> Gb.
>
Thanks, in fairness 512 MB was the default and we're new to this. We'll look at
what we're allocating to Solr to
culating this is correct) is less than 4 MB. I
naively assumed a heap size-related issue would result from larger data sets.
Thanks for your recommendation,
Leon Stringer
>
rel inc after GC: 6,360.3K/coll (delta=19.963M)
Slope full GC: -126,380B/s
Slope GC: 14.317M/s
InitiatingOccFraction (avg / max): 65.9% / 100.0%
Avg promotion: 2,215.324K/coll (delta=6,904.174K) [greyed]
Total promotion: 12,504.467M
Can anyone can shed any light on this? Is it a problem or is this all normal?
Thanks,
Leon Stringer
, but it does mean that they are quickly cycled (every
3 hours).
Operations seem much slower in this state but I haven't collected figures for
this.
When Solr gets into this state it stays like it until it's restarted.
Thanks,
Leon Stringer
>
> On 14 February 2017 at 05:45 Erick Er
urrent-reset-start]
2017-02-13T16:19:11.546+: 5092.956: [CMS-concurrent-reset: 0.001/0.001 secs]
[Times: user=0.00 sys=0.00, real=0.00 secs]
Regards,
Leon Stringer
is tempting, but it makes some assumptions.
>
> Best,
> Erick
>
> On Thu, Dec 29, 2016 at 1:53 AM, Leon STRINGER
> <leon.strin...@ntlworld.com> wrote:
> > Hi,
> >
> > I'm new to Solr and am trying to set up a ne
a does.
I can't see anything obvious in the log apart from the above error.
Solr 6.3.0 on Fedora 25 with OpenJDK 1.8.0_111.
Thanks,
Leon Stringer