Package Details: elasticsearch 8.17.0-1

Git Clone URL: https://aur.archlinux.org/elasticsearch.git (read-only, click to copy)
Package Base: elasticsearch
Description: Free and Open, Distributed, RESTful Search Engine
Upstream URL: https://www.elastic.co/elasticsearch/
Licenses: custom:Elastic-2.0
Conflicts: elasticsearch-bin, elasticsearch7
Provides: elasticsearch
Submitter: hashworks
Maintainer: ipaqmaster
Last Packager: ipaqmaster
Votes: 11
Popularity: 0.059864
First Submitted: 2022-01-08 16:30 (UTC)
Last Updated: 2024-12-12 16:50 (UTC)

Dependencies (2)

Required by (18)

Sources (9)

Latest Comments

« First ‹ Previous 1 .. 8 9 10 11 12 13 14 Next › Last »

hashworks commented on 2022-09-07 17:04 (UTC)

Please change the maintainer line in the PKGBUILD, it's no longer correct.

thenumeralone commented on 2022-09-01 22:26 (UTC) (edited on 2022-09-01 22:27 (UTC) by thenumeralone)

In 8.3.3-1 release, I get timeout errors from systemd while starting Elasticsearch up. This is caused because Elasticsearch now uses a forked process to notify systemd. Systemd ignores notifications from forked processes by default. In order to get systemd to not ignore the notifications, NotifyAccess=all needs to be added to elasticsearch.service.

kusoneko commented on 2022-07-18 00:26 (UTC)

I have made a modified PKGBUILD that allows elasticsearch to build on JDK 18, and thus stop blocking the update from 17 => 18. Link: https://gist.github.com/Kusoneko/32c2e627b12cb8dc8b6caae6d0aa4590

It isn't a massive change to the PKGBUILD and doesn't touch the code or source files at all, only adds a ">" to the makedepends, and in the build/package code point to openjdk-18 instead of openjdk-17.

kusoneko commented on 2022-05-10 22:53 (UTC)

According to the following git issue and pull requests, 8.2.0 (which is currently the version used here) should be able to compile and run on JDK 18, so there shouldn't be any more reason for this AUR package to continue blocking the upgrade of openjdk/jre packages to version 18.

https://github.com/elastic/elasticsearch/issues/85357 https://github.com/elastic/elasticsearch/pull/85875 https://github.com/elastic/elasticsearch/pull/85376

HLFH commented on 2022-04-18 13:55 (UTC)

Related to the JDK 18 issue: https://github.com/elastic/elasticsearch/pull/85376

I guess we need to wait for 8.1.4 release.

df8oe commented on 2022-04-06 10:13 (UTC)

Dependency to java-environment=17 points to an outdated version. It blocks updating to the recent version jdk-openjdk (18-2).

mailme_gx commented on 2022-04-04 12:39 (UTC) (edited on 2022-04-06 01:31 (UTC) by mailme_gx)

Ive installed elasticsearch 8.1.1-1 (with no existing data) and keep getting corruption issues.

it seems zlib-1:1.2.12-1-x86_64.pkg.tar.zst causes file corruption, reverting to zlib-1:1.2.11-5-x86_64.pkg.tar.zst works

Has no one else seen this problem?

So far I have had no response on archlinux forum nor elasticsearch github

https://bbs.archlinux.org/viewtopic.php?id=275249

https://github.com/elastic/elasticsearch/issues/85546

[EDIT] as per the bug report on github DaveCTurner pointed out it is a CPU specific issue Finally in proxmox change cpu (from kvm64) to Haswell - issue resolved!

srd commented on 2022-03-11 06:49 (UTC)

A hint for others trying to install this package using aura: I encountered the misleading dependency error aura >>= The package elasticsearch depends on version =17 of jdk11-openjdk, but the most recent version is 11.0.15.u3.

The version mismatch isn't regarding the jdk11-openjdk package, but the java environment itself. After installing the jdk-openjdk package (which supplies JRE 17), this package could be installed.

crabvk commented on 2022-03-06 21:03 (UTC)

Why the home dir of elasticsearch user is / and not /var/lib/elasticsearch?

brauliobo commented on 2022-02-18 11:14 (UTC)

indeed, configuring path.data is better

« First ‹ Previous 1 .. 8 9 10 11 12 13 14 Next › Last »