[
https://issues.apache.org/jira/browse/PHOENIX-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14164429#comment-14164429
]
James Taylor commented on PHOENIX-1011:
---------------------------------------
Sounds too expensive for a runtime thing. How about for debugging this, you
locally just capture the stack trace of where the chunk was allocated. Then in
the finalizer you print out the stack trace so you know where it was allocated?
Then once these get fixed, just don't check in the stack trace stuff?
> Warning from Global Memory Manager Orphaned chunks
> --------------------------------------------------
>
> Key: PHOENIX-1011
> URL: https://issues.apache.org/jira/browse/PHOENIX-1011
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 3.0.0
> Environment: Phoenix JDBC 3.0.0-incubating
> Reporter: Nandanavanam Karthik
> Assignee: Maryann Xue
>
> I am seeing a warning message when running upsert queries using Phoenix JDBC
> 3.0.0-incubating version. I am not seeing any issues as such but the warning
> is alarming.
> James Taylor asked me to create a Jira ticket for it. Below is the warning I
> am seeing.
> [Finalizer] WARN org.apache.phoenix.memory.GlobalMemoryManager - Orphaned
> chunk of 6462 bytes found during finalize
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
