Uploaded image for project: 'Phoenix'
  1. Phoenix
  2. PHOENIX-938

Use higher priority queue for index updates to prevent deadlock

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 4.0.0, 4.3.0
    • 4.1.0
    • None

    Description

      With our current global secondary indexing solution, a batched Put of table data causes a RS to do a batch Put to other RSs. This has the potential to lead to a deadlock if all RS are overloaded and unable to process the pending batched Put. To prevent this, we should use a higher priority queue to submit these Puts so that they're always processed before other Puts. This will prevent the potential for a deadlock under high load. Note that this will likely require some HBase 0.98 code changes and would not be feasible to implement for HBase 0.94.

      Attachments

        1. phoenix-938-4.0-v0.patch
          41 kB
          Jesse Yates
        2. phoenix-938-4.0-v0.patch
          34 kB
          Jesse Yates
        3. phoenix-938-master-v0.patch
          20 kB
          Jesse Yates
        4. phoenix-938-master-v1.patch
          34 kB
          Jesse Yates
        5. phoenix-938-master-v2.patch
          59 kB
          Jesse Yates
        6. PHOENIX-938-master-v3.patch
          62 kB
          Andrew Kyle Purtell
        7. phoenix-938-master-v4.patch
          41 kB
          Jesse Yates
        8. phoenix-938-master-v5.patch
          42 kB
          Jesse Yates

        Issue Links

          Activity

            People

              jesse_yates Jesse Yates
              jamestaylor James R. Taylor
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: