[jira] [Commented] (SOLR-4754) solrcloud does not detect an implicit "host" and does not provide clear error using 4x example

[Hoss Man (JIRA)]

    [ 
https://issues.apache.org/jira/browse/SOLR-4754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13639784#comment-13639784
 ] 

Hoss Man commented on SOLR-4754:
--------------------------------

Steps used to run solr nodes that caused problem...

{noformat}
# terminal #1
rm -r example/solr/collection1/data/*
cp -r example example2
cd example
java -Dbootstrap_confdir=./solr/collection1/conf -Dcollection.configName=myconf 
-DzkRun -DnumShards=2 -jar start.jar

# terminal #2
cd example2
java -Djetty.port=7574 -DzkHost=localhost:9983 -jar start.jar
{noformat}

clusterstate after starting both nodes...

{code}
{"collection1":{
    "shards":{
      "shard1":{
        "range":"80000000-ffffffff",
        "state":"active",
        "replicas":{":8983_solr_collection1":{
            "shard":"shard1",
            "state":"active",
            "core":"collection1",
            "collection":"collection1",
            "node_name":":8983_solr",
            "base_url":"http://:8983/solr";,
            "leader":"true"}}},
      "shard2":{
        "range":"0-7fffffff",
        "state":"active",
        "replicas":{":7574_solr_collection1":{
            "shard":"shard2",
            "state":"active",
            "core":"collection1",
            "collection":"collection1",
            "node_name":":7574_solr",
            "base_url":"http://:7574/solr";,
            "leader":"true"}}}},
    "router":"compositeId"}}
{code}

Content of ZK: /collections/collection1/leaders/shard1 ...

{code}
{
  "core":"collection1",
  "node_name":":8983_solr",
  "base_url":"http://:8983/solr"}
{code}

Content of ZK: /collections/collection1/leaders/shard2 ...

{code}
{
  "core":"collection1",
  "node_name":":7574_solr",
  "base_url":"http://:7574/solr"}
{code}

Steps used that succeeded (same as above but use explict "host" property)...

{noformat}
# terminal #1
rm -r example/solr/collection1/data/*
cp -r example example2
cd example
java -Dhost=localhost -Dbootstrap_confdir=./solr/collection1/conf 
-Dcollection.configName=myconf -DzkRun -DnumShards=2 -jar start.jar

# terminal #2
cd example2
java -Dhost=localhost -Djetty.port=7574 -DzkHost=localhost:9983 -jar start.jar
{noformat}

                
> solrcloud does not detect an implicit "host" and does not provide clear error 
> using 4x example
> ----------------------------------------------------------------------------------------------
>
>                 Key: SOLR-4754
>                 URL: https://issues.apache.org/jira/browse/SOLR-4754
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Hoss Man
>
> Testing out the 4.3.0 RC3, I tried to run through the SolrCloud examples.
> Following the steps for "Example A: Simple two shard cluster" my two nodes 
> started up w/o any obvious problem, however the I noticed the cluster graph 
> was empty, and attempts to index documents failed with invalid url errors 
> when trying to forward the distributed updates.  Closer inspection of the 
> cluster state lead me to discover that the URLs for the nodes as registered 
> with ZK did not include any host information at all.  (details to follow in 
> comment)
> Apparently, the logic for implicitly detecting a hostname to use with 
> SolrCloud failed to work, and did not cause any sort of startup error.
> Important things to note:
> # java clearly _did_ know what the current configured hostname was for my 
> machine, because it appeared correctly in the {{<title/>}} tag of the admin 
> UI (pulled from "/admin/system") so i don't think this probablem is specific 
> to any sort of glitch in my hostname configuration.
> # explicitly setting the "host" sys prop (as used in the example solr.xml) 
> worked around the problem
> # I could _not_ reproduce this problem with Solr 4.2.1 (using the 4.2.1 
> example configs)
> We should try to make the hostname/url detection logic smarter (i'm not sure 
> why it isn't working as well as the SystemInfoHandler) and it should fail 
> loudly on startup as last resort rather then registering the node with ZK 
> using an invalid URL.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org