[
https://issues.apache.org/jira/browse/NIFI-2585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15736129#comment-15736129
]
ASF GitHub Bot commented on NIFI-2585:
--------------------------------------
Github user randerzander commented on the issue:
https://github.com/apache/nifi/pull/1307
This may be an artifact of Docker generating hostnames that don't parse
well.
Here's what I see in my testing:
monitor.dev_1 | 2016-12-09 19:41:34,127 INFO [Site-to-Site Worker
Thread-6] o.a.nifi.remote.SocketRemoteSiteListener Received connection from
techops_web-service.dev_1.techops_dev/172.18.0.5, User DN: null
monitor.dev_1 | 2016-12-09 19:41:34,127 ERROR [Site-to-Site Worker
Thread-6] o.a.nifi.remote.SocketRemoteSiteListener Handshake failed when
communicating with nifi://techops_web-service.dev_1.techops_dev:42626; closing
connection. Reason for failure: java.lang.IllegalStateException: Unable to get
host or port from peerUrlnifi://techops_web-service.dev_1.techops_dev:42626
> Add attributes to track where a flow file came from when receiving over
> site-to-site
> ------------------------------------------------------------------------------------
>
> Key: NIFI-2585
> URL: https://issues.apache.org/jira/browse/NIFI-2585
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Bryan Bende
> Assignee: Randy Gelhausen
> Priority: Minor
>
> With MiNiFi starting be used to send data to a central NiFi, it would be
> helpful if information about the sending host and port was added to each flow
> file received over site-to-site. Currently this information is available and
> used to generate the transit URI in the RECEIVE event, but this information
> isn't available to downstream processors that might want to make routing
> decisions.
> For reference:
> https://github.com/apache/nifi/blob/e23b2356172e128086585fe2c425523c3628d0e7/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-site-to-site/src/main/java/org/apache/nifi/remote/protocol/AbstractFlowFileServerProtocol.java#L452
> A possible approach might be to add two attributes to each flow file,
> something like "remote.host" and "remote.address" where remote.host has only
> the sending hostname, and remote.address has the sending host and port.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
