[Bug] [cli] Pulsar-client cli doesn't support timeout values given in apache pulsar reference website

[sandeep-mst]

Search before asking

• [X] I searched in the issues and found nothing similar.

Read release policy

• [X] I understand that unsupported versions don't get bug fixes. I will attempt to reproduce the issue on a supported version of Pulsar client and Pulsar broker.

Version

OS: Linux, macOS Java: 17 Pulsar Client and Broker: 3.2.2

Minimal reproduce step

• Update the conf/client.conf file with lookupTimeoutMs, operationTimeoutMs and other timeout values described here
• Run pulsar-perf or pulsar-client and observe the logs.
• We get this info log from org.apache.pulsar.client.impl.ConsumerStatsRecorderImpl where the timeout values doesn't change with the configuration.

"operationTimeoutMs":30000,"lookupTimeoutMs":30000

What did you expect to see?

The timeout values getting picked up from the conf/client.conf.

What did you see instead?

The timeout values are always default values.

Anything else?

This works fine with Java client. The pulsar-cli tools have this issue.

Are you willing to submit a PR?

• [X] I'm willing to submit a PR!