[
https://issues.apache.org/jira/browse/SOLR-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12789759#action_12789759
]
Yonik Seeley commented on SOLR-1277:
------------------------------------
Been trying to get the cloud branch going... but I'm running into issues
somewhere (BasicZooKeeperTest):
{code}
"log4j:WARN No appenders could be found for logger
(org.apache.zookeeper.server.ZooKeeperServerMain).
log4j:WARN Please initialize the log4j system properly.
make:/solr
make:/collections/collection1/config=collection1
put:/configs/collection1/solrconfig.xml solr\conf\solrconfig.xml
make:/configs/collection1/solrconfig.xml
put:/configs/collection1/schema.xml solr\conf\schema.xml
make:/configs/collection1/schema.xml
put:/configs/collection1/stopwords.txt solr\conf\stopwords.txt
make:/configs/collection1/stopwords.txt
put:/configs/collection1/protwords.txt solr\conf\protwords.txt
make:/configs/collection1/protwords.txt
put:/configs/collection1/mapping-ISOLatin1Accent.txt
solr\conf\mapping-ISOLatin1Accent.txt
make:/configs/collection1/mapping-ISOLatin1Accent.txt
put:/configs/collection1/old_synonyms.txt solr\conf\old_synonyms.txt
make:/configs/collection1/old_synonyms.txt
Dec 12, 2009 11:17:42 AM org.apache.solr.AbstractZooKeeperTestCase setUp
INFO: ####SETUP_START testBasic
look for collection config:/collections/collection1
java.lang.RuntimeException: org.apache.solr.common.SolrException: ZooKeeper
Exception
at org.apache.solr.util.TestHarness.<init>(TestHarness.java:152)
at
org.apache.solr.AbstractZooKeeperTestCase.setUp(AbstractZooKeeperTestCase.java:81)
at
com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:40)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:90)
Caused by: org.apache.solr.common.SolrException: ZooKeeper Exception
at
org.apache.solr.core.ZooKeeperController.loadConfigPath(ZooKeeperController.java:103)
at
org.apache.solr.core.ZooKeeperController.<init>(ZooKeeperController.java:48)
at
org.apache.solr.core.CoreContainer$Initializer.initialize(CoreContainer.java:132)
at org.apache.solr.util.TestHarness.<init>(TestHarness.java:139)
... 19 more
Caused by: org.apache.zookeeper.KeeperException$ConnectionLossException:
KeeperErrorCode = ConnectionLoss for /collections/collection1
at org.apache.zookeeper.KeeperException.create(KeeperException.java:90)
at org.apache.zookeeper.KeeperException.create(KeeperException.java:42)
at org.apache.zookeeper.ZooKeeper.getChildren(ZooKeeper.java:1214)
at
org.apache.solr.core.ZooKeeperController.loadConfigPath(ZooKeeperController.java:91)
... 22 more
{code}
> Implement a Solr specific naming service (using Zookeeper)
> ----------------------------------------------------------
>
> Key: SOLR-1277
> URL: https://issues.apache.org/jira/browse/SOLR-1277
> Project: Solr
> Issue Type: New Feature
> Affects Versions: 1.4
> Reporter: Jason Rutherglen
> Assignee: Grant Ingersoll
> Priority: Minor
> Fix For: 1.5
>
> Attachments: log4j-1.2.15.jar, SOLR-1277.patch, SOLR-1277.patch,
> SOLR-1277.patch, SOLR-1277.patch, zookeeper-3.2.1.jar
>
> Original Estimate: 672h
> Remaining Estimate: 672h
>
> The goal is to give Solr server clusters self-healing attributes
> where if a server fails, indexing and searching don't stop and
> all of the partitions remain searchable. For configuration, the
> ability to centrally deploy a new configuration without servers
> going offline.
> We can start with basic failover and start from there?
> Features:
> * Automatic failover (i.e. when a server fails, clients stop
> trying to index to or search it)
> * Centralized configuration management (i.e. new solrconfig.xml
> or schema.xml propagates to a live Solr cluster)
> * Optionally allow shards of a partition to be moved to another
> server (i.e. if a server gets hot, move the hot segments out to
> cooler servers). Ideally we'd have a way to detect hot segments
> and move them seamlessly. With NRT this becomes somewhat more
> difficult but not impossible?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
