You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "David A. Wynne (JIRA)" <ji...@apache.org> on 2016/04/05 23:46:25 UTC
[jira] [Updated] (NIFI-1735) Confusing messages in app log when DNS
issues occur on a system with a NCM
[ https://issues.apache.org/jira/browse/NIFI-1735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David A. Wynne updated NIFI-1735:
---------------------------------
Description:
When a system running with a NCM instance of NiFi has DNS issues, the logging is confusing to the user and leads the user to believe there is a firewall issue.
INFO [Process Pending Heartbeats] o.a.n.c.manager.impl.WebClusterManager Node Event: [id=xxx, apiAddress=hostname, apiPort=port, socketAddress=hostname, socketPort=port] -- 'Firewall blocked received heartbeat. Issuing disconnection request.'
INFO [Process Pending Heartbeats] o.a.n.c.manager.impl.WebClusterManager Node Event: [id=xxx, apiAddress=hostname, apiPort=port, socketAddress=hostname, socketPort=port] -- 'Disconnection requested due to Blocked By Firewall'
ERROR [Process Pending Heartbeats] o.a.n.c.manager.impl.WebClusterManager Failed to process heartbeat from hostname:port due to org.apache.nifi.cluster.protocol.ProtocolException: Failed to create socket due to: java.net.UnknownHostException: hostname
was:
When a system running with a NCM instance of NiFi has DNS issues, the logging is confusing to the user and leads to believe there is a firewall issue.
INFO [Process Pending Heartbeats] o.a.n.c.manager.impl.WebClusterManager Node Event: [id=xxx, apiAddress=hostname, apiPort=port, socketAddress=hostname, socketPort=port] -- 'Firewall blocked received heartbeat. Issuing disconnection request.'
INFO [Process Pending Heartbeats] o.a.n.c.manager.impl.WebClusterManager Node Event: [id=xxx, apiAddress=hostname, apiPort=port, socketAddress=hostname, socketPort=port] -- 'Disconnection requested due to Blocked By Firewall'
ERROR [Process Pending Heartbeats] o.a.n.c.manager.impl.WebClusterManager Failed to process heartbeat from hostname:port due to org.apache.nifi.cluster.protocol.ProtocolException: Failed to create socket due to: java.net.UnknownHostException: hostname
> Confusing messages in app log when DNS issues occur on a system with a NCM
> --------------------------------------------------------------------------
>
> Key: NIFI-1735
> URL: https://issues.apache.org/jira/browse/NIFI-1735
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: David A. Wynne
> Priority: Minor
>
> When a system running with a NCM instance of NiFi has DNS issues, the logging is confusing to the user and leads the user to believe there is a firewall issue.
> INFO [Process Pending Heartbeats] o.a.n.c.manager.impl.WebClusterManager Node Event: [id=xxx, apiAddress=hostname, apiPort=port, socketAddress=hostname, socketPort=port] -- 'Firewall blocked received heartbeat. Issuing disconnection request.'
> INFO [Process Pending Heartbeats] o.a.n.c.manager.impl.WebClusterManager Node Event: [id=xxx, apiAddress=hostname, apiPort=port, socketAddress=hostname, socketPort=port] -- 'Disconnection requested due to Blocked By Firewall'
> ERROR [Process Pending Heartbeats] o.a.n.c.manager.impl.WebClusterManager Failed to process heartbeat from hostname:port due to org.apache.nifi.cluster.protocol.ProtocolException: Failed to create socket due to: java.net.UnknownHostException: hostname
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)