Uploaded image for project: 'HBase'
  1. HBase
  2. HBASE-21462

Add note for CopyTable section explained it does not perform a diff, but a full write from source to target

VotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Minor
    • Resolution: Fixed
    • 3.0.0-alpha-1, 2.1.5
    • 3.0.0-alpha-1
    • documentation
    • None

    Description

      Performance is a common issue with CopyTable is when the key/time range for the data to be copied is large because it basically scans all rows on the specified range, in the source and perform related puts on the source. We should add extra note explaining that on the reference guide, to help users/admins understand when to choose between the different tools/approaches for syncing clusters.

      Attachments

        1. HBASE-21462.master.001.patch
          1 kB
          Wellington Chevreuil
        2. HBASE-21462-master.002.patch
          1 kB
          Wellington Chevreuil

        Activity

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

          People

            wchevreuil Wellington Chevreuil
            wchevreuil Wellington Chevreuil
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment