You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Ashish Singhi (JIRA)" <ji...@apache.org> on 2017/06/16 05:19:00 UTC
[jira] [Updated] (HBASE-18212) In Standalone mode with local
filesystem HBase logs Warning message:Failed to invoke 'unbuffer' method in
class class org.apache.hadoop.fs.FSDataInputStream
[ https://issues.apache.org/jira/browse/HBASE-18212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ashish Singhi updated HBASE-18212:
----------------------------------
Attachment: HBASE-18212.patch
Attached patch, moving log level from warn to trace.
> In Standalone mode with local filesystem HBase logs Warning message:Failed to invoke 'unbuffer' method in class class org.apache.hadoop.fs.FSDataInputStream
> ------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-18212
> URL: https://issues.apache.org/jira/browse/HBASE-18212
> Project: HBase
> Issue Type: Bug
> Affects Versions: 2.0.0
> Reporter: Umesh Agashe
> Attachments: HBASE-18212.patch
>
>
> New users may get nervous after seeing following warning level log messages (considering new users will most likely run HBase in Standalone mode first):
> {code}
> WARN [MemStoreFlusher.1] io.FSDataInputStreamWrapper: Failed to invoke 'unbuffer' method in class class org.apache.hadoop.fs.FSDataInputStream . So there may be a TCP socket connection left open in CLOSE_WAIT state.
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)