|
| 1 | +--- |
| 2 | +title: Manage disk space in Azure HDInsight |
| 3 | +description: Troubleshooting steps and possible resolutions for issues when interacting with Azure HDInsight clusters. |
| 4 | +author: hrasheed-msft |
| 5 | +ms.author: hrasheed |
| 6 | +ms.reviewer: jasonh |
| 7 | +ms.service: hdinsight |
| 8 | +ms.topic: troubleshooting |
| 9 | +ms.date: 02/17/2020 |
| 10 | +--- |
| 11 | + |
| 12 | +# Manage disk space in Azure HDInsight |
| 13 | + |
| 14 | +This article describes troubleshooting steps and possible resolutions for issues when interacting with Azure HDInsight clusters. |
| 15 | + |
| 16 | +## Hive log configurations |
| 17 | + |
| 18 | +1. From a web browser, navigate to `https://CLUSTERNAME.azurehdinsight.net`, where `CLUSTERNAME` is the name of your cluster. |
| 19 | + |
| 20 | +1. Navigate to **Hive** > **Configs** > **Advanced** > **Advanced hive-log4j**. Review the following settings: |
| 21 | + |
| 22 | + * `hive.root.logger=DEBUG,RFA`. This is the default value, modify the [log level](https://logging.apache.org/log4j/2.x/log4j-api/apidocs/org/apache/logging/log4j/Level.html) to `INFO` to print less logs entries. |
| 23 | + |
| 24 | + * `log4jhive.log.maxfilesize=1024MB`. This is the default value, modify as desired. |
| 25 | + |
| 26 | + * `log4jhive.log.maxbackupindex=10`. This is the default value, modify as desired. If the parameter has been omitted, the generated log files will be endless. |
| 27 | + |
| 28 | +## Yarn log configurations |
| 29 | + |
| 30 | +Review the following configurations: |
| 31 | + |
| 32 | +* Apache Ambari |
| 33 | + |
| 34 | + 1. From a web browser, navigate to `https://CLUSTERNAME.azurehdinsight.net`, where `CLUSTERNAME` is the name of your cluster. |
| 35 | + |
| 36 | + 1. Navigate to **Hive** > **Configs** > **Advanced** > **Resource Manager**. Ensure **Enable Log Aggregation** is checked. If disabled, name nodes will keep the logs locally and not aggregate them in remote store on application completion or termination. |
| 37 | + |
| 38 | +* Ensure that the cluster size is appropriate for the workload. The workload might have changed recently or the cluster might have been resized. [Scale up](../hdinsight-scaling-best-practices.md) the cluster to match a higher workload. |
| 39 | + |
| 40 | +* `/mnt/resource` might be filled with orphaned files (as in the case of resource manager restart). If necessary, manually clean `/mnt/resource/hadoop/yarn/log` and `/mnt/resource/hadoop/yarn/local`. |
| 41 | + |
| 42 | +## Next steps |
| 43 | + |
| 44 | +If you didn't see your problem or are unable to solve your issue, visit one of the following channels for more support: |
| 45 | + |
| 46 | +* Get answers from Azure experts through [Azure Community Support](https://azure.microsoft.com/support/community/). |
| 47 | + |
| 48 | +* Connect with [@AzureSupport](https://twitter.com/azuresupport) - the official Microsoft Azure account for improving customer experience. Connecting the Azure community to the right resources: answers, support, and experts. |
| 49 | + |
| 50 | +* If you need more help, you can submit a support request from the [Azure portal](https://portal.azure.com/?#blade/Microsoft_Azure_Support/HelpAndSupportBlade/). Select **Support** from the menu bar or open the **Help + support** hub. For more detailed information, review [How to create an Azure support request](https://docs.microsoft.com/azure/azure-supportability/how-to-create-azure-support-request). Access to Subscription Management and billing support is included with your Microsoft Azure subscription, and Technical Support is provided through one of the [Azure Support Plans](https://azure.microsoft.com/support/plans/). |
0 commit comments