[
https://issues.apache.org/jira/browse/HBASE-12630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14239815#comment-14239815
]
stack commented on HBASE-12630:
-------------------------------
bq. As shown in description, this JIRA handles ConfigurationObserver(s) which
constantly produce exception when notified.
Description 'shows' nothing other than that you are probably harrassing
[~manukranthk] offline. Is this a problem? Has it been observed in the wild?
bq. Stack, I am not pretty sure why we are doing this way!
[~ashish singhi] You do good work. Suggest you pick clean issues that clearly
move the project forward. If you need input, just ask on dev list (Stuff
marked critical or major against 1.0 would be good in general. I am not sure
why this issue is marked major for 1.0... how often are folks deploying new
classes with ConfigurationObserver implementations?)
> 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)
