Hi there：
In solr4.3 source code , I found overseer use 3 queues to handle all
solrcloud management request:
1: /overseer/queue
2: /overseer/queue-work
3: /overseer/collection-queue-work
ClusterStateUpdater use 1st & 2nd queue to handle solrcloud shard or
state request.
When peek request from 1st queue, then offer it to 2nd queue and
handle it.
OverseerCollectionProcessor use 3rd queue to handle collection related
request.
My question is why ClusterStateUpdater use 2 queues but
OverseerCollectionProcessor use 1 also can handle request correctly?
Is there any additional design for ClusterStateUpdater?
Thanks in advance:)
Best Regards,
Illu Ying
Assistant Supervisor, NESC-SH.MIS
+86-021-51530666*41417
Floor 19, KaiKai Plaza, 888, Wanhangdu Rd, Shanghai (200042)
ONCE YOU KNOW, YOU NEWEGG.
CONFIDENTIALITY NOTICE: This email and any files transmitted with it may
contain privileged or otherwise confidential information. It is intended only
for the person or persons to whom it is addressed. If you received this message
in error, you are not authorized to read, print, retain, copy, disclose,
disseminate, distribute, or use this message any part thereof or any
information contained therein. Please notify the sender immediately and delete
all copies of this message. Thank you in advance for your cooperation.
保密注意：此邮件及其附随文件可能包含了保密信息。该邮件的目的是发送给指定收件人。如果您非指定收件人而错误地收到了本邮件，您将无权阅读、打印、保存、复制、泄露、传播、分发或使用此邮件全部或部分内容或者邮件中包含的任何信息。请立即通知发件人，并删除该邮件。感谢您的配合！
