[
https://issues.apache.org/jira/browse/SOLR-11443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cao Manh Dat updated SOLR-11443:
--------------------------------
Attachment: SOLR-11443.patch
Updated patch for master
1. Adding fallbackQueue concept, in the startup, we consider workQueue as
fallbackQueue. Which contains messages that need to process one by one - if
there a message that causes exception on writing new clusterstate to Zk,
consider that as bad message and poll out from fallbackQueue.
2. After that, stateUpdateQueue is used as fallbackQueue, cause we writing in
batch, so if an exception is thrown on writing new clusterstate, we don't know
which message is bad, so we go back to the beginning of the loop and do 1.
> Remove the usage of workqueue for Overseer
> ------------------------------------------
>
> Key: SOLR-11443
> URL: https://issues.apache.org/jira/browse/SOLR-11443
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Cao Manh Dat
> Assignee: Cao Manh Dat
> Attachments: SOLR-11443.patch, SOLR-11443.patch, SOLR-11443.patch
>
>
> If we can remove the usage of workqueue, We can save a lot of IO blocking in
> Overseer, hence boost performance a lot.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
