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/r-server/r-server-hdinsight-manage.md
+6-10Lines changed: 6 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,10 +1,10 @@
1
1
---
2
2
title: Manage ML Services cluster on HDInsight - Azure
3
3
description: Learn how to manage various tasks on ML Services cluster in Azure HDInsight.
4
-
ms.service: hdinsight
5
4
author: hrasheed-msft
6
5
ms.author: hrasheed
7
6
ms.reviewer: jasonh
7
+
ms.service: hdinsight
8
8
ms.custom: hdinsightactive
9
9
ms.topic: conceptual
10
10
ms.date: 06/19/2019
@@ -18,22 +18,20 @@ In this article, you learn how to manage an existing ML Services cluster on Azur
18
18
19
19
* An ML Services cluster on HDInsight. See [Create Apache Hadoop clusters using the Azure portal](../hdinsight-hadoop-create-linux-clusters-portal.md) and select **ML Services** for **Cluster type**.
20
20
21
-
22
21
* A Secure Shell (SSH) client: An SSH client is used to remotely connect to the HDInsight cluster and run commands directly on the cluster. For more information, see [Use SSH with HDInsight.](../hdinsight-hadoop-linux-use-ssh-unix.md).
23
22
24
-
25
23
## Enable multiple concurrent users
26
24
27
25
You can enable multiple concurrent users for ML Services cluster on HDInsight by adding more users for the edge node on which the RStudio community version runs. When you create an HDInsight cluster, you must provide two users, an HTTP user and an SSH user:
28
26
29
-

-**Cluster login username**: an HTTP user for authentication through the HDInsight gateway that is used to protect the HDInsight clusters you created. This HTTP user is used to access the Apache Ambari UI, Apache Hadoop YARN UI, as well as other UI components.
32
30
-**Secure Shell (SSH) username**: an SSH user to access the cluster through secure shell. This user is a user in the Linux system for all the head nodes, worker nodes, and edge nodes. So you can use secure shell to access any of the nodes in a remote cluster.
33
31
34
32
The R Studio Server Community version used in the ML Services cluster on HDInsight accepts only Linux username and password as a sign in mechanism. It does not support passing tokens. So, when you try to access R Studio for the first time on an ML Services cluster, you need to sign in twice.
35
33
36
-
- First sign in using the HTTP user credentials through the HDInsight Gateway.
34
+
- First sign in using the HTTP user credentials through the HDInsight Gateway.
37
35
38
36
- Then use the SSH user credentials to sign in to RStudio.
39
37
@@ -61,7 +59,7 @@ To add a user to the edge node, execute the commands:
61
59
62
60
The following screenshot shows the outputs.
63
61
64
-

When prompted for "Current Kerberos password:", just press **Enter** to ignore it. The `-m` option in `useradd` command indicates that the system will create a home folder for the user, which is required for RStudio Community version.
67
65
@@ -200,11 +198,9 @@ To install R packages on the worker nodes of the cluster, you must use a Script
200
198
> [!NOTE]
201
199
> 1. By default, all R packages are installed from a snapshot of the Microsoft MRAN repository consistent with the version of ML Server that has been installed. If you want to install newer versions of packages, then there is some risk of incompatibility. However this kind of install is possible by specifying `useCRAN` as the first element of the package list, for example `useCRAN bitops, stringr, arules`.
202
200
> 2. Some R packages require additional Linux system libraries. For convenience, the HDInsight ML Services comes pre-installed with the dependencies needed by the top 100 most popular R packages. However, if the R package(s) you install require libraries beyond these then you must download the base script used here and add steps to install the system libraries. You must then upload the modified script to a public blob container in Azure storage and use the modified script to install the packages.
203
-
> For more information on developing Script Actions, see [Script Action development](../hdinsight-hadoop-script-actions-linux.md).
204
-
>
205
-
>
201
+
> For more information on developing Script Actions, see [Script Action development](../hdinsight-hadoop-script-actions-linux.md).
206
202
207
-

0 commit comments