[jira] [Commented] (WHIRR-540) Java Processes Terminate Immediately when starting elasticsearch cluster at EC2

["Andrei Savu (Commented) (JIRA)" <ji...@apache.org>]

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

Andrei Savu commented on WHIRR-540:
-----------------------------------

Please attach and I'm sure we can find a way to commit to trunk. 
                
> Java Processes Terminate Immediately when starting elasticsearch cluster at EC2
> -------------------------------------------------------------------------------
>
>                 Key: WHIRR-540
>                 URL: https://issues.apache.org/jira/browse/WHIRR-540
>             Project: Whirr
>          Issue Type: Bug
>          Components: service/elasticsearch
>    Affects Versions: 0.7.1
>         Environment: EC2 attempting to run 5 M1 Large Instances
>            Reporter: eric chazan
>              Labels: patch
>             Fix For: 0.8.0
>
>   Original Estimate: 3h
>  Remaining Estimate: 3h
>
> When using latest whirr from github (commit f5fd55ef8656b247d9f4ff722264abd0106de669),  and trying to bring up a cluster at EC2 using whirr, The machines have ElasticSearch (0.17.9, 0.18.5) installed, but after about 20 seconds the java process terminates.  This is due to permission problems with the remote filesystems.  Whirr is not configuring the permissions of the cluster's ephemerial storage properly, and ElasticSearch fails to run.  
> I have a suggested patch, but as I don't know Whirr very well, I don't know if it meets your project's goals.  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira