Uploaded image for project: 'Solr'
  1. Solr
  2. SOLR-14416

Nodes view doesn't work correctly when Solr is hosted on Windows



    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Duplicate
    • Affects Version/s: 7.7.2, 8.1, 8.1.1, 8.2, 8.3, 8.3.1, 8.4, 8.4.1
    • Fix Version/s: 8.5
    • Component/s: Admin UI
    • Labels:


      I sent a message about this on the mailing list a long time ago and got no replies.
      Originally I saw it on 8.1.1, it's a problem in 8.3.1 and I don't expect it's fixed in 8.5, but I will check.

      On Solr 8.1.1 / 7.7.2 with Oracle 1.8.0_191 25.191-b12 with Solr running on Windows 10

      In the Nodes view of the Admin UI,http://localhost:8983/solr/#/~cloud?view=nodes there is a refresh button. However when you click it, the only thing that gets visibly refreshed is the 'bar chart' (not sure what to call it - it's shown when you choose show details) of the index shard size on disk. The other stats do not update.
      Also, when there is more than one node, only some of the node information is shown

      Firefox dev console shows:

      _Error: s.system.uptime is undefined

      The system response has upTimeMs in it for the JVM/JMX properties, but no system/uptime

            "solr-impl-version":"8.1.1 fcbe46c28cef11bc058779afba09521de1b19bef - ab - 2019-05-22 15:20:01",
            "lucene-impl-version":"8.1.1 fcbe46c28cef11bc058779afba09521de1b19bef - ab - 2019-05-22 15:15:24"},
            "version":"1.8.0_211 25.211-b12",
            "name":"Oracle Corporation Java HotSpot(TM) 64-Bit Server VM",
              "vendor":"Oracle Corporation",
              "name":"Java Platform API Specification",
              "vendor":"Oracle Corporation",
              "vendor":"Oracle Corporation",
              "name":"Java HotSpot(TM) 64-Bit Server VM",
              "free":"1.4 GB",
              "total":"2 GB",
              "max":"2 GB",
              "used":"566.7 MB (%27.7)",
            "name":"Windows 10",

      The SystemInfoHandler does this:

      // Try some command line things:
          try {
            if (!Constants.WINDOWS) {
              info.add( "uname",  execute( "uname -a" ) );
              info.add( "uptime", execute( "uptime" ) );
          } catch( Exception ex ) {
            log.warn("Unable to execute command line tools to get operating system properties.", ex);

      Which appears to be the problem since it won't return uname and uptime on windows, but the UI expects them

      If I run uptime from my Ubuntu shell in WSL the output is like "16:41:40 up 7 min, 0 users, load average: 0.52, 0.58, 0.59". If I make the System handler return that then there are no further dev console errors...
      However, even with that "fixed", refresh doesn't actually seem to refresh anything other than the graph.

      In contrast, refreshing the System (e.g. memory) section on the main dashboard does correctly update.

      The missing "uptime" from the response looks like the problem, but isn't actually stopping refresh from doing anything when I return an uptime. So, is the Nodes view supposed to be refreshing everything, or are my expectations wrong?


        1. screenshot-1.png
          18 kB
          Colvin Cowie

          Issue Links



              • Assignee:
                cjcowie Colvin Cowie
              • Votes:
                0 Vote for this issue
                2 Start watching this issue


                • Created: