Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Date: Thu, 6 Oct 2011 19:55:29 +0000 (UTC)
From: "Mark Miller (Issue Comment Edited) (JIRA)" <jira@apache.org>
To: dev@lucene.apache.org
Message-ID: <2801030.4777.1317930929840.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <560922570.26875.1316012530080.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Issue Comment Edited] (SOLR-2765) Shard/Node states
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Mark Miller edited comment on SOLR-2765 at 10/6/11 7:54 PM:
------------------------------------------------------------

This is where incremental update of the cloud state gets tricky...

If you have something like these roles at the shard level, all of a sudden you cannot change them on the fly because the new incremental update will not pick them up.

Its a tricky situation - without incremental, things start to get nasty at a huge number of shards. One possibility is that everyone also watches another node, that when pinged, causes a full read - so that most cloud state updates are incremental, but when per shard info like this is changed on the fly, you can then trigger a full read by everyone...
                
      was (Author: markrmiller@gmail.com):
    This is where incremental update of the cloud state gets tricky...

If you have something like these roles at the shard level, all of a sudden you cannot change them on the fly because the new incremental update will not pick them up.

Its a tricky situation - without incremental, things start to get nasty at a huge number of shards. One possibility is that everyone also watches another node, that when pinged, causes a full read - so that must cloud state updates are incremental, but when per shard info like this is changed on the fly, you can then trigger a full read by everyone...
                  
> Shard/Node states
> -----------------
>
>                 Key: SOLR-2765
>                 URL: https://issues.apache.org/jira/browse/SOLR-2765
>             Project: Solr
>          Issue Type: Sub-task
>          Components: SolrCloud, update
>            Reporter: Yonik Seeley
>             Fix For: 4.0
>
>         Attachments: shard-roles.patch
>
>
> Need state for shards that indicate they are recovering, active/enabled, or disabled.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

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