Make Netty Acceptor ThreadPool size configurable

[shoothzj]

Motivation

When the consumer application which serves ten thousands of consumers start, the default netty acceptor config opens slow. Make the consumer bootstrap costs long time.

Modifications

Make Netty acceptor threads can config, so people can tuning.

Verifying this change

• Make sure that the change passes the CI checks.

(Please pick either of the following options)

This change is a trivial rework / code cleanup without any test coverage.

(or)

This change is already covered by existing tests, such as (please describe tests).

(or)

This change added tests and can be verified as follows:

(example:)

• Added integration tests for end-to-end deployment with large payloads (10MB)
• Extended integration test for recovery after broker failure

Does this pull request potentially affect one of the following parts:

If yes was chosen, please highlight the changes

• Dependencies (does it add or upgrade a dependency): (no)
• The public API: (no)
• The schema: (no)
• The default values of configurations: (no)
• The wire protocol: (no)
• The rest endpoints: (no)
• The admin cli options: (no)
• Anything that affects deployment: (yes / no / don't know)

Documentation

• Does this pull request introduce a new feature? yes
• If yes, how is the feature documented? docs / JavaDocs

[codelipenghui]

@shoothzj It's better to use a new branch to push PR, For more details, you can see http://pulsar.apache.org/en/contributing/

[eolivelli]

LGTM

Please edit the title: "Make Netty Acceptor ThreadPool size configurable"

[shoothzj]

/pulsarbot run-failure-checks

[shoothzj]

LGTM

Please edit the title: "Make Netty Acceptor ThreadPool size configurable"

Alreay Edited

[shoothzj]

@shoothzj It's better to use a new branch to push PR, For more details, you can see http://pulsar.apache.org/en/contributing/

Ok, next time I will use a new branch to push PR.