Hi @Amn_468    In Kudu Table is divided into multiple tablets and those tables are distributed across the cluster. So the table data will be stored across multiple TS (kudu nodes)   You can get that info from Kudu master WebUI CM->Kudu ->Webui -> Tables ->select table    curl -i -k --negotiate -u : "http://Abcde-host:8051/tables"   Also, You can run ksck command to get that info :-  https://kudu.apache.org/docs/command_line_tools_reference.html#table-list   Does that answer your question, if yes please feel free to mark the post as solution accepted and give a thumbs up.   regards,   ... View more

Hi @sakitha    Seems to be a known issue.  Is the topic whitelist is set to " * " ?  Can you please try with dot  - " .*"    Let us know if that works for you.    Regards,   ~ If the above answers your questions. Please give a thumbs up and mark the post as accept as solution. ... View more

Hi @wert_1311    That's right, balancer just balances the tablet across the kudu cluster. If one host is consuming more space, it could be that the size of tablets is huge.  Thats right, Kudu cant rebalance like HDFS based on dfs usage.  one of the workaround you can try:- - Stop that specific kudu TS role - Run ksck until it comes healthy.  - once ksck is healthy, rebuild that particular Kudu TS (rebuilding = wiping all data and wal dir) https://kudu.apache.org/docs/administration.html#rebuilding_kudu - start that specific TS  - Run rebalance again   That should help. Let me know how did that go.   Cheers,   ~ If that answers your question - Please  give the thumbs up & mark the post as accept as solution.  ... View more

Hi @Chetankumar    You can perform disk hot swap of DN.  https://docs.cloudera.com/documentation/enterprise/6/6.3/topics/admin_dn_swap.html   If the Replication factor is set to 3 for all the files then taking down one disk shouldn't be a problem as Namenode will auto-replicate the under-replicated blocks. As part of small test first stop the datanode and wait for sometime (While NN copies the blocks to other available datanodes).  Run fsck to confirm if HDFS file system is healthy. When it is healthy, you can easily play around with that stopped datanode. Idea is to ensure the replication factor to 3 so that you dont incur any dataloss.   if the Replication factor is set to 1 for some files and if those blocks are hosted on that /data01 disk. Then it could be a potential loss. As long as you have RF=3 you would be good.    Does that answer your questions ? Let us know   Regards,           ... View more