Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Date: Wed, 27 Feb 2013 13:13:13 +0000 (UTC)
From: "Alfonso Presa (JIRA)" <jira@apache.org>
To: dev@lucene.apache.org
Message-ID: <JIRA.12634400.1361969671662.349933.1361970793496@arcas>
In-Reply-To: <JIRA.12634400.1361969671662@arcas>
References: <JIRA.12634400.1361969671662@arcas>
Subject: [jira] [Commented] (SOLR-4507) Cloud option not showing in admin UI
 when not using -DzkHost command line option
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Alfonso Presa commented on SOLR-4507:
-------------------------------------

Doesn't seem that either /solr/admin/system nor /solr/admin/cores provide any information about the Solr cloud is active when not using the -DzkHost command line argument :-(. 

After doing some researching, may be the easiest way to solve this issue could be calling to http://host:port/solr/zookeeper service and checking if response does contain a tree element, if so the #cloud element of the menu should be displayed.

                
> Cloud option not showing in admin UI when not using -DzkHost command line option
> --------------------------------------------------------------------------------
>
>                 Key: SOLR-4507
>                 URL: https://issues.apache.org/jira/browse/SOLR-4507
>             Project: Solr
>          Issue Type: Bug
>          Components: SolrCloud
>    Affects Versions: 4.1
>         Environment: Linux
>            Reporter: Alfonso Presa
>            Priority: Minor
>
> I've found out that in Solr 4.1, when using the zkHost attribute of the solr tag in solr.xml, instead of the -DzkHost command line option, SolrCloud works perfectly but the cloud option in the admin UI doesn't appear.
> Bug seems to be on app.js file in lines 316-322 in Solr 4.1 (406-412 in current trunk) when the UI tries to guess if SolrCloud is enabled. Not sure about the correct way of detecting if cloud is active but the current implementation is inconsistent with the funtionality available in solr.xml to provide the list of zkHosts.
> Afected snippet from app.js:
> {quote}
> if( response.jvm && response.jvm.jmx && response.jvm.jmx.commandLineArgs )
> {
>   var command_line_args = response.jvm.jmx.commandLineArgs.join( ' | ' );
>   environment_args = command_line_args.match( /-Dsolr.environment=((dev|test|prod)?[\w\d]*)/i );
>   cloud_args = command_line_args.match( /-Dzk/i );
> }
> {quote}
> *How to reproduce*
> In a Solr ensemble using zookeeper, start up a node specifing the list of hosts in the zkHost attribute of the solr tag of solr.xml file and do not provide the -DzkHost atribute.
> *Result*
> The cloud option is not available on the admin UI for that node. Though the node is registered correctly as client in the zk ensemble and is working as expected. In fact if you directly access the 'htt://host:port/solr/#/~cloud' url the cloud info is shown, but the option is still hidden.
> *Excepted result*
> When accesing the solr admin UI of the node the cloud menu option should be visible.

--
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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org