The migration you speak of is in Lucene, not Solr. It would be noticed by
"Watchers".
~ David Smiley
Apache Lucene/Solr Search Developer
http://www.linkedin.com/in/davidwsmiley
On Tue, Jul 19, 2022 at 12:29 PM Ishan Chattopadhyaya <
ichattopadhy...@gmail.com> wrote:
> Great find! Lets have it
Great find! Lets have it committed.
On Tue, Jul 19, 2022 at 9:49 PM Bram Van Dam wrote:
> Thanks for your reply, David. Given the apparent migration from from
> Jira->Github, I didn't think that would get more response than the
> mailing list 😅
>
> We've been running a patched version of 7.7 wit
Thanks for your reply, David. Given the apparent migration from from
Jira->Github, I didn't think that would get more response than the
mailing list 😅
We've been running a patched version of 7.7 with a smaller Versions
arraylist for a while now, without any ill effects.
- Bram
On 13/07/202
Makes sense Bram.
I note that it's been over a month with no response. Just a suggestion --
try commenting on the pertinent JIRA because it will get the attention of
the last committer (and interested parties).
BTW we could cap the initial ArrayList size to, say, Math.min(1024,n)
~ David Smiley
Howdy,
We've noticed that enabling larger transaction logs causes the memory
requirements for Solr to increase: Solr consumes large amounts of memory
at startup.
After procuring a heap dump, this seems to be because Solr initializes
ArrayLists in UpdateLog::getVersions with size
maxNbTransa
