Solr
  1. Solr
  2. SOLR-4968

The collection alias api should have a list cmd.

    Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 4.9, 5.0
    • Component/s: SolrCloud
    • Labels:
      None

      Activity

      Hide
      Uwe Schindler added a comment -

      Move issue to Solr 4.9.

      Show
      Uwe Schindler added a comment - Move issue to Solr 4.9.
      Hide
      Shawn Heisey added a comment -

      Is there currently a workaround to getting this list of aliases?

      Where do they get stored? If they only get stored in Zookeeper then how can they be backed up in case of a Zookeeper failure where all the config needs to be reloaded back into Zookeeper? Would I just have to recreate all of the aliases?

      As far as I know, they are indeed only in zookeeper. You can see them in the Admin UI by clicking the Cloud tab, then Tree, then /aliases.json in the tree view. You should maintain documentation on how you built your SolrCloud and Zookeeper configs so you can recreate them if you lose them entirely.

      A fully redundant zookeeper ensemble with three or more hosts should keep you from encountering a situation where you have to entirely reconstruct the ZK database, but but you do bring up a good point - it is always a good idea to have actual backups in case of severe bugs, human error, or malicious intent.

      Here's some information at the zookeeper level on maintenance and data file management:

      http://zookeeper.apache.org/doc/current/zookeeperAdmin.html#sc_maintenance
      http://zookeeper.apache.org/doc/current/zookeeperAdmin.html#sc_dataFileManagement

      I found these URLs in a Stack Overflow question about backing up zookeeper:

      http://stackoverflow.com/questions/6394140/how-do-you-backup-zookeeper

      Show
      Shawn Heisey added a comment - Is there currently a workaround to getting this list of aliases? Where do they get stored? If they only get stored in Zookeeper then how can they be backed up in case of a Zookeeper failure where all the config needs to be reloaded back into Zookeeper? Would I just have to recreate all of the aliases? As far as I know, they are indeed only in zookeeper. You can see them in the Admin UI by clicking the Cloud tab, then Tree, then /aliases.json in the tree view. You should maintain documentation on how you built your SolrCloud and Zookeeper configs so you can recreate them if you lose them entirely. A fully redundant zookeeper ensemble with three or more hosts should keep you from encountering a situation where you have to entirely reconstruct the ZK database, but but you do bring up a good point - it is always a good idea to have actual backups in case of severe bugs, human error, or malicious intent. Here's some information at the zookeeper level on maintenance and data file management: http://zookeeper.apache.org/doc/current/zookeeperAdmin.html#sc_maintenance http://zookeeper.apache.org/doc/current/zookeeperAdmin.html#sc_dataFileManagement I found these URLs in a Stack Overflow question about backing up zookeeper: http://stackoverflow.com/questions/6394140/how-do-you-backup-zookeeper
      Hide
      Bryce Griner added a comment -

      Is there currently a workaround to getting this list of aliases?

      Where do they get stored? If they only get stored in Zookeeper then how can they be backed up in case of a Zookeeper failure where all the config needs to be reloaded back into Zookeeper? Would I just have to recreate all of the aliases?

      Show
      Bryce Griner added a comment - Is there currently a workaround to getting this list of aliases? Where do they get stored? If they only get stored in Zookeeper then how can they be backed up in case of a Zookeeper failure where all the config needs to be reloaded back into Zookeeper? Would I just have to recreate all of the aliases?
      Hide
      Steve Rowe added a comment -

      Bulk move 4.4 issues to 4.5 and 5.0

      Show
      Steve Rowe added a comment - Bulk move 4.4 issues to 4.5 and 5.0
      Hide
      Mark Miller added a comment -

      First patch. Response needs some tweaking, test needs some asserts.

      Show
      Mark Miller added a comment - First patch. Response needs some tweaking, test needs some asserts.

        People

        • Assignee:
          Mark Miller
          Reporter:
          Mark Miller
        • Votes:
          0 Vote for this issue
          Watchers:
          4 Start watching this issue

          Dates

          • Created:
            Updated:

            Development