You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Mark Miller (JIRA)" <ji...@apache.org> on 2011/08/19 20:24:30 UTC
[jira] [Created] (SOLR-2722) If hostPort is not specified, we
should just look for jetty.port - and if that is not found, fall back to
the default of 8983.
If hostPort is not specified, we should just look for jetty.port - and if that is not found, fall back to the default of 8983.
------------------------------------------------------------------------------------------------------------------------------
Key: SOLR-2722
URL: https://issues.apache.org/jira/browse/SOLR-2722
Project: Solr
Issue Type: Improvement
Components: SolrCloud
Reporter: Mark Miller
Assignee: Mark Miller
Priority: Trivial
Fix For: 4.0
Originally we didn't rely on jetty.port as it's container specific - but rather than require you specify the port twice in this case, we should simply use jetty.port when it's there.
The example from the SolrCloud wiki:
java -Djetty.port=7574 -DhostPort=7574 -DzkHost=localhost:9983 -jar start.jar
instead becomes:
java -Djetty.port=7574 -DzkHost=localhost:9983 -jar start.jar
We should also look at simply specifying the shard name in this example case (see the solrwiki examples) by system property rather than asking the user to edit solr.xml.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Resolved] (SOLR-2722) In solr.xml, default hostPort to
${jetty.port}
Posted by "Mark Miller (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Miller resolved SOLR-2722.
-------------------------------
Resolution: Fixed
> In solr.xml, default hostPort to ${jetty.port}
> ----------------------------------------------
>
> Key: SOLR-2722
> URL: https://issues.apache.org/jira/browse/SOLR-2722
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Reporter: Mark Miller
> Assignee: Mark Miller
> Priority: Trivial
> Fix For: 4.0
>
>
> Originally we didn't rely on jetty.port as it's container specific - but rather than require you specify the port twice in this case, we should simply use jetty.port when it's there.
> The example from the SolrCloud wiki:
> java -Djetty.port=7574 -DhostPort=7574 -DzkHost=localhost:9983 -jar start.jar
> instead becomes:
> java -Djetty.port=7574 -DzkHost=localhost:9983 -jar start.jar
> We should also look at simply specifying the shard name in this example case (see the solrwiki examples) by system property rather than asking the user to edit solr.xml.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-2722) If hostPort is not specified, we
should just look for jetty.port - and if that is not found, fall back to
the default of 8983.
Posted by "Mark Miller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087889#comment-13087889 ]
Mark Miller commented on SOLR-2722:
-----------------------------------
bq. it's just a sys property name we've specified in
Keeping in mind, we didn't really specify it - this is a jetty default - we just changed the port. Most jetty installations will respect this prop unless you happen to change it.
> If hostPort is not specified, we should just look for jetty.port - and if that is not found, fall back to the default of 8983.
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-2722
> URL: https://issues.apache.org/jira/browse/SOLR-2722
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Reporter: Mark Miller
> Assignee: Mark Miller
> Priority: Trivial
> Fix For: 4.0
>
>
> Originally we didn't rely on jetty.port as it's container specific - but rather than require you specify the port twice in this case, we should simply use jetty.port when it's there.
> The example from the SolrCloud wiki:
> java -Djetty.port=7574 -DhostPort=7574 -DzkHost=localhost:9983 -jar start.jar
> instead becomes:
> java -Djetty.port=7574 -DzkHost=localhost:9983 -jar start.jar
> We should also look at simply specifying the shard name in this example case (see the solrwiki examples) by system property rather than asking the user to edit solr.xml.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-2722) If hostPort is not specified, we
should just look for jetty.port - and if that is not found, fall back to
the default of 8983.
Posted by "Mark Miller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087886#comment-13087886 ]
Mark Miller commented on SOLR-2722:
-----------------------------------
Sure, sounds good - if people don't mind changing jetty.port to something else, I certainly don't mind.
> If hostPort is not specified, we should just look for jetty.port - and if that is not found, fall back to the default of 8983.
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-2722
> URL: https://issues.apache.org/jira/browse/SOLR-2722
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Reporter: Mark Miller
> Assignee: Mark Miller
> Priority: Trivial
> Fix For: 4.0
>
>
> Originally we didn't rely on jetty.port as it's container specific - but rather than require you specify the port twice in this case, we should simply use jetty.port when it's there.
> The example from the SolrCloud wiki:
> java -Djetty.port=7574 -DhostPort=7574 -DzkHost=localhost:9983 -jar start.jar
> instead becomes:
> java -Djetty.port=7574 -DzkHost=localhost:9983 -jar start.jar
> We should also look at simply specifying the shard name in this example case (see the solrwiki examples) by system property rather than asking the user to edit solr.xml.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-2722) If hostPort is not specified, we
should just look for jetty.port - and if that is not found, fall back to
the default of 8983.
Posted by "Mark Miller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13103621#comment-13103621 ]
Mark Miller commented on SOLR-2722:
-----------------------------------
After discussing again with Hossman some time back, I'm going to just put ${jetty.port} as the default value in Solr.xml I think.
> If hostPort is not specified, we should just look for jetty.port - and if that is not found, fall back to the default of 8983.
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-2722
> URL: https://issues.apache.org/jira/browse/SOLR-2722
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Reporter: Mark Miller
> Assignee: Mark Miller
> Priority: Trivial
> Fix For: 4.0
>
>
> Originally we didn't rely on jetty.port as it's container specific - but rather than require you specify the port twice in this case, we should simply use jetty.port when it's there.
> The example from the SolrCloud wiki:
> java -Djetty.port=7574 -DhostPort=7574 -DzkHost=localhost:9983 -jar start.jar
> instead becomes:
> java -Djetty.port=7574 -DzkHost=localhost:9983 -jar start.jar
> We should also look at simply specifying the shard name in this example case (see the solrwiki examples) by system property rather than asking the user to edit solr.xml.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-2722) If hostPort is not specified, we
should just look for jetty.port - and if that is not found, fall back to
the default of 8983.
Posted by "Hoss Man (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087880#comment-13087880 ]
Hoss Man commented on SOLR-2722:
--------------------------------
"jetty.port" isn't anything special for jetty, it's just a sys property name we've specified in example/etc/jetty.xml that defaults to 8983.
so rather then making SolrCloud code explicitly look for a sys property named after a particular container, why not change our example jetty.xml to use "solr.port" as the sysproperty for overriding the 8983 default, and the code SolrCloud to look for that more generic name as the defualt for "hostPort" in the config ?
> If hostPort is not specified, we should just look for jetty.port - and if that is not found, fall back to the default of 8983.
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-2722
> URL: https://issues.apache.org/jira/browse/SOLR-2722
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Reporter: Mark Miller
> Assignee: Mark Miller
> Priority: Trivial
> Fix For: 4.0
>
>
> Originally we didn't rely on jetty.port as it's container specific - but rather than require you specify the port twice in this case, we should simply use jetty.port when it's there.
> The example from the SolrCloud wiki:
> java -Djetty.port=7574 -DhostPort=7574 -DzkHost=localhost:9983 -jar start.jar
> instead becomes:
> java -Djetty.port=7574 -DzkHost=localhost:9983 -jar start.jar
> We should also look at simply specifying the shard name in this example case (see the solrwiki examples) by system property rather than asking the user to edit solr.xml.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Updated] (SOLR-2722) In solr.xml, default hostPort to
${jetty.port}
Posted by "Mark Miller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Miller updated SOLR-2722:
------------------------------
Summary: In solr.xml, default hostPort to ${jetty.port} (was: If hostPort is not specified, we should just look for jetty.port - and if that is not found, fall back to the default of 8983.)
> In solr.xml, default hostPort to ${jetty.port}
> ----------------------------------------------
>
> Key: SOLR-2722
> URL: https://issues.apache.org/jira/browse/SOLR-2722
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Reporter: Mark Miller
> Assignee: Mark Miller
> Priority: Trivial
> Fix For: 4.0
>
>
> Originally we didn't rely on jetty.port as it's container specific - but rather than require you specify the port twice in this case, we should simply use jetty.port when it's there.
> The example from the SolrCloud wiki:
> java -Djetty.port=7574 -DhostPort=7574 -DzkHost=localhost:9983 -jar start.jar
> instead becomes:
> java -Djetty.port=7574 -DzkHost=localhost:9983 -jar start.jar
> We should also look at simply specifying the shard name in this example case (see the solrwiki examples) by system property rather than asking the user to edit solr.xml.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-2722) In solr.xml, default hostPort to
${jetty.port}
Posted by "Mark Miller (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13177252#comment-13177252 ]
Mark Miller commented on SOLR-2722:
-----------------------------------
I've been doing this in the solrcloud branch - it will come in when we bring that back to trunk.
> In solr.xml, default hostPort to ${jetty.port}
> ----------------------------------------------
>
> Key: SOLR-2722
> URL: https://issues.apache.org/jira/browse/SOLR-2722
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Reporter: Mark Miller
> Assignee: Mark Miller
> Priority: Trivial
> Fix For: 4.0
>
>
> Originally we didn't rely on jetty.port as it's container specific - but rather than require you specify the port twice in this case, we should simply use jetty.port when it's there.
> The example from the SolrCloud wiki:
> java -Djetty.port=7574 -DhostPort=7574 -DzkHost=localhost:9983 -jar start.jar
> instead becomes:
> java -Djetty.port=7574 -DzkHost=localhost:9983 -jar start.jar
> We should also look at simply specifying the shard name in this example case (see the solrwiki examples) by system property rather than asking the user to edit solr.xml.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org