You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whirr.apache.org by "eric chazan (Created) (JIRA)" <ji...@apache.org> on 2012/02/28 14:45:46 UTC
[jira] [Created] (WHIRR-540) Java Processes Terminate Immediately
when starting elasticsearch cluster at EC2
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
Fix For: 0.8.0
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
[jira] [Commented] (WHIRR-540) Java Processes Terminate Immediately
when starting elasticsearch cluster at EC2
Posted by "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=13218187#comment-13218187 ]
Andrei Savu commented on WHIRR-540:
-----------------------------------
Can you attach a diff? That would be much easier to review & commit. Also see:
https://cwiki.apache.org/confluence/display/WHIRR/How+To+Contribute
> 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
>
> Attachments: elasticsearch_whirr.tar.gz
>
> 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
[jira] [Updated] (WHIRR-540) Java Processes Terminate Immediately
when starting elasticsearch cluster at EC2
Posted by "eric chazan (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
eric chazan updated WHIRR-540:
------------------------------
Attachment: WHIRR-540.patch
> 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
>
> Attachments: WHIRR-540.patch, elasticsearch_whirr.tar.gz
>
> 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
[jira] [Updated] (WHIRR-540) Java Processes Terminate Immediately
when starting elasticsearch cluster at EC2
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (WHIRR-540) Java Processes Terminate Immediately
when starting elasticsearch cluster at EC2
Posted by "Andrei Savu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrei Savu updated WHIRR-540:
------------------------------
Fix Version/s: (was: 0.8.0-alpha.1)
0.8.0
> 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
>
> Attachments: WHIRR-540.patch, elasticsearch_whirr.tar.gz
>
> 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
[jira] [Commented] (WHIRR-540) Java Processes Terminate Immediately
when starting elasticsearch cluster at EC2
Posted by "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
[jira] [Commented] (WHIRR-540) Java Processes Terminate Immediately
when starting elasticsearch cluster at EC2
Posted by "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=13218350#comment-13218350 ]
Andrei Savu commented on WHIRR-540:
-----------------------------------
Looks good. Before committing I will try to replicate the problem you are seeing by changing the integration test do index a document. Thanks!
> 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
>
> Attachments: WHIRR-540.patch, elasticsearch_whirr.tar.gz
>
> 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
[jira] [Updated] (WHIRR-540) Java Processes Terminate Immediately
when starting elasticsearch cluster at EC2
Posted by "eric chazan (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
eric chazan updated WHIRR-540:
------------------------------
Attachment: elasticsearch_whirr.tar.gz
> 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
>
> Attachments: elasticsearch_whirr.tar.gz
>
> 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
[jira] [Commented] (WHIRR-540) Java Processes Terminate Immediately
when starting elasticsearch cluster at EC2
Posted by "eric chazan (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13218340#comment-13218340 ]
eric chazan commented on WHIRR-540:
-----------------------------------
Sorry, I've never done this before. Let me know if the format is incorrect.
> 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
>
> Attachments: WHIRR-540.patch, elasticsearch_whirr.tar.gz
>
> 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
[jira] [Commented] (WHIRR-540) Java Processes Terminate Immediately
when starting elasticsearch cluster at EC2
Posted by "eric chazan (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13218184#comment-13218184 ]
eric chazan commented on WHIRR-540:
-----------------------------------
Thanks Andrei!
> 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
>
> Attachments: elasticsearch_whirr.tar.gz
>
> 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