[Bug] Version 1.3.3 After 1 or 2 weeks of stable operation, the database error Failed to connect to config node.

### Search before asking

- [x] I searched in the [issues](https://github.com/apache/iotdb/issues) and found nothing similar.

### Version

Operating system: CentOS 7
iotdb version 1.3.3 (Build: ad95a7e)
Docker version 27.4.0, build bde2b89
docker-compose version 1.24.1, build 4667896b

### Describe the bug and provide the minimal reproduce step

I use docker-compose script to start a stand-alone iotdb service, and when my service runs stably for 1-2 weeks, the system will report the following error, causing my Java SessionPool to fail to connect to the iotdb database，Writes and reads per second are about 100-300
`
2025-01-15 00:51:06,966 [pool-30-IoTDB-ClientRPC-Processor-141] WARN o.a.i.d.p.c.ConfigNodeClient:299 - The current node may have been down TEndPoint(ip:127.0.0.1, port:10710),try next node
2025-01-15 00:51:07,967 [pool-30-IoTDB-ClientRPC-Processor-141] INFO o.a.i.c.c.ThriftClient:91 - Broken pipe error happened in sending RPC, we need to clear all previous cached connection, error msg is java.net.ConnectException: Connection refused
2025-01-15 00:51:07,968 [pool-30-IoTDB-ClientRPC-Processor-141] WARN o.a.i.d.p.c.ConfigNodeClient:299 - The current node may have been down TEndPoint(ip:127.0.0.1, port:10710),try next node
2025-01-15 00:51:07,970 [pool-30-IoTDB-ClientRPC-Processor-141] ERROR o.a.i.d.a.ClusterAuthorityFetcher:410 - Failed to connect to config node.
2025-01-15 00:51:07,989 [pool-30-IoTDB-ClientRPC-Processor-141] INFO o.a.i.c.c.ThriftClient:91 - Broken pipe error happened in sending RPC, we need to clear all previous cached connection, error msg is java.net.ConnectException: Connection refused
`
The content of my docker-compose file is：
`
version: "3.3"

services:
iotdb-service:
image: apache/iotdb:latest
hostname: iotdb
container_name: iotdb
restart: always
network_mode: "host"
environment:
- cn_internal_address=127.0.0.1
- cn_internal_port=10710
- cn_consensus_port=10720
- cn_seed_config_node=127.0.0.1:10710
- dn_rpc_address=0.0.0.0
- dn_internal_address=127.0.0.1
- dn_rpc_port=6667
- dn_mpp_data_exchange_port=10740
- dn_schema_region_consensus_port=10750
- dn_data_region_consensus_port=10760
- dn_seed_config_node=127.0.0.1:10710
privileged: true
volumes:
- ./iotdb/data:/iotdb/data
- ./iotdb/logs:/iotdb/logs
`
When I restart the container, the service is restored

### What did you expect to see?

Is there a problem with my configuration? Or whether the docker container runs this problem

### What did you see instead?


### Anything else?

_No response_

### Are you willing to submit a PR?

- [ ] I'm willing to submit a PR!

Sử dụng cấu hình docker-compose được cung cấp và các mục nhật ký của ConfigNodeClient, ClusterAuthorityFetcher và ThriftClient làm điểm bắt đầu. Điều tra lý do dịch vụ standalone mất kết nối với config-node sau 1–2 tuần trong thiết lập CentOS 7, Docker và IoTDB 1.3.3 đã nêu. Công việc được xem là hoàn thành khi xác định được nguyên nhân đã được xác nhận và ghi lại một bản sửa lỗi hoặc thay đổi cấu hình có thể tái hiện.

Do mô hình lập chỉ mục viết ra từ nội dung của issue.