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

Share the same EventLoopGroup for NettyRpcServer, NettyRpcClient and AsyncFSWALProvider at RS side

VotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 3.0.0-alpha-1, 2.0.0-alpha-1
    • 2.0.0-alpha-2, 2.0.0
    • io, rpc, wal
    • None
    • Reviewed
    • Hide
      There are two configuration name changes as the event loop configs will not only effect rpc server but be shared by different components in the same RS instance.

      'hbase.rpc.server.nativetransport' -> 'hbase.netty.nativetransport'

      'hbase.netty.rpc.server.worker.count' -> 'hbase.netty.worker.count'

      Show
      There are two configuration name changes as the event loop configs will not only effect rpc server but be shared by different components in the same RS instance. 'hbase.rpc.server.nativetransport' -> 'hbase.netty.nativetransport' 'hbase.netty.rpc.server.worker.count' -> 'hbase.netty.worker.count'

    Description

      Need a find a proper way to pass a EventLoopGroup instance through a Configuration object.

      Attachments

        1. HBASE-18307.patch
          61 kB
          Duo Zhang
        2. HBASE-18307-v1.patch
          55 kB
          Duo Zhang
        3. HBASE-18307-v2.patch
          55 kB
          Duo Zhang

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            zhangduo Duo Zhang
            zhangduo Duo Zhang
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment