Hi Geoffrey, Thanks for looking in this, HDP Version: 2.6.5 HDF Version: HDF-3.1.2.0-7 Ambari Version: 2.6.2.2 Actually am not interested in SAM and Schema registry as i dont need high availability for this.. I hope Nifi works with out SAM and Schema registry. [root@mn3 mohandv1]# ls /var/lib/ambari-server/resources/mpacks/ cache hdf-ambari-mpack-3.1.2.0-7 mpacks_replay.log Not sure about HTH.. Is it mandatory for the Nifi setup? What does HTH do? And do we need to enable the HDF local repository across all the nodes in the cluster? i have just enabled only in Ambari server host. ( in which am trying to install nifi ) Thanks, Vignesh Mohandass ... View more

Hi Roberto, So you mean you were not able to install Nifi through Ambari? When you install manually, which mean you managing it separately? example, start stop in command line and not through ambari? ... View more

I have opened a new thread on this issue, https://community.hortonworks.com/questions/236968/how-to-setup-hdf-nifi-on-existing-hdp-cluster.html Kindly help.. ... View more

Hi Roberto/All, Am stuck at the same.. I have installed Mpack on the ambari server host I have configured a local repo and enabled it on one master server where am installing nifi and nifi registry ( same as ambari server host) I have not registered it as a new component but added the nifi repo url to the existing HDP version. And if i do add service, all looks OK but the service is not getting installed. Any help please? Thanks, Vignesh ... View more

Hai,   Did you get any resolution for this ? Even am facing the same problem now.   Thanks ... View more

Hi Harsh,   I have the same problem in my cluster running CDH 5.7.2. Could you please guide me in this. What can be done to avoid this.   FAILOVER CONTROLER LOGS: ------------------------------------------   2016-10-12 12:36:57,428 WARN org.apache.hadoop.ha.HealthMonitor: Transport-level exception trying to monitor health of NameNode at namenode1:8022: java.net.SocketTimeoutException: 45000 millis timeout while waiting for channel to be ready for read. ch : java.nio.channels.SocketChannel[connected local=/x.x.x.x:54851 remote=namenode1:8022] Call From namenode1 to namenode1:8022 failed on socket timeout exception: java.net.SocketTimeoutException: 45000 millis timeout while waiting for channel to be ready for read. ch : java.nio.channels.SocketChannel[connected local=/x.x.x.x:54851 remote=namenode1:8022]; For more details see: http://wiki.apache.org/hadoop/SocketTimeout 2016-10-12 12:36:57,428 INFO org.apache.hadoop.ha.HealthMonitor: Entering state SERVICE_NOT_RESPONDING 2016-10-12 12:36:57,429 INFO org.apache.hadoop.ha.ZKFailoverController: Local service NameNode at namenode1:8022 entered state: SERVICE_NOT_RESPONDING 2016-10-12 12:37:17,453 WARN org.apache.hadoop.hdfs.tools.DFSZKFailoverController: Can't get local NN thread dump due to Read timed out 2016-10-12 12:37:17,453 INFO org.apache.hadoop.ha.ZKFailoverController: Quitting master election for NameNode at namenode1:8022 and marking that fencing is necessary 2016-10-12 12:37:17,453 INFO org.apache.hadoop.ha.ActiveStandbyElector: Yielding from election 2016-10-12 12:37:17,456 INFO org.apache.zookeeper.ZooKeeper: Session: 0x2572780883a39b5 closed 2016-10-12 12:37:17,456 WARN org.apache.hadoop.ha.ActiveStandbyElector: Ignoring stale result from old client with sessionId 0x2572780883a39b5 2016-10-12 12:37:17,456 INFO org.apache.zookeeper.ClientCnxn: EventThread shut down 2016-10-12 12:37:33,291 INFO org.apache.hadoop.ha.HealthMonitor: Entering state SERVICE_HEALTHY 2016-10-12 12:37:33,291 INFO org.apache.hadoop.ha.ZKFailoverController: Local service NameNode at namenode1:8022 entered state: SERVICE_HEALTHY 2016-10-12 12:37:33,295 INFO org.apache.zookeeper.ZooKeeper: Initiating client connection, connectString=namenode1:2181,namenode2:2181,resourcemanger1:2181 sessionTimeout=5000 watcher=org.apache.hadoop.ha.ActiveStandbyElector$WatcherWithClientRef@4d2b3d47 2016-10-12 12:37:33,303 INFO org.apache.zookeeper.ClientCnxn: Opening socket connection to server namenode2:2181. Will not attempt to authenticate using SASL (unknown error) 2016-10-12 12:37:33,303 INFO org.apache.zookeeper.ClientCnxn: Socket connection established, initiating session, client: /x.x.x.x:60657, server: namenode2:2181 2016-10-12 12:37:33,304 INFO org.apache.zookeeper.ClientCnxn: Session establishment complete on server namenode2:2181, sessionid = 0x357278087a35a6b, negotiated timeout = 5000 2016-10-12 12:37:33,308 INFO org.apache.hadoop.ha.ActiveStandbyElector: Session connected. 2016-10-12 12:37:33,311 INFO org.apache.hadoop.ha.ZKFailoverController: ZK Election indicated that NameNode at namenode1:8022 should become standby 2016-10-12 12:37:33,595 INFO org.apache.hadoop.ha.ZKFailoverController: Successfully transitioned NameNode at namenode1:8022 to standby state ... View more