About Juanes

Juanes · ‎04-04-2024

Good morning Community, i'm suffering of DNS resolution getting the following fatalistic view every time I access to CM: I'm reading a lot but not getting any robust conclussion of what is the test that concludes in "DNS resolution error". it checks "host's hostname and canonical name" but, what does it means? is it the hostname? the name in the /etc/hosts? In my case, having [root@master1 ~]# hostname master1 [root@master1 ~]# python -c "import socket; print socket.getfqdn(); print socket.gethostbyname(socket.getfqdn())" master1.domain.net 192.168.0.90 does it means the discrepancy between hostname and socket.getfqdn()? I can see how many people is getting this error but not a consistent response, could anyone give the solution here? for trying to understand this common issue? Many thanks in advance.

Juanes · ‎04-03-2024

Hello again, I finally managed to pass by using "custom Repository" and adding the apropriate one, but the issue that I was facing was about using the first option "Cloudera Repository (direct Internet Access)". this should be more automatic, or at least adding possible things to check, because it's not mentioned the allkeys.asc As i'm not using a web or local repo, i'm reaching directly the cloudera one. Many thanks anyway 🙂

Juanes · ‎04-03-2024

Hello, First of all, thanks for your time. then, i'm not creating a local repo, i'm using Cloudera repos with direct internet access, as I can see, the file is in the repo (in Cloudera) and this should be downloaded automatically I think...

Juanes · ‎04-03-2024

Hello Community, Installation is failing because of allkeys.asc not found... This is not mentioned in the installation proccess and not additional config required, why is this happening and how to fix it? why is this not mentioned in the documentation? I can see the file there, is that a bug? Thanks in advance

Juanes · ‎04-02-2024

Hello Community, I would like to rise a big inconsistency about requirements. Starting by the Cloudera Support Matrix that says: CDP Private Cloud Base7.1.8 > will need Cloudera Manager 7.7.1 and OS: RHEL8.4 will work. Now, regarding to NTP, based on teh OS: "In RHEL 8, the NTP protocol is implemented only by the chronyd daemon, provided by the chrony package. The ntp daemon is no longer available. If you used ntp on your RHEL 7 system, you might need to migrate to chrony" in the other hand: https://docs.cloudera.com/cdp-private-cloud-base/7.1.8/kudu-management/topics/kudu-server-management-limitations.html "Kudu releases have only been tested with NTP. Other time synchronization providers such as Chrony may not work." Could someone from Kudu team give some consistency here? RHEL8 not having ntpd anymore but mandatory for KUDU... Please help.

Juanes · ‎06-21-2023

Hello, I wanted to install Impala-shell for remote querying my CDP cluster, but looking with no much success I found the latest impala-shell client is in: archive.cloudera.com/p/cdh7/7.1.2.1/redhat7/yum nothing about 8 version, nothing about my CDP version: 7.1.8... Finally going with this "old" version but now I'm facing these issues: I already have python2 and 3 But not sure what more to try... no information at all in cloudera docs, even in apache impala web page 😞

Juanes · ‎06-21-2023

Hi all, The issue is not related to browsers, simply it has not the option to modify the queues... After many tests I managed to add the queues and resources to the ResourceManager Advanced config: [CM] > Yarn -> Configuration -> ResourceManager -> Fair Scheduler XML Advanced Configuration Snippet (Safety Valve) [CM] > Yarn -> Configuration -> ResourceManager -> yarn.resourcemanager.scheduler.class: org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler by this way the queues are defined.

Juanes · ‎05-30-2023

Correct, 50GB is the limit, reccomended: 10GB 🙂

Juanes · ‎05-30-2023

Hi again, you should be able to see the tablet size of every table (in the Kudu Tablet server UI): http://KUDUTABLET1:8050/tablets Then go to "Tablets" in the top menu and then you can search in the empty box your desired table. you will see all tablets (blocks) and some interesting information like Tablet ID, Partition, State, On-disk size and RaftConfig (Master) Then you can see how the tablets are more or less similar size.

Juanes · ‎05-30-2023

Hi @yagoaparecidoti Here the key is not the table size but the tablets. One table of 50GB could have 50 tablets, then each tablet of 1GB (that's good) or One table of 50GB could have 2 tablets, then each tablet of 25GB (that's no so good: The recommended target size for tablets is under 10 GiB) you can take a look in your Kudu Master UI: http://Master:8051/tables and look for your tables and partitions (tablets). I'm using this chart to see the kudu table sizing in the clart builder: select total_kudu_on_disk_size_across_kudu_replicas where category=KUDU_TABLE

Online	Offline
Last Visited	‎09-13-2024 03:44 AM

Member Since	‎12-17-2020 04:51 AM
Last Visited	‎09-13-2024 03:44 AM
Posts	44
Kudos received	15

Cloudera Community

Re: Failed to install cloudera-manager-agent packa...

Re: DNS Resolution: hostname and canonical name fo...

Re: Failed to download https://archive.cloudera.co...

Re: Can't edit queues in Yarn Queue Manager / CM7....

Re: what recommended size of a kudu table

DNS Resolution: hostname and canonical name for th...

Re: Failed to download https://archive.cloudera.co...

Re: Failed to download https://archive.cloudera.co...

Failed to download https://archive.cloudera.com/cm...

NTPD, CDH7.1.8 KUDU, RHEL8.4 - inconsistency

Impala-shell client Install in Centos/RHEL8

Re: Can't edit queues in Yarn Queue Manager / CM7....

Re: what recommended size of a kudu table

Re: what recommended size of a kudu table

Re: what recommended size of a kudu table