[jira] [Issue Comment Deleted] (HBASE-18762) Canary sink type cast error

["Gavin (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HBASE-18762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gavin updated HBASE-18762:
--------------------------
    Comment: was deleted

(was: A comment with security level 'jira-users' was removed.)

> Canary sink type cast error
> ---------------------------
>
>                 Key: HBASE-18762
>                 URL: https://issues.apache.org/jira/browse/HBASE-18762
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Chinmay Kulkarni
>            Assignee: Chinmay Kulkarni
>            Priority: Major
>             Fix For: 1.4.0, 2.0.0
>
>         Attachments: HBASE-18762.001.patch, HBASE-18830-addendum.patch
>
>
>  When running the main method of Canary.java, we see the following error:
> Exception in thread "main" java.lang.ClassCastException: org.apache.hadoop.hbase.tool.Canary$RegionServerStdOutSink cannot be cast to org.apache.hadoop.hbase.tool.Canary$RegionStdOutSink
> 	at org.apache.hadoop.hbase.tool.Canary.newMonitor(Canary.java:911)
> 	at org.apache.hadoop.hbase.tool.Canary.run(Canary.java:796)
> 	at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
> 	at org.apache.hadoop.hbase.tool.Canary.main(Canary.java:1571)
> This happens because we typecast the sink depending on the mode (zookeeper mode/region server mode) that Canary is configured in. In case no mode is specified, we typecast the sink into _RegionStdOutSink_. In general, it is possible to provide inconsistent mode and sink types while running Canary. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)