[
https://issues.apache.org/jira/browse/HBASE-12630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14239683#comment-14239683
]
Ashish Singhi commented on HBASE-12630:
---------------------------------------
bq. Why we need this? If problematic config, load a replacement or a restore?
[[email protected]], I am not pretty sure why we are doing this way!
[~tedyu] or [~manukranthk] will have a answer to this.
> Provide capability for dropping malfunctioning ConfigurationObserver
> automatically
> ----------------------------------------------------------------------------------
>
> Key: HBASE-12630
> URL: https://issues.apache.org/jira/browse/HBASE-12630
> Project: HBase
> Issue Type: Improvement
> Reporter: Ted Yu
> Assignee: Ashish Singhi
> Fix For: 1.0.0, 2.0.0
>
> Attachments: HBASE-12630-v2.patch, HBASE-12630-v3.patch,
> HBASE-12630.patch
>
>
> Chatting with Manukranth, online config update feature should handle the case
> where certain ConfigurationObserver(s) constantly produce exception when
> notified of config update.
> We can handle such ConfigurationObserver by sidelining it after configurable
> number of exceptions seen from the ConfigurationObserver.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
