Re: Question regarding Upgrading to SolrCloud
The 7.0 Ref Guide was released Monday. An overview of the new replica types is available online here: https://lucene.apache.org/solr/guide/7_0/shards-and-indexing-data-in-solrcloud.html#types-of-replicas. The replica type is specified when you either create the collection or add a replica. On Thu, Oct 5, 2017 at 9:01 AM, Erick Erickson wrote: > Gopesh: > > There is brand new functionality in Solr 7, see: SOLR-10233, the > "PULL" replica type which is a hybrid SolrCloud replica that uses > master/slave type replication. You should find this in the reference > guide, the 7.0 ref guide should be published soon. Meanwhile, that > JIRA will let you know. Also see .../solr/CHANGES.txt. As Emir says, > though, it would require ZooKeeper. > > Really, though, once you move to SolrCloud (if you do) I'd stick with > the standard NRT replica type unless I had reason to use one of the > other two, (TLOG and PULL) as they're for pretty special situations. > > All that said, if you're happy with master/slave there's no compelling > reason to go to SolrCloud, especially for smaller installations. > > Best, > Erick > > On Wed, Oct 4, 2017 at 11:46 PM, Gopesh Sharma > wrote: >> Hello Guys, >> >> As of now we are running Solr 3.4 with Master Slave Configuration. We are >> planning to upgrade it to the lastest version (6.6 or 7). Questions I have >> before upgrading >> >> >> 1. Since we do not have a lot of data, is it required to move to >> SolrCloud or continue using it Master Slave >> 2. Is the support for Master Slave will be there in the future release or >> do you plan to remove it. >> 3. Can we configure master-slave replication in Solr Cloud, if yes then >> do we need zookeeper as well. >> >> Thanks, >> Gopesh Sharma
Re: Question regarding Upgrading to SolrCloud
Gopesh: There is brand new functionality in Solr 7, see: SOLR-10233, the "PULL" replica type which is a hybrid SolrCloud replica that uses master/slave type replication. You should find this in the reference guide, the 7.0 ref guide should be published soon. Meanwhile, that JIRA will let you know. Also see .../solr/CHANGES.txt. As Emir says, though, it would require ZooKeeper. Really, though, once you move to SolrCloud (if you do) I'd stick with the standard NRT replica type unless I had reason to use one of the other two, (TLOG and PULL) as they're for pretty special situations. All that said, if you're happy with master/slave there's no compelling reason to go to SolrCloud, especially for smaller installations. Best, Erick On Wed, Oct 4, 2017 at 11:46 PM, Gopesh Sharma wrote: > Hello Guys, > > As of now we are running Solr 3.4 with Master Slave Configuration. We are > planning to upgrade it to the lastest version (6.6 or 7). Questions I have > before upgrading > > > 1. Since we do not have a lot of data, is it required to move to SolrCloud > or continue using it Master Slave > 2. Is the support for Master Slave will be there in the future release or > do you plan to remove it. > 3. Can we configure master-slave replication in Solr Cloud, if yes then do > we need zookeeper as well. > > Thanks, > Gopesh Sharma
Question regarding Upgrading to SolrCloud
Hello Guys, As of now we are running Solr 3.4 with Master Slave Configuration. We are planning to upgrade it to the lastest version (6.6 or 7). Questions I have before upgrading 1. Since we do not have a lot of data, is it required to move to SolrCloud or continue using it Master Slave 2. Is the support for Master Slave will be there in the future release or do you plan to remove it. 3. Can we configure master-slave replication in Solr Cloud, if yes then do we need zookeeper as well. Thanks, Gopesh Sharma
Re: Question regarding Upgrading to SolrCloud
Hi Sharma, Please see inline answers. Thanks, Emir -- Monitoring - Log Management - Alerting - Anomaly Detection Solr & Elasticsearch Consulting Support Training - http://sematext.com/ > On 5 Oct 2017, at 09:00, Gopesh Sharma wrote: > > Hello Guys, > > As of now we are running Solr 3.4 with Master Slave Configuration. We are > planning to upgrade it to the lastest version (6.6 or 7). Questions I have > before upgrading > > > 1. Since we do not have a lot of data, is it required to move to SolrCloud > or continue using it Master Slave It is not required to move to SolrCloud if you are ok with MS limitations. The main drivers to move to SC are: data volume that requires sharding NRT requirements that cannot be met with MS model FT requirements - with MS you have SPOF - master node that can prevent updates, but if you NRT requirements are not strict and can tolerate longer periods without updates, this can be ignored > 2. Is the support for Master Slave will be there in the future release or > do you plan to remove it. SolrCloud also uses replication as backup mechanism, so it is there to stay. > 3. Can we configure master-slave replication in Solr Cloud, if yes then do > we need zookeeper as well. SolrCloud requires ZK - it is where it keeps cluster state. Like mentioned above, SolrCloud have replication handlers enabled, so you can have some hybrid model, but it will not make your system simpler. > > Thanks, > Gopesh Sharma >
Question regarding Upgrading to SolrCloud
Hello Guys, As of now we are running Solr 3.4 with Master Slave Configuration. We are planning to upgrade it to the lastest version (6.6 or 7). Questions I have before upgrading 1. Since we do not have a lot of data, is it required to move to SolrCloud or continue using it Master Slave 2. Is the support for Master Slave will be there in the future release or do you plan to remove it. 3. Can we configure master-slave replication in Solr Cloud, if yes then do we need zookeeper as well. Thanks, Gopesh Sharma
Re: Upgrading to SolrCloud
On 10/6/2016 9:02 AM, Steven White wrote: > We currently have a component that uses SolrJ and Solr REST API to admin > Solr (adding new fields, changing handlers, etc. to customize Solr's > schema) based on customer's DB schema before we start indexing. > > If we switch over to SolrCloud: > > 1) Will our existing usage of SolrJ and REST API still work as-is? Generally speaking, if you change from a variant like HttpSolrClient connecting to a non-cloud install to CloudSolrClient connecting to a cloud install, the rest of your SolrJ code will *probably* work with no other changes. That will largely depend on the config/schema being similar between the cloud install and the non-cloud install. > 2) Not all of our customers need that high availability of Solr. For > those, single server and single index will do just fine. In this case, can > I configure SolrCloud to single server with single core? When I do so, am > I impacting performance of Solr? You can have collections in the cloud that have a single shard and a single replica -- only one core in the entire collection. These kinds of collections are vulnerable to failures if the server with the single core goes down, of course. Aside from that, they work just like collections with more shards and/or more replicas. The "old" http API still works even in cloud mode, using collection names instead of core names in the URL -- with the added advantage that you can send such requests to ANY node in the cloud, and they will find their way to the correct location. Updates are more efficient if they are sent to the correct shard leader, which CloudSolrClient does by default. Thanks, Shawn
Re: Upgrading to SolrCloud
> 6. okt. 2016 kl. 17.02 skrev Steven White : > If we switch over to SolrCloud: > > 1) Will our existing usage of SolrJ and REST API still work as-is? Yes, probably > 2) Not all of our customers need that high availability of Solr. For > those, single server and single index will do just fine. In this case, can > I configure SolrCloud to single server with single core? When I do so, am > I impacting performance of Solr? If you have a collection with only one shard, there’s no overhead during indexing or querying. You would use CloudSolrClient which will talk to ZK but that does not happen for every request, so it will be smart enough to send the requests directly to the node that should serve them. > I'm thinking performance will be impacted because there is now an extra > layer my requests will have to go through. Nope. But note that when you create collections, Solr may assign you a node which is already used by other collections, and that may potentially cause performance issues if the node is not powerful enough to drive both collections. But you can also choose what node to use when creating the collection -- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com
Upgrading to SolrCloud (take 2)
(sorry if this a second post, the first one 1 posted 1 hour ago has yet to make it to the mailing list!!) Hi everyone, Currently, we are on Solr 5.2 and use 1 core and none of the cloud features. We are planning to upgrade to Solr 6.2 and utilize SolrCloud not because our data need to scale (single core with no cloud is doing just fine on our index of 2 million records and about 15 gb index size) but because some of our customers want high availability. We currently have a component that uses SolrJ and Solr REST API to admin Solr (adding new fields, changing handlers, etc. to customize Solr's schema) based on customer's DB schema before we start indexing. If we switch over to SolrCloud: 1) Will our existing usage of SolrJ and REST API still work as-is? 2) Not all of our customers need that high availability of Solr. For those, single server and single index will do just fine. In this case, can I configure SolrCloud to single server with single core? When I do so, am I impacting performance of Solr? I'm thinking performance will be impacted because there is now an extra layer my requests will have to go through. Thanks in advanced. Steve
Upgrading to SolrCloud
Hi everyone, Currently, we are on Solr 5.2 and use 1 core and none of the cloud features. We are planning to upgrade to Solr 6.2 and utilize SolrCloud not because our data need to scale (single core with no cloud is doing just fine on our index of 2 million records and about 15 gb index size) but because some of our customers want high availability. We currently have a component that uses SolrJ and Solr REST API to admin Solr (adding new fields, changing handlers, etc. to customize Solr's schema) based on customer's DB schema before we start indexing. If we switch over to SolrCloud: 1) Will our existing usage of SolrJ and REST API still work as-is? 2) Not all of our customers need that high availability of Solr. For those, single server and single index will do just fine. In this case, can I configure SolrCloud to single server with single core? When I do so, am I impacting performance of Solr? I'm thinking performance will be impacted because there is now an extra layer my requests will have to go through. Thanks in advanced. Steve
