[ 
https://issues.apache.org/jira/browse/SPARK-8684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14604600#comment-14604600
 ] 

Vincent Warmerdam edited comment on SPARK-8684 at 6/28/15 11:26 AM:
--------------------------------------------------------------------

I'll double check. I've done this before but I recall it was always a bit 
messy. Do we prefer using yum or is installing from source also a possbility? 

What centos version will we use? I just worked up a quick server from digital 
ocean with centos 7 and this seems to work just fine: 

```
[root@servy-server ~]# yum install -y epel-release
[root@servy-server ~]# yum update -y
[root@servy-server ~]# yum install -y R
[root@servy-server ~]# R

R version 3.2.0 (2015-04-16) -- "Full of Ingredients"
Copyright (C) 2015 The R Foundation for Statistical Computing
Platform: x86_64-redhat-linux-gnu (64-bit)

>
```

The downside of YUM is that it is not always up to date (the latest version is 
3.2.1, not 3.2.0 which is what yum gives us). The yum version of R should allow 
almost all Rstudio packages to just go and work out of the box though, so it 
might not be the biggest issue.  

Depending of which version of CentOS we use, getting epel might be a problem. 
In the past this  made it more practical to just go and install R from source. 
This is not too terrible, it can be done this way: 

```
[root@servy-server ~]# wget http://cran.rstudio.com/src/base/R-3/R-3.2.1.tar.gz
[root@servy-server ~]# tar xvf R-3.2.1.tar.gz
[root@servy-server ~]# cd R-3.2.1
[root@servy-server ~]# ./configure --prefix=$HOME/R-3.2 --with-readline=no 
--with-x=no
[root@servy-server ~]# make && make install
```

The main downside is that this will take a fair amount of time. 

Another thing we might need to keep in mind is that R has many C++ dependencies 
so we may also need to install up to date compilers for it. 


was (Author: cantdutchthis):
I'll double check. I've done this before but I recall it was always a bit 
messy. Do we prefer using yum or is installing from source also a possbility? 

What centos version will we use? I just worked up a quick server from digital 
ocean with centos 7 and this seems to work just fine: 

```
[root@servy-server ~]# yum install -y epel-release
[root@servy-server ~]# yum update -y
[root@servy-server ~]# yum install -y R
[root@servy-server ~]# R

R version 3.2.0 (2015-04-16) -- "Full of Ingredients"
Copyright (C) 2015 The R Foundation for Statistical Computing
Platform: x86_64-redhat-linux-gnu (64-bit)

>
```

The downside of YUM is that it is not always up to date (the latest version is 
3.2.1). This version of R should allow almost all Rstudio packages to just go 
and work out of the box. 

Depending of which version of CentOS we use, getting epel might be a problem. 
In the past this  made it more practical to just go and install R from source. 
This is not too terrible, it can be done this way: 

```
[root@servy-server ~]# wget http://cran.rstudio.com/src/base/R-3/R-3.2.1.tar.gz
[root@servy-server ~]# tar xvf R-3.2.1.tar.gz
[root@servy-server ~]# cd R-3.2.1
[root@servy-server ~]# ./configure --prefix=$HOME/R-3.2 --with-readline=no 
--with-x=no
[root@servy-server ~]# make && make install
```

The main downside is that this will take a fair amount of time. 

> Update R version in Spark EC2 AMI
> ---------------------------------
>
>                 Key: SPARK-8684
>                 URL: https://issues.apache.org/jira/browse/SPARK-8684
>             Project: Spark
>          Issue Type: Improvement
>          Components: EC2, SparkR
>            Reporter: Shivaram Venkataraman
>            Priority: Minor
>
> Right now the R version in the AMI is 3.1 -- However a number of R libraries 
> need R version 3.2 and it will be good to update the R version on the AMI 
> while launching a EC2 cluster.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org

Reply via email to