Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.6, Trunk
    • Component/s: SolrCloud
    • Labels:
      None

      Description

      Provide a way to split a shard using a route key such that all documents of the specified route key end up in a single dedicated sub-shard.

      Example:
      Assume that collection1, shard1 has hash range [0, 20]. Also that route key 'A!' has hash range [12,15]. Then invoking:

      /admin/collections?action=SPLIT&collection=collection1&split.key=A!
      

      should produce three sub-shards with hash range [0,11], [12,15] and [16,20].

      Specifying the source shard is not required here because the route key is enough to figure it out. Route keys spanning more than one shards will not be supported.

      Note that the sub-shard with the hash range of the route key may also contain documents for other route keys whose hash ranges overlap.

      1. SOLR-5338-remove-exception.patch
        2 kB
        Shalin Shekhar Mangar
      2. SOLR-5338.patch
        20 kB
        Shalin Shekhar Mangar
      3. SOLR-5338.patch
        20 kB
        Shalin Shekhar Mangar
      4. SOLR-5338.patch
        18 kB
        Shalin Shekhar Mangar

        Issue Links

          Activity

          Shalin Shekhar Mangar created issue -
          Shalin Shekhar Mangar made changes -
          Field Original Value New Value
          Link This issue is related to SOLR-5308 [ SOLR-5308 ]
          Shalin Shekhar Mangar made changes -
          Description Provide a way to split a shard using a route key such that all documents of the specified route key end up in a single dedicated sub-shard.

          Example:
          Assume that collection1, shard1 has hash range [0, 20]. Also that route key 'A!' has hash range [12,15]. Then invoking:
          {code}
          /admin/collections?action=SPLIT&collection=collection1&shard=shard1&split.key=A!
          {code}
          should produce three sub-shards with hash range [0,11], [12,15] and [16,20].

          Now the sub-shard dedicated to documents for route key 'A!' can be scaled separately.
          Provide a way to split a shard using a route key such that all documents of the specified route key end up in a single dedicated sub-shard.

          Example:
          Assume that collection1, shard1 has hash range [0, 20]. Also that route key 'A!' has hash range [12,15]. Then invoking:
          {code}
          /admin/collections?action=SPLIT&collection=collection1&split.key=A!
          {code}
          should produce three sub-shards with hash range [0,11], [12,15] and [16,20]. Then the sub-shard dedicated to documents for route key 'A!' can be scaled separately.

          Specifying the source shard is not required here because the route key is enough to figure it out.

          Shalin Shekhar Mangar made changes -
          Description Provide a way to split a shard using a route key such that all documents of the specified route key end up in a single dedicated sub-shard.

          Example:
          Assume that collection1, shard1 has hash range [0, 20]. Also that route key 'A!' has hash range [12,15]. Then invoking:
          {code}
          /admin/collections?action=SPLIT&collection=collection1&split.key=A!
          {code}
          should produce three sub-shards with hash range [0,11], [12,15] and [16,20]. Then the sub-shard dedicated to documents for route key 'A!' can be scaled separately.

          Specifying the source shard is not required here because the route key is enough to figure it out.

          Provide a way to split a shard using a route key such that all documents of the specified route key end up in a single dedicated sub-shard.

          Example:
          Assume that collection1, shard1 has hash range [0, 20]. Also that route key 'A!' has hash range [12,15]. Then invoking:
          {code}
          /admin/collections?action=SPLIT&collection=collection1&split.key=A!
          {code}
          should produce three sub-shards with hash range [0,11], [12,15] and [16,20].

          Specifying the source shard is not required here because the route key is enough to figure it out. Route keys spanning more than one shards will not be supported.

          Note that the sub-shard with the hash range of the route key may also contain documents for other route keys whose hashes collide.

          Shalin Shekhar Mangar made changes -
          Attachment SOLR-5338.patch [ 12607970 ]
          Shalin Shekhar Mangar made changes -
          Attachment SOLR-5338.patch [ 12608192 ]
          Shalin Shekhar Mangar made changes -
          Attachment SOLR-5338.patch [ 12608197 ]
          Shalin Shekhar Mangar made changes -
          Description Provide a way to split a shard using a route key such that all documents of the specified route key end up in a single dedicated sub-shard.

          Example:
          Assume that collection1, shard1 has hash range [0, 20]. Also that route key 'A!' has hash range [12,15]. Then invoking:
          {code}
          /admin/collections?action=SPLIT&collection=collection1&split.key=A!
          {code}
          should produce three sub-shards with hash range [0,11], [12,15] and [16,20].

          Specifying the source shard is not required here because the route key is enough to figure it out. Route keys spanning more than one shards will not be supported.

          Note that the sub-shard with the hash range of the route key may also contain documents for other route keys whose hashes collide.

          Provide a way to split a shard using a route key such that all documents of the specified route key end up in a single dedicated sub-shard.

          Example:
          Assume that collection1, shard1 has hash range [0, 20]. Also that route key 'A!' has hash range [12,15]. Then invoking:
          {code}
          /admin/collections?action=SPLIT&collection=collection1&split.key=A!
          {code}
          should produce three sub-shards with hash range [0,11], [12,15] and [16,20].

          Specifying the source shard is not required here because the route key is enough to figure it out. Route keys spanning more than one shards will not be supported.

          Note that the sub-shard with the hash range of the route key may also contain documents for other route keys whose hash ranges overlap.

          Shalin Shekhar Mangar made changes -
          Status Open [ 1 ] Resolved [ 5 ]
          Resolution Fixed [ 1 ]
          Shalin Shekhar Mangar made changes -
          Attachment SOLR-5338-remove-exception.patch [ 12608780 ]

            People

            • Assignee:
              Shalin Shekhar Mangar
              Reporter:
              Shalin Shekhar Mangar
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development