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

make memory locking configuration of regioservers more flexible

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 0.95.2
    • Fix Version/s: 0.95.0
    • Component/s: scripts
    • Labels:
      None
    • Hadoop Flags:
      Incompatible change, Reviewed
    • Release Note:
      Hide
      Removes --mlock start flag. Adds the below instead:

      HBASE_REGIONSERVER_MLOCK binary: empty/not set – disabled, non empty – enabled
      HBASE_REGIONSERVER_UID string: a target user for the running process regardless of any other feature that is enabled
      Show
      Removes --mlock start flag. Adds the below instead: HBASE_REGIONSERVER_MLOCK binary: empty/not set – disabled, non empty – enabled HBASE_REGIONSERVER_UID string: a target user for the running process regardless of any other feature that is enabled

      Description

      The current implementation of the memory locking feature of regisoservers has a downside of not being flexible to configure for permanent use. Sure there is a --mlock flag but that needs to be explicitly passed on every invocation and thus require extra steps to be configured for permanent use (IOW, there's not a single env variable I can set to have a desired effect). The only other alternative – the explicit setting of HBASE_REGIONSERVER_OPTS – has a downside of being pretty cryptic to the novice user and has a killer problem of not explicitly telling higher level scripts (like init.d or upstart ones) which user the initial hbase process should be executed as.

      I propose a very simple solution (which is essentially making --mlock setting into an env. variable): add a variable called HBASE_REGIONSERVER_MLOCK that can be set in hbase-env.sh and has the following semantics:

      • [default] not set: mlocking feature is disabled
      • set but empty: mlocking feature is enabled and the target user is hbase
      • set and not empty: mlocking feature is enabled and the target user is the value of the variable

      Thoughts?

        Attachments

        1. HBASE-6567-v0.patch
          2 kB
          Matteo Bertozzi

          Issue Links

            Activity

              People

              • Assignee:
                mbertozzi Matteo Bertozzi
                Reporter:
                rvs Roman Shaposhnik
              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: