[ 
https://issues.apache.org/jira/browse/HBASE-15832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16515856#comment-16515856
 ] 

Hadoop QA commented on HBASE-15832:
-----------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red}  0m  4s{color} 
| {color:red} HBASE-15832 does not apply to master. Rebase required? Wrong 
Branch? See https://yetus.apache.org/documentation/0.7.0/precommit-patchnames 
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HBASE-15832 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12804772/HBASE-15832-v1.patch |
| Console output | 
https://builds.apache.org/job/PreCommit-HBASE-Build/13300/console |
| Powered by | Apache Yetus 0.7.0   http://yetus.apache.org |


This message was automatically generated.



> memory leak in FSHLog.
> ----------------------
>
>                 Key: HBASE-15832
>                 URL: https://issues.apache.org/jira/browse/HBASE-15832
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 1.1.2
>            Reporter: Jeongdae Kim
>            Assignee: Vladimir Rodionov
>            Priority: Major
>         Attachments: HBASE-15832-v1.patch, Screenshot-Java - 
> -home-jeongdae-work-regionserver_jmap_104p_sn5_20160509-sn5_heap.hprof - 
> Eclipse -1.png
>
>
> FSHLog module uses a map to reuse SyncFuture objects, and assumes that this 
> map will be used by RPC Handler threads only. but, in some cases, this 
> assumption is wrong. 
> for example, if some coprocessors are registered, and these coprocessors uses 
> CoprocessorHConnection insteadof HConnection, and request some puts/ or 
> deletes throgh CoprocessorHConnection, all mutations will be handled by 
> hconnection's batchPool, not RPC Handlers. because hconnection's batchPool is 
> dynamically growing or shrinking, all new threads in hconnection are put to 
> the map in FSHLog, and this map will grow continuously.
> in attached image file, the map to reuse SyncFuture occupies about 4GB memory 
> and has (almost all) entries holding hconnection's thread.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to