Hi Team, I am facing below issue in HBase for two tables and remaning all the tables are looking good.     Getting alerts for above issue but when i am checking the HBCK, i am not find anything and i can see below output, 0 inconsistencies detected. Status: OK Below logs i can see for the same, Unhealthy Regions by Table Report DMX_EVENTS Number of Unhealthy Regions: 2 Region Name: DMX_EVENTS,000019861785:1555120520:1555120520,1562868060261.5cb6dce7a9716deb28f38a94cb95b1b9., Hostname: xxxxxxxxxxxxxxx, Content: "Slow read (ms): 1,569" Region Name: DMX_EVENTS,000020372472:1555140529,1562867348509.5401fcb5715c85fc41cfe63ee9e1ba3a., Hostname: xxxxxxxxxxxxxx Content: "Slow read (ms): 2,115" STAGING_DMXS Number of Unhealthy Regions: 98 Region Name: STAGING_DMXS,00 189,1562876321188.6ff32926370e95a246b3698844ff0790., Hostname: xxxxxxxxxx , Content: "Slow read (ms): 5,274" Region Name: STAGING_DMXS,01 18806693 /home/mediaworks/collection/1/dmxs/201905/25/93/18806693/18806693.945.1,1562876321707.40af5f68617afa59176dac967d6bc019., Hostname: xxxxxxxxxx, Content: "Slow read (ms): 4,916" Like this i can see the logs, Can some one please help me on this. Thanks in advance...!! ... View more

Hello Team,   Find below details,   My cluster Capacity is 13 TB and so far we used around 10 TB of its space. I am trying to clear the un wanted files but i can see Non DFS is occupied more in each data node.   hostname$ sudo -u hdfs hdfs dfsadmin -report | grep Non Non DFS Used: 1009442598912 (940.12 GB) Non DFS Used: 949231187249 (884.04 GB) Non DFS Used: 966384629041 (900.02 GB) Non DFS Used: 1085142044371 (1010.62 GB) Non DFS Used: 944683108325 (879.80 GB) Non DFS Used: 1045682881204 (973.87 GB) Non DFS Used: 1006219386880 (937.11 GB) Non DFS Used: 543543034548 (506.21 GB)   Any help from your side ?   Thanks, Vinod ... View more

Hello ,   In my Cloudera Hadoop Cluster service monitor was failing frequently from last 2 day's and everytime i can see the logs like,   Apr 2, 4:09:11.402 AM ERROR com.cloudera.cmon.kaiser.BaseTestRunner Error running subject health tests java.util.concurrent.ExecutionException: java.lang.NullPointerException at java.util.concurrent.FutureTask.report(FutureTask.java:122) at java.util.concurrent.FutureTask.get(FutureTask.java:188) at com.cloudera.cmon.kaiser.BaseTestRunner.submitTestsOnSubjectsByType(BaseTestRunner.java:232) at com.cloudera.cmon.kaiser.SMONTestRunner.runRoleAndServiceTestsForSession(SMONTestRunner.java:166) at com.cloudera.cmon.kaiser.SMONTestRunner.runTestsForSession(SMONTestRunner.java:137) at com.cloudera.cmon.kaiser.BaseTestRunner.runTestsOnAllSubjects(BaseTestRunner.java:143) at com.cloudera.cmon.kaiser.KaiserService$KaiserServiceRunner.run(KaiserService.java:138) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.NullPointerException at com.cloudera.cmon.kaiser.KaiserSubjectRecordFactory.extendStatusForSpecialRoles(KaiserSubjectRecordFactory.java:732) at com.cloudera.cmon.kaiser.KaiserSubjectRecordFactory.createForRole(KaiserSubjectRecordFactory.java:485) at com.cloudera.cmon.kaiser.BaseTestRunner$2.run(BaseTestRunner.java:295) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) ... 1 more     I have increased the heap memory of service monitor "Java Heap Size of Service Monitor 5GB to 8GB " and "Maximum Non-Java Memory of Service Monitor 12 GB to 16 GB"   Can some please provide me a solution for this frequent failure's.     Thanks in advance, Vinod ... View more

Hello Team,   Can any one help me one below issue,   We are recently upgraded OS from RHEL to CentOS and we are successfully done with out any impact to the application except one server. lets say "hostname1" is the server and here we installed clouderamanager. We done OS change but when we modifying the hostname and trying to login cloudera admin console but not happening.   We modified hostname1 to hostname2 and trying to login using hostname2:7180 but no luck.   Any clues or any help on this, Checking this from last 1 week but no luck. Your help is much appriciated.     Best Regards, Vinod         ... View more