hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-4014) Coprocessors: Flag the presence of coprocessors in logged exceptions
Date Tue, 21 Jun 2011 17:33:47 GMT

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

Andrew Purtell commented on HBASE-4014:

We just need a concurrent update safe {{Set<? extends Coprocessor>}} in the global scope
of the regionserver and master that gets updated whenever a CoprocessorHost is created during
HRegion load.

There is no need to worry about removing listed CPs if all tables for which a CP was loaded
are disabled or if all relevant regions move off a RegionServer; currently once a CP is loaded
the classes remain resident in the JVM even if no active instances. (Class unloading is tricky.
We've decided to not do it for CPs unless there is a compelling reason.)

> Coprocessors: Flag the presence of coprocessors in logged exceptions
> --------------------------------------------------------------------
>                 Key: HBASE-4014
>                 URL: https://issues.apache.org/jira/browse/HBASE-4014
>             Project: HBase
>          Issue Type: Improvement
>          Components: coprocessors
>            Reporter: Andrew Purtell
> For some initial triage of bug reports for core versus for deployments with loaded coprocessors,
we need something like the Linux kernel's taint flag, and list of linked in modules that show
up in the output of every OOPS, to appear above or below exceptions that appear in the logs.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message