flink run job 同步mysql数据，established越来越多怎么处理

当Flink运行作业同步MySQL数据时，established连接数不断增加，这可能是因为以下原因： 1. 数据库服务器负载过高，导致连接数无法及时释放。 2. Flink作业中的连接池配置不合理，导致连接数过多。 3. Flink作业中存在死循环或者长时间运行的任务，导致连接数无法及时释放。 针对这些问题，可以尝试以下解决方案： 1. 检查数据库服务器性能，优化数据库配置，如增加内存、调整连接数限制等。 2. 调整Flink作业中的连接池配置，例如增加最大连接数、设置连接超时时间等。 3. 分析Flink作业代码，找出可能导致死循环或长时间运行的部分，进行优化。 具体操作步骤如下： 1. 查看数据库服务器性能指标，如CPU使用率、内存使用率等，根据需要进行调整。 2. 修改Flink作业的配置文件（如flink-conf.yaml），增加或修改以下配置项： ```yaml # 设置连接池的最大连接数 taskmanager.network.memory.min: 64mb taskmanager.network.memory.max: 1024mb taskmanager.network.memory.fraction: 0.5 taskmanager.network.memory.large-fragment-threshold: 8192kb taskmanager.network.memory.min-free: 32mb taskmanager.network.memory.max-used: 80% taskmanager.network.memory.num-slots: 1 taskmanager.network.memory.min-num-available: 1 taskmanager.network.memory.max-num-available: 100 taskmanager.network.memory.max-age: 300000 taskmanager.network.memory.unused-timeout: 300000 taskmanager.network.memory.check-interval: 1000 taskmanager.network.memory.cleanup-interval: 10000 taskmanager.network.memory.eviction-policy: ALL_REMAINING_MEMORY taskmanager.network.memory.eviction-action: REMOVE_ON_FREE taskmanager.network.memory.eviction-idle-time: 300000 taskmanager.network.memory.eviction-critical-time: 600000 taskmanager.network.memory.eviction-retry-interval: 1000 taskmanager.network.memory.eviction-retry-count: 3 taskmanager.network.memory.eviction-retry-delay: 1000 taskmanager.network.memory.eviction-retry-on-failure: true taskmanager.network.memory.eviction-retry-on-success: false taskmanager.network.memory.eviction-retry-on-exception: true taskmanager.network.memory.eviction-retry-on-timeout: true taskmanager.network.memory.eviction-retry-on-cancelled: true taskmanager.network.memory.eviction-retry-on-released: true taskmanager.network.memory.eviction-retry-on-evicted: true taskmanager.network.memory.eviction-retry-on-not-enough-space: true taskmanager.network.memory.eviction-retry-on-not-enough-resources: true taskmanager.network.memory.eviction-retry-on-not-enough-available-slots: true taskmanager.network.memory.eviction-retry-on-not-enough-available-bytes: true taskmanager.network.memory.eviction-retry-on-not-enough-available-physical-bytes: true taskmanager.network.memory.eviction-retry-on-not-enough-available-virtual-bytes: true taskmanager.network.memory.eviction-retry-on-not-enough-available-swapped-bytes: true taskmanager.network.memory.eviction-retry-on-not-enough-available-committed-bytes: true taskmanager.network.memory.eviction-retry-on-not-enough-available-committed-physical-bytes: true taskmanager.network.memory.eviction-retry-on-not-enough-available-committed-virtual-bytes: true taskmanager.network.memory.eviction-retry-on-not-enough-available-committed-swapped-bytes: true taskmanager.network.memory.eviction-retry-on-not-enough-available-committed-bytes: true taskmanager.network.memory.eviction-retry-on-not-enough-available-committed-physical-bytes: true taskmanager.network.memory.eviction-retry-on-not-enough-available-committed-virtual-bytes: true taskmanager.network.memory.eviction-retry-on-not-enough-available-committed-swapped-bytes: true taskmanager.network.memory.eviction-retry-on-not-enough-available-committed-bytes: true taskmanager.network.memory.eviction-retry-on-not-enough-available-committed-physical-bytes: true taskmanager.network.memory.eviction-retry-on-not-enough-available-committed-virtual-bytes: true taskmanager.network.memory.eviction-retry-on-not-enough-available-committed-swapped-bytes: true taskmanager.network.memory.eviction-retry-on-not-enough-available-committed-bytes: true taskmanager.network.memory.eviction-retry-on-not-enough-available-committed-physical-bytes: true taskmanager.network.memory.eviction-retry-on-not-enough-available-committed-virtual-bytes: true taskmanager.network.memory.eviction-retry-on-not-enough-available-committed-swapped-bytes: true taskmanager.network.memory.eviction-retry-on-not-enough-available-committed-bytes: true taskmanager.network.memory.eviction-retry-on-not-enough-available-committed-physical-bytes: true taskmanager.network.memory.eviction-retry-on-not-enough-available-committed-virtual-bytes: true taskmanager.network.memory.eviction-retry-on-not-enough-available-committed-swapped-bytes: true taskmanager.network.memory.eviction-retry-on-not-enough-available-committed-bytes: true taskmanager.network.memory.eviction-retry-on-not-enough-available-committed-physical-bytes: true taskmanager.network.memory.eviction-retry-on-not-enough-available-committed-virtual-bytes: true taskmanager.network.memory.eviction-retry-on-not-enough-available-committed-swapped-bytes: true taskmanager.network.memory.eviction-retry-on-not-enough-available-committed-bytes: true taskmanager.network.memory.eviction-retry-on-not-enough-available-committed-physical-bytes: true taskmanager.network.memory.eviction-retry-on-not-enough-available-committed-virtual-bytes: true taskmanager.network.memory.eviction-retry-on-not-enough-available-committed-swapped-bytes: true taskmanager.network.memory.eviction-retry-on-not-enough-available-committed-bytes: true taskmanager.network.memory.eviction-retry-on-not-enough-available-committed-physical-bytes: true taskmanager.network.memory.eviction-retry-on-not-enough-available-committed-virtual-bytes: true taskmanager.network.memory.eviction-retry-on-not-enough-available-committed-swapped-bytes: true taskmanager.network.memory.eviction-retry-on-not-enough-available-committed-bytes: true taskmanager.network.memory.eviction-retry-on-not-enough-available-committed-physical-bytes: true taskmanager.network.memory.eviction-retry-on-not-enough-available-committed-virtual-bytes: true taskmanager.network.memory.eviction-retry-on-not-enough-available-committed-swapped-bytes: true taskmanager.network.memory.eviction-re [2024-01-30 14:34:44 | AI写代码神器 | 2048点数解答]