RE: Getting rid of Master/Slave nomenclature in Solr
Marcus, Thank you for tackling this. I'm not a developer, just a user, so my ability to help is limited to moral support. And I support your efforts 100%. Thank you, --Jamie -Original Message- From: Marcus Eagan Sent: Monday, August 3, 2020 12:15 PM To: solr-user@lucene.apache.org Subject: Re: Getting rid of Master/Slave nomenclature in Solr Here is some of the work I did to remedy this effort before I knew about this email: https://github.com/apache/lucene-solr/pull/1712 https://issues.apache.org/jira/browse/SOLR-14702page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel&focusedCommentId=17169865 It makes me sick to read master/slave and this issue has alienated a buddy I've tried to recruit to volunteer on the project. All comments welcome, but please read the above docs as I will review this email thread now to understand what has already been discussed. I put in a lot of work to get this solid. Happy to discuss. Marcus On 2020/06/17 19:37:20, Anshum Gupta wrote: > Hi everyone,> > > Moving a conversation that was happening on the PMC list to the public> > forum. Most of the following is just me recapping the conversation that has> > happened so far.> > > Some members of the community have been discussing getting rid of the> > master/slave nomenclature from Solr.> > > While this may require a non-trivial effort, a general consensus so far> > seems to be to start this process and switch over incrementally, if a> > single change ends up being too big.> > > There have been a lot of suggestions around what the new nomenclature might> > look like, a few people don’t want to overlap the naming here with what> > already exists in SolrCloud i.e. leader/follower.> > > Primary/Replica was an option that was suggested based on what other> > vendors are moving towards based on Wikipedia:> > https://en.wikipedia.org/wiki/Master/slave_(technology) > > , however there were concerns around the use of “replica” as that denotes a> > very specific concept in SolrCloud. Current terminology clearly> > differentiates the use of the traditional replication model from SolrCloud> > and reusing the names would make it difficult for that to happen.> > > There were similar concerns around using Leader/follower.> > > Let’s continue this conversation here while making sure that we converge> > without much bike-shedding.> > > -Anshum> > Sent via Superhuman ( https://sprh.mn/?vip=m...@marcuseagan.com )
RE: Can't start Solr 7.7.1 due to name-resolution issue
This info might help: https://serverfault.com/questions/228140/lost-modified-etc-hosts-file-on-amazon-ec2-every-reboot-instance --Jamie -Original Message- From: Christopher Schultz Sent: Thursday, August 22, 2019 4:01 PM To: solr-user@lucene.apache.org Subject: Can't start Solr 7.7.1 due to name-resolution issue -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 All, I'm getting a failure to start my Solr instance. Here's the error from the console log: Error: Exception thrown by the agent : java.net.MalformedURLException: Local host name unknown: java.net.UnknownHostException: [hostname]: [hostname]: Name or service not known sun.management.AgentConfigurationError: java.net.MalformedURLException: Local host name unknown: java.net.UnknownHostException: [hostname]: [hostname]: Name or service not known at sun.management.jmxremote.ConnectorBootstrap.startRemoteConnectorServer(C onnectorBootstrap.java:480) at sun.management.Agent.startAgent(Agent.java:262) at sun.management.Agent.startAgent(Agent.java:452) Caused by: java.net.MalformedURLException: Local host name unknown: java.net.UnknownHostException: [hostname]: [hostname]: Name or service not known at javax.management.remote.JMXServiceURL.(JMXServiceURL.java:289) at javax.management.remote.JMXServiceURL.(JMXServiceURL.java:253) at sun.management.jmxremote.ConnectorBootstrap.exportMBeanServer(ConnectorB ootstrap.java:739) at sun.management.jmxremote.ConnectorBootstrap.startRemoteConnectorServer(C onnectorBootstrap.java:468) ... 2 more Now, my hostname is just the first part of the hostname, so like "www" instead of "www.example.com". Running "host [hostname]" on the CLI returns "Host [hostname]" not found: 3(NXDOMAIN)" so it's not entirely surprising that this name resolution is failing. What's the best way for me to get around this? I'm running on Debian Stretch in Amazon EC2. I've tried fixing the local name resolution so that it actually works, but when I reboot, the EC2 instance reverts my DNS settings so those changes won't survive a reboot. Can I give the fully-qualified hostname to the JMX component in some way ? I've this answer[1] on SO and everyone seems to say "edit /etc/hosts" and, as I said, the EC2 startup scripts end up resetting those files during a reboot. Any ideas? - -chris [1] https://stackoverflow.com/questions/20093854/jmx-agent-throws-java-net-m alformedurlexception-when-host-name-is-set-to-all-num -BEGIN PGP SIGNATURE- Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/ iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAl1e9IQACgkQHPApP6U8 pFjG6g//XM6nPgioIuJs40gB9534GnsG9q8d42AUIoiDzJ+t8isFFxtphEChdcye 9/5ePo36fODIsNkzzXsAJh9L1iRgmnVy7QGQIDp07WEo9v2bVo2RkWl42zm+UQ5u XIz//bpT+J9y3eBPdPCKaXou+UYeR9/2W/UYyN08/uayP2QVVd2ZavC6AbFW93i1 IF5vOmETOsxBgVlgngX4TQRNSKfe5gCqWT0l/diHpm7PjT2BDzNO7x3vRbfioOMS ktXcRqdBJAzM9XLV1acI+0z7I1kzs/A+jCymT/4++VmI0Lf4AACIhoaqnmS9pxyY nrXU8tttozbaHMiBS3dIIMZP1ZF4jzY0+/UPBfgXqM4OcErWTjrha4G/5oBlLqf8 msuVRTg6qbsQJP//UcDhN8kl593xCK/bcQMkzq1ABkwFUhb8PhXp/3IJCRjJm5q3 U3gTwMwA/k+R4aM8qGaLw+07aFCdVJKrIUW0NEEHEnwkjJxAeqIRdpV8acfrT6uy 3v78cVFvWaxcOtAyioUhek0jhKzCobcxsZEcxZqWWxY0DOFHWbip/agTJESC/sXV wLY2P9lldo+S5dAoaGM7Ze1WJ5FOSLm6Juvl4CvyMeebyPFie4PrWX7b7ess8I+A YwLyqfKQOV4qmWoiO7yNGcwfgIYNn3bJ/1b/vkmo+ua0KvjscYk= =zeBa -END PGP SIGNATURE-
SSL certificate automated rotation/renewal?
Folks, I've done plenty of searching, but haven't found anything addressing this issue. I have an existing SolrCloud 3 server cluster in production. We need to enable SSL/TLS encryption, both for clients and between the 3 servers. I've read through the documentation, and while I've not done it yet, it all makes sense. Related, we're also using Consul and working up the infrastructure to use Consul Connect with sidecar proxies for client-to-service end-to-end TLS encryption. That's great because it automatically handles SSL/TLS certificate rotation without any manual interaction. But that doesn't help me with the intra-cluster SolrCloud communication. So here's my question. How do folks handle SSL/TLS certificate rotation on SolrCloud instances in production? Update the certificate and restart solr on each box, one at a time? Just use extra long-lasting certificates? Or is there another way, like using an external truststore/keystore in Vault? I'm assuming that wouldn't work because you have to restart Solr to get the new cert, but maybe there's something I don't know? Any thoughts welcome, --Jamie
