newrelic / newrelic/newrelic-java-agent
[Spike] Investigate possible issues with lettuce 6.5 instrumentation
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 240
- Forks
- 170
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 21
Description
We've received reports of unusual behavior with the lettuce 6.5 instrumentation enabled. At the surface, this instrumentation is near-identical to our existing 6.0 instrumentation. Further investigation is needed to diagnose and troubleshoot possible issues this module may be causing.
So far, the issue has manifested as apparent (very slow) increase in memory consumption, as well as, possibly, many connection attempts (see the GTSE below).
GTSE showing some possible symptoms: https://new-relic.atlassian.net/browse/NR-467339
Other GTSE showing possible memory issues: https://new-relic.atlassian.net/browse/NR-461651?focusedCommentId=1400636
Contributor guide
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
No source files or tests are named. Start by reproducing the reported behavior with lettuce 6.5 instrumentation enabled and compare it with the existing 6.0 instrumentation, using the linked GTSE reports as symptoms to investigate. Done means documenting whether the instrumentation causes the memory growth or connection attempts and identifying the cause or a clear next step.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- observability-sre
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100