hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-8607) Run HBase server in an OSGi container
Date Tue, 04 Jun 2013 00:18:21 GMT

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

James Taylor commented on HBASE-8607:
-------------------------------------

To a large degree, Phoenix gets it's performance from being able to run inside the JVM of
the region server, so if I understand this idea, we'd lose that with this approach.

I'm no OSGi expert, but I talked with some folks here, and it seems that we could do what
we want through OSGi and swap in new jars without requiring a rolling restart. 

Might be worth a visit here to explore? I'm happy to set something up.


                
> 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

Mime
View raw message