"queued": "0 / 0 bytes",
"events": [
{
"timestamp": "05/09/2017 17:44:17 GMT",
"category": "INFO",
"message": "Node Status changed from CONNECTING to CONNECTED&qu
No I just meant the original phantom node that seems to be in the cluster
even though I think the VM's been decommissioned.
On Fri, May 5, 2017 at 1:14 AM, Jeff wrote:
> Neil,
>
> Quick question... by "The nodes that are healthy are all able to ping
> each other", i
Neil,
Quick question... by "The nodes that are healthy are all able to ping each
other", is one of the nodes not able to ping the other nodes?
On Thu, May 4, 2017 at 11:23 AM Neil Derraugh <
neil.derra...@intellifylearning.com> wrote:
> Our three zookeepers are external. The nodes that are heal
Our three zookeepers are external. The nodes that are healthy are all able
to ping each other. nifi.properties follow (with minor mods around
hostnames/IPs).
# Core Properties #
nifi.version=1.1.2
nifi.flow.configuration.file=/mnt/mesos/sandbox/conf/flow.xml.gz
nifi.flow.configuration.archive.en
Can you provide some information on the configuration (nifi.properties) of
the nodes in your cluster? Can each node in your cluster ping all the
other nodes? Are you running embedded ZooKeeper, or an external one?
On Wed, May 3, 2017 at 8:11 PM Neil Derraugh <
neil.derra...@intellifylearning.com
I can't load the canvas right now on our cluster. I get this error from
one of the nodes nifi-app.logs
2017-05-03 23:40:30,207 WARN [Replicate Request Thread-2]
o.a.n.c.c.h.r.ThreadPoolRequestReplicator Failed to replicate request GET
/nifi-api/flow/current-user to 10.80.53.39:31212 due to {}
com
