[improve][proxy] When adding new brokers resolve the DNS name more quickly

[frankjkelly]

Fixes #21206

Motivation

When autoscaling brokers, the current default negative ttl is 10 seconds so it might take up to 10 seconds before the proxy realizes the broker was available and this could lead to errors at the pulsar client if the operation timeout was below 10 seconds .
Similarly this should have positive impact for broker --> bookie (when new bookies are autoscaling).

Modifications

Added a line to the Dockerfile to override the negative.ttl in the java.security file

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 the box was checked, please highlight the changes

• Dependencies (add or upgrade a dependency)
• The public API
• The schema
• The default values of configurations
• The threading model
• The binary protocol
• The REST endpoints
• The admin CLI options
• The metrics
• Anything that affects deployment

Documentation

• doc
• doc-required
• doc-not-needed
• doc-complete

Matching PR in forked repository

PR in forked repository:

[github-actions]

@frankjkelly Please add the following content to your PR description and select a checkbox:

- [ ] `doc` <!-- Your PR contains doc changes -->
- [ ] `doc-required` <!-- Your PR changes impact docs and you will update later -->
- [ ] `doc-not-needed` <!-- Your PR changes do not impact docs -->
- [ ] `doc-complete` <!-- Docs have been already added -->

[frankjkelly]

CC: @Technoboy- @tisonkun @lhotari as they touched DnsResolverUtil.java which is related
https://github.com/apache/pulsar/blob/master/pulsar-common/src/main/java/org/apache/pulsar/common/util/netty/DnsResolverUtil.java

[tisonkun]

Thank you!

[tisonkun]

I suggest this to be an improvement rather than a bugfix?

[frankjkelly]

I suggest this to be an improvement rather than a bugfix?

Makes sense - done.

[tisonkun]

Merging..

Thanks for your contribution!

[frankjkelly]

Merging..

Thanks for your contribution!

Thanks @tisonkun - if I wanted to backport this change to active branches (e.g. 3.1/3.0/2.11/2.10 etc) does that make sense?

[tisonkun]

@frankjkelly thanks for your question!

I'd hear from @codelipenghui @Technoboy- & @eolivelli.

Generally, I'm OK to backport this patch. For the target branches, 3.0 and 3.1 is undoubtedly supported, but I'm not sure for 2.10 and 2.11.

The best way for such discussion would be that you send an email to the dev@pulsar.apache.org mailing list. Subscribe following the instruction here, and refer to previous discussions like this one.

[nodece]

I think this is a bug, and I would like to backport this patch to the branch-3.0.