[fix][broker] log update in class:LeastResourceUsageWithWeight

[StevenLuMT]

Motivation

base PR: #18964 ,log update in class(org.apache.pulsar.broker.loadbalance.extensions.strategy.LeastResourceUsageWithWeight)

Modifications

when log's level is debug,call log.debug to print log

Verifying this change

• Make sure that the change passes the CI checks.
  This change is a trivial rework / code cleanup without any test coverage.

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

Check the box below or label this PR directly.

Need to update docs?

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

Matching PR in forked repository

PR in forked repository: StevenLuMT#9

[StevenLuMT]

/pulsarbot run-failure-checks

[Technoboy-]

New loadbalancer has always been print info log with this flag.

[StevenLuMT]

@heesung-sn help me review it ,thanks

[heesung-sn]

We print info logs under the debugMode flag. Whats the intention?

[StevenLuMT]

We print info logs under the debugMode flag. Whats the intention?

@heesung-sn In your PR #18964 ,you print info log in debugMode flag,
but I think when debugMode is true,we should print debug log in PR #20168

[heesung-sn]

The intention about the info logs under this debugMode flag is to dynamically print the useful operational logs when there are issues and monitor the decision logics, without restarting brokers. One can turn off this debug mode, when done. With this dynamic flag, one may not need to change the log level as it currently outputs logs at the info level. I understand some other projects strictly matches log levels in config and code. However, it appears that Pulsar does not have such strict practice as we have other code that prints info level logs under some debug flags(e.g log.isDebugEnabled).

I would let Pulsar PMC members decide on such practice, and we follow it.

[github-actions]

The pr had no activity for 30 days, mark with Stale label.

[tisonkun]

Closed as no consensus. There is no relation between debugMode and debug log level.