lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shalin Shekhar Mangar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-8722) Don't force a full ZkStateReader refresh on every Overseer operation
Date Wed, 02 Mar 2016 15:45:18 GMT

    [ https://issues.apache.org/jira/browse/SOLR-8722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15175816#comment-15175816
] 

Shalin Shekhar Mangar commented on SOLR-8722:
---------------------------------------------

bq. In that case, should we land this patch as-is and then come back with a more holistic
answer for async failures?

+1, I'll commit after running tests.

> Don't force a full ZkStateReader refresh on every Overseer operation
> --------------------------------------------------------------------
>
>                 Key: SOLR-8722
>                 URL: https://issues.apache.org/jira/browse/SOLR-8722
>             Project: Solr
>          Issue Type: Improvement
>          Components: SolrCloud
>    Affects Versions: 5.4.1
>            Reporter: Scott Blum
>            Assignee: Shalin Shekhar Mangar
>              Labels: patch, performance, solrcloud
>         Attachments: SOLR-8722.patch
>
>
> We're doing an unnecessary ZkStateReader forced refresh on all Overseer operations. 
This isn't necessary because ZkStateReader keeps itself up to date.
> According to [~shalinmangar]'s analysis, we just need to put a wait loop at the end of
addReplica to observe the state change.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message