mysqljs/mysql

Connection error details with a pool cluster with canRetry=true

Open

#1,612 创建于 2016年12月26日

在 GitHub 查看
 (1 评论) (0 反应) (0 负责人)JavaScript (18,137 star) (2,502 fork)batch import
help wanted

描述

When using pool cluster with canRetry=true, it would be nice to log all node connection errors to later investigate what was the problem. But while it is possible to subscribe to 'offline' event on PoolCluster, it does not provide error details why node was put offline.

Is there any way to get connection errors info from PoolCluster other than not using "canRetry=true" and doing re-tries manually?

Emitting something like 'node-error' event on PoolCluster with node and error details would be nice. Another way can be accumulating errors in node object and passing them into 'offline' event.

贡献者指南

技术栈
javascriptnodejs
领域
backenddatabase
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
half day
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
basic understanding of MySQL pool clusterNode.js event system
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
40
研究方向
Investigate the PoolCluster class in lib/pool cluster.js, specifically the handling of node errors and the 'offline' event. Consider adding a new 'node error' event that emits error details when a node connection fails, or alternatively modifying the 'offline' event to include accumulated errors. Ensure backward compatibility.