Re: join with big 2nd collection

2021-05-05 Thread Joel Bernstein
; got an OOM in some cases. > Will memory requirements change for a single node when adding more nodes > with replicas ? > > Best Regards > Jens > > -Ursprüngliche Nachricht- > Von: Joel Bernstein > Gesendet: Montag, 3. Mai 2021 14:42 > An: users@solr.apache.

AW: join with big 2nd collection

2021-05-05 Thread Jens Viebig
Nachricht- Von: Joel Bernstein Gesendet: Montag, 3. Mai 2021 14:42 An: users@solr.apache.org Betreff: Re: join with big 2nd collection Here is the jira that describes it: https://issues.apache.org/jira/browse/SOLR-15049 The description and comments don't describe the full impa

Re: join with big 2nd collection

2021-05-03 Thread Joel Bernstein
is solution is that we loose the possibility >> completely reindex the a "document type". For example collection1 was >> pretty fast to completely reindex and possibly the schema changes more >> often, while collection2 is "index once / delete after x days" and i

Re: join with big 2nd collection

2021-05-03 Thread Joel Bernstein
delete after x days" and is heavy > to reindex. > > Best Regards > Jens > > -----Ursprüngliche Nachricht- > Von: Jens Viebig > Gesendet: Mittwoch, 28. April 2021 19:12 > An: users@solr.apache.org > Betreff: join with big 2nd collection > > Hi List, >

AW: join with big 2nd collection

2021-04-30 Thread Jens Viebig
is "index once / delete after x days" and is heavy to reindex. Best Regards Jens -Ursprüngliche Nachricht- Von: Jens Viebig Gesendet: Mittwoch, 28. April 2021 19:12 An: users@solr.apache.org Betreff: join with big 2nd collection Hi List, We have a join perfomance issue

join with big 2nd collection

2021-04-28 Thread Jens Viebig
Hi List, We have a join perfomance issue and are not sure in which direction we should look to solve the issue. We currently only have a single node setup We have 2 collections where we do join querys, joined by a "primary key" string field contentId_s Each dataset for a single contentId_s cons