GitHub user richardcloudsoft opened a pull request:
https://github.com/apache/brooklyn-library/pull/97
Bring ElasticSearch entity up-to-date
Switch to latest version, and fix issues that prevented the entity starting.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/rdowner/brooklyn-library
update-elasticsearch-entity
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/brooklyn-library/pull/97.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #97
----
commit 8a0b60e14356d4d2b220c5332c0b2017591f8f67
Author: Richard Downer <[email protected]>
Date: 2017-04-10T09:16:13Z
ElasticSearch: update config for newest version
Brings version up to 5.3.0, updates the download location URL, and
specifies the required version of Java to be 1.8.
commit dfcc39e83d9293fd3f8aba85fdaa84743b386f6f
Author: Richard Downer <[email protected]>
Date: 2017-04-10T09:17:17Z
ElasticSearch: fix command line options
Newest version changes the command line options. Fixes appropriately.
commit be5d101a3c35cab688330b74829f4db08edcf229
Author: Richard Downer <[email protected]>
Date: 2017-04-10T09:18:28Z
ElasticSearch: configure to listen on network i/f
Newest version defaults to listening on localhost only. Explicitly
configure listening on the network.
commit 87b6ff852be73d57121cb51a649d8f0e03c35060
Author: Richard Downer <[email protected]>
Date: 2017-04-10T09:19:46Z
ElasticSearch: ulimit/sysctl configuration updates
Newest version requires increased ulimit/sysctl values. Configure Linux
with the required values.
commit 31fac60d85d12e90b06553e622c5d38a0292f760
Author: Richard Downer <[email protected]>
Date: 2017-04-10T09:20:07Z
ElasticSearch: ulimit/sysctl configuration updates
Newest version requires increased ulimit/sysctl values. Apply values
immediately so that a reboot is not required.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
