Solr
  1. Solr
  2. SOLR-4507

Cloud option not showing in admin UI when not using -DzkHost command line option

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 4.1
    • Fix Version/s: 4.2, Trunk
    • Component/s: SolrCloud
    • Labels:
      None
    • Environment:

      Linux

      Description

      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:

      if( response.jvm && response.jvm.jmx && response.jvm.jmx.commandLineArgs )

      Unknown macro: { var command_line_args = response.jvm.jmx.commandLineArgs.join( ' | ' ); environment_args = command_line_args.match( /-Dsolr.environment=((dev|test|prod)?[wd]*)/i ); cloud_args = command_line_args.match( /-Dzk/i ); }

      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.

        Activity

        Alfonso Presa created issue -
        Alfonso Presa made changes -
        Field Original Value New Value
        Description 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.

        {quote}
        /*Afected SNIPPET from app.js*/
        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 );
        }
        /*//Afected SNIPPET from app.js*/
        {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 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.
        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.

        {quote}
        /*Afected SNIPPET from app.js*/
        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 );
        }
        /*//Afected SNIPPET from app.js*/
        {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.
        Alfonso Presa made changes -
        Description 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.

        {quote}
        /*Afected SNIPPET from app.js*/
        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 );
        }
        /*//Afected SNIPPET from app.js*/
        {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.
        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.
        Alfonso Presa made changes -
        Description 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.
        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.
        Mark Miller made changes -
        Fix Version/s 4.2 [ 12323893 ]
        Fix Version/s 5.0 [ 12321664 ]
        Mark Miller made changes -
        Assignee Mark Miller [ markrmiller@gmail.com ]
        Mark Miller made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Uwe Schindler made changes -
        Status Resolved [ 5 ] Closed [ 6 ]

          People

          • Assignee:
            Mark Miller
            Reporter:
            Alfonso Presa
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development