[
https://issues.apache.org/jira/browse/SOLR-15715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17603095#comment-17603095
]
Ishan Chattopadhyaya commented on SOLR-15715:
---------------------------------------------
bq. Can you pretend that I'm a junior engineer and explain this conclusion to
me?
It seems that during the query phase, a data node (lets say the red line) goes
through 9 cycles of GC in scenario 1, whereas during scenario 2 same line goes
via 6 cycles. Hence, I arrived at the conclusion that there's less GC cycles,
thus indicating lower heap usage, when using coordinator nodes for querying.
Does it make sense, Mike?
> Dedicated query coordinator nodes in the solr cluster
> -----------------------------------------------------
>
> Key: SOLR-15715
> URL: https://issues.apache.org/jira/browse/SOLR-15715
> Project: Solr
> Issue Type: New Feature
> Components: SearchComponents - other
> Affects Versions: 8.10.1
> Reporter: Hitesh Khamesra
> Assignee: Noble Paul
> Priority: Major
> Attachments: coordinator-poc.jpg, coordinator-poc.pdf,
> coordinator-vs-data-nodes.jpg, regular-node.jpg, regular-node.pdf
>
> Time Spent: 3.5h
> Remaining Estimate: 0h
>
> We have a large collection with 1000s of shards in the solr cluster. We have
> observed that distributed solr query takes many resources(thread, memory,
> etc.) on the solr data node(node which contains indexes). Thus we need
> dedicated query nodes to execute distributed queries on large solr
> collection. That would reduce the memory/cpu pressure from solr data nodes.
> Elastis search has similar functionality
> [here|https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-node.html#coordinating-node]
>
> [~noble.paul] [~ichattopadhyaya]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
