Github user JamesRTaylor commented on the pull request:
https://github.com/apache/phoenix/commit/48e589773cbf46a10a2c1bd5cf483f2390ae1160#commitcomment-16795354
There was no symptoms, but only a warning in the logs. In this case,
Phoenix is purely tracking memory usage, but wasn't issuing a close under some
circumstances on the client and thus not freeing memory on the server (until a
GC occurred). I don't think it's related to what you're seeing. Are you seeing
this in our 4.7.0 release and if so can you reliably reproduce it? If you
wouldn't mind filing a JIRA with the steps necessary to reproduce the issue,
that be much appreciated. We have a lot of regression tests in place, but it's
always possible something slipped through the cracks.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
