Member since
07-30-2020
219
Posts
46
Kudos Received
60
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 4887 | 11-20-2024 11:11 PM | |
| 2924 | 09-26-2024 05:30 AM | |
| 2459 | 10-26-2023 08:08 AM | |
| 4193 | 09-13-2023 06:56 AM | |
| 4503 | 08-25-2023 06:04 AM |
05-17-2023
09:00 AM
@JobBranwl This is Kerberos issue now and moreover with the usage of keyring for ticket cache which is not supported. You can refer to the below post to see if that helps. https://community.cloudera.com/t5/Support-Questions/Unable-to-access-Hadoop-CLI-after-enabling-Kerberos/m-p/305291
... View more
05-17-2023
08:27 AM
@JobBranwl can you try running the command from a node that has an HDFS gateway role assigned to it or from the Namenode host itself and verify.
... View more
05-17-2023
08:23 AM
Hi @stephen_obrien As discussed via Cloudera case, there is a performance bottleneck when connecting via knox ( tracked in internal jira ) than directly from phoenix-sqlline from the edge node. You can test the same when the runtime version 7.2.17 is released.
... View more
05-17-2023
08:18 AM
@quangbilly79 This depends on the change you are making. if you have made changes to the client configurations such as modifying connection properties, or updating authentication settings, selecting "Redeploy Client Configuration" can be beneficial. If you have made only service-level config changes, you can choose to avoid Redeploying the Client config so that only the specific services that received a change will be restarted.
... View more
05-17-2023
02:33 AM
Hi @Tonystark , The ERROR message doesn't reveal much info as to why the RM is failing to start. I would suggest looking into the RM logs to find the Root cause. https://issues.apache.org/jira/browse/HADOOP-16305
... View more
05-01-2023
02:49 AM
@iamlazycoder Have you tried putting the file with -Ddfs.replication=1 ?
... View more
04-28-2023
11:53 AM
@iamlazycoder As you have only a single Datanode, the blockplacement policy won't allow putting the second replica on the same Datanode. You can try to put the file with a single replica and check. hdfs dfs -Ddfs.replication=1 -put /path/to/local/file /path/to/hdfs/dir Or you can change the dfs.replication in hdfs-site.xml to 1 at a cluster level.
... View more
04-03-2023
10:51 PM
Hi @BrianChan Both the alerts are related. The checkpointing is done by the Standby Namenode and if it's not functioning properly, then the checkpoint process is not done and you will see those alerts. You can go through the logs of the Standby Namenode and check why the checkpoint thread is stopped. Maybe the Standby Namenode is down? So you may want to restart the Standby Namenode to fix this.
... View more
02-14-2023
01:53 AM
As of now and I believe in the future as well, Phoenix will be a packaged component. Afaik, License for Phoenix was needed in CDH but it is tied to Hbase in CDP onwards. Was your question answered? Please take some time to click on “Accept as Solution” below this post.
... View more
02-13-2023
10:16 AM
Hi @SagarCapG, Phoenix is still there in CDP 7.1.8 and as well as in Cloudera Operation Databases ( COD ) which uses CDP. https://blog.cloudera.com/getting-started-with-cloudera-data-platform-operational-database-cod/
... View more