Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 10 Feb 2016 14:58:18 +0000 (UTC)
From: "Hudson (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12936954.1454652262000.16160.1455116298176@Atlassian.JIRA>
In-Reply-To: <JIRA.12936954.1454652262000@Atlassian.JIRA>
References: <JIRA.12936954.1454652262000@Atlassian.JIRA>
 <JIRA.12936954.1454652262684@arcas>
Subject: [jira] [Commented] (HBASE-15216) Canary does not accept config
 params from command line
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hudson commented on HBASE-15216:
--------------------------------

SUCCESS: Integrated in HBase-1.3-IT #490 (See [https://builds.apache.org/job/HBase-1.3-IT/490/])
HBASE-15216 Canary does not accept config params from command line (apurtell: rev 7a718cce71260016cd48801e69dae64857cad04f)
* hbase-server/src/main/java/org/apache/hadoop/hbase/tool/Canary.java
* src/main/asciidoc/_chapters/ops_mgt.adoc


> Canary does not accept config params from command line
> ------------------------------------------------------
>
>                 Key: HBASE-15216
>                 URL: https://issues.apache.org/jira/browse/HBASE-15216
>             Project: HBase
>          Issue Type: Bug
>          Components: canary
>    Affects Versions: 0.98.16
>            Reporter: Vishal Khandelwal
>            Assignee: Vishal Khandelwal
>             Fix For: 2.0.0, 1.3.0, 1.2.1, 0.98.18
>
>         Attachments: HBASE-15216.v1.patch, HBASE-15216.v2.patch
>
>
> At present there are few configs which needs to be present in  hbase-site or default xml for it to work. following are the list.
> hbase.canary.threads.num
> hbase.canary.sink.class
> hbase.client.keytab.file
> hbase.client.kerberos.principal
> Execution in secure expects keytab and princ to be present 
> {noformat}
> 2016-02-05 05:58:44,024 ERROR [main] hbase.AuthUtil - Error while trying to perform the initial login: Running in secure mode, but config doesn't have a keytab
> java.io.IOException: Running in secure mode, but config doesn't have a keytab
> 	at org.apache.hadoop.security.SecurityUtil.login(SecurityUtil.java:236)
> 	at org.apache.hadoop.hbase.security.User$SecureHadoopUser.login(User.java:392)
> 	at org.apache.hadoop.hbase.security.User.login(User.java:259)
> 	at org.apache.hadoop.hbase.security.UserProvider.login(UserProvider.java:116)
> 	at org.apache.hadoop.hbase.AuthUtil.launchAuthChore(AuthUtil.java:64)
> 	at org.apache.hadoop.hbase.tool.Canary.main(Canary.java:1146)
> Exception in thread "main" java.io.IOException: Running in secure mode, but config doesn't have a keytab
> 	at org.apache.hadoop.security.SecurityUtil.login(SecurityUtil.java:236)
> 	at org.apache.hadoop.hbase.security.User$SecureHadoopUser.login(User.java:392)
> 	at org.apache.hadoop.hbase.security.User.login(User.java:259)
> 	at org.apache.hadoop.hbase.security.UserProvider.login(UserProvider.java:116)
> 	at org.apache.hadoop.hbase.AuthUtil.launchAuthChore(AuthUtil.java:64)
> 	at org.apache.hadoop.hbase.tool.Canary.main(Canary.java:1146)
> {noformat}
> {code}
> public static void main(String[] args) throws Exception {
>     final Configuration conf = HBaseConfiguration.create();
>     AuthUtil.launchAuthChore(conf);
>     int numThreads = conf.getInt("hbase.canary.threads.num", MAX_THREADS_NUM);
>     ExecutorService executor = new ScheduledThreadPoolExecutor(numThreads);
>     Class<? extends Sink> sinkClass =
>         conf.getClass("hbase.canary.sink.class", StdOutSink.class, Sink.class);
>     Sink sink = ReflectionUtils.newInstance(sinkClass);
>     int exitCode = ToolRunner.run(conf, new Canary(executor, sink), args);
>     executor.shutdown();
>     System.exit(exitCode);
>   }
> {code}
> In main class these params should be parsed and updated. else for any change to these value hbase-stie.xml needs to be updated 


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)