Whirr
  1. Whirr
  2. WHIRR-540

Java Processes Terminate Immediately when starting elasticsearch cluster at EC2

    Details

    • Type: Bug Bug
    • Status: Patch Available
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 0.7.1
    • Fix Version/s: 0.9.0
    • Component/s: service/elasticsearch
    • Labels:
    • Environment:

      EC2 attempting to run 5 M1 Large Instances

      Description

      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.

      1. WHIRR-540.patch
        3 kB
        eric chazan
      2. elasticsearch_whirr.tar.gz
        2 kB
        eric chazan

        Activity

          People

          • Assignee:
            Unassigned
            Reporter:
            eric chazan
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:

              Time Tracking

              Estimated:
              Original Estimate - 3h
              3h
              Remaining:
              Remaining Estimate - 3h
              3h
              Logged:
              Time Spent - Not Specified
              Not Specified

                Development