Member since
07-30-2020
219
Posts
45
Kudos Received
60
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
468 | 11-20-2024 11:11 PM | |
499 | 09-26-2024 05:30 AM | |
1090 | 10-26-2023 08:08 AM | |
1866 | 09-13-2023 06:56 AM | |
2134 | 08-25-2023 06:04 AM |
05-17-2023
07:57 PM
Turn out there will be two icons if you need to "redeploy client conf" If the blue icon below appears, means you have to tick the "redeploy client conf" button to restart the whole cluster If only this orange icon appears, mean you don't need to do that
... View more
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: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
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-02-2023
04:43 AM
Exception in thread "main" org.apache.hadoop.ipc.RemoteException(java.io.IOException): File /home/maria_dev/read_write_hdfs_example.txt could only be replicated to 0 nodes instead of minReplication (=1). There are 1 datanode(s) running and 1 node(s) are excluded in this operation. This is the exception from the client side. so it is clearly ignoring the datanode because of some issue. @rki_
... View more
05-01-2023
04:23 AM
hello, i am new here from india, here to share some thoughts with you all
... View more
04-18-2023
10:35 AM
Hello @rki_ , as we stil have some clusters running with HDP 2.6.5 (HDP 2.6.5.363-1)for some months before moving to CDP, does exist workarounds to mitigate this CVE ? Thanks in advance for your answer.
... View more
04-06-2023
02:15 PM
@BrianChan You will need to manually perform the checkpoint on the faulty node. If the standby NameNode is faulty for a long time, generated edit log will accumulate. In this case, this will cause the HDFS or active NN to take a long time to restart and could even fail to restart because if the HDFS or active NameNode is restarted, the active NameNode reads a large amount of unmerged editlog. Is your NN setup active/standby? Fr the below steps you could as well use CM UI to perfom the tasks Quickest solution 1 I have had occasions when a simple rolling restart of the Zk's would resolve that biut I see the checkpoint lag goes to > 2 days Solution 2 Check the most up to date on both NN by comparing the dates of files in the directory. $ ls -lrt /dfs/nn/current/ On the Active NN with the latest editlogs as hdfs user $ hdfs dfsadmin -safemode enter $ hdfs dfsadmin -saveNamespace Check whether the latest generated fsimage timestamp is the current time. If yes, the combination is executed correctly and is complete. $ hdfs dfsadmin -safemode leave Before restarting the HDFS or active NameNode, perform a checkpoint manually to merge the metadata of the active NameNode. The restart the standby the newly generated files should now automatically be shipped and synced this could take a while < 5 minutes and your NN should all be green
... View more
04-03-2023
09:44 PM
Hello @RammiSE Your Post is being replied a bit late, yet I am posting a response anyways. Assuming your Team has resolved the Issue, Appreciate your Team sharing the details in the Post for wider audience. For HMaster to be Initialised, "hbase:meta" & "hbase:namespace" Table Region needs to be Online. In your previous thread, the HMaster is reporting "hbase:meta" isn't Online [1]. As such, Use the HBCK2 JAR to assign the "hbase:meta" Region "1588230740" first & review (Via HBase UI) whether Regions are being assigned successfully. It's feasible the "hbase:namespace" Table Region would also reporting similar tracing, in which case your Team needs to use HBCK2 JAR to assign the "hbase:namespace" Region. Restarting HMaster after manually performing HBCK2 Assign isn't required always, yet the same won't harm as well. Regards, Smarak [1] 2023-01-23 16:05:34,990 WARN [master/ctrlsu-hbaseMS:16000:becomeActiveMaster] master.HMaster: hbase:meta,,1.1588230740 is NOT online; state={1588230740 state=OPEN, ts=1674468867063, server=hadoop-datanode2,16020,1674362337687}; ServerCrashProcedures=true. Master startup cannot progress, in holding-pattern until region onlined
... View more
03-29-2023
03:18 AM
Hello Jero, Can you please let me know where you saw the parameters and how did you handle it ?
... View more