hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anoop Sam John (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-14960) Fallback to using default RPCControllerFactory if class cannot be loaded
Date Thu, 10 Dec 2015 05:42:10 GMT

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

Anoop Sam John commented on HBASE-14960:
----------------------------------------

So when some one wants custom RPCControllerFactory  and configured that and there was an issue
in instantiate (Say the constructor he written was not correct wrt args) he will not get a
correct feedback..  The system will fallback to default factory.  When things dont work as
per his need, he will have to see the log to get the warn..   A bit strange IMHO..   But its
ok..  We can document the behavior clearly in our book.   Any way it will be found out by
user after the custom factory dev and 1st time test. 

+1 with a clear doc.

> Fallback to using default RPCControllerFactory if class cannot be loaded
> ------------------------------------------------------------------------
>
>                 Key: HBASE-14960
>                 URL: https://issues.apache.org/jira/browse/HBASE-14960
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Enis Soztutar
>            Assignee: Enis Soztutar
>             Fix For: 2.0.0, 1.2.0, 1.3.0
>
>         Attachments: hbase-14960_v1.patch, hbase-14960_v2.patch, hbase-14960_v3.patch
>
>
> In Phoenix + HBase clusters, the hbase-site.xml configuration will point to a custom
rpc controller factory which is a Phoenix-specific one to configure the priorities for index
and system catalog table. 
> However, sometimes these Phoenix-enabled clusters are used from pure-HBase client applications
resulting in ClassNotFoundExceptions in application code or MapReduce jobs. Since hbase configuration
is shared between Phoenix-clients and HBase clients, having different configurations at the
client side is hard. 
> We can instead try to load up the RPCControllerFactory from conf, and if not found, fallback
to the default one (in case this is a pure HBase client). In case Phoenix is already in the
classpath, it will work as usual. 
> This does not affect the rpc scheduler factory since it is only used at the server side.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message