lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cao Manh Dat (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-3227) Solr Cloud should continue working when a logical shard goes down
Date Fri, 30 Sep 2016 03:44:21 GMT

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

Cao Manh Dat commented on SOLR-3227:
------------------------------------

I belived this ticket can be closed. We can deal with this problem by different ways that
available to SolrCloud now
https://cwiki.apache.org/confluence/display/solr/Distributed+Requests

> Solr Cloud should continue working when a logical shard goes down
> -----------------------------------------------------------------
>
>                 Key: SOLR-3227
>                 URL: https://issues.apache.org/jira/browse/SOLR-3227
>             Project: Solr
>          Issue Type: New Feature
>          Components: SolrCloud
>    Affects Versions: 4.0-ALPHA
>            Reporter: Ranjan Bagchi
>
> I can start up a SolrCloud instance up one instance w/ zookeeper, and started a second
instance defining a shard name in solr.xml, and the second shard shows up in zookeeper and
both indexes are searchable.
> However, if I bring the second server down -- the first one stops working until I restart
server #2.
> The desired behavior is that SolrCloud deregisters server #2 and the cloud remains searchable
with only server #1's index.



--
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