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         ... View more

Okay this makes sense I think, but what I meant is that users that access through Impala will be subject to Impala's more fine-grained permissions from Sentry. On the other hand, users that access using another method such as Kudu CLI will not be since it accesses Kudu directly, which is not directly integrated with Sentry, thus not picking up Hive or HDFS ACLs applied there.   Thanks, Braz ... View more

So to limit access exclusively through Impala, we would add the impala user to the Kudu User Access Control List without adding individual IDs who would interact with Kudu via Impala? This would prevent these same user IDs from being able to delete or view data from the Kudu CLI, since only 'impala' is allowed access? Would this also prevent users from accessing from Kudu APIs, including through Spark?      Thanks, Braz ... View more

Okay, and I hope I'm not asking too much in this one forum post, but since it's related: what is the recommended number of Tablet Server directories? Could we number of directories to each JBOD disk used by the DataNode? Of course without using a sub-directory of the DataNode. ... View more

Thanks for these answers. Having issues with replying, but for your last answer concerning the WAL directory and the metadata, would you recommend having a separate directory for the Tablet Server WAL? Thanks ... View more

Below are the contents of the haproxy.cfg file:   #--------------------------------------------------------------------- # Example configuration for a possible web application. See the # full configuration options online. # # http://haproxy.1wt.eu/download/1.4/doc/configuration.txt # #--------------------------------------------------------------------- #--------------------------------------------------------------------- # Global settings #--------------------------------------------------------------------- global # to have these messages end up in /var/log/haproxy.log you will # need to: # # 1) configure syslog to accept network log events. This is done # by adding the '-r' option to the SYSLOGD_OPTIONS in # /etc/sysconfig/syslog # # 2) configure local2 events to go to the /var/log/haproxy.log # file. A line like the following can be added to # /etc/sysconfig/syslog # # local2.* /var/log/haproxy.log # log 172.28.xx.xx local2 chroot /var/lib/haproxy pidfile /var/run/haproxy.pid maxconn 4000 user haproxy group haproxy daemon # turn on stats unix socket # stats socket /var/lib/haproxy/stats #--------------------------------------------------------------------- # common defaults that all the 'listen' and 'backend' sections will # use if not designated in their block #--------------------------------------------------------------------- defaults mode tcp log global option tcplog option dontlognull # option http-server-close # option forwardfor except 127.0.0.0/8 option redispatch retries 3 timeout http-request 10s timeout queue 1m timeout connect 10s #Values increased for fixing timeout issue with impala queries #timeout client 1m #timeout server 1m timeout client 120m timeout server 120m timeout http-keep-alive 10s timeout check 10s maxconn 3000 #--------------------------------------------------------------------- # main frontend which proxys to the backends #--------------------------------------------------------------------- frontend main *:5000 acl url_static path_beg -i /static /images /javascript /stylesheets acl url_static path_end -i .jpg .gif .png .css .js use_backend static if url_static default_backend app option tcplog log 172.28.xx.xx local2 debug #--------------------------------------------------------------------- # static backend for serving up images, stylesheets and such #--------------------------------------------------------------------- backend static balance roundrobin #server static 127.0.0.1:4331 check #This sets up the admin page for HA proxy at port 25002 #listen stats :25002 # listen stats # bind hdp004v.cmssvc.local:20020 ssl crt /data/security/hdp004v/hdp004v.crt.pem # balance # mode http # stats enable # stats auth username:password # stats uri /haproxy?stats #This is the setup for Imapala. Impala client connect to load_balancer_host:25003 #HAProxy will balance connections among the list of servers listed below. # The list of impalad is listening at port 21000 for beeswax (impala-shell) or original ODBC driver. # For JDBC or ODBC version 2.x driver, use port 21050 instead of 21000 listen impala :25003 mode tcp option tcplog balance leastconn server impalad1 hdp104v.cmssvc.local:21000 server impalad2 hdp105v.cmssvc.local:21000 # setup for hue or toher JDBC-enabled applications. Hue requires sticky sessions. # The application connects to load_balancer_host:21051, and HAProxy balances # connections to the associated hosts, where Imapala listens for JDBC # requests on port 21050 listen impalajdbc :21051 mode tcp option tcplog balance source log 172.28.xx.xx local2 debug server impalajdbc1 hdp104v.cmssvc.local:21050 server impalajdbc2 hdp105v.cmssvc.local:21050 #--------------------------------------------------------------------- # round robin balancing between the various backends #--------------------------------------------------------------------- backend app balance roundrobin #server app1 127.0.0.1:5001 check #server app2 127.0.0.1:5002 check #server app3 127.0.0.1:5003 check #server app4 127.0.0.1:5004 check Thanks, Braz ... View more