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

Gary Helmling resolved HBASE-15573.
-----------------------------------
    Resolution: Invalid

This JIRA instance is used for tracking development issues and bugs.

Please send an email to the u...@hbase.apache.org mailing list to ask any 
questions.  Sounds like a configuration issue with your client application.

> Indefinite pause while trying to cleanup data
> ---------------------------------------------
>
>                 Key: HBASE-15573
>                 URL: https://issues.apache.org/jira/browse/HBASE-15573
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 1.1.2, 1.1.4
>            Reporter: Jorge Figueira
>            Priority: Blocker
>         Attachments: hbase-hadoop-master-HBASE.log, 
> hbase-hadoop-regionserver-HBASE.log, hbase-hadoop-zookeeper-HBASE.log
>
>
> Can't retrieve any information with hbase  rpc java client.
> With hbase shell its possible to scan data and retrieve all the information 
> normally.
> But with any rpc client region server don't retrieve data, all data come with 
> null values.
> Region Server log:
> DEBUG [RpcServer.reader=2,bindAddress=HBASE,port=16020] ipc.RpcServer: 
> RpcServer.listener,port=16020: DISCONNECTING client SERVER:37088 because read 
> count=-1
> DEBUG [RpcServer.reader=2,bindAddress=HBASE,port=16020] ipc.RpcServer: 
> RpcServer.listener,port=16020: DISCONNECTING client SERVER2:36997 because 
> read count=-1
> Master log:
> 2016-03-31 18:16:27,998 DEBUG [ProcedureExecutorTimeout] 
> procedure2.ProcedureExecutor$CompletedProcedureCleaner: No completed 
> procedures to cleanup.
> 2016-03-31 18:16:57,998 DEBUG [ProcedureExecutorTimeout] 
> procedure2.ProcedureExecutor$CompletedProcedureCleaner: No completed 
> procedures to cleanup.
> 2016-03-31 18:17:27,998 DEBUG [ProcedureExecutorTimeout] 
> procedure2.ProcedureExecutor$CompletedProcedureCleaner: No completed 
> procedures to cleanup



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

Reply via email to