[
https://issues.apache.org/jira/browse/NIFI-683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14597517#comment-14597517
]
Matt Gilman commented on NIFI-683:
----------------------------------
[~markap14] You say that the NCM does not recognize the node's hostname, gets a
socket read timeout, and returns a 409 to the UI. What REST endpoint was being
invoked? Did the 409 response contain any relevant message about the current
state?
I think I understand the underlying issue on the UI side, with regards to the
splash screen situation, but I don't follow the first part of the description.
Was it during the connection handshake that it was unable to resolve the
hostname? Processing heartbeats? Or during a user request replication?
> When connecting to cluster, splash screen remains indefinitely if error sent
> back
> ---------------------------------------------------------------------------------
>
> Key: NIFI-683
> URL: https://issues.apache.org/jira/browse/NIFI-683
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core UI
> Reporter: Mark Payne
> Fix For: 0.2.0
>
>
> I created a cluster with the NCM running on my host and a single node running
> in a VM. In the VM, I configured the node to report its fully qualified
> hostname. The Host running the NCM, however, does not recognize the fully
> qualified hostname of the VM and gets a Socket Read timeout. This is returned
> to the UI as a 409: Conflict.
> The UI ignores this, leaving the splash screen. The UI should instead report
> back an error, as it does if there are no connected nodes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
