Details

    • Sub-task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 3.0.0-alpha-1
    • 3.0.0-alpha-1, 2.3.0, HBASE-18095
    • Client
    • None
    • Hide
      <!-- markdown -->
      Enables master based registry as the default registry used by clients to fetch connection metadata.
      Refer to the section "Master Registry" in the client documentation for more details and advantages
      of this implementation over the default Zookeeper based registry.

      Configuration parameter that controls the registry in use: `hbase.client.registry.impl`

      Where to set this: HBase client configuration (hbase-site.xml)

      Possible values:
      - `org.apache.hadoop.hbase.client.ZKConnectionRegistry` (For ZK based registry implementation)
      - `org.apache.hadoop.hbase.client.MasterRegistry` (New, for master based registry implementation)

      Notes on defaults:

      - For v3.0.0 and later, MasterRegistry is the default registry
      - For all releases in 2.x line, ZK based registry is the default.

      This feature has been back ported to 2.3.0 and later releases. MasterRegistry can be enabled by setting the following client configuration.

      ```
      <property>
        <name>hbase.client.registry.impl</name>
        <value>org.apache.hadoop.hbase.client.MasterRegistry</value>
      </property>
      ```
      Show
      <!-- markdown --> Enables master based registry as the default registry used by clients to fetch connection metadata. Refer to the section "Master Registry" in the client documentation for more details and advantages of this implementation over the default Zookeeper based registry. Configuration parameter that controls the registry in use: `hbase.client.registry.impl` Where to set this: HBase client configuration (hbase-site.xml) Possible values: - `org.apache.hadoop.hbase.client.ZKConnectionRegistry` (For ZK based registry implementation) - `org.apache.hadoop.hbase.client.MasterRegistry` (New, for master based registry implementation) Notes on defaults: - For v3.0.0 and later, MasterRegistry is the default registry - For all releases in 2.x line, ZK based registry is the default. This feature has been back ported to 2.3.0 and later releases. MasterRegistry can be enabled by setting the following client configuration. ``` <property>   <name>hbase.client.registry.impl</name>   <value>org.apache.hadoop.hbase.client.MasterRegistry</value> </property> ```

    Description

      Now that we are close to getting the registry implementation patch in, the idea here is to make it the default implementation in 3.0.0 and this means

      • No known bugs with the implementation
      • No known performance issues
      • Entire nightly test suite is green (and without flakes).

      Attachments

        Issue Links

          Activity

            People

              bharathv Bharath Vissapragada
              bharathv Bharath Vissapragada
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: