It sounds like you have some sort of configuration issue perhaps. When things
are setup right, you should not be seeing anything like this.
Whether or not you can do without ZooKeeper depends on what your requirements
are and what you want to support. You can use SolrCloud mode and non SolrCloud
mode - there are advantages and disadvantages to each.
- Mark
On Mar 1, 2013, at 9:03 AM, Martin Koch <m...@issuu.com> wrote:
> On a host that is running two separate solr (jetty) processes and a single
> zookeeper process, we're often seeing solr complain that it can't find a
> particular core. If we restart the solr process, when it comes back up, it
> has lost all information about its cores
>
> Feb 28, 2013 10:26:47 PM org.apache.solr.core.SolrCore registerSearcher
> INFO: [core0] Registered new searcher
> Searcher@14df33aemain{StandardDirectoryReader(segments_aat:181977
> _16pu(4.0.0.2):C263610
> /78380 _vwv(4.0.0.2):C285538/130332 ... [snip]
> Feb 28, 2013 10:26:47 PM org.apache.solr.common.cloud.ZkStateReader$2
> process
> INFO: A cluster state change has occurred - updating...
> Feb 28, 2013 10:27:47 PM org.apache.solr.common.SolrException log
> *SEVERE: null:org.apache.solr.common.SolrException: Could not get shard_id
> for core: core0*
> at
> org.apache.solr.cloud.ZkController.doGetShardIdProcess(ZkController.java:995)
> at
> org.apache.solr.cloud.ZkController.preRegister(ZkController.java:1053)
> at
> org.apache.solr.core.CoreContainer.register(CoreContainer.java:662)
> [snip]
>
> SEVERE: null:org.apache.solr.common.SolrException: Could not get shard_id
> for core: core1
>
> etc for all the cores.
>
> The solution has been so far to shut down solr and zookeeper, delete the
> zookeeper configuration from disk, and then bring everything back up again.
>
> Has anyone else seen this problem? I'd love to be able to do with the
> hassle of having to run zookeeper, and the problems that are associated
> with it. Is this possible?
>
> Thanks,
> /Martin Koch - Senior Systems Architect - Issuu.com
