bug: lots of warning logs for batch-processor-manager.lua removing batch processor stale object

[cataglyphis]

Current Behavior

A lot of warning logs for batch-process-manager at output logs of Apisix pod

Expected Behavior

No response

Error Logs

| 2025/02/21 01:08:20 [warn] 49#49: *4638532 [lua] batch-processor-manager.lua:60: removing batch processor stale object, conf: {"max_resp_body_bytes":524888,"name":"kafka-logger","cluster_name":1,"batch_max_size":1,"include_resp_body":true,"meta_format":"default","max_retry_count":0,"required_acks":-1,"kafka_topic":"test-apisix","timeout":6,"max_req_body_bytes":524288,"inactive_timeout":5,"meta_refresh_interval":30,"producer_max_buffering":50000,"buffer_duration":60,"producer_batch_size":1048576,"include_req_body":true,"producer_time_linger":1,"producer_type":"async","producer_batch_num":200,"retry_delay":1,"brokers":[{"host":"xxx1.c1.kafka.us-west-2.amazonaws.com","port":9092},{"host":"xxx2.c1.kafka.us-west-2.amazonaws.com","port":9092},{"host":"xxx3.c1.kafka.us-west-2.amazonaws.com","port":9092}]}, context: ngx.timer, client: 10.170.50.129, server: 0.0.0.0:9080 |

Steps to Reproduce

1. run apisix in k8s env
2. enable kafka logger plugin in global rules

Environment

• APISIX version (run apisix version): 3.10.0
• Operating system (run uname -a): debian
• OpenResty / Nginx version (run openresty -V or nginx -V):
• etcd version, if relevant (run curl http://127.0.0.1:9090/v1/server_info):
• APISIX Dashboard version, if relevant:
• Plugin runner version, for issues related to plugin runners:
• LuaRocks version, for installation issues (run luarocks --version):

[bzp2010]

This is usually related to the logger plugin not being able to handle log uploads correctly, such as network errors or authentication errors. When a data batch upload fails and the maximum number of retries is exceeded, it will be deleted.
Therefore, this is the result of an error, not the cause of the error, and you have to check the log for other errors related to this and fix it.

Please provide a more complete log, otherwise this issue is pointless.