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

Andrew Purtell commented on BIGTOP-1007:
----------------------------------------

{quote}
bq. Yes. However, there is a cost associated with creating every Configuration 
object of going to disk and reading those resources added during the directory 
scan. The more files there are, the more substantial that cost. Configuration 
objects are created all over the place for various reasons. This is why I 
wonder if merging to one file is the better option. Could try this suggestion 
out though.

This is only done on start, isn't it?
{quote}

No, Configuration objects, and the read of XML site files, are created and used 
throughout the regionserver lifetime. 

bq. And also we are not talking about hundreds of configuration files.

True

bq. We could have the jars (symlink?) being dumped in a lib directory dedicated 
to modules and have that directory referenced in the classpath.

Yes.

bq. I am not very fond of auto-generating config files on installation/startup.

Ok, I will push ahead on this with your preference.

                
> Introduce a modules system for HBase coprocessor applications
> -------------------------------------------------------------
>
>                 Key: BIGTOP-1007
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-1007
>             Project: Bigtop
>          Issue Type: Improvement
>    Affects Versions: 0.7.0
>            Reporter: Andrew Purtell
>            Assignee: Andrew Purtell
>
> Consider a modules system convention ("/etc/hbase/modules.d"), a common 
> pattern used for example by Apache httpd, for easily installation and removal 
> of HBase coprocessor applications.
> Within the modules.d/ directory, one additional level of subdirectories can 
> be created, into which a package can drop site xml fragments and scripts to 
> execute after regionserver and master (re)start. Future packages that ship an 
> HBase coprocessor application could then add configuration bits without 
> concern about collisions and trigger a regionserver reload in postinstall.
> HBase already ships a tool for merging configuration files. Changes required 
> for this will be proposed upstream if needed.

--
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

Reply via email to