Member since
11-12-2018
218
Posts
179
Kudos Received
35
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
342 | 08-08-2025 04:22 PM | |
419 | 07-11-2025 08:48 PM | |
635 | 07-09-2025 09:33 PM | |
1124 | 04-26-2024 02:20 AM | |
1489 | 04-18-2024 12:35 PM |
12-26-2018
10:48 AM
3 Kudos
For example your physical memory size is 10GB you need to allocated for every container request at the RM, is around 9GB (90% of your physical memory) then you can mention in below parameter yarn.scheduler.maximum-allocation-mb 9216 Similarly amount of physical memory allocated for containers in node manager, that can be mention using below parameter. yarn.nodemanager.resource.memory-mb 9216 These all settings are manage by single configuration file I.e., yarn-site.xml which you can modify via ambari under Yarn —> Configs —> Settings —>Advanced —> Advanced yarn-site I hope that the above answers your questions. Please accept the answer you found most useful.
... View more
12-26-2018
10:21 AM
2 Kudos
@Anjali Shevadkar Below article help you to configure spark fine grain security. https://community.hortonworks.com/content/kbentry/72454/apache-spark-fine-grain-security-with-llap-test-dr.html Please accept the answer you found most useful.
... View more
12-26-2018
10:05 AM
3 Kudos
If you set 100% ram only for yarn then other services will get crash / GC issue. It's not recommendable to set all physical memory to one component.
... View more
12-26-2018
08:37 AM
3 Kudos
For changing memory value through ambari configuration manager, login into ambari UI, Yarn —> Configs —> Settings —> memory —> Memory allocated for all YARN containers on a node and Minimum / Maximum Container Size memory. and for advanced turning of yarn modify Yarn —> Configs —> Settings —>Advanced —> Advanced yarn-site
... View more
12-26-2018
07:48 AM
3 Kudos
@Jack From your above output I can see it's MANAGED_TABLE. If the table has TBLPROPERTIES ("auto.purge"="true") the previous data of the table is not moved to Trash when INSERT OVERWRITE query is run against the table. This functionality is applicable only for managed tables and is turned off when "auto.purge" property is unset or set to false. For more detail HIVE-15880
... View more
12-26-2018
07:36 AM
3 Kudos
@Jack Please can you share output of below command. It is hive 3.x or hive 2.x ? DESCRIBE FORMATTED <table_name>
... View more
12-26-2018
06:45 AM
3 Kudos
@Ilia K You can manually configure your memory allocation settings based on the hardware specifications. Please refer below links for more tuning up RAM in yarn configuration. https://hortonworks.com/blog/how-to-plan-and-configure-yarn-in-hdp-2-0/ https://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.6.5/bk_command-line-installation/content/determine-hdp-memory-config.htm
... View more
12-26-2018
06:20 AM
3 Kudos
@Jack Seems your tables are not partitions. When you try to “INSERT OVERWRITE” to a partition of an external table under existing HDFS directory, depending on whether the partition definition already exists in the HIVE metastore or not, Hive will behave differently: Suppose if partition definition does not exist, it will not try to guess where the target partition directories are either static or dynamic partitions, so it will not be able to delete existing files/data under those partitions. So that will retained as historical data of HDFS like your case. But if partition definition does exist, it will attempt to remove all files/data under the target partition directory before writing new data into those directories. Reference here Please accept the answer you found most useful.
... View more
12-26-2018
06:02 AM
3 Kudos
@Michael Bronson 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
... View more