BSD Ports

textproc/elasticsearch8 8.11.3 DragonFly

Distributed, RESTful search and analytics engine

System
DragonFly
Repository
DPorts
Maintainer
[email protected] (as in FreeBSD)
License
APACHE20
Categories
devel, java, textproc
Package size
238241.1 KiB, 427269.2 KiB installed

Description

Elasticsearch is a distributed, RESTful search and analytics engine capable of addressing a growing number of use cases. As the heart of the Elastic Stack, it centrally stores your data for lightning fast search, fine-tuned relevancy, and powerful analytics that scale with ease.

In the other systems

SystemPortVersion
DragonFlytextproc/elasticsearch88.11.3
FreeBSDtextproc/elasticsearch88.11.3_2
MidnightBSDtextproc/elasticsearch88.19.23
HardenedBSDtextproc/elasticsearch88.11.3_2
GhostBSDtextproc/elasticsearch88.11.3_2

Install

Binary package:

pkg install elasticsearch8

From DPorts:

cd /usr/dports/textproc/elasticsearch8 && make install clean

Dependencies

Run dependencies 3

No port depends on this one.

Configuration

No options to configure.

Service scripts
none

Message after installing

Please see /usr/local/etc/elasticsearch for sample versions of
elasticsearch.yml and logging.yml.

ElasticSearch requires memory locking of large amounts of RAM.
You may need to set:

sysctl security.bsd.unprivileged_mlock=1

When running within a jail, it's highly advisable to set:

enforce_statfs = 1

for the jail running elasticsearch instance.

NOTICE: elasticsearch port now installs elasticsearch-specific utilities
as symbolic links into /usr/local/bin.

!!! PLUGINS NOTICE !!!

ElasticSearch plugins should only be installed via the elasticsearch-plugin
included with this software. As we strive to provide a minimum semblance
of security, the files installed by the package are owned by root:wheel.
This is different than upstream which expects all of the files to be
owned by the user and for you to execute the elasticsearch-plugin script
as said user.

You will encounter permissions errors with configuration files and
directories created by plugins which you will have to manually correct.
This is the price we have to pay to protect ourselves in the face of
a poorly designed security model.

e.g., after installing X-Pack you will have to correct:

/usr/local/etc/elasticsearch/elasticsearch.keystore file to be owned by elasticsearch:elasticsearch
/usr/local/etc/elasticsearch/x-pack directory/files to be owned by elasticsearch:elasticsearch

!!! PLUGINS NOTICE !!!