[
https://issues.apache.org/jira/browse/HBASE-18212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16056208#comment-16056208
]
Hudson commented on HBASE-18212:
--------------------------------
SUCCESS: Integrated in Jenkins build HBase-1.1-JDK7 #1883 (See
[https://builds.apache.org/job/HBase-1.1-JDK7/1883/])
HBASE-18212 reduce log level for unbuffer warning. (busbey: rev
b5a08a89dc9e81d5ad60e46c1c7259afaba6e4ad)
* (edit)
hbase-server/src/main/java/org/apache/hadoop/hbase/io/FSDataInputStreamWrapper.java
> 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
> Components: Operability
> Affects Versions: 2.0.0, 1.4.0
> Reporter: Umesh Agashe
> Assignee: Ashish Singhi
> Priority: Minor
> Fix For: 3.0.0, 1.4.0, 1.3.2, 1.2.7, 2.0.0-alpha-1, 1.1.12
>
> 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)
