I agree with David that the first step would be to make SolrCloud the default mode. I made a dev list thread about this a few months ago, but I think I failed to respond at some point. I will get back on that and address the
I also really like Mike's idea that we enable very similar use cases with embedded Zookeeper's, if at all possible, to make the transition easy for users who want to stay on the user-manager mode. Marcus, I think it would be a great idea to fix up the documentation to make SolrCloud the first and most prominent mode advertised. Never saw your original PR, but would love to give it a look if you resuscitate it at some point. - Houston On Mon, Aug 9, 2021 at 2:48 PM David Smiley <[email protected]> wrote: > Given that SolrCloud is not even the default mode, I think it is premature > to deprecate standalone mode. Let's do this first and maybe consider > deprecating standalone after some time? > > ~ David Smiley > Apache Lucene/Solr Search Developer > http://www.linkedin.com/in/davidwsmiley > > > On Mon, Aug 9, 2021 at 1:58 PM Mike Drob <[email protected]> wrote: > >> Could we simulate user managed replication with an embedded zookeeper >> on the primary and pull replicas on the followers? >> >> On Mon, Aug 9, 2021 at 12:56 PM Jason Gerlowski <[email protected]> >> wrote: >> > >> > Hey Marcus, >> > >> > The places I've worked in the past have all used SolrCloud primarily >> > so I can't speak to any specifics, but my impression from reading >> > user-list traffic is that a sizable chunk of Solr's user base prefers >> > "User-Managed" mode (formerly called "standalone"). Some because they >> > don't want to manage a ZooKeeper cluster. Some because the >> > replication model in 'user-managed' fits their needs better. Some I >> > imagine just haven't bothered to update in many years. >> > >> > I'm absolutely sympathetic to efforts to streamline development and >> > reduce collective debt, but it might be tough to displace such a big >> > chunk of users. I'm curious what others think though. Maybe the >> > proportion of 'user-managed' users out there is smaller than I >> > imagine. >> > >> > Jason >> > >> > On Fri, Aug 6, 2021 at 11:59 PM Marcus Eagan <[email protected]> >> wrote: >> > > >> > > Hello again, >> > > >> > > Has the time come for us to reduce scope to move faster and with more >> focus? Even for those not in the cloud, SolrCloud has been the undisputed >> performance and usability champ since version 8.0. In version 9.0, I'd like >> to propose that the deciders in the community deprecate standalone mode in >> favor of SolrCloud. >> > > >> > > There are a few drivers: >> > > >> > > We only need to support changes that impact SolrCloud going forward. >> I know that this is hard to stomach. But by the time Solr reaches version >> 10.0, everyone should have migrated to SolrCloud as there is little reason >> to continue to run standalone. >> > > The new features keep coming to SolrCloud, but not to standalone. You >> can see in a few ways how I embarrassingly discovered this late one night >> while trying out a PR. If not careful, users can accidentally start Solr in >> standalone mode. Think of all the features that they will see documented >> but not in their environment. What a confusing user experience? >> > > Last but certainly not least, the number of contributors to the >> project, and the velocity of those contributions has dropped. . It does not >> have to be that way, though. Two ways are for the community to observe our >> push for modernization and improved user experience. Simply eliminating the >> need to include the -c flag in the start command would be a huge win for >> many engineers.We should make life easier for our users as much as the >> maintainers here. We can strive to make the upgrade process from 9 to 10 >> very simple. >> > > >> > > I tried to make one step in this direction last year by re-ordering >> the README to show the Solr Cloud command before the standalone command. I >> believe that patch died on the vine, but I would be excited to revive it to >> document this effort when the time is appropriate. >> > > >> > > Reason not to do it: >> > > >> > > Some large company out there might view this move as introducing >> risk. I view the risk here as negligible but I welcome any perspective >> there. >> > > Some things I inevitably don't know. >> > > >> > > What do you all think? >> > > >> > > Thank you all for your voluntary contributions, >> > > -- >> > > Marcus Eagan >> > > >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: [email protected] >> > For additional commands, e-mail: [email protected] >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >>
