Details

    • Type: New Feature New Feature
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: client
    • Labels:

      Description

      For some high capacity ingest, the desired path is to do some pre-splits, bulk import, and then let it naturally split down the rest of the way. If all of the pre-split tablets made split evenly, then the system will have continuous ranges bundled together on tservers. This poor distribution can impact performance depending on the operations performed. This could be handled in the load balancer, but it could be tricky. You don't want to randomly reassign tablets with any sort of frequency. Rather, you want to do a one-time operation in doing so. Given the initial assignment code is a bit random (needs to be validated), this could easily be done by offlining a table, purging all location records for it from the !METADATA table, and bringing it back online. The balancer will assign the table randomly, at which point the user could force a major compaction to restablish locality (as well some permanence in tablet assignment).

        Activity

        Hide
        Adam Fuchs added a comment -

        Does this boil down to a "randomize the location of all tablets in a range" operation? How would you test the effectiveness of this action?

        Show
        Adam Fuchs added a comment - Does this boil down to a "randomize the location of all tablets in a range" operation? How would you test the effectiveness of this action?

          People

          • Assignee:
            Unassigned
            Reporter:
            John Vines
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:

              Development