[fix][doc] Fix maxNumberOfRejectedRequestPerConnection doc

[coderzc]

Motivation

The maximum number of rejected requests of a broker in a certain time frame (30 seconds) after the current connection is closed and the client creates a new connection to connect to a different broker.

According to code, the time frame should be in the 60s instead of the 30s, see:

pulsar/pulsar-client/src/main/java/org/apache/pulsar/client/impl/ClientCnx.java

Line 157 in 7913fe5

private final int rejectedRequestResetTimeSec = 60;

pulsar/pulsar-client/src/main/java/org/apache/pulsar/client/impl/ClientCnx.java

Lines 1134 to 1145 in 7913fe5

	private void incrementRejectsAndMaybeClose() {
	long rejectedRequests = NUMBER_OF_REJECTED_REQUESTS_UPDATER.getAndIncrement(this);
	if (rejectedRequests == 0) {
	// schedule timer
	eventLoopGroup.schedule(() -> NUMBER_OF_REJECTED_REQUESTS_UPDATER.set(ClientCnx.this, 0),
	rejectedRequestResetTimeSec, TimeUnit.SECONDS);
	} else if (rejectedRequests >= maxNumberOfRejectedRequestPerConnection) {
	log.error("{} Close connection because received {} rejected request in {} seconds ", ctx.channel(),
	NUMBER_OF_REJECTED_REQUESTS_UPDATER.get(ClientCnx.this), rejectedRequestResetTimeSec);
	ctx.close();
	}
	}

Modifications

30 seconds -> 60seconds

Documentation

• doc
  (Your PR contains doc changes)

[coderzc]

@Anonymitaet @momo-jun PTAL

[momo-jun]

@coderzc thanks for maintaining the docs. Can you pls also include the update in 2.8.x docs and invite a peer to review the PR for technical validity?

[coderzc]

@coderzc thanks for maintaining the docs. Can you pls also include the update in 2.8.x docs and invite a peer to review the PR for technical validity?

I updated it 2.8.x docs.