Try running invalidate metadata; At end clearing browser cache worked for me. ... View more

@Braz wrote: Is there not a Kudu command which will allow for obtaining table size information? If not, then how does Cloudera Manager perform this? We would like to be able to replicate this behavior so that we can configure e-mail alerts to be sent whenever a table reaches a particular size.   Thanks, Braz     CM is scrapping and aggregating the /metrics pages from the tablet server instances for each tablet/table.   Have you reviewed CM triggers/alerts?[1] You might be able to configure email alerts with a similar trigger rule for table sizes. Alternatively, you could implement what CM currently does by scraping each tablet server's /metrics page and aggregating the data together per tablet/table.     [1] https://www.cloudera.com/documentation/enterprise/latest/topics/cm_dg_triggers_usecases.html ... View more

For CDH / CDK Kafka users, the command is already in your PATH as "kafka-consumer-groups". ... View more

I didnt quite understand your statement..why does it matter if BDM has other execution engines like Blaze and spark?   Impala itself is another execution engine like spark and blaze, we dont need to use impala jdbc connection in BDM using spark and Blaze you can just use it in native mode. ... View more

Hi, is this the only solution for this kind of error - increasing the memory limit? Thannks ... View more

user mapred:hadoop for logs in /tmp ... View more

Looks like this is resloved in hadoop 2.8.0 ( not sure though)  check this ==.> https://github.com/minio/minio/issues/2965   only workaround i found is first load data without  encryption and then enable encryption  on file copied in S3 (manually) .    btw i have a general question . this SSE is to portect data in S3 only ,what about if someone with aws admin role download data to local disk ,its not more encrypted data    ... View more

Thank you for the information. This does not appear to be the same issue as initiated in this thread.   However, the error is clear: "ERROR Error, CM server guid updated, expected 93c963d9-3566-4f25-847a-faffb020866b, received ba4e4402-6ab3-4cdc-a403-39415df12824"   There is a 'cm_guid' file that is used by the Cloudera Manager (CM) server to know which host belong to it. It appears that this host may have been part of a different CM cluster or the database was recently changed. This keeps users from inadvertently pointing the agent ot another CM instance.   In any case, the solution is to: 1. Archive/remove the /var/lib/cloudera-scm-agent/cm_guid file. 2. Restart the agent: sudo service cloudera-scm-agent restart 3. Run the Host inspector, from the Hosts page in CM and verisfy that all hosts are functioning. If other hosts fail, they too may be in this state.   ... View more