You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Ashish Singhi (JIRA)" <ji...@apache.org> on 2014/12/08 07:47:13 UTC

[jira] [Commented] (HBASE-12630) Provide capability for dropping malfunctioning ConfigurationObserver automatically

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

Ashish Singhi commented on HBASE-12630:
---------------------------------------

Hi [~tedyu]
bq. We can handle such ConfigurationObserver by sidelining it after configurable number of exceptions seen from the ConfigurationObserver.
By sidelining you mean deregister it from ConfigurationObserver ?

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