You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Anoop Sam John (JIRA)" <ji...@apache.org> on 2017/06/15 11:39:02 UTC
[jira] [Comment Edited] (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:comment-tabpanel&focusedCommentId=16050367#comment-16050367 ]
Anoop Sam John edited comment on HBASE-18212 at 6/15/17 11:38 AM:
------------------------------------------------------------------
+1 on reducing the Log level .
was (Author: anoop.hbase):
+1 on reducing the scope.
> 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
>
> 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)