incubator-bigtop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bruno Mahé (JIRA) <j...@apache.org>
Subject [jira] [Comment Edited] (BIGTOP-648) hbase-thrift cannot be started properly
Date Fri, 22 Jun 2012 22:33:43 GMT

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

Bruno Mahé edited comment on BIGTOP-648 at 6/22/12 10:32 PM:
-------------------------------------------------------------

This is not going to work at all.
Deployment/configuration management tools only use one argument (start/stop/status) and do
not expect any additional arguments. Forcing additional arguments will force people to implement
hacks and workaround for this non-standard behavior. 
Furthermore this is against the LSB. See http://refspecs.linuxbase.org/LSB_3.1.0/LSB-Core-generic/LSB-Core-generic/iniscrptact.html
{quote}Conforming applications which need to execute commands on changes to the system run
level (including boot and shutdown), may install one or more init scripts. Init scripts provided
by conforming applications shall accept a single argument which selects the action:

start	start the service
stop	stop the service
restart	stop and restart the service if the service is already running, otherwise start the
service
try-restart	restart the service if the service is already running
reload	cause the configuration of the service to be reloaded without actually stopping and
restarting the service
force-reload	cause the configuration to be reloaded if the service supports this, otherwise
restart the service if it is running
status	print the current status of the service{quote}


There is no reason to force people to pass additional arguments.
HBase should be fixed so that argument can be made a configuration option.
                
      was (Author: bmahe):
    This is not going to work at all.
Deployment/configuration management tools only use one argument (start/stop/status) and do
not expect any additional arguments. Forcing additional arguments will force people to implement
hacks and workaround for this non-standard behavior. 
Furthermore this is against the LSB. See http://refspecs.linuxbase.org/LSB_3.1.0/LSB-Core-generic/LSB-Core-generic/iniscrptact.html
{quote}Conforming applications which need to execute commands on changes to the system run
level (including boot and shutdown), may install one or more init scripts. Init scripts provided
by conforming applications shall accept a single argument which selects the action:

start	start the service
stop	stop the service
restart	stop and restart the service if the service is already running, otherwise start the
service
try-restart	restart the service if the service is already running
reload	cause the configuration of the service to be reloaded without actually stopping and
restarting the service
force-reload	cause the configuration to be reloaded if the service supports this, otherwise
restart the service if it is running
status	print the current status of the service{quote}


There is no reason to force people to pass additional arguments.
HBase should be fixed so that argument can be made a parameter.
                  
> hbase-thrift cannot be started properly
> ---------------------------------------
>
>                 Key: BIGTOP-648
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-648
>             Project: Bigtop
>          Issue Type: Bug
>          Components: Init scripts
>    Affects Versions: 0.4.0
>            Reporter: Johnny Zhang
>
> although hbase-master/regionserver/rest all started fine, fail to start hbase-thrift
(SLES)
> {noformat}
> # service hbase-thrift start
> Starting  (hbase-thrift):                                                           
                          done
> starting thrift, logging to /var/log/hbase/hbase-hbase-thrift-pkgtest-sles64-11.out
> # service hbase-thrift status
> thrift is not running                                                               
                          failed
> # cat /var/log/hbase/hbase-hbase-thrift-pkgtest-sles64-11.out
> Exception in thread "main" java.lang.AssertionError: Exactly one option out of [-hsha,
-nonblocking, -threadpool, -threadedselector] has to be specified
> 	at org.apache.hadoop.hbase.thrift.ThriftServerRunner$ImplType.setServerImpl(ThriftServerRunner.java:201)
> 	at org.apache.hadoop.hbase.thrift.ThriftServer.processOptions(ThriftServer.java:169)
> 	at org.apache.hadoop.hbase.thrift.ThriftServer.doMain(ThriftServer.java:85)
> 	at org.apache.hadoop.hbase.thrift.ThriftServer.main(ThriftServer.java:192)
> {noformat}
> tried to follow the message to add the option, doesn't work (Centos5)
> {noformat}
> # service hbase-thrift start -nonblocking
> starting thrift, logging to /var/log/hbase/hbase-hbase-thrift-pkgtest-centos64-5.mtv.cloudera.com.out
> Exception in thread "main" java.lang.AssertionError: Exactly one option out of [-hsha,
-nonblocking, -threadpool, -threadedselector] has to be specified
> 	at org.apache.hadoop.hbase.thrift.ThriftServerRunner$ImplType.setServerImpl(ThriftServerRunner.java:201)
> 	at org.apache.hadoop.hbase.thrift.ThriftServer.processOptions(ThriftServer.java:169)
> 	at org.apache.hadoop.hbase.thrift.ThriftServer.doMain(ThriftServer.java:85)
> 	at org.apache.hadoop.hbase.thrift.ThriftServer.main(ThriftServer.java:192)
> {noformat}
> tried a full restart also (SLES)
> {noformat}
> # service hbase-thrift --full-restart
> Stopping  (hbase-thrift):                                                           
                          done
> no thrift to stop because kill -0 of pid 9010 failed with status 1
> Starting  (hbase-thrift):                                                           
                          done
> starting thrift, logging to /var/log/hbase/hbase-hbase-thrift-pkgtest-sles64-11.out
> Exception in thread "main" 
> # service hbase-thrift status
> thrift is not running                                                               
                          failed
> {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message