Member since
02-18-2019
83
Posts
3
Kudos Received
0
Solutions
03-01-2020
08:50 PM
Hello,
I would like to know if there a way to rebalance data in Kudu evenly across all kudu t-servers. Our Kudu deployment is as follows:
3 Kudu Masters
9 Tablet Servers
kudu 1.7.0-cdh5.16.2/ CM 5.16.2
Data across these 9 T-Servers is not evenly distributed, out these 9 t-servers, I see data is more stored on 3 t-servers and not distributed evenly. I was going through some articles and found that currently there is no rebalance tool like HDFS (https://community.cloudera.com/t5/Support-Questions/Kudu-Tablet-Server-Data-Directories-rebalancing/td-p/79649),
However if we Go to Clusters > Kudu > Click Actions I see Run Kudu Rebalancer Tool, would like to know, what is the purpose of this. Will this distribute data for overall Kudu or just Kudu Master or Kudu T-Servers too. Request some advice / assistance on the same.
Thanks
Amn
... View more
Labels:
- Labels:
-
Apache Kudu
02-09-2020
07:43 PM
Hi @kingpin Thanks for the assistance, wanted to confirm if restarting TS have any impact on Kudu service? Regards
... View more
01-23-2020
09:49 PM
Hello, We have been getting alerts for Open file descriptors on Kudu T-servers “Concerning: Open file descriptors: 16,954. File descriptor limit: 32,768. Percentage in use: 51.74%. Warning threshold: 50.00%.” request assistance in resolving this. Also does restarting services on affected T-Servers have any performance impact on Kudu as whole. [root@myserver ~]# ulimit -a core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 1546606 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 1546606 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited [root@myserver ~]# cat /proc/sys/fs/file-max 39233193 [root@myserver ~]# cat /proc/sys/fs/file-nr 35200 0 39233193 [root@myserver ~]# lsof -u kudu |wc -l 18326 Regards Amn
... View more
Labels:
- Labels:
-
Apache Kudu
-
Cloudera Manager
11-28-2019
09:37 PM
Hi Tim, Thanks for you reply, we ran couple of other queries and don't encounter this issue, we will resolve this as a one of case, appreciate your explanation in this regard.
... View more
11-27-2019
01:47 AM
Hello, I am facing an issue with Impala queries, though the query status says 'finished' on Impala status page it still shows 'executing'. I was following Cloudera Article : https://my.cloudera.com/knowledge/Finished-Queries-show-as-Executing-in-the-Cloudera-Manager?id=71576 the difference in my case is queries were run through impala shell via jdbc connection. would the resolution outlined in the article be applicable, for queries submitted through impala jdbc connection? and secondly what would be the fix for such queries which are in hung state. Regards Amn
... View more
Labels:
- Labels:
-
Apache Impala
-
Cloudera Manager
10-06-2019
10:56 PM
Hello All, We are facing issue with one of our clients cluster, we see some files over 2GB, and would like to know the purpose of these files, and if these could be deleted to make way for some space. 1. Eventserver [root@TestBed ~]# du -sh /var/lib/cloudera-scm-eventserver/v3/* |grep G 5.4G /var/lib/cloudera-scm-eventserver/v3/_1bx6l.fdt 1.2G /var/lib/cloudera-scm-eventserver/v3/_1hgcy.fdt 1.4G /var/lib/cloudera-scm-eventserver/v3/_1mz17.fdt 2. Cloudera-Scm-Headlamp [root@TestBed ~]# du -sh /var/lib/cloudera-scm-headlamp/hdfs/nameservice1/index/* |grep G 2.3G /var/lib/cloudera-scm-headlamp/hdfs/nameservice1/index/_2t.fdt 2.2G /var/lib/cloudera-scm-headlamp/hdfs/nameservice1/index/_5m.fdt 2.1G /var/lib/cloudera-scm-headlamp/hdfs/nameservice1/index/_8f.fdt Also is there a way to limit TS data in SMON & HMON, I understand that 10GB is the minimum requirement for these roles but what could be done if a clients has limited resources. Any help / guidance is appreciated Thanks
... View more
Labels:
- Labels:
-
Cloudera Manager
07-25-2019
10:42 AM
Hello, We have upgraded our cluster and are getting error " The Oozie Server build version(4.1.0-cdh5.16.2) and the Oozie Server shared library version(4.1.0-cdh5.14.2) do not match". We have done the following: Upgrade the Oozie SharedLib Go to the Oozie service If the Oozie service is stopped, start it: Select Actions > Start and click Start to confirm. Select Actions > Install Oozie SharedLib and click Install Oozie SharedLib to confirm. The service became Green from some time and then again its Red, kindly suggest / guide path to fix this
... View more
Labels:
- Labels:
-
Apache Oozie
- « Previous
- Next »