[
https://issues.apache.org/jira/browse/HBASE-10147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13859314#comment-13859314
]
takeshi.miao commented on HBASE-10147:
--------------------------------------
hi [~gustavoanatoly],
I just refresh my memory to call out there is a simple way to deal with the
public _Sink_ API change is...
to add _deprecate_ on this one obsolete methods in it. for example...
{code}
public interface Sink {
public void publishReadFailure(HRegionInfo region, Exception e);
public void publishReadFailure(HRegionInfo region, HColumnDescriptor column,
Exception e);
@deprecate // this method will removed in the future release
public void publishReadTiming(HRegionInfo region, HColumnDescriptor column,
long msTime);
public void publishInfo(HRegionInfo region, ServerName serverName);
public void publishInfoTimeout(HRegionInfo region, ServerName serverName);
}
{code}
> Canary additions
> ----------------
>
> Key: HBASE-10147
> URL: https://issues.apache.org/jira/browse/HBASE-10147
> Project: HBase
> Issue Type: Improvement
> Reporter: stack
> Assignee: Gustavo Anatoly
> Attachments: HBASE-10147-v2.patch, HBASE-10147.patch,
> HBASE-10147.patch, HBASE-10147.patch, HBASE-10147.patch
>
>
> I've been using the canary to quickly identify the dodgy machine in my
> cluster. It is useful for this. What would make it better would be:
> + Rather than saying how long it took to get a region after you have gotten
> the region, it'd be sweet to log BEFORE you went to get the region the
> regionname and the server it is on. I ask for this because as is, I have to
> wait for the canary to timeout which can be a while.
> + Second ask is that when I pass the -t, that when it fails, it says what it
> failed against -- what region and hopefully what server location (might be
> hard).
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
