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

Comment ClientScanner logic for NSREs.

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • None
    • 0.99.0, 0.94.23, 0.98.6
    • None
    • None

    Description

      We ran into an issue with Phoenix where a RegionObserver coprocessor intercepts a scan and returns an aggregate (in this case a count) with a fake row key. It turns out this does not work when the ClientScanner encounters NSREs, as it uses the last key it saw to reset the scanner to try again (which in this case would be the fake key).

      While this is arguably a rare case and one could also argue that a region observer just shouldn't do this... While looking at ClientScanner's code I found this logic not necessary.
      A NSRE occurred because we contacted a region server with a key that it no longer hosts. This is the start key, so it is always correct to retry with this same key. That simplifies the ClientScanner logic and also make this sort of coprocessors possible,

      Attachments

        1. 11667-0.94.txt
          3 kB
          Lars Hofhansl
        2. 11667-doc-0.94.txt
          1 kB
          Lars Hofhansl
        3. 11667-trunk.txt
          5 kB
          Lars Hofhansl
        4. HBASE-11667-0.98.patch
          4 kB
          Andrew Kyle Purtell
        5. IntegrationTestBigLinkedListWithRegionMovement.patch
          4 kB
          Andrew Kyle Purtell

        Issue Links

          Activity

            People

              larsh Lars Hofhansl
              larsh Lars Hofhansl
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: