[
https://issues.apache.org/jira/browse/HBASE-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13630724#comment-13630724
]
Jimmy Xiang commented on HBASE-1936:
------------------------------------
Yes, that's right. The reason for the rolling restart is to unload the old
version. If you just add some new filters to the existing jar file even the jar
file name is the same, you don't need rolling restart.
It will be helpful if we can unload an old version class. However, this means
we need to track where the class is loaded, and when the jar file is changed,
to avoid performance issue. We also need to come up a way to unload a class in
this scenario, which is not trivial.
> ClassLoader that loads from hdfs; useful adding filters to classpath without
> having to restart services
> -------------------------------------------------------------------------------------------------------
>
> Key: HBASE-1936
> URL: https://issues.apache.org/jira/browse/HBASE-1936
> Project: HBase
> Issue Type: New Feature
> Reporter: stack
> Assignee: Jimmy Xiang
> Labels: noob
> Fix For: 0.98.0, 0.95.1
>
> Attachments: 0.94-1936.patch, cp_from_hdfs.patch,
> HBASE-1936-trunk(forReview).patch, trunk-1936.patch, trunk-1936_v2.1.patch,
> trunk-1936_v2.2.patch, trunk-1936_v2.patch, trunk-1936_v3.patch
>
>
--
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
