Member since
02-16-2016
176
Posts
197
Kudos Received
17
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
3073 | 11-18-2016 08:48 PM | |
5472 | 08-23-2016 04:13 PM | |
1501 | 03-26-2016 12:01 PM | |
1432 | 03-15-2016 12:12 AM | |
15353 | 03-14-2016 10:54 PM |
02-01-2018
03:54 PM
Thank You. You pointed me in right direction.
... View more
01-31-2018
03:22 PM
I recently upgraded cluster to HDP 2.6.4.0 from 2.5.3.0 and Ambari to 2.5.1.0. After cluster upgrade, Grafana dashboards for System - Servers show "No datapoints." Dropdown for cluster in dashboards doesn't have correct value for cluster. Please see attached screenshot.screen-shot-2018-01-31-at-100524-am.png How can I fix this ?
... View more
Labels:
- Labels:
-
Apache Ambari
08-10-2017
01:27 PM
In HDP 2.6.0.3 ( ATLAs version 0.8.0 ), cluster is generating log files of approx 1 GB/day. ATLAS log settings are set to INFO level. Is there any way to reduce volume of entries in log files ?
... View more
Labels:
- Labels:
-
Apache Atlas
06-09-2017
06:44 PM
1 Kudo
@Saikrishna Tarapareddy @Sushanth Sowmyan One way to handle this is to use another JSONSerde that has support for skipping malformed records. I had exactly similar situation and worked around it by using org.openx.data.jsonserde.JsonSerDe. This SerDe has support for handling malformed JSON. You need to create table with following TBLPROPERTIES. 'ignore.malformed.json'='true'
and ensure this Serde is available to Hive by using ADD JAR command before using this Serde or modifying your Hive JAR path.
... View more
11-26-2016
03:20 PM
2 Kudos
@Randy Gelhausen Under conf there is a templates directory where all the templates are located.
... View more
11-22-2016
04:43 PM
@spdvnz @Andrew Grande By input/output being in root Top level processing group what Andrew means is that it shouldn't be part of a process group. If you look at bottom left hand corner, your input port should be under NiFi Flow, not under a process group. Also, site to site property in B should have nifi.remote.input.host=FQDN of B. instance A of NiFi will initially talk to instance B of Nifi on public port ( how you access instance B UI ). Then instance B will reply with information available in nifi.remote.* properties. instance A, will then communicate with instance B on host and port specified in remote properties. Can you please post a screenshot of your setup?
... View more
11-22-2016
04:27 PM
Thanks Matt for your help. I finally resolved this issue by referring to internal ip of hosts.
... View more
11-18-2016
09:23 PM
Thanks Matt. Source Nifi instance is not able to talk to target cluster because it it trying to access public ip that it can't access. I guess it is more of EC2 question, how can I get my node to communicate using public ip. Only one of the node is public facing. Other node is not public facing and doesn't have a public facing FQDN.
... View more
11-18-2016
09:06 PM
HDF 2.0. Source nifi is also running on same instance. Looking at logs, it looks like nifi is trying to communicate on public ip address, but it can't communicate. How do I specify private ip for communication.
... View more
11-18-2016
08:56 PM
I have a Nifi cluster setup with 2 nodes in AWS EC2. One Nifi node has a public ip and 2nd one is on vpc. My cluster is up and running and I can see both my nodes from nifi public instance. I want to add a remote process group pointing to same instance for load balancing. When I add a remote process group with same address as public server, it fails to communicate to node. I have left nifi.remote.input.host as blank. Should I populate it with public ip address of server or private ip address of server ? Thanks for any help.
... View more
Labels:
- Labels:
-
Apache NiFi