COLSTATUS api raw size summary of shard

Hi Solr Users, The "COLSTATUS " api that generates a summary of collection index is timing out when querying a large size index even with sampling size set to 0.01. Any other alternatives? Is it po

Re: Search Request Strategy on Solr Cloud

>From the other POV, a node can be excluded from LB pool via balancer API before restart and brought back then. On Wed, Jun 14, 2023 at 6:09 PM Saksham Gupta wrote: > Have you configured an URL for health check? Which one? > The load balancer checks if the solr port is in use or not. If yes, the

Re: join query parser performance

yes, we would return 'D'. So, are you asking why not just do the join in the main index? I started that way, then realized that a document that 'belongs' to another doc both need to be on the same shard for the join to work. That's when I moved to the 'fromIndex' approach and created the small '

Re: join query parser performance

Thanks for the clarification, Ron. Why the membership is extracted into a separate index? Join is heavy anyway, but run it cross core is even more heavier. Example you give is not really specific. I can implement it via fq=-group_member_id:* Let's extend it doc# group_id. group_member_id 1.