[
https://issues.apache.org/jira/browse/HBASE-8466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13648879#comment-13648879
]
Hudson commented on HBASE-8466:
-------------------------------
Integrated in HBase-TRUNK #4096 (See
[https://builds.apache.org/job/HBase-TRUNK/4096/])
HBASE-8466 Netty messages in the logs (Revision 1478664)
Result = FAILURE
nkeywal :
Files :
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/ClusterStatusPublisher.java
> Netty messages in the logs
> --------------------------
>
> Key: HBASE-8466
> URL: https://issues.apache.org/jira/browse/HBASE-8466
> Project: HBase
> Issue Type: Bug
> Components: master
> Affects Versions: 0.98.0, 0.95.0
> Reporter: Nicolas Liochon
> Assignee: Nicolas Liochon
> Priority: Minor
> Fix For: 0.98.0, 0.95.1
>
> Attachments: 8466.v1.patch, 8466.v2.patch
>
>
> We've got this:
> {noformat}
> ATTENTION: The pipeline contains no upstream handlers; discarding: [id:
> 0x1f79354a] OPEN
> ATTENTION: The pipeline contains no upstream handlers; discarding: [id:
> 0x1f79354a] BOUND: 0.0.0.0/0.0.0.0:37250
> ATTENTION: The pipeline contains no upstream handlers; discarding: [id:
> 0x1f79354a, 0.0.0.0/0.0.0.0:37250 => /226.1.1.3:60100] CONNECTED:
> /226.1.1.3:60100
> ATTENTION: The pipeline contains no upstream handlers; discarding: [id:
> 0x1f79354a, 0.0.0.0/0.0.0.0:37250 => /226.1.1.3:60100] WRITTEN_AMOUNT: 129
> ATTENTION: The pipeline contains no upstream handlers; discarding: [id:
> 0x1f79354a, 0.0.0.0/0.0.0.0:37250 :> /226.1.1.3:60100] DISCONNECTED
> ATTENTION: The pipeline contains no upstream handlers; discarding: [id:
> 0x1f79354a, 0.0.0.0/0.0.0.0:37250 :> /226.1.1.3:60100] UNBOUND
> ATTENTION: The pipeline contains no upstream handlers; discarding: [id:
> 0x1f79354a, 0.0.0.0/0.0.0.0:37250 :> /226.1.1.3:60100] CLOSED
> {noformat}
> We can fix this by adding an upstream handler that discards the message
> without printing them.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
