Ron, how often both indices are updated? Presumably if they are static, filter cache may help. It's worth making sure that the app gives a chance to filter cache.; To better understand the problem it is worth taking a few treadumps under load: a deep stack gives a clue for hotspot (or just take a sampling profile). Once we know the hot spot we can think about a workaround. https://issues.apache.org/jira/browse/SOLR-16717 about sharding "fromIndex" https://issues.apache.org/jira/browse/SOLR-16242 about keeping "local/to" index cache when fromIndex is updated.
On Thu, May 25, 2023 at 5:01 PM Andy Lester <[email protected]> wrote: > > > > On May 25, 2023, at 7:51 AM, Ron Haines <[email protected]> wrote: > > > > So, when this feature is enabled, this negative &fq gets added: > > -{!join fromIndex=primary_rollup from=group_id_mv to=group_member_id > > score=none}${q} > > > Can we see collection definitions of both the source collection and the > join? Also, a sample query, not just the one parameter? Also, how often are > either of these collections updated? One thing that killed off an entire > project that we were doing was that the join table was getting updated > about once a minute, and this destroyed all our caching, and made the > queries we wanted to do unusable. > > > Thanks, > Andy -- Sincerely yours Mikhail Khludnev
