You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/hdinsight/hdinsight-overview-before-you-start.md
+9-8Lines changed: 9 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,23 +12,24 @@ As part of the best practices, consider the following points before starting to
12
12
13
13
## Bring your own database
14
14
15
-
HDInsight have two options to configure the databased in the clusters.
15
+
HDInsight have two options to configure the databases in the clusters.
16
16
17
-
1. Bring your own database (external).
18
-
1.Internal default database.
17
+
1. Bring your own database (external)
18
+
1.Default database (internal)
19
19
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.
21
21
22
22
For more information, see how to [Set up HDInsight clusters with a custom Ambari DB](/azure/hdinsight/hdinsight-custom-ambari-db.md)
23
23
24
-
# Keep your clusters up to date
24
+
##Keep your clusters up to date
25
25
26
26
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
+
27
28
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
30
29
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)
0 commit comments