linkedin / linkedin/dr-elephant
Killing off this connection while collecting the application jobs
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.4k
- Forks
- 839
- PR merge metrics
- No merged PRs in 30d
Description
I have deployed dr. elephant on our EMR master with local history server. and dr. elephant can list our application job in UI but much more ERROR logs in logs/application.log
```
2018-02-08 11:17:19,669 - [ERROR] - from com.jolbox.bonecp.ConnectionHandle in dr-el-executor-thread-2
Database access problem. Killing off this connection and all remaining connections in the connection pool. SQL State = HY000
```
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the error in logs/application.log, especially the com.jolbox.bonecp.ConnectionHandle message about the connection pool. Review the EMR deployment with the local history server and identify which database access triggers the connection shutdown. Done means the cause is reproduced and the excess ERROR logs no longer occur while application jobs are collected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, java
- Domain
- backend, cloud, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100