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

Gavin updated HBASE-19025:
--------------------------
    Comment: was deleted

(was: A comment with security level 'jira-users' was removed.)

> Hbase MasterProcWALs getting pile up
> ------------------------------------
>
>                 Key: HBASE-19025
>                 URL: https://issues.apache.org/jira/browse/HBASE-19025
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 1.2.6
>            Reporter: Irfan 
>            Priority: Major
>
> MasterProcWALs getting pile up and getting below error in Hmaster log
> 2017-10-17 03:34:42,141 INFO  [ip-176-0-0-44:16000.activeMasterManager] 
> hdfs.DFSClient: Successfully connected to /176.0.0.29:50010 for 
> BP-1665161556-176.0.
> 0.44-1498805562805:blk_1073773522_32746
> 2017-10-17 03:34:42,182 INFO  [ip-176-0-0-44:16000.activeMasterManager] 
> util.FSHDFSUtils: Recover lease on dfs file 
> hdfs://192.168.168.1:9000/hbase2/MasterProcWALs/state-00000000000000005592.log
> 2017-10-17 03:34:42,182 INFO  [ip-176-0-0-44:16000.activeMasterManager] 
> util.FSHDFSUtils: Recovered lease, attempt=0 on 
> file=hdfs://ec2-34-195-113-113.compu
> te-1.amazonaws.com:9000/hbase2/MasterProcWALs/state-00000000000000005592.log 
> after 0ms
> 2017-10-17 03:34:42,184 WARN  [ip-176-0-0-44:16000.activeMasterManager] 
> hdfs.BlockReaderFactory: I/O error constructing remote block reader.
> java.io.IOException: Got error, status message opReadBlock 
> BP-1665161556-176.0.0.44-1498805562805:blk_1073773523_32747 received 
> exception java.io.FileNotFou
> ndException: 
> /data/datanode/data/current/BP-1665161556-176.0.0.44-1498805562805/current/finalized/subdir0/subdir123/blk_1073773523_32747.meta
>  (Too many open
>  files), for OP_READ_BLOCK, self=/176.0.0.44:59340, remote=/176.0.0.44:50010, 
> for file /hbase2/MasterProcWALs/state-00000000000000005592.log, for pool BP-16
> 65161556-176.0.0.44-1498805562805 block 1073773523_32747



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to