About balajip

balajip · ‎10-25-2021

@railincdba Seems ambari database not updated. Can you restart ambari-server and ambari-agent from the decommission nodemanager host and check. If issues still persist you can revert the changes (Recommission NodeManagers) then decommission it and check.

balajip · ‎10-25-2021

Hello @MikeB As for automatic clean up not getting triggered, well it may be due to (or at-least related to) this unresolved bug reported on Yarn. https://issues.apache.org/jira/browse/YARN-4540 You can reduce the below property value to lower the local file cache size. yarn.nodemanager.localizer.cache.target-size-mb

balajip · ‎10-11-2021

@Sam7 Was the query working fine before in das ?

balajip · ‎10-07-2021

@MikeB To resolve this issue, configure Hive Metastore to use SerdeStorageSchemaReader implementation: Go to Ambari > Hive > Config > Custom hive-site. Set the following property to configure Hive Metastore: metastore.storage.schema.reader.impl=org.apache.hadoop.hive.metastore.SerDeStorageSchemaReader

balajip · ‎09-21-2021

@drgenious You can find the impala memory consumption in the "impala_memory_total_used" chart. In Cm -> impala -> charts library -> impala_memory_total_used

balajip · ‎09-14-2021

@Sayed016 Can you set the property below and try to rerun the query. set hive.fetch.task.conversion=none;

balajip · ‎08-23-2021

@Amn_468 Please refer the below Knowledge base article for heap memory calculation. https://lighthouse.cloudera.com/s/article/Impaladembeddedjvmheapsize-has-a-default-value-of-32-GB-after-upgrading-to-CDH-516https://my.cloudera.com/knowledge/Impaladembeddedjvmheapsize-has-a-default-value-of-32-GB-after?id=278279

balajip · ‎07-21-2021

@MattSchmitz Please check the permission for the Log directory. you can find the log location in LogPath.

balajip · ‎10-28-2020

@kuldeephawks 1. Enable debug for HiveServer Interactive from Ambari -> Hive -> Configs -> Advanced hive-log4j2. Update below property and set it to DEBUG: property.hive.log.level = DEBUG 2. Restart HSI or From ambari > Hive > Configs > Hive log level > change to DEBUG from INFO.

balajip · ‎10-13-2020

Seems you are hitting the number of max buckets limit in hive. For more information please refer below apache jira. https://issues.apache.org/jira/browse/TEZ-4130

Online	Offline
Last Visited	‎12-02-2022 06:25 AM

Member Since	‎12-18-2018 11:13 AM
Last Visited	‎12-02-2022 06:25 AM
Posts	109
Kudos received	5

Cloudera Community

Re: Ozzie Hive Script

Re: Retry in oozie through hue

Re: Yarn Queue Manager Not starting

Re: Decomissioning a NodeManager in HDP 2.6.1

Re: /hadoop/yarn/local/usercache/hive/filecache/ g...

Re: Decomissioning a NodeManager in HDP 2.6.1

Re: /hadoop/yarn/local/usercache/hive/filecache/ g...

Re: SQL statement to capitalize the first letter

Re: message:java.lang.UnsupportedOperationExceptio...

Re: Find the % of the used memory in impala

Re: Hive Error while calling watcher java.util.co...

Re: Impala Catalogue Server OOM

Re: Impala ODBC Logging Options: Automatically Rev...

Re: How to set the logging level of the hiveserver...

Re: bucketId out of range: 4147