Skip to content

Commit d297fd9

Browse files
authored
Update hdinsight-overview-before-you-start.md
1 parent f2fb8cf commit d297fd9

File tree

1 file changed

+9
-8
lines changed

1 file changed

+9
-8
lines changed

articles/hdinsight/hdinsight-overview-before-you-start.md

Lines changed: 9 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -12,23 +12,24 @@ As part of the best practices, consider the following points before starting to
1212

1313
## Bring your own database
1414

15-
HDInsight have two options to configure the databased in the clusters.
15+
HDInsight have two options to configure the databases in the clusters.
1616

17-
1. Bring your own database (external).
18-
1. Internal default database.
17+
1. Bring your own database (external)
18+
1. Default database (internal)
1919

20-
During cluster creation, default configuration will use internal database. Once the cluster is created, customer can’t change the database type. Hence, it is recommended to create and use the external database. You can create custom databases for Ambari, Hive, and Ranger.
20+
During cluster creation, default configuration will use internal database. Once the cluster is created, customer can’t change the database type. Hence, it's recommended to create and use the external database. You can create custom databases for Ambari, Hive, and Ranger.
2121

2222
For more information, see how to [Set up HDInsight clusters with a custom Ambari DB](/azure/hdinsight/hdinsight-custom-ambari-db.md)
2323

24-
# Keep your clusters up to date
24+
## Keep your clusters up to date
2525

2626
To take advantage of the latest HDInsight features, we recommend regularly migrating your HDInsight clusters to the latest version. HDInsight doesn't support in-place upgrades where existing clusters are upgraded to new component versions. You need to create a new cluster with the desired components and platform version and migrate your application to use the new cluster.
27+
2728
As part of the best practices, we recommend you keep your clusters updated on regular basis.
28-
HDInsight release happens every 30 to 60 days. It is always good to move to the latest release as early possible. The recommended max period is less six months.
29-
For more information, see how to
3029

31-
For more information, see how to [Migrate HDInsight cluster to a newer version](/azure/hdinsight/hdinsight-upgrade-cluster)
30+
HDInsight release happens every 30 to 60 days. It's always good to move to the latest release as early possible. The recommended maximum duration for cluster upgrades is less than six months.
31+
32+
For more information, see how to [Migrate HDInsight cluster to a newer version](/azure/hdinsight/hdinsight-upgrade-cluster.md)
3233

3334
## Next steps
3435

0 commit comments

Comments
 (0)