[
https://issues.apache.org/jira/browse/SOLR-10619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15999590#comment-15999590
]
Cao Manh Dat commented on SOLR-10619:
-------------------------------------
bq. I completely follow your logic. But then, why do we need a singleConsumer
flag? Couldn't we just do the optimization in all cases?
I thought the reason about not doing this one in the first place. The only
reason is in case of multiple consumer, the current logic makes sense.
Yeah, your idea seems work. Will update the patch in that way
> When DQ.knowChildren is not empty, DQ should not refetch node children in
> case of single consumer
> -------------------------------------------------------------------------------------------------
>
> Key: SOLR-10619
> URL: https://issues.apache.org/jira/browse/SOLR-10619
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Cao Manh Dat
> Assignee: Cao Manh Dat
> Attachments: SOLR-10619.patch, SOLR-10619.patch
>
>
> Right now, for every time childWatcher is kicked off. We refetch all children
> of DQ's node. It is a wasted in case of single consumer.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
