[
https://issues.apache.org/jira/browse/SOLR-9272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amrit Sarkar updated SOLR-9272:
-------------------------------
Attachment: SOLR-9272.patch
Got to the crux of the problem ::
SolrCLIZkUtilsTest extends SolrCloudTestCase, SolrCloudTestCase extends
SolrTestCaseJ. In SolrTestCaseJ ::
{code}
private static SSLTestConfig buildSSLConfig() {
SSLRandomizer sslRandomizer =
SSLRandomizer.getSSLRandomizerForClass(RandomizedContext.current().getTargetClass());
if (Constants.MAC_OS_X) {
// see SOLR-9039
// If a solution is found to remove this, please make sure to also update
// TestMiniSolrCloudClusterSSL.testSslAndClientAuth as well.
sslRandomizer = new SSLRandomizer(sslRandomizer.ssl, 0.0D,
(sslRandomizer.debug + " w/ MAC_OS_X supressed clientAuth"));
}
SSLTestConfig result = sslRandomizer.createSSLTestConfig();
log.info("Randomized ssl ({}) and clientAuth ({}) via: {}",
result.isSSLMode(), result.isClientAuthMode(),
sslRandomizer.debug);
return result;
}
{code}
Whether the current cluster will be SSL configured (HTTPS) or conventional
HTTP, is RANDOMIZED. Either https or http will be supported, not both in any
case.
Now, in our code, specifically say, we look for zk host corresponding to ::
{{http://localhost:[solr_port]/solr}}. What should be done? We should check
whether SSL is configured or not and according to that use the scheme e.g.
if (useSSL == true ) then {{solrURL = https://localhost:.......}}
else {{solrURL = http://localhost:........}}
A little guidance here will be deeply appreciated.
> Auto resolve zkHost for bin/solr zk for running Solr
> ----------------------------------------------------
>
> Key: SOLR-9272
> URL: https://issues.apache.org/jira/browse/SOLR-9272
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: scripts and tools
> Affects Versions: 6.2
> Reporter: Jan Høydahl
> Assignee: Jan Høydahl
> Labels: newdev
> Attachments: SOLR-9272.patch, SOLR-9272.patch, SOLR-9272.patch,
> SOLR-9272.patch, SOLR-9272.patch
>
>
> Spinoff from SOLR-9194:
> We can skip requiring {{-z}} for {{bin/solr zk}} for a Solr that is already
> running. We can optionally accept the {{-p}} parameter instead, and with that
> use StatusTool to fetch the {{cloud/ZooKeeper}} property from there. It's
> easier to remember solr port than zk string.
> Example:
> {noformat}
> bin/solr start -c -p 9090
> bin/solr zk ls / -p 9090
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
