[
https://issues.apache.org/jira/browse/HBASE-12630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14238178#comment-14238178
]
Ted Yu commented on HBASE-12630:
--------------------------------
Looks like the hanging test was caused by the addition of the Map.
Can you expand the following data structure to include count of failed
notifications ?
{code}
private Set<ConfigurationObserver> configurationObservers =
Collections.newSetFromMap(new WeakHashMap<ConfigurationObserver,
Boolean>());
{code}
> 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.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)
