Member since
09-06-2016
108
Posts
36
Kudos Received
11
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
2520 | 05-11-2017 07:41 PM | |
1185 | 05-06-2017 07:36 AM | |
6616 | 05-05-2017 07:00 PM | |
2316 | 05-05-2017 06:52 PM | |
6354 | 05-02-2017 03:56 PM |
02-06-2017
02:01 PM
Nice workaround @kkawamura!
... View more
02-05-2017
07:40 PM
1 Kudo
Can you create hyperlinks to a process group? I would like to create a hyperlink that will directly open the NIFI UI with the contents of the process group.
... View more
Labels:
- Labels:
-
Apache NiFi
12-29-2016
01:44 PM
`atlas-application.properties` referred to a `rangertagsync.service.keytab` that wasn't generated for that host. Regenerating the Kerberos keytabs from Ambari fixed it. Thx!
... View more
12-28-2016
02:19 PM
2 Kudos
Hi, Tags that I create in Atlas, are not showing up in Ranger. Tagsync service is running, however I notice the following Warning in the tagsync log: 28 Dec 2016 14:13:47 WARN ClientUtils$ [ranger_entities_consumer_wbekkerdv2-1482932174435-afd1c862-leader-finder-thread] - 89 Fetching topic metadata with correlation id 10939 for topics [Set(ATLAS_ENTITIES)] from broker [BrokerEndPoint(1001,wbekkerdv0.field.hortonworks.com,6667)] failed
java.nio.channels.ClosedChannelException
at kafka.network.BlockingChannel.send(BlockingChannel.scala:122)
at kafka.producer.SyncProducer.liftedTree1$1(SyncProducer.scala:82)
at kafka.producer.SyncProducer.kafka$producer$SyncProducer$doSend(SyncProducer.scala:81)
at kafka.producer.SyncProducer.send(SyncProducer.scala:126)
at kafka.client.ClientUtils$.fetchTopicMetadata(ClientUtils.scala:59)
at kafka.client.ClientUtils$.fetchTopicMetadata(ClientUtils.scala:96)
at kafka.consumer.ConsumerFetcherManager$LeaderFinderThread.doWork(ConsumerFetcherManager.scala:67)
at kafka.utils.ShutdownableThread.run(ShutdownableThread.scala:63) Any pointers?
... View more
Labels:
- Labels:
-
Apache Atlas
-
Apache Ranger
12-20-2016
03:31 PM
1 Kudo
Incompatible clusterIDs in/hadoop/hdfs/data: namenode clusterID = CID-35394708-aa35-4f25-b43b-0072da288d03; datanode clusterID = CID-d723cf5b-ba4a-43d3-afe1-781149930f3e ClusterID's need to be the same. This can happen after a reformat of your namenode. You can fix by a format, but you will loose all data `hdfs namenode -format`. Alternatively copy and replace the cluster ID in the version file, explained here: http://www.dedunu.info/2015/05/how-to-fix-incompatible-clusterids-in.html
... View more
12-20-2016
03:09 PM
1 Kudo
Hi Abhishek, Seems Ambari can't connect to the HBASE Region Server. Sometimes a (re)start of the service fixes this. If not, anything in the hbase region server log?
... View more
12-20-2016
03:06 PM
What does `hadoop dfsadmin -report` show?
... View more
12-20-2016
02:58 PM
HI Prakash, Error code 403 is normally a Status Forbidden msg. Any specific error message in the log of the datanode? It could be a DNS issue
... View more
12-20-2016
02:35 PM
No restrictions that I'm aware of, but make sure you give it enough RAM.
... View more
12-20-2016
02:16 PM
Hi Isa, Azure HDInsight is powered by HDP. Version of HDP 2.5 is available. Additionally, at the bottom of this community article you can find scripts (see option 2 ) to install HDP 2.5 on any cloud
... View more
- « Previous
- Next »