[
https://issues.apache.org/jira/browse/SOLR-8203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14985612#comment-14985612
]
Mark Miller commented on SOLR-8203:
-----------------------------------
bq. Should that be added here?
+1 - I think we should do this too. We can add some doc around the fact that
the update executor should not do any disk IO. Technically, it's probably fine
since it lives the length of the container, but I think it's best to avoid it
for proper shutdown.
> Stop processing updates more quickly on shutdown
> ------------------------------------------------
>
> Key: SOLR-8203
> URL: https://issues.apache.org/jira/browse/SOLR-8203
> Project: Solr
> Issue Type: Bug
> Reporter: Yonik Seeley
> Assignee: Yonik Seeley
> Fix For: 5.4
>
> Attachments: SOLR-8203.patch
>
>
> As we discovered in SOLR-8129, existing update streams can continue to be
> processed for some time when the CoreContainer is being shut down. If this
> node is the leader, updates can continue to flow to replicas over the
> existing streaming client (although new or idle clients won't be allowed to
> send anything).
> This can cause large reorders of updates and shard inconsistencies that we
> can't detect with the current PeerSync mechanism.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
