hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zhihua Deng (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-16212) Many Connections are created by wrong seeking pos on InputStream
Date Tue, 12 Jul 2016 11:59:20 GMT

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

Zhihua Deng updated HBASE-16212:
    Priority: Trivial  (was: Major)

> Many Connections are created by wrong seeking pos on InputStream
> ----------------------------------------------------------------
>                 Key: HBASE-16212
>                 URL: https://issues.apache.org/jira/browse/HBASE-16212
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 1.1.2
>            Reporter: Zhihua Deng
>            Priority: Trivial
> As described in https://issues.apache.org/jira/browse/HDFS-8659, the datanode is suffering
from logging the same repeatedly. Adding log to DFSInputStream, it outputs as follows:
> 2016-07-10 21:31:42,147 INFO  [B.defaultRpcServer.handler=22,queue=1,port=16020] hdfs.DFSClient:
DFSClient_NONMAPREDUCE_1984924661_1 seek DatanodeInfoWithStorage[,DS-086bc494-d862-470c-86e8-9cb7929985c6,DISK]
for BP-360285305- pos: 111506876, targetPos:
>  ...
> As the pos of this input stream is larger than targetPos(the pos trying to seek), A new
connection to the datanode will be created, the older one will be closed as a consequence.
When the wrong seeking ops are large, the datanode's block scanner info message is spamming
logs, as well as many connections to the same datanode will be created.

This message was sent by Atlassian JIRA

View raw message