Member since
11-17-2021
1158
Posts
260
Kudos Received
30
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 275 | 04-23-2026 02:02 PM | |
| 754 | 03-17-2026 05:26 PM | |
| 5739 | 11-05-2025 10:13 AM | |
| 986 | 10-16-2025 02:45 PM | |
| 1698 | 10-06-2025 01:01 PM |
04-09-2024
05:23 AM
Hi Matt, we configured 24GB as xms and xmx parameters. For now we have a normal use of memory without OOM errors. Thank you, Fortunato
... View more
04-08-2024
08:43 AM
@darkcoffeelake Has the reply helped resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future. Thanks.
... View more
04-04-2024
04:23 AM
1 Kudo
Good Morning -- any takers on helping answer this question? I would be super appreciative.
... View more
04-03-2024
01:09 AM
@rizalt I had a same bug when used ODP stack to deploy Ambari. After debug, I found code in ambari-agent bug when runtime to try start Hive Server2. Problem: This below codes output {out} parameter to handle hdfs path, but this code returned not valid hdfs URI 163 metatool_cmd = format("hive --config {conf_dir} --service metatool")
164 cmd = as_user(format("{metatool_cmd} -listFSRoot", env={'PATH': execution_path}), params.hive_user) \
165 + format(" 2>/dev/null | grep hdfs:// | cut -f1,2,3 -d '/' | grep -v '{fs_root}' | head -1")
166 code, out = shell.call(cmd) 2024-04-03 07:40:48,317 - call['ambari-sudo.sh su hive -l -s /bin/bash -c 'hive --config /usr/odp/current/hive-server2/conf/ --service metatool -listFSRoot' 2>/dev/null | grep hdfs:// | cut -f1,2,3 -d '/' | grep -v 'hdfs://vm-ambari.internal.cloudapp.net:8020' | head -1'] {}
2024-04-03 07:40:58,721 - call returned (0, '07:40:53.268 [main] DEBUG org.apache.hadoop.fs.FileSystem - hdfs:// = class org.apache.hadoop.hdfs.DistributedFileSystem from ') To fix: Step 1: edit row 170 in file "/var/lib/ambari-agent/cache/stacks/ODP/1.0/services/HIVE/package/scripts/hive_service.py" as below: I hard code old_path to valid URI, this help by pass updateLocation config # cmd = format("{metatool_cmd} -updateLocation {fs_root} {out}")
cmd = format("{metatool_cmd} -updateLocation {fs_root} hdfs://oldpath") You can see as below image: Step 2: Restart ambari agent sudo ambari-agent restart Step 3: Try to restart Hive server2 in Ambari Service started successful.
... View more
04-03-2024
12:11 AM
1 Kudo
Thanks for the reply. I have found the answer myself. The table name must be all in capital letters. No need to add schema or catalog name.
... View more
04-02-2024
07:26 PM
@Deepak_Unravel This is a regression on the python3 upgrade or more specifically something that worked by mistake in the past. Before py3 avro used to be more flexible with it's schema's and used to ignore any extra fields. If a value didn't exist in the schema it could have any value without invalidating the parcel. Now it expects data to be in exact format to the schema which is more accurate. During the py3 migration most fields were added but looks like we missed the conflicts field. A workaround for now can be to remove the conflicts field from the parcel since it doesn't have any conflicts right now. Please remove the conflicts entry in /opt/cloudera/parcels/UNRAVEL_SENSOR-1.0.4791002_cdh7.1_h3.1_s2.4/meta/parcel.json file on all the agents. Post conflicts entry removal you will able to distribute the parcel.
... View more
04-02-2024
09:34 AM
Yes the controller service was working before aks version upgrade
... View more
03-28-2024
07:43 AM
@TreantProtector Everything the user adds to the canvas including controller service and reporting tasks are auto-saved in the flow.json.gz. Each time a change is made the current flow.json.gz is archived and new flow.json.gz is generated. Within the flow.json.g are all components (processors, connections, controller services, reporting tasks, funnels, process groups, ports, parameters, etc.) and their configurations. Any configuration property that is "sensitive" (passwords) are going to be encrypted in the flow.json.gz file. So in order to load that flow.json.gz in another NiFi, you would need to know the nifi.sensitive.props.algorithm and nifi.sensitive.props.key used by the original NiFi which it came from. Encrypted Passwords in Flows If you don't have that info, the flow.json.gz can still be loaded on another NiFi after manually editing the file to remove all the "enc{...}" values. Once flow.json.gz loads, an authorized user would need to re-enter all passwords in all components where it is needed via the NiFi UI. Please help our community grow. If you found any of the suggestions/solutions provided helped you with solving your issue or answering your question, please take a moment to login and click "Accept as Solution" on one or more of them that helped. Thank you, Matt
... View more
03-27-2024
10:38 AM
@luisCookie Welcome to the Cloudera Community! To help you get the best possible solution, I have tagged our NiFi experts @MattWho @steven-matison who may be able to assist you further. Please keep us updated on your post, and we hope you find a satisfactory solution to your query.
... View more
03-26-2024
08:24 AM
The error message was related to a date field being used in a Parameter. I set up a Parameter to update to the newest date when the workbook opened. The date addition caused an issue with the refresh.
... View more