HBase
  1. HBase
  2. HBASE-5312 Closed parent region present in Hlog.lastSeqWritten
  3. HBASE-5376

Add more logging to triage HBASE-5312: Closed parent region present in Hlog.lastSeqWritten

    Details

    • Type: Sub-task Sub-task
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Later
    • Affects Version/s: 0.90.7
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      It is hard to find out what exactly caused HBASE-5312. Some logging will be helpful to shine some lights.

      1. hbase-5376.txt
        2 kB
        Jimmy Xiang

        Activity

        Hide
        Jimmy Xiang added a comment -

        Close it for now. We haven't seen such a problem for quite a long time.

        Show
        Jimmy Xiang added a comment - Close it for now. We haven't seen such a problem for quite a long time.
        Hide
        Jonathan Hsieh added a comment -

        Jimmy, this patch look trivial, do you want to commit this the 0.90 branch? Other branches?

        Show
        Jonathan Hsieh added a comment - Jimmy, this patch look trivial, do you want to commit this the 0.90 branch? Other branches?
        Hide
        Jimmy Xiang added a comment -

        I added some warnings. Anywhere else should I add too?

        Show
        Jimmy Xiang added a comment - I added some warnings. Anywhere else should I add too?
        Hide
        Jimmy Xiang added a comment -

        I was thinking to use YCSB to load lots of data while set the region size small, so that lots of region split will be triggered. How is that?

        Show
        Jimmy Xiang added a comment - I was thinking to use YCSB to load lots of data while set the region size small, so that lots of region split will be triggered. How is that?
        Hide
        Todd Lipcon added a comment -

        I bet we could also write a stress test - sounds like some race where we don't block off updates at the right spot when closing a region. Maybe a test which continually opens/closes a region while making edits, and after every close, verify it's not in the map?

        Show
        Todd Lipcon added a comment - I bet we could also write a stress test - sounds like some race where we don't block off updates at the right spot when closing a region. Maybe a test which continually opens/closes a region while making edits, and after every close, verify it's not in the map?

          People

          • Assignee:
            Jimmy Xiang
            Reporter:
            Jimmy Xiang
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development