[
https://issues.apache.org/jira/browse/SOLR-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley updated SOLR-4442:
-------------------------------
Fix Version/s: (was: 4.7)
4.8
> Developer Curb Appeal: Consider bringing up Solr in Cloud mode by default, or
> enable it with a single switch, or other system trivial setting
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-4442
> URL: https://issues.apache.org/jira/browse/SOLR-4442
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Affects Versions: 4.1
> Reporter: Mark Bennett
> Fix For: 4.8
>
>
> There's some talk that the days of single node search is dead. I don't quite
> agree, but many people are doing multinode deployments, and other engines are
> assuming distributed search by default.
> Should we consider giving Solr this ability? Perhaps in 5.0?
> Or at a minimum, have some other single switch or system setting or separate
> jar that causes Solr to do all of it's magic Zookeeper stuff by default.
> I've logged some other JIRA items to take care of some of the other things
> that you currently need to specify when starting up 4.1. Until reasonable
> defaults can be worked out, this auto-cloud mode wouldn't make as much sense.
> Is there any harm in bringing up Solr with ZK even if you're only working on
> a single machine? (assuming all the defaults are taken care of)
> Or perhaps there would be some switches, effectively:
> * -cloud = assume cloud mode
> * -dev_cloud = turn on multicast, autoport selection
> * -laptop_cloud = assume we're doing cloud, autoports, etc, except limit it
> to localhost
> I realize there's a lot of technical details here, but the current Solr
> startup syntax and directories overhead makes it less appealing.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
