[cleanup] remove unused config messagePublishBufferCheckIntervalInMillis (#24252)

Author: dao-jun

deployment/terraform-ansible/templates/broker.conf

@@ -410,10 +410,6 @@ replicatedSubscriptionsSnapshotMaxCachedPerSubscription=10
 # Use -1 to disable the memory limitation. Default is 1/2 of direct memory.
 maxMessagePublishBufferSizeInMB=
 
-# Interval between checks to see if message publish buffer size is exceed the max message publish buffer size
-# Use 0 or negative number to disable the max publish buffer limiting.
-messagePublishBufferCheckIntervalInMillis=100
-
 # Check between intervals to see if consumed ledgers need to be trimmed
 # Use 0 or negative number to disable the check
 retentionCheckIntervalInSeconds=120

pulsar-broker-common/src/main/java/org/apache/pulsar/broker/ServiceConfiguration.java

@@ -1474,13 +1474,6 @@ The max allowed delay for delayed delivery (in milliseconds). If the broker rece
     private int maxMessagePublishBufferSizeInMB = Math.max(64,
         (int) (DirectMemoryUtils.jvmMaxDirectMemory() / 2 / (1024 * 1024)));
 
-    @FieldContext(
-        category = CATEGORY_SERVER,
-        doc = "Interval between checks to see if message publish buffer size is exceed the max message publish "
-                + "buffer size"
-    )
-    private int messagePublishBufferCheckIntervalInMillis = 100;
-
     @FieldContext(category = CATEGORY_SERVER, doc = "Whether to recover cursors lazily when trying to recover a "
             + "managed ledger backing a persistent topic. It can improve write availability of topics.\n"
             + "The caveat is now when recovered ledger is ready to write we're not sure if all old consumers last mark "