[ https://issues.apache.org/jira/browse/HBASE-7205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13527205#comment-13527205 ]
Ted Yu commented on HBASE-7205: ------------------------------- Looking at RegionCoprocessorHost.loadTableCoprocessors(), it simply logs a warning for any Exception. User has to parse region server log to find out why his/her coprocessor wasn't loaded. I wish there is a more prominent way of informing the user. In CoprocessorHost.abortServer(), coprocessorName is given. This is how RegionCoprocessorHost handles Throwable from coprocessor: {code} } catch (Throwable e) { handleCoprocessorThrowable(env, e); {code} I think similar action should be taken, for ClassNotFoundException thrown out of CoprocessorHost.load(). > 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 > Assignee: Ted Yu > Priority: Critical > Fix For: 0.96.0, 0.94.4 > > Attachments: 7205-v1.txt, 7205-v3.txt, 7205-v4.txt, 7205-v5.txt, > 7205-v6.txt, 7205-v7.txt, 7205-v8.txt, HBASE-7205_v2.patch > > > 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