lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Erick Erickson <erickerick...@gmail.com>
Subject Re: Solr Delete By Id Out of memory issue
Date Wed, 22 Mar 2017 04:23:39 GMT
Chris:

OK, The whole DBQ thing baffles the heck out of me so this may be
totally off base. But would committing help here? Or at least be worth
a test?

On Tue, Mar 21, 2017 at 4:28 PM, Chris Hostetter
<hossman_lucene@fucit.org> wrote:
>
> : Thanks for replying. We are using Solr 6.1 version. Even I saw that it is
> : bounded by 1K count, but after looking at heap dump I was amazed how can it
> : keep more than 1K entries. But Yes I see around 7M entries according to
> : heap dump and around 17G of memory occupied by BytesRef there.
>
> what exactly are you looking at when you say you see "7M entries" ?
>
> are you sure you aren't confusing the keys in oldDeletes with other
> instances of BytesRef in the JVM?
>
> : It would be better to know why old deletes Map is used there. I am still
> : digging, If I find something then I will share that.
>
> See UpdateLog.lookupVersion for where the mapping is used if you are
> curious. Replicas recieving updates need to be able to verify (and in some
> casees ask the leader via RTG) for the version used when a doc was deleted
> in the even of concurrent/out-of-order updates for the same uniqueKey.
>
>
>
> -Hoss
> http://www.lucidworks.com/

Mime
View raw message