[
https://issues.apache.org/jira/browse/HBASE-8607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13672938#comment-13672938
]
Nicolas Liochon commented on HBASE-8607:
----------------------------------------
Running the coprocessor within the region server removes the problem of
managing the life cycle of two different processes, with all the questions of
"the coprocessor takes time, is it dead? Is it gc-ing?" (with the same
questions on the coprocessor side: "I'm not called, why?").
btw, do we manage today the fact that we can have conflicts between hbase third
parties and the coprocessor ones?
While OSGi is nice (and allows more features on the long term), I also think
that the rolling restart should work well enough (or should be made working
well enough) for most cases, as it shares a lot of code with stuff like balance
or recovery.
> Run HBase server in an OSGi container
> -------------------------------------
>
> Key: HBASE-8607
> URL: https://issues.apache.org/jira/browse/HBASE-8607
> Project: HBase
> Issue Type: New Feature
> Components: regionserver
> Reporter: James Taylor
>
> Run the HBase server in an OSGi container to support updating custom filters
> and coprocessor updates without requiring a region server reboot. Typically,
> applications that use coprocessors and custom filters also have shared
> classes underneath, so putting the burden on the user to include some kind of
> version name in the class is not adequate. Including the version name in the
> package might work in some cases (at least until dependent jars start to
> change as well), but is cumbersome and overburdens the app developer.
--
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
