[Bug 902086] Review request: Elasticsearch

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



https://bugzilla.redhat.com/show_bug.cgi?id=902086



--- Comment #16 from Jörg Prante <joergprante@xxxxxx> ---
The vm.max_map_count setting is mainly required for better memory management
for virtual machines on Ubuntu/Debian, but it does not hurt to add it to the
systemd startup. 

More important is increasing the file descriptor limit from 1024 to a more
reasonable size (>10000 or even 65535).

Here is my idea: I would travel down the path like the Solr package build which
is at

https://bugzilla.redhat.com/show_bug.cgi?id=1025904

because both depend on Lucene.

I would like to contribute to offer a source RPM, but I do not know what is the
best point to start from. From what I understand I could install an F20 or
RHEL7 Beta for a private build system, or both?

>From there, I could build Solr RPMs, then make appropriate changes to build
Elasticsearch, so they are based on the same dependencies.

I'd like to note, because of sigar and jna, that means building for a noarch
target is not correct because there are architecture dependent shared
libraries. There should be a build for the target x86_64.

For many reasons, 32bit i686 target will result in some runtime glitches in
Elasticsearch (several memory tuning options rely on 64bit JVM). This is well
aligned with RHEL7 where there is no more 32bit support. So I'm not sure if a
32bit Elasticsearch RPM target would make sense.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component
_______________________________________________
package-review mailing list
package-review@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/package-review





[Index of Archives]     [Fedora Legacy]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]     [Fedora Tools]