stack created HBASE-9001:
----------------------------

             Summary: TestThriftServerCmdLine.testRunThriftServer[0] failed
                 Key: HBASE-9001
                 URL: https://issues.apache.org/jira/browse/HBASE-9001
             Project: HBase
          Issue Type: Bug
          Components: test
            Reporter: stack
             Fix For: 0.95.2


https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/624/testReport/junit/org.apache.hadoop.hbase.thrift/TestThriftServerCmdLine/testRunThriftServer_0_/

It seems stuck here:

{code}
2013-07-19 03:52:03,158 INFO  [Thread-131] thrift.TestThriftServerCmdLine(132): 
Starting HBase Thrift server with command line: -hsha -port 56708 start
2013-07-19 03:52:03,174 INFO  [ThriftServer-cmdline] 
thrift.ThriftServerRunner$ImplType(208): Using thrift server type hsha
2013-07-19 03:52:03,205 WARN  [ThriftServer-cmdline] conf.Configuration(817): 
fs.default.name is deprecated. Instead, use fs.defaultFS
2013-07-19 03:52:03,206 WARN  [ThriftServer-cmdline] conf.Configuration(817): 
mapreduce.job.counters.limit is deprecated. Instead, use 
mapreduce.job.counters.max
2013-07-19 03:52:03,207 WARN  [ThriftServer-cmdline] conf.Configuration(817): 
io.bytes.per.checksum is deprecated. Instead, use dfs.bytes-per-checksum
2013-07-19 03:54:03,156 INFO  [pool-1-thread-1] hbase.ResourceChecker(171): 
after: thrift.TestThriftServerCmdLine#testRunThriftServer[0] Thread=146 (was 
155), OpenFileDescriptor=295 (was 311), MaxFileDescriptor=4096 (was 4096), 
SystemLoadAverage=293 (was 240) - SystemLoadAverage LEAK? -, ProcessCount=145 
(was 143) - ProcessCount LEAK? -, AvailableMemoryMB=779 (was 1263), 
ConnectionCount=4 (was 4)
2013-07-19 03:54:03,157 DEBUG [pool-1-thread-1] 
thrift.TestThriftServerCmdLine(107): implType=-hsha, specifyFramed=false, 
specifyBindIP=false, specifyCompact=true
{code}

My guess is that we didn't get scheduled because load was almost 300 on this 
box at the time?

Let me up the timeout of two minutes.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to