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

UI: Cloud>NOdes screen can't display disk usage from replicas using non-standard core names (ie: implicit router)

Agile BoardAttach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 9.3
    • None
    • None

    Description

      Consider the following cluster w/three collections (including the gettingstarted collection created by the example)...

      ./solr/packaging/build/dev/bin/solr -e cloud -noprompt
      curl -sS 'http://localhost:8983/solr/admin/collections?action=CREATE&name=named_shards&router.name=compositeId&numShards=2&shards=shardX,shardY'
      curl -sS 'http://localhost:8983/solr/admin/collections?action=CREATE&name=implicit_named_shards&router.name=implicit&shards=shardA,shardB'

       

      If you look at the Cloud>Nodes screen for this cluster, the "Disk Usage" (and other metrics) for the cores from the implicit_named_shards collection wound show up. (see screenshot)

       

      The problem is that cloud.js expects core names to follow a very specific format, but implicit router names it's cores directly after the shard names specified.

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            janhoy Jan Høydahl
            hossman Chris M. Hostetter
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

              Estimated:
              Original Estimate - Not Specified
              Not Specified
              Remaining:
              Remaining Estimate - 0h
              0h
              Logged:
              Time Spent - 1.5h
              1.5h

              Slack

                Issue deployment