hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-18762) Canary sink type cast error
Date Tue, 26 Sep 2017 08:25:00 GMT

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

Hudson commented on HBASE-18762:
--------------------------------

FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #3781 (See [https://builds.apache.org/job/HBase-Trunk_matrix/3781/])
HBASE-18762 Canary sink type cast error (apurtell: rev 176571a852f9f6afd8a0b77e3e0f187286e80264)
* (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/tool/Canary.java


> 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
>             Fix For: 2.0.0, 3.0.0, 1.4.0, 1.5.0
>
>         Attachments: HBASE-18762.001.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
(v6.4.14#64029)

Mime
View raw message