Hi @yagoaparecidoti ,   I do not think we have such option of blocking but as i know i think you can make it using sentry authorisation. If sentry is enabled in the cluster you should grant only "SELECT" privilege to all the users for all the databases/tables so if the users try any other DDL commands it will throw 'Authorisation exceptions".   Do refer the below documentation: https://docs.cloudera.com/documentation/enterprise/6/6.3/topics/cm_sg_sentry_service.html   If you are using Ranger same can be achieved from ranger also.   Regards, Chethan YM     ... View more

Hi @yagoaparecidoti ,   Each host that runs the Impala Daemon acts as both a coordinator and as an executor and if you want to deploy dedicated coordinators and executors please refer the below documentation for complete details:   https://docs.cloudera.com/documentation/enterprise/6/6.3/topics/impala_dedicated_coordinator.html   Regards, Chethan YM ... View more

Hi,   Can you regenerate the kerberos credentials for impala from CM and see if it helps?   Regards, Chethan YM ... View more

Hi @swapko ,   > Please provide the error stacktrace that you are seeing when you refresh the impala tables. > was it working earlier?   Regards, Chethan YM ... View more

Hi @jagad ,   I think you are facing the above error for an impala query am i right? If Yes please increase the memory limit for that query using set MEM_LIMIT=xg; parameter and try to rerun the query. This usually occurs if there is not enough memory for a query.   Regards, Chethan YM ... View more

Hi @dmharshit ,   This error can occures if you have deployed the "Hive Server 2" and "WebHCat" roles under the Hive Service.   Can you stop and delete the "Hive Server 2" and "WebHCat" instances from Cloudera Manager -> Hive -> Instances?    Restart if any stale configurations are present in the cluster and try the hive query.   Regards, Chethan YM ... View more

Hi,   As per the above Jira- HUE-2782 the resolution is "won't fix" so issue cannot be fixed. We do not know you are facing the same issue or not so please attach the error screenshot and  error stacktrcae to look into it.   Regards, Chethan YM ... View more

Hi @PratCloudDev ,   "Spill to disk" happens when there is no enough memory available for a running query, Below is the example.   Suppose you are running a query which is using 10gb ( per node peak memory) of memory and in case this query needs 12 gb of memory in this situation spill to disk happen on the configured scratch directories. you can see the directory by searching the "Impala Daemon Scratch Directories" property in the impala configurations. If you do not want to fail the query then you need to make sure the configured scratch directories/disk has enough space to store spilling information, this can potentially be large amounts of data.   Check the query profile for "per node peak memory" it is the actual memory used for that query on each daemon, suppose if it is 15GB then set the MEM_LIMIT to 10gb or 12gb to see the spill to disk functionality.  To understand why you are seeing the error[1] i need few details from your side.   1. Screenshot of impala admission control pool settings. 2. How much memory you are setting and seeing the below error[1]? 3. Which pool you are using to run the query? 4. If possible you can provide the query profile.   Regards, Chethan YM   [1]. Rejected query from pool root.centos: minimum memory reservation is greater than memory available to the query for buffer reservations. ... View more

Hi ,   Previous execution means previous workflow execution or previous action execution with in a workflow? I think as i know if you have multiple actions with in a wokflow next action will start only if previous action is succeeded otherwise it fails. If its not working like this can you give the info output for that workflow id?   oozie job -oozie http://<oozie-server-host>:11000 -info <workflow-id>   Regards, Chethan YM ... View more