MySQLDetector异常导致的死循环
Open
- Dominant language
- Java
- Stars
- 3.2k
- Forks
- 1.2k
- PR merge metrics
- No merged PRs in 30d
Description
MySQLDetector 在出现异常情况下,使用的NIOReactor没有对异常进行处理,导致注册的OP_READ key没有取消掉,出现死循环打印错误异常的问题

Contributor guide
Research direction
Start by locating MySQLDetector and the NIOReactor path that registers OP_READ, then reproduce or inspect the exception flow shown in the issue. Done means the exceptional state no longer leaves the read key registered and the repeated error-printing loop stops.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100