Cloudera Community
Braz
user rank
Explorer
My Accepted Solutions
Show All

Re: Ranger HDFS Policies Failing

by Contributor Contributor in Support Questions
‎06-25-2020 05:02 PM
‎06-25-2020 05:02 PM
@Braz  Are you still facing the issue? ... View more

Re: kudu table size

by Contributor Contributor in Support Questions
‎04-18-2019 03:36 PM
‎04-18-2019 03:36 PM
@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

Re: Kudu Security and CLI

by Contributor Contributor in Support Questions
‎04-25-2018 01:05 PM
1 Kudo
‎04-25-2018 01:05 PM
1 Kudo
Yep, that's correct.  That's the limitation implied by 'coarse-grained authorization'.  Applying Sentry's fine-grained authorization policies in the Kudu server is a long-term roadmap item. ... View more

Re: Kudu Master Directories

by Rising Star Rising Star in Support Questions
‎04-05-2018 10:23 AM
1 Kudo
‎04-05-2018 10:23 AM
1 Kudo
That is up to your workload and how much storage you need per node. It's common to see anywhere from 6 to 12 disks per tablet server. Check out the limitations documentation for some guidance there. ... View more

Re: HAProxy Not Producing Sufficient Logs

by Explorer in Support Questions
‎03-28-2018 11:22 AM
‎03-28-2018 11:22 AM
All I'm seeing are messages like the following when restarting haproxy: 2018-03-28T11:32:41-04:00 172.28.2.234 haproxy[26642]: Proxy main started. 2018-03-28T11:32:41-04:00 172.28.2.234 haproxy[26642]: Proxy static started. 2018-03-28T11:32:41-04:00 172.28.2.234 haproxy[26642]: Proxy impala started. 2018-03-28T11:32:41-04:00 172.28.2.234 haproxy[26642]: Proxy impalajdbc started. 2018-03-28T11:32:41-04:00 172.28.2.234 haproxy[26642]: Proxy main started. 2018-03-28T11:32:41-04:00 172.28.2.234 haproxy[26642]: Proxy impalajdbc started. 2018-03-28T11:32:41-04:00 172.28.2.234 haproxy[26642]: Proxy app started.   And sometimes other messages like the following in the haproxy log - but they don't come in immediately after running an Impala query over JDBC such as from Hue or beeline:   2018-03-27T15:51:47-04:00 172.28.2.234 haproxy[4286]: 172.28.6.234:37768 [27/Mar/2018:15:51:47.621] impalajdbc impalajdbc/impalajdbc1 0/0/+0 +0 -- 2/2/2/1/0 0/0 2018-03-27T18:08:08-04:00 172.28.2.234 haproxy[4286]: 172.28.2.20:39978 [27/Mar/2018:18:08:08.888] impala impala/impalad1 0/0/+0 +0 -- 3/1/1/1/0 0/0 However, no logs come in when accessing from a BI tool such as Tableau using its native Cloudera Impala connector or the Cloudera Impala ODBC driver.   Is there a way to increase the logging for haproxy so that we can know which Impala Daemon a query is executing on for the purpose of debugging potential issues of someone accessing from a BI application? I already have it said to debug under the listen section for impalajdbc.   listen impalajdbc :21051 mode tcp option tcplog balance roundrobin log 172.28.xx.xx local2 debug server impalajdbc1 hdp104v.cmssvc.local:21050 server impalajdbc2 hdp105v.cmssvc.local:21050 Thanks, Braz ... View more
Contact Me
Online
Offline
Last Visited
‎09-14-2020 05:15 PM
Community Statistics
Member Since ‎12-13-2017 10:02 AM
Last Visited ‎09-14-2020 05:15 PM
Posts 11