Hi @wert_1311    It shows the number of impalad connections are hitting the limit.   You can check on these below points:   1. you can increase the value of "Impala Daemon Max Client Connections" property in the impala configs if really more number of connections are coming. 2. If you think the connections are less but the opened connections are not closing properly and causing the issue you can check the timeouts has been set properly in the Hue safety-valve advance configs.   -idle_session_timeout=3600 -idle_query_timeout=3600      Regards, Chethan YM ... View more

Hi @RajB    We need to check the logs for that coordinator/workflow to find out why it is stuck.   oozie job -oozie http://<oozie-server-host>:11000 -log <workflow-id>   Regards, Chethan YM ... View more

Hi @ChethanYM , Thanks for the help, gracefully shutting down the region server triggers the hbase Master to perform a bulk assignment of all regions hosted by that region server. regards, KPG1 ... View more

hi @ChethanYM    unfortunately we need to do this type of blocking only in IMPALA, in HIVE it has to work normally.   when blocking by sentry, it will be replicated for any type of access that the user will use, such as hive, impala, beeline, etc. ... View more

hi@ChethanYM    Thank you for the link.   another question that popped up:   we didn't find anything saying if the coordinators can be used in virtual machines, can you tell us if there is a problem? ... View more

Thank you for the attention, the Principal name is complete and correct. Impala Catalog and Impala Server will report an error:   9236 authentication.cc:177] SASL message (Kerberos (internal)): GSSAPI Error: Unspecified GSS failure. Minor code may provide more information (Server krbtgt/statestore_hostname@TEST.COM not found in Kerberos database)   When I set "-skip_internal_kerberos_auth=true", only Coordinator gets this error. When I set "-skip_internal_kerberos_auth=true" and "-skip_external_kerberos_auth=true", all components are fine, but then Kerberos authentication is lost.     ... 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

@hbenner89 , In addition to what @ChethanYM wrote above, you should also share the file size that you are attempting to upload. As a general matter, you can't expect a web browser to enable you to upload a file with arbitrarily large size, so the perhaps unstated reason the Jira issue you pointed to was resolved with the status "won't fix" is because this is not a limitation that is specific to Hue.     ... 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 @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