You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Ted Yu (JIRA)" <ji...@apache.org> on 2012/12/04 00:51:58 UTC

[jira] [Commented] (HBASE-7205) Coprocessor classloader is replicated for all regions in the HRegionServer

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

Ted Yu commented on HBASE-7205:
-------------------------------

{code}
  public CoprocessorClassLoader(List<URL> paths, ClassLoader parent) {
    super(paths.toArray(new URL[]{}), parent);
{code}
CoprocessorClassLoader is given a list of URLs.
{code}
  synchronized public Class<?> loadClass(String name) 
{code}
loadClass() delegates locating class to URLClassLoader.findClass().
Looks like we can extract the path where the class is actually loaded by calling http://docs.oracle.com/javase/6/docs/api/java/net/URLClassLoader.html#findResource%28java.lang.String%29.
                
> Coprocessor classloader is replicated for all regions in the HRegionServer
> --------------------------------------------------------------------------
>
>                 Key: HBASE-7205
>                 URL: https://issues.apache.org/jira/browse/HBASE-7205
>             Project: HBase
>          Issue Type: Bug
>          Components: Coprocessors
>    Affects Versions: 0.92.2, 0.94.2
>            Reporter: Adrian Muraru
>            Priority: Critical
>             Fix For: 0.96.0, 0.94.4
>
>
> HBASE-6308 introduced a new custom CoprocessorClassLoader to load the coprocessor classes and a new instance of this CL is created for each single HRegion opened. This leads to OOME-PermGen when the number of regions go above hundres / region server. 
> Having the table coprocessor jailed in a separate classloader is good however we should create only one for all regions of a table in each HRS.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira