whirr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom White (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (WHIRR-540) Java Processes Terminate Immediately when starting elasticsearch cluster at EC2
Date Tue, 09 Oct 2012 10:02:07 GMT

     [ https://issues.apache.org/jira/browse/WHIRR-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Tom White updated WHIRR-540:
----------------------------

    Fix Version/s:     (was: 0.8.0)
                   0.8.1
    
> 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.1
>
>         Attachments: elasticsearch_whirr.tar.gz, WHIRR-540.patch
>
>   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
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message