Request: Please Test the RPM

Hey folks,

with the release of 0.90.0.RC2 we also released an official RPM package.
You can download it at
http://www.elasticsearch.org/downloads/0-90-0-rc2/

The initial thought was to provide one RPM for all distributions. During
packaging I already stumbled about some problems with this approach
(different locations of init script etc), so I would be very thankful to
get some feedback if the package works for you.

If systemd is available on your system, it is used for starting
elasticsearch automatically (for example on opensuse), otherwise chkconfig
is used.

I'd like to get some feedback if this one-rpm-to-rule-them-all approach is
feasible for our users at all, of if we have to provide more specialized
packages for the big RPM based distros.

Thanks a lot!

--Alex

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

I've just started using it (after building my own RPM
from https://github.com/tavisto/elasticsearch-rpms). I'm running OEL
(don't ask). Works dandy for me so thanks for that!

The only feedback I'd recommend (for me, don't know about anyone else) is
to not start the service after installing the RPM. I have some extra
customization that needs to be done post install (setting cluster.name
etc). As it stands right now, I stop the elasticsearch service right after
install then go about my config and start it back up.

On Thursday, April 11, 2013 4:28:00 AM UTC-5, Alexander Reelsen wrote:

Hey folks,

with the release of 0.90.0.RC2 we also released an official RPM package.
You can download it at
http://www.elasticsearch.org/downloads/0-90-0-rc2/

The initial thought was to provide one RPM for all distributions. During
packaging I already stumbled about some problems with this approach
(different locations of init script etc), so I would be very thankful to
get some feedback if the package works for you.

If systemd is available on your system, it is used for starting
elasticsearch automatically (for example on opensuse), otherwise chkconfig
is used.

I'd like to get some feedback if this one-rpm-to-rule-them-all approach is
feasible for our users at all, of if we have to provide more specialized
packages for the big RPM based distros.

Thanks a lot!

--Alex

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

+1 for not stopping/starting automatically a running ES node while
installing/updating the RPM. This would make updates with custom configs
or add-ons (plugins etc.) a nightmare.

I did not test the package, mostly because I build my own RPM on RHEL
with a spec of my plugins and custom config, also I prefer to include
the service wrapper. The service wrapper allows cross platform
start/stop function with nice auto restart so I can install ES on
Solaris just like on RHEL (yes, I ported RPM to Solaris SPARC, don't ask
why).

Also, I like to have multiple ES versions installed side-by-side. From
the install scripts, I assume there should be only one elasticsearch
version installable at once. Switching back and forth between versions
should be desirable, just like between Java JVM versions, maybe with
/usr/sbin/alternatives.

Jörg

Am 11.04.13 20:01, schrieb Andrew Ochsner:

I've just started using it (after building my own RPM
from https://github.com/tavisto/elasticsearch-rpms). I'm running OEL
(don't ask). Works dandy for me so thanks for that!

The only feedback I'd recommend (for me, don't know about anyone else)
is to not start the service after installing the RPM. I have some
extra customization that needs to be done post install (setting
cluster.name etc). As it stands right now, I stop the elasticsearch
service right after install then go about my config and start it back up.

On Thursday, April 11, 2013 4:28:00 AM UTC-5, Alexander Reelsen wrote:

Hey folks,

with the release of 0.90.0.RC2 we also released an official RPM
package. You can download it at
http://www.elasticsearch.org/downloads/0-90-0-rc2/
<http://www.elasticsearch.org/downloads/0-90-0-rc2/>

The initial thought was to provide one RPM for all distributions.
During packaging I already stumbled about some problems with this
approach (different locations of init script etc), so I would be
very thankful to get some feedback if the package works for you.

If systemd is available on your system, it is used for starting
elasticsearch automatically (for example on opensuse), otherwise
chkconfig is used.

I'd like to get some feedback if this one-rpm-to-rule-them-all
approach is feasible for our users at all, of if we have to
provide more specialized packages for the big RPM based distros.

Thanks a lot!


--Alex

--
You received this message because you are subscribed to the Google
Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

On Thu, 2013-04-11 at 20:27 +0200, Jörg Prante wrote:

+1 for not stopping/starting automatically a running ES node while
installing/updating the RPM. This would make updates with custom configs
or add-ons (plugins etc.) a nightmare.

agreed

Also, I like to have multiple ES versions installed side-by-side. From
the install scripts, I assume there should be only one elasticsearch
version installable at once. Switching back and forth between versions
should be desirable, just like between Java JVM versions, maybe with
/usr/sbin/alternatives.

I think this is an "expert" option, and ends up complicating things for
95% of users, who simply want the single latest version of ES installed.
If you have multiple versions then you also have to consider storing the
data in different directories etc.

Pretty much the only time you want multiple versions installed is for
testing and comparing, and it is so easy to just unzip ES into different
directories that I don't see the benefit of complicating the standard
RPM install to support it.

clint

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Oh, it's not complicated, just a version in the path name of the target
directory, such as "/var/lib/elasticsearch/0.90RC2", that's all.

Jörg

Am 12.04.13 12:24, schrieb Clinton Gormley:

Pretty much the only time you want multiple versions installed is for
testing and comparing, and it is so easy to just unzip ES into different
directories that I don't see the benefit of complicating the standard
RPM install to support it.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Hey there,

first, thanks to Andrew and Joerg for your feedback. We had exactly the
same discussion when creating the RPM. You both chose the administrator
friendly route, by making requests, which are a good fit for sysadmins. We
decided this RPM to be 'entry-level' usable. This means for us, that it is
most important to support beginners with this RPM. Therefore we tried to
adhere to other data stores in their behaviour. If you install mysql it
should work similar to elasticsearch by starting after installing, etc...
so you can start playing around with it.

The same applies for your version+path solution, you have to have some ES
knowledge in order to make use of this design decision.

Regarding the starting/stopping of elasticsearch. Is it feasible to have an
option in the configuration file - which decides if elasticsearch is
started/stopped on your node? I could add something like that in the
installation shell scripts.

--Alex

On Fri, Apr 12, 2013 at 3:50 PM, Jörg Prante joergprante@gmail.com wrote:

Oh, it's not complicated, just a version in the path name of the target
directory, such as "/var/lib/elasticsearch/0.**90RC2", that's all.

Jörg

Am 12.04.13 12:24, schrieb Clinton Gormley:

Pretty much the only time you want multiple versions installed is for

testing and comparing, and it is so easy to just unzip ES into different
directories that I don't see the benefit of complicating the standard
RPM install to support it.

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@**googlegroups.comelasticsearch%2Bunsubscribe@googlegroups.com
.
For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out
.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Just to add some thoughts because you mention mysql...

  • on every mysql upgrade, the user is recommended to backup the data first

  • the mysql server daemon does not touch tables or user generated data
    when being started after upgrade, instead, the user must run an extra
    upgrade script to get the data touched

  • there are different RPM-based upgrade "strategies" for
    Fedora/RHEL/Centos/OEL, where OEL customers must have a support
    agreement with Oracle, (there is also OpenSuse which I am not familiar with)

Fedora/Centos: Remi's repo, http://rpms.famillecollet.com/
MySQL RPM download: http://dev.mysql.com/downloads/mirror.php?id=411922
(Oracle account needed for download)
Oracle Linux: public YUM repo at
http://public-yum.oracle.com/repo/OracleLinux/OL6/MySQL/x86_64/

As you can see from Remi's effort

https://github.com/remicollet/remirepo/blob/master/mysql55/mysql55.spec

and

https://github.com/remicollet/remirepo/blob/master/mysql56/mysql56.spec

there are different RPM package spec per version, so you can easily
install MySQL 5.5 and 5.6 beside each other. Although I would prefer
installing with "rpm -i" and "rpm -U" for install/update of different
version.

Note the vendor-specific differences of handling mysql in RPM. Usually
the mysql daemon is restarted (with try-restart). From what I can read
in OEL's mysql.5.5.27.spec in
http://public-yum.oracle.com/repo/OracleLinux/OL6/MySQL/x86_64/mysql-5.5.27-1.el6.src.rpm
the mysql server daemon is stopped when being uninstalled, but not
started after installation. Since Oracle offers commercial support, this
should be considered as a feature.

In the current state of ES without backup/restore tooling and upgrade
scripts, the risk is that many first time users will simply run rpm,
while a restarted elasticsearch will then touch their data and maybe
ignore/modify/delete it (or just move a shard to another node,
whatever). This is definitely not the mysql way of thinking and I assume
this could be very demanding for offering successful support.

Note, you must always have superuser privileges to change files under
/usr or /etc , so in the suggested directory layout offered in the ES
RPM, ES is targeted to sysadmins but not to users. Maybe not true for
certain desktop-only Linux variants or VM instances, but I think RPM
managed ES will always run in a server environment.

Jörg

Am 15.04.13 08:35, schrieb Alexander Reelsen:

If you install mysql it should work similar to elasticsearch by
starting after installing, etc... so you can start playing around with it.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

I noticed the elasticsearch user's home directory gets set to
"/usr/lib/elasticsearch" It doesn't automatically create the directory (i
think that would be option -m). The problem I end up having is that when I
setup some cron jobs under elasticsearch user's crontab, it fails with
"CROND[25231]: (CRON) ERROR chdir failed (/usr/lib/elasticsearch): No such
file or directory"

Just checking if this is intentional. I'd actually probably prefer the
elasticsearch's home directory to be the ES_HOME
(/usr/share/elasticsearch)...

Thoughts?

On Monday, April 15, 2013 5:22:12 AM UTC-5, Jörg Prante wrote:

Just to add some thoughts because you mention mysql...

  • on every mysql upgrade, the user is recommended to backup the data first

  • the mysql server daemon does not touch tables or user generated data
    when being started after upgrade, instead, the user must run an extra
    upgrade script to get the data touched

  • there are different RPM-based upgrade "strategies" for
    Fedora/RHEL/Centos/OEL, where OEL customers must have a support
    agreement with Oracle, (there is also OpenSuse which I am not familiar
    with)

Fedora/Centos: Remi's repo, http://rpms.famillecollet.com/
MySQL RPM download: http://dev.mysql.com/downloads/mirror.php?id=411922
(Oracle account needed for download)
Oracle Linux: public YUM repo at
http://public-yum.oracle.com/repo/OracleLinux/OL6/MySQL/x86_64/

As you can see from Remi's effort

https://github.com/remicollet/remirepo/blob/master/mysql55/mysql55.spec

and

https://github.com/remicollet/remirepo/blob/master/mysql56/mysql56.spec

there are different RPM package spec per version, so you can easily
install MySQL 5.5 and 5.6 beside each other. Although I would prefer
installing with "rpm -i" and "rpm -U" for install/update of different
version.

Note the vendor-specific differences of handling mysql in RPM. Usually
the mysql daemon is restarted (with try-restart). From what I can read
in OEL's mysql.5.5.27.spec in

http://public-yum.oracle.com/repo/OracleLinux/OL6/MySQL/x86_64/mysql-5.5.27-1.el6.src.rpm
the mysql server daemon is stopped when being uninstalled, but not
started after installation. Since Oracle offers commercial support, this
should be considered as a feature.

In the current state of ES without backup/restore tooling and upgrade
scripts, the risk is that many first time users will simply run rpm,
while a restarted elasticsearch will then touch their data and maybe
ignore/modify/delete it (or just move a shard to another node,
whatever). This is definitely not the mysql way of thinking and I assume
this could be very demanding for offering successful support.

Note, you must always have superuser privileges to change files under
/usr or /etc , so in the suggested directory layout offered in the ES
RPM, ES is targeted to sysadmins but not to users. Maybe not true for
certain desktop-only Linux variants or VM instances, but I think RPM
managed ES will always run in a server environment.

Jörg

Am 15.04.13 08:35, schrieb Alexander Reelsen:

If you install mysql it should work similar to elasticsearch by
starting after installing, etc... so you can start playing around with
it.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Hey Andrew,

good point, will check and likely change that today. Thx a lot for your
reporting!

--Alex

On Thu, May 16, 2013 at 10:41 PM, Andrew Ochsner
aochsner@cs.stanford.eduwrote:

I noticed the elasticsearch user's home directory gets set to
"/usr/lib/elasticsearch" It doesn't automatically create the directory (i
think that would be option -m). The problem I end up having is that when I
setup some cron jobs under elasticsearch user's crontab, it fails with
"CROND[25231]: (CRON) ERROR chdir failed (/usr/lib/elasticsearch): No such
file or directory"

Just checking if this is intentional. I'd actually probably prefer the
elasticsearch's home directory to be the ES_HOME
(/usr/share/elasticsearch)...

Thoughts?

On Monday, April 15, 2013 5:22:12 AM UTC-5, Jörg Prante wrote:

Just to add some thoughts because you mention mysql...

  • on every mysql upgrade, the user is recommended to backup the data
    first

  • the mysql server daemon does not touch tables or user generated data
    when being started after upgrade, instead, the user must run an extra
    upgrade script to get the data touched

  • there are different RPM-based upgrade "strategies" for
    Fedora/RHEL/Centos/OEL, where OEL customers must have a support
    agreement with Oracle, (there is also OpenSuse which I am not familiar
    with)

Fedora/Centos: Remi's repo, http://rpms.famillecollet.com/
MySQL RPM download: http://dev.mysql.com/**downloads/mirror.php?id=411922http://dev.mysql.com/downloads/mirror.php?id=411922
(Oracle account needed for download)
Oracle Linux: public YUM repo at
http://public-yum.oracle.com/**repo/OracleLinux/OL6/MySQL/**x86_64/http://public-yum.oracle.com/repo/OracleLinux/OL6/MySQL/x86_64/

As you can see from Remi's effort

https://github.com/remicollet/remirepo/blob/master/mysql55/
mysql55.spechttps://github.com/remicollet/remirepo/blob/master/mysql55/mysql55.spec

and

https://github.com/remicollet/remirepo/blob/master/mysql56/
mysql56.spechttps://github.com/remicollet/remirepo/blob/master/mysql56/mysql56.spec

there are different RPM package spec per version, so you can easily
install MySQL 5.5 and 5.6 beside each other. Although I would prefer
installing with "rpm -i" and "rpm -U" for install/update of different
version.

Note the vendor-specific differences of handling mysql in RPM. Usually
the mysql daemon is restarted (with try-restart). From what I can read
in OEL's mysql.5.5.27.spec in
http://public-yum.oracle.com/repo/OracleLinux/OL6/MySQL/
x86_64/mysql-5.5.27-1.el6.src.**rpmhttp://public-yum.oracle.com/repo/OracleLinux/OL6/MySQL/x86_64/mysql-5.5.27-1.el6.src.rpm
the mysql server daemon is stopped when being uninstalled, but not
started after installation. Since Oracle offers commercial support, this
should be considered as a feature.

In the current state of ES without backup/restore tooling and upgrade
scripts, the risk is that many first time users will simply run rpm,
while a restarted elasticsearch will then touch their data and maybe
ignore/modify/delete it (or just move a shard to another node,
whatever). This is definitely not the mysql way of thinking and I assume
this could be very demanding for offering successful support.

Note, you must always have superuser privileges to change files under
/usr or /etc , so in the suggested directory layout offered in the ES
RPM, ES is targeted to sysadmins but not to users. Maybe not true for
certain desktop-only Linux variants or VM instances, but I think RPM
managed ES will always run in a server environment.

Jörg

Am 15.04.13 08:35, schrieb Alexander Reelsen:

If you install mysql it should work similar to elasticsearch by
starting after installing, etc... so you can start playing around with
it.

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Hi Alexander,
I just tried the RPM out with Fedora 18.

Worked fine for me, the only thing is I didn't know exactly where to find
the data directory, but the nodes info api luckily helped me out with that
:slight_smile:
I see it's under /var/lib/elasticsearch, where I have directly the
directory with the cluster name, which contains the nodes folder and so on.
I would have liked to see the data subfolder too there
(/var/lib/elasticsearch/data), but maybe that's me!

Let me know if I can help with other tests.

Thanks for the great work!

Luca

On Friday, May 17, 2013 8:40:42 AM UTC+2, Alexander Reelsen wrote:

Hey Andrew,

good point, will check and likely change that today. Thx a lot for your
reporting!

--Alex

On Thu, May 16, 2013 at 10:41 PM, Andrew Ochsner <aoch...@cs.stanford.edu<javascript:>

wrote:

I noticed the elasticsearch user's home directory gets set to
"/usr/lib/elasticsearch" It doesn't automatically create the directory (i
think that would be option -m). The problem I end up having is that when I
setup some cron jobs under elasticsearch user's crontab, it fails with
"CROND[25231]: (CRON) ERROR chdir failed (/usr/lib/elasticsearch): No such
file or directory"

Just checking if this is intentional. I'd actually probably prefer the
elasticsearch's home directory to be the ES_HOME
(/usr/share/elasticsearch)...

Thoughts?

On Monday, April 15, 2013 5:22:12 AM UTC-5, Jörg Prante wrote:

Just to add some thoughts because you mention mysql...

  • on every mysql upgrade, the user is recommended to backup the data
    first

  • the mysql server daemon does not touch tables or user generated data
    when being started after upgrade, instead, the user must run an extra
    upgrade script to get the data touched

  • there are different RPM-based upgrade "strategies" for
    Fedora/RHEL/Centos/OEL, where OEL customers must have a support
    agreement with Oracle, (there is also OpenSuse which I am not familiar
    with)

Fedora/Centos: Remi's repo, http://rpms.famillecollet.com/
MySQL RPM download: http://dev.mysql.com/**
downloads/mirror.php?id=411922http://dev.mysql.com/downloads/mirror.php?id=411922
(Oracle account needed for download)
Oracle Linux: public YUM repo at
http://public-yum.oracle.com/**repo/OracleLinux/OL6/MySQL/**x86_64/http://public-yum.oracle.com/repo/OracleLinux/OL6/MySQL/x86_64/

As you can see from Remi's effort

https://github.com/remicollet/remirepo/blob/master/mysql55/
mysql55.spechttps://github.com/remicollet/remirepo/blob/master/mysql55/mysql55.spec

and

https://github.com/remicollet/remirepo/blob/master/mysql56/
mysql56.spechttps://github.com/remicollet/remirepo/blob/master/mysql56/mysql56.spec

there are different RPM package spec per version, so you can easily
install MySQL 5.5 and 5.6 beside each other. Although I would prefer
installing with "rpm -i" and "rpm -U" for install/update of different
version.

Note the vendor-specific differences of handling mysql in RPM. Usually
the mysql daemon is restarted (with try-restart). From what I can read
in OEL's mysql.5.5.27.spec in
http://public-yum.oracle.com/repo/OracleLinux/OL6/MySQL/
x86_64/mysql-5.5.27-1.el6.src.**rpmhttp://public-yum.oracle.com/repo/OracleLinux/OL6/MySQL/x86_64/mysql-5.5.27-1.el6.src.rpm
the mysql server daemon is stopped when being uninstalled, but not
started after installation. Since Oracle offers commercial support, this
should be considered as a feature.

In the current state of ES without backup/restore tooling and upgrade
scripts, the risk is that many first time users will simply run rpm,
while a restarted elasticsearch will then touch their data and maybe
ignore/modify/delete it (or just move a shard to another node,
whatever). This is definitely not the mysql way of thinking and I assume
this could be very demanding for offering successful support.

Note, you must always have superuser privileges to change files under
/usr or /etc , so in the suggested directory layout offered in the ES
RPM, ES is targeted to sysadmins but not to users. Maybe not true for
certain desktop-only Linux variants or VM instances, but I think RPM
managed ES will always run in a server environment.

Jörg

Am 15.04.13 08:35, schrieb Alexander Reelsen:

If you install mysql it should work similar to elasticsearch by
starting after installing, etc... so you can start playing around with
it.

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearc...@googlegroups.com <javascript:>.
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

+1 for not stopping/starting automatically. Need to be able to make config changes + enable plugins before starting elasticsearch

Any chance we could add a logrotate.d/elasticsearch script to keep that at
a reasonable size?
https://github.com/tavisto/elasticsearch-rpms/blob/master/SOURCES/logrotate.d-elasticsearch might
be a reasonable place to start?

On Friday, May 17, 2013 1:38:06 PM UTC-5, Luca Cavanna wrote:

Hi Alexander,
I just tried the RPM out with Fedora 18.

Worked fine for me, the only thing is I didn't know exactly where to find
the data directory, but the nodes info api luckily helped me out with that
:slight_smile:
I see it's under /var/lib/elasticsearch, where I have directly the
directory with the cluster name, which contains the nodes folder and so on.
I would have liked to see the data subfolder too there
(/var/lib/elasticsearch/data), but maybe that's me!

Let me know if I can help with other tests.

Thanks for the great work!

Luca

On Friday, May 17, 2013 8:40:42 AM UTC+2, Alexander Reelsen wrote:

Hey Andrew,

good point, will check and likely change that today. Thx a lot for your
reporting!

--Alex

On Thu, May 16, 2013 at 10:41 PM, Andrew Ochsner <aoch...@cs.stanford.edu

wrote:

I noticed the elasticsearch user's home directory gets set to
"/usr/lib/elasticsearch" It doesn't automatically create the directory (i
think that would be option -m). The problem I end up having is that when I
setup some cron jobs under elasticsearch user's crontab, it fails with
"CROND[25231]: (CRON) ERROR chdir failed (/usr/lib/elasticsearch): No such
file or directory"

Just checking if this is intentional. I'd actually probably prefer the
elasticsearch's home directory to be the ES_HOME
(/usr/share/elasticsearch)...

Thoughts?

On Monday, April 15, 2013 5:22:12 AM UTC-5, Jörg Prante wrote:

Just to add some thoughts because you mention mysql...

  • on every mysql upgrade, the user is recommended to backup the data
    first

  • the mysql server daemon does not touch tables or user generated data
    when being started after upgrade, instead, the user must run an extra
    upgrade script to get the data touched

  • there are different RPM-based upgrade "strategies" for
    Fedora/RHEL/Centos/OEL, where OEL customers must have a support
    agreement with Oracle, (there is also OpenSuse which I am not familiar
    with)

Fedora/Centos: Remi's repo, http://rpms.famillecollet.com/
MySQL RPM download: http://dev.mysql.com/**
downloads/mirror.php?id=411922http://dev.mysql.com/downloads/mirror.php?id=411922
(Oracle account needed for download)
Oracle Linux: public YUM repo at
http://public-yum.oracle.com/**repo/OracleLinux/OL6/MySQL/**x86_64/http://public-yum.oracle.com/repo/OracleLinux/OL6/MySQL/x86_64/

As you can see from Remi's effort

https://github.com/remicollet/remirepo/blob/master/mysql55/
mysql55.spechttps://github.com/remicollet/remirepo/blob/master/mysql55/mysql55.spec

and

https://github.com/remicollet/remirepo/blob/master/mysql56/
mysql56.spechttps://github.com/remicollet/remirepo/blob/master/mysql56/mysql56.spec

there are different RPM package spec per version, so you can easily
install MySQL 5.5 and 5.6 beside each other. Although I would prefer
installing with "rpm -i" and "rpm -U" for install/update of different
version.

Note the vendor-specific differences of handling mysql in RPM. Usually
the mysql daemon is restarted (with try-restart). From what I can read
in OEL's mysql.5.5.27.spec in
http://public-yum.oracle.com/repo/OracleLinux/OL6/MySQL/
x86_64/mysql-5.5.27-1.el6.src.**rpmhttp://public-yum.oracle.com/repo/OracleLinux/OL6/MySQL/x86_64/mysql-5.5.27-1.el6.src.rpm
the mysql server daemon is stopped when being uninstalled, but not
started after installation. Since Oracle offers commercial support,
this
should be considered as a feature.

In the current state of ES without backup/restore tooling and upgrade
scripts, the risk is that many first time users will simply run rpm,
while a restarted elasticsearch will then touch their data and maybe
ignore/modify/delete it (or just move a shard to another node,
whatever). This is definitely not the mysql way of thinking and I
assume
this could be very demanding for offering successful support.

Note, you must always have superuser privileges to change files under
/usr or /etc , so in the suggested directory layout offered in the ES
RPM, ES is targeted to sysadmins but not to users. Maybe not true for
certain desktop-only Linux variants or VM instances, but I think RPM
managed ES will always run in a server environment.

Jörg

Am 15.04.13 08:35, schrieb Alexander Reelsen:

If you install mysql it should work similar to elasticsearch by
starting after installing, etc... so you can start playing around
with it.

--
You received this message because you are subscribed to the Google
Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to elasticsearc...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Hey Luca!

to be honest, I haven't thought too much about the data directory, but just
made sure it is the same in the debian package and the RPM in order to
avoid confusion there.

On another side note I am still not sure about starting and stopping after
installation and during upgrades. Someone on IRC mentioned that redhat
never starts a service after installing, so maybe we should change that.
Plenty of people with more knowledge about redhat based distributions and
RPMs have spoken out against it now :slight_smile:
Do you have any opinion on that?

--Alex

On Fri, May 17, 2013 at 8:38 PM, Luca Cavanna cavannaluca@gmail.com wrote:

Hi Alexander,
I just tried the RPM out with Fedora 18.

Worked fine for me, the only thing is I didn't know exactly where to find
the data directory, but the nodes info api luckily helped me out with that
:slight_smile:
I see it's under /var/lib/elasticsearch, where I have directly the
directory with the cluster name, which contains the nodes folder and so on.
I would have liked to see the data subfolder too there
(/var/lib/elasticsearch/data), but maybe that's me!

Let me know if I can help with other tests.

Thanks for the great work!

Luca

On Friday, May 17, 2013 8:40:42 AM UTC+2, Alexander Reelsen wrote:

Hey Andrew,

good point, will check and likely change that today. Thx a lot for your
reporting!

--Alex

On Thu, May 16, 2013 at 10:41 PM, Andrew Ochsner <aoch...@cs.stanford.edu

wrote:

I noticed the elasticsearch user's home directory gets set to
"/usr/lib/elasticsearch" It doesn't automatically create the directory (i
think that would be option -m). The problem I end up having is that when I
setup some cron jobs under elasticsearch user's crontab, it fails with
"CROND[25231]: (CRON) ERROR chdir failed (/usr/lib/elasticsearch): No such
file or directory"

Just checking if this is intentional. I'd actually probably prefer the
elasticsearch's home directory to be the ES_HOME
(/usr/share/elasticsearch)...

Thoughts?

On Monday, April 15, 2013 5:22:12 AM UTC-5, Jörg Prante wrote:

Just to add some thoughts because you mention mysql...

  • on every mysql upgrade, the user is recommended to backup the data
    first

  • the mysql server daemon does not touch tables or user generated data
    when being started after upgrade, instead, the user must run an extra
    upgrade script to get the data touched

  • there are different RPM-based upgrade "strategies" for
    Fedora/RHEL/Centos/OEL, where OEL customers must have a support
    agreement with Oracle, (there is also OpenSuse which I am not familiar
    with)

Fedora/Centos: Remi's repo, http://rpms.famillecollet.com/
MySQL RPM download: http://dev.mysql.com/downloads
/mirror.php?id=411922http://dev.mysql.com/downloads/mirror.php?id=411922
(Oracle account needed for download)
Oracle Linux: public YUM repo at
http://public-yum.oracle.com/repo/OracleLinux/OL6/MySQL/**x86_**64/http://public-yum.oracle.com/repo/OracleLinux/OL6/MySQL/x86_64/

As you can see from Remi's effort

https://github.com/remicollet/****remirepo/blob/master/mysql55/m
ysql55.spechttps://github.com/remicollet/remirepo/blob/master/mysql55/mysql55.spec

and

https://github.com/remicollet/****remirepo/blob/master/mysql56/m
ysql56.spechttps://github.com/remicollet/remirepo/blob/master/mysql56/mysql56.spec

there are different RPM package spec per version, so you can easily
install MySQL 5.5 and 5.6 beside each other. Although I would prefer
installing with "rpm -i" and "rpm -U" for install/update of different
version.

Note the vendor-specific differences of handling mysql in RPM. Usually
the mysql daemon is restarted (with try-restart). From what I can read
in OEL's mysql.5.5.27.spec in
http://public-yum.oracle.com/repo/OracleLinux/OL6/MySQL/x86_
64/mysql-5.5.27-1.el6.src.**rpmhttp://public-yum.oracle.com/repo/OracleLinux/OL6/MySQL/x86_64/mysql-5.5.27-1.el6.src.rpm
the mysql server daemon is stopped when being uninstalled, but not
started after installation. Since Oracle offers commercial support,
this
should be considered as a feature.

In the current state of ES without backup/restore tooling and upgrade
scripts, the risk is that many first time users will simply run rpm,
while a restarted elasticsearch will then touch their data and maybe
ignore/modify/delete it (or just move a shard to another node,
whatever). This is definitely not the mysql way of thinking and I
assume
this could be very demanding for offering successful support.

Note, you must always have superuser privileges to change files under
/usr or /etc , so in the suggested directory layout offered in the ES
RPM, ES is targeted to sysadmins but not to users. Maybe not true for
certain desktop-only Linux variants or VM instances, but I think RPM
managed ES will always run in a server environment.

Jörg

Am 15.04.13 08:35, schrieb Alexander Reelsen:

If you install mysql it should work similar to elasticsearch by
starting after installing, etc... so you can start playing around
with it.

--
You received this message because you are subscribed to the Google
Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to elasticsearc...@**googlegroups.com.

For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out
.

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Hey Andrew,

why not using a log4j configuration with rolling files for that?

--Alex

On Wed, May 22, 2013 at 11:02 PM, Andrew Ochsner
aochsner@cs.stanford.eduwrote:

Any chance we could add a logrotate.d/elasticsearch script to keep that at
a reasonable size?
https://github.com/tavisto/elasticsearch-rpms/blob/master/SOURCES/logrotate.d-elasticsearch might
be a reasonable place to start?

On Friday, May 17, 2013 1:38:06 PM UTC-5, Luca Cavanna wrote:

Hi Alexander,
I just tried the RPM out with Fedora 18.

Worked fine for me, the only thing is I didn't know exactly where to find
the data directory, but the nodes info api luckily helped me out with that
:slight_smile:
I see it's under /var/lib/elasticsearch, where I have directly the
directory with the cluster name, which contains the nodes folder and so on.
I would have liked to see the data subfolder too there
(/var/lib/elasticsearch/data), but maybe that's me!

Let me know if I can help with other tests.

Thanks for the great work!

Luca

On Friday, May 17, 2013 8:40:42 AM UTC+2, Alexander Reelsen wrote:

Hey Andrew,

good point, will check and likely change that today. Thx a lot for your
reporting!

--Alex

On Thu, May 16, 2013 at 10:41 PM, Andrew Ochsner <
aoch...@cs.stanford.edu> wrote:

I noticed the elasticsearch user's home directory gets set to
"/usr/lib/elasticsearch" It doesn't automatically create the directory (i
think that would be option -m). The problem I end up having is that when I
setup some cron jobs under elasticsearch user's crontab, it fails with
"CROND[25231]: (CRON) ERROR chdir failed (/usr/lib/elasticsearch): No such
file or directory"

Just checking if this is intentional. I'd actually probably prefer the
elasticsearch's home directory to be the ES_HOME
(/usr/share/elasticsearch)...

Thoughts?

On Monday, April 15, 2013 5:22:12 AM UTC-5, Jörg Prante wrote:

Just to add some thoughts because you mention mysql...

  • on every mysql upgrade, the user is recommended to backup the data
    first

  • the mysql server daemon does not touch tables or user generated data
    when being started after upgrade, instead, the user must run an extra
    upgrade script to get the data touched

  • there are different RPM-based upgrade "strategies" for
    Fedora/RHEL/Centos/OEL, where OEL customers must have a support
    agreement with Oracle, (there is also OpenSuse which I am not familiar
    with)

Fedora/Centos: Remi's repo, http://rpms.famillecollet.com/
MySQL RPM download: http://dev.mysql.com/downloads
/mirror.php?id=411922http://dev.mysql.com/downloads/mirror.php?id=411922
(Oracle account needed for download)
Oracle Linux: public YUM repo at
http://public-yum.oracle.com/repo/OracleLinux/OL6/MySQL/x86_
64/ http://public-yum.oracle.com/repo/OracleLinux/OL6/MySQL/x86_64/

As you can see from Remi's effort

https://github.com/remicollet/****remirepo/blob/master/mysql55/m
ysql55.spechttps://github.com/remicollet/remirepo/blob/master/mysql55/mysql55.spec

and

https://github.com/remicollet/****remirepo/blob/master/mysql56/m
ysql56.spechttps://github.com/remicollet/remirepo/blob/master/mysql56/mysql56.spec

there are different RPM package spec per version, so you can easily
install MySQL 5.5 and 5.6 beside each other. Although I would prefer
installing with "rpm -i" and "rpm -U" for install/update of different
version.

Note the vendor-specific differences of handling mysql in RPM. Usually
the mysql daemon is restarted (with try-restart). From what I can read
in OEL's mysql.5.5.27.spec in
http://public-yum.oracle.com/repo/OracleLinux/OL6/MySQL/x86_
64/mysql-5.5.27-1.el6.src.**rpmhttp://public-yum.oracle.com/repo/OracleLinux/OL6/MySQL/x86_64/mysql-5.5.27-1.el6.src.rpm
the mysql server daemon is stopped when being uninstalled, but not
started after installation. Since Oracle offers commercial support,
this
should be considered as a feature.

In the current state of ES without backup/restore tooling and upgrade
scripts, the risk is that many first time users will simply run rpm,
while a restarted elasticsearch will then touch their data and maybe
ignore/modify/delete it (or just move a shard to another node,
whatever). This is definitely not the mysql way of thinking and I
assume
this could be very demanding for offering successful support.

Note, you must always have superuser privileges to change files under
/usr or /etc , so in the suggested directory layout offered in the ES
RPM, ES is targeted to sysadmins but not to users. Maybe not true for
certain desktop-only Linux variants or VM instances, but I think RPM
managed ES will always run in a server environment.

Jörg

Am 15.04.13 08:35, schrieb Alexander Reelsen:

If you install mysql it should work similar to elasticsearch by
starting after installing, etc... so you can start playing around
with it.

--
You received this message because you are subscribed to the Google
Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to elasticsearc...@googlegroups.**com.
For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out
.

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Hey Alexander,
no worries about the data directory.

Regarding starting the service, I'm personally against starting it
automatically. On the other hand, for beginners it's probably better to do
it as I previously read, isn't it?

Up to you :wink:

Luca

On Thu, May 23, 2013 at 8:30 AM, Alexander Reelsen alr@spinscale.de wrote:

Hey Luca!

to be honest, I haven't thought too much about the data directory, but
just made sure it is the same in the debian package and the RPM in order to
avoid confusion there.

On another side note I am still not sure about starting and stopping after
installation and during upgrades. Someone on IRC mentioned that redhat
never starts a service after installing, so maybe we should change that.
Plenty of people with more knowledge about redhat based distributions and
RPMs have spoken out against it now :slight_smile:
Do you have any opinion on that?

--Alex

On Fri, May 17, 2013 at 8:38 PM, Luca Cavanna cavannaluca@gmail.comwrote:

Hi Alexander,
I just tried the RPM out with Fedora 18.

Worked fine for me, the only thing is I didn't know exactly where to find
the data directory, but the nodes info api luckily helped me out with that
:slight_smile:
I see it's under /var/lib/elasticsearch, where I have directly the
directory with the cluster name, which contains the nodes folder and so on.
I would have liked to see the data subfolder too there
(/var/lib/elasticsearch/data), but maybe that's me!

Let me know if I can help with other tests.

Thanks for the great work!

Luca

On Friday, May 17, 2013 8:40:42 AM UTC+2, Alexander Reelsen wrote:

Hey Andrew,

good point, will check and likely change that today. Thx a lot for your
reporting!

--Alex

On Thu, May 16, 2013 at 10:41 PM, Andrew Ochsner <
aoch...@cs.stanford.edu> wrote:

I noticed the elasticsearch user's home directory gets set to
"/usr/lib/elasticsearch" It doesn't automatically create the directory (i
think that would be option -m). The problem I end up having is that when I
setup some cron jobs under elasticsearch user's crontab, it fails with
"CROND[25231]: (CRON) ERROR chdir failed (/usr/lib/elasticsearch): No such
file or directory"

Just checking if this is intentional. I'd actually probably prefer the
elasticsearch's home directory to be the ES_HOME
(/usr/share/elasticsearch)...

Thoughts?

On Monday, April 15, 2013 5:22:12 AM UTC-5, Jörg Prante wrote:

Just to add some thoughts because you mention mysql...

  • on every mysql upgrade, the user is recommended to backup the data
    first

  • the mysql server daemon does not touch tables or user generated data
    when being started after upgrade, instead, the user must run an extra
    upgrade script to get the data touched

  • there are different RPM-based upgrade "strategies" for
    Fedora/RHEL/Centos/OEL, where OEL customers must have a support
    agreement with Oracle, (there is also OpenSuse which I am not familiar
    with)

Fedora/Centos: Remi's repo, http://rpms.famillecollet.com/
MySQL RPM download: http://dev.mysql.com/downloads
/mirror.php?id=411922http://dev.mysql.com/downloads/mirror.php?id=411922
(Oracle account needed for download)
Oracle Linux: public YUM repo at
http://public-yum.oracle.com/repo/OracleLinux/OL6/MySQL/x86_
64/ http://public-yum.oracle.com/repo/OracleLinux/OL6/MySQL/x86_64/

As you can see from Remi's effort

https://github.com/remicollet/****remirepo/blob/master/mysql55/m
ysql55.spechttps://github.com/remicollet/remirepo/blob/master/mysql55/mysql55.spec

and

https://github.com/remicollet/****remirepo/blob/master/mysql56/m
ysql56.spechttps://github.com/remicollet/remirepo/blob/master/mysql56/mysql56.spec

there are different RPM package spec per version, so you can easily
install MySQL 5.5 and 5.6 beside each other. Although I would prefer
installing with "rpm -i" and "rpm -U" for install/update of different
version.

Note the vendor-specific differences of handling mysql in RPM. Usually
the mysql daemon is restarted (with try-restart). From what I can read
in OEL's mysql.5.5.27.spec in
http://public-yum.oracle.com/repo/OracleLinux/OL6/MySQL/x86_
64/mysql-5.5.27-1.el6.src.**rpmhttp://public-yum.oracle.com/repo/OracleLinux/OL6/MySQL/x86_64/mysql-5.5.27-1.el6.src.rpm
the mysql server daemon is stopped when being uninstalled, but not
started after installation. Since Oracle offers commercial support,
this
should be considered as a feature.

In the current state of ES without backup/restore tooling and upgrade
scripts, the risk is that many first time users will simply run rpm,
while a restarted elasticsearch will then touch their data and maybe
ignore/modify/delete it (or just move a shard to another node,
whatever). This is definitely not the mysql way of thinking and I
assume
this could be very demanding for offering successful support.

Note, you must always have superuser privileges to change files under
/usr or /etc , so in the suggested directory layout offered in the ES
RPM, ES is targeted to sysadmins but not to users. Maybe not true for
certain desktop-only Linux variants or VM instances, but I think RPM
managed ES will always run in a server environment.

Jörg

Am 15.04.13 08:35, schrieb Alexander Reelsen:

If you install mysql it should work similar to elasticsearch by
starting after installing, etc... so you can start playing around
with it.

--
You received this message because you are subscribed to the Google
Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to elasticsearc...@**googlegroups.com.

For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out
.

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/Ouwjuyawte0/unsubscribe?hl=en-US
.
To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Well, I'm not aware of any log4j configuration where it can limit the
number of days to keep. Can do that if you limit by size but not date...
No big deal, just thought i'd throw it out there

On Thursday, May 23, 2013 1:31:01 AM UTC-5, Alexander Reelsen wrote:

Hey Andrew,

why not using a log4j configuration with rolling files for that?

--Alex

On Wed, May 22, 2013 at 11:02 PM, Andrew Ochsner <aoch...@cs.stanford.edu<javascript:>

wrote:

Any chance we could add a logrotate.d/elasticsearch script to keep that
at a reasonable size?
https://github.com/tavisto/elasticsearch-rpms/blob/master/SOURCES/logrotate.d-elasticsearch might
be a reasonable place to start?

On Friday, May 17, 2013 1:38:06 PM UTC-5, Luca Cavanna wrote:

Hi Alexander,
I just tried the RPM out with Fedora 18.

Worked fine for me, the only thing is I didn't know exactly where to
find the data directory, but the nodes info api luckily helped me out with
that :slight_smile:
I see it's under /var/lib/elasticsearch, where I have directly the
directory with the cluster name, which contains the nodes folder and so on.
I would have liked to see the data subfolder too there
(/var/lib/elasticsearch/data), but maybe that's me!

Let me know if I can help with other tests.

Thanks for the great work!

Luca

On Friday, May 17, 2013 8:40:42 AM UTC+2, Alexander Reelsen wrote:

Hey Andrew,

good point, will check and likely change that today. Thx a lot for your
reporting!

--Alex

On Thu, May 16, 2013 at 10:41 PM, Andrew Ochsner <
aoch...@cs.stanford.edu> wrote:

I noticed the elasticsearch user's home directory gets set to
"/usr/lib/elasticsearch" It doesn't automatically create the directory (i
think that would be option -m). The problem I end up having is that when I
setup some cron jobs under elasticsearch user's crontab, it fails with
"CROND[25231]: (CRON) ERROR chdir failed (/usr/lib/elasticsearch): No such
file or directory"

Just checking if this is intentional. I'd actually probably prefer
the elasticsearch's home directory to be the ES_HOME
(/usr/share/elasticsearch)...

Thoughts?

On Monday, April 15, 2013 5:22:12 AM UTC-5, Jörg Prante wrote:

Just to add some thoughts because you mention mysql...

  • on every mysql upgrade, the user is recommended to backup the data
    first

  • the mysql server daemon does not touch tables or user generated
    data
    when being started after upgrade, instead, the user must run an extra
    upgrade script to get the data touched

  • there are different RPM-based upgrade "strategies" for
    Fedora/RHEL/Centos/OEL, where OEL customers must have a support
    agreement with Oracle, (there is also OpenSuse which I am not
    familiar with)

Fedora/Centos: Remi's repo, http://rpms.famillecollet.com/
MySQL RPM download: http://dev.mysql.com/downloads
/mirror.php?id=411922http://dev.mysql.com/downloads/mirror.php?id=411922
(Oracle account needed for download)
Oracle Linux: public YUM repo at
http://public-yum.oracle.com/repo/OracleLinux/OL6/MySQL/x86_
64/ http://public-yum.oracle.com/repo/OracleLinux/OL6/MySQL/x86_64/

As you can see from Remi's effort

https://github.com/remicollet/****remirepo/blob/master/mysql55/m
ysql55.spechttps://github.com/remicollet/remirepo/blob/master/mysql55/mysql55.spec

and

https://github.com/remicollet/****remirepo/blob/master/mysql56/m
ysql56.spechttps://github.com/remicollet/remirepo/blob/master/mysql56/mysql56.spec

there are different RPM package spec per version, so you can easily
install MySQL 5.5 and 5.6 beside each other. Although I would prefer
installing with "rpm -i" and "rpm -U" for install/update of different
version.

Note the vendor-specific differences of handling mysql in RPM.
Usually
the mysql daemon is restarted (with try-restart). From what I can
read
in OEL's mysql.5.5.27.spec in
http://public-yum.oracle.com/repo/OracleLinux/OL6/MySQL/x86_
64/mysql-5.5.27-1.el6.src.**rpmhttp://public-yum.oracle.com/repo/OracleLinux/OL6/MySQL/x86_64/mysql-5.5.27-1.el6.src.rpm
the mysql server daemon is stopped when being uninstalled, but not
started after installation. Since Oracle offers commercial support,
this
should be considered as a feature.

In the current state of ES without backup/restore tooling and upgrade
scripts, the risk is that many first time users will simply run rpm,
while a restarted elasticsearch will then touch their data and maybe
ignore/modify/delete it (or just move a shard to another node,
whatever). This is definitely not the mysql way of thinking and I
assume
this could be very demanding for offering successful support.

Note, you must always have superuser privileges to change files under
/usr or /etc , so in the suggested directory layout offered in the ES
RPM, ES is targeted to sysadmins but not to users. Maybe not true for
certain desktop-only Linux variants or VM instances, but I think RPM
managed ES will always run in a server environment.

Jörg

Am 15.04.13 08:35, schrieb Alexander Reelsen:

If you install mysql it should work similar to elasticsearch by
starting after installing, etc... so you can start playing around
with it.

--
You received this message because you are subscribed to the Google
Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to elasticsearc...@googlegroups.**com.
For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out
.

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearc...@googlegroups.com <javascript:>.
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Hey,

I think the option is called MaxBackupIndex in log4j (on top of my head, no
100% guarantee), which allows you to control how many logfiles you want to
keep.

--Alex

On Thu, May 23, 2013 at 4:15 PM, Andrew Ochsner aochsner@cs.stanford.eduwrote:

Well, I'm not aware of any log4j configuration where it can limit the
number of days to keep. Can do that if you limit by size but not date...
No big deal, just thought i'd throw it out there

On Thursday, May 23, 2013 1:31:01 AM UTC-5, Alexander Reelsen wrote:

Hey Andrew,

why not using a log4j configuration with rolling files for that?

--Alex

On Wed, May 22, 2013 at 11:02 PM, Andrew Ochsner <aoch...@cs.stanford.edu

wrote:

Any chance we could add a logrotate.d/elasticsearch script to keep that
at a reasonable size? https://github.com/tavisto/**
elasticsearch-rpms/blob/**master/SOURCES/logrotate.d-**elasticsearchhttps://github.com/tavisto/elasticsearch-rpms/blob/master/SOURCES/logrotate.d-elasticsearch might
be a reasonable place to start?

On Friday, May 17, 2013 1:38:06 PM UTC-5, Luca Cavanna wrote:

Hi Alexander,
I just tried the RPM out with Fedora 18.

Worked fine for me, the only thing is I didn't know exactly where to
find the data directory, but the nodes info api luckily helped me out with
that :slight_smile:
I see it's under /var/lib/elasticsearch, where I have directly the
directory with the cluster name, which contains the nodes folder and so on.
I would have liked to see the data subfolder too there
(/var/lib/elasticsearch/data), but maybe that's me!

Let me know if I can help with other tests.

Thanks for the great work!

Luca

On Friday, May 17, 2013 8:40:42 AM UTC+2, Alexander Reelsen wrote:

Hey Andrew,

good point, will check and likely change that today. Thx a lot for
your reporting!

--Alex

On Thu, May 16, 2013 at 10:41 PM, Andrew Ochsner <
aoch...@cs.stanford.edu> wrote:

I noticed the elasticsearch user's home directory gets set to
"/usr/lib/elasticsearch" It doesn't automatically create the directory (i
think that would be option -m). The problem I end up having is that when I
setup some cron jobs under elasticsearch user's crontab, it fails with
"CROND[25231]: (CRON) ERROR chdir failed (/usr/lib/elasticsearch): No such
file or directory"

Just checking if this is intentional. I'd actually probably prefer
the elasticsearch's home directory to be the ES_HOME
(/usr/share/elasticsearch)...

Thoughts?

On Monday, April 15, 2013 5:22:12 AM UTC-5, Jörg Prante wrote:

Just to add some thoughts because you mention mysql...

  • on every mysql upgrade, the user is recommended to backup the data
    first

  • the mysql server daemon does not touch tables or user generated
    data
    when being started after upgrade, instead, the user must run an
    extra
    upgrade script to get the data touched

  • there are different RPM-based upgrade "strategies" for
    Fedora/RHEL/Centos/OEL, where OEL customers must have a support
    agreement with Oracle, (there is also OpenSuse which I am not
    familiar with)

Fedora/Centos: Remi's repo, http://rpms.famillecollet.com/
MySQL RPM download: http://dev.mysql.com/downloads**
/mirror.php?id=411922http://dev.mysql.com/downloads/mirror.php?id=411922
(Oracle account needed for download)
Oracle Linux: public YUM repo at
http://public-yum.oracle.com/**r****epo/OracleLinux/OL6/MySQL/**x86_
****64/http://public-yum.oracle.com/repo/OracleLinux/OL6/MySQL/x86_64/

As you can see from Remi's effort

https://github.com/remicollet/******remirepo/blob/master/mysql55/**m
****ysql55.spechttps://github.com/remicollet/remirepo/blob/master/mysql55/mysql55.spec

and

https://github.com/remicollet/******remirepo/blob/master/mysql56/**m
****ysql56.spechttps://github.com/remicollet/remirepo/blob/master/mysql56/mysql56.spec

there are different RPM package spec per version, so you can easily
install MySQL 5.5 and 5.6 beside each other. Although I would prefer
installing with "rpm -i" and "rpm -U" for install/update of
different
version.

Note the vendor-specific differences of handling mysql in RPM.
Usually
the mysql daemon is restarted (with try-restart). From what I can
read
in OEL's mysql.5.5.27.spec in
http://public-yum.oracle.com/**r****epo/OracleLinux/OL6/MySQL/**x86_
****64/mysql-5.5.27-1.el6.src.**rpmhttp://public-yum.oracle.com/repo/OracleLinux/OL6/MySQL/x86_64/mysql-5.5.27-1.el6.src.rpm
the mysql server daemon is stopped when being uninstalled, but not
started after installation. Since Oracle offers commercial support,
this
should be considered as a feature.

In the current state of ES without backup/restore tooling and
upgrade
scripts, the risk is that many first time users will simply run rpm,
while a restarted elasticsearch will then touch their data and maybe
ignore/modify/delete it (or just move a shard to another node,
whatever). This is definitely not the mysql way of thinking and I
assume
this could be very demanding for offering successful support.

Note, you must always have superuser privileges to change files
under
/usr or /etc , so in the suggested directory layout offered in the
ES
RPM, ES is targeted to sysadmins but not to users. Maybe not true
for
certain desktop-only Linux variants or VM instances, but I think RPM
managed ES will always run in a server environment.

Jörg

Am 15.04.13 08:35, schrieb Alexander Reelsen:

If you install mysql it should work similar to elasticsearch by
starting after installing, etc... so you can start playing around
with it.

--
You received this message because you are subscribed to the Google
Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to elasticsearc...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_outhttps://groups.google.com/groups/opt_out
.

--
You received this message because you are subscribed to the Google
Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to elasticsearc...@**googlegroups.com.
For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out
.

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Yep, unfortunately that only applies to the RollingFileAppender not the
DailyRollingFileAppender... http://stackoverflow.com/questions/896530/use-maxbackupindex-in-dailyrollingfileappender-log4j

On Thursday, May 23, 2013 10:16:29 AM UTC-5, Alexander Reelsen wrote:

Hey,

I think the option is called MaxBackupIndex in log4j (on top of my head,
no 100% guarantee), which allows you to control how many logfiles you want
to keep.

--Alex

On Thu, May 23, 2013 at 4:15 PM, Andrew Ochsner <aoch...@cs.stanford.edu<javascript:>

wrote:

Well, I'm not aware of any log4j configuration where it can limit the
number of days to keep. Can do that if you limit by size but not date...
No big deal, just thought i'd throw it out there

On Thursday, May 23, 2013 1:31:01 AM UTC-5, Alexander Reelsen wrote:

Hey Andrew,

why not using a log4j configuration with rolling files for that?

--Alex

On Wed, May 22, 2013 at 11:02 PM, Andrew Ochsner <
aoch...@cs.stanford.edu> wrote:

Any chance we could add a logrotate.d/elasticsearch script to keep that
at a reasonable size? https://github.com/tavisto/**
elasticsearch-rpms/blob/**master/SOURCES/logrotate.d-**elasticsearchhttps://github.com/tavisto/elasticsearch-rpms/blob/master/SOURCES/logrotate.d-elasticsearch might
be a reasonable place to start?

On Friday, May 17, 2013 1:38:06 PM UTC-5, Luca Cavanna wrote:

Hi Alexander,
I just tried the RPM out with Fedora 18.

Worked fine for me, the only thing is I didn't know exactly where to
find the data directory, but the nodes info api luckily helped me out with
that :slight_smile:
I see it's under /var/lib/elasticsearch, where I have directly the
directory with the cluster name, which contains the nodes folder and so on.
I would have liked to see the data subfolder too there
(/var/lib/elasticsearch/data), but maybe that's me!

Let me know if I can help with other tests.

Thanks for the great work!

Luca

On Friday, May 17, 2013 8:40:42 AM UTC+2, Alexander Reelsen wrote:

Hey Andrew,

good point, will check and likely change that today. Thx a lot for
your reporting!

--Alex

On Thu, May 16, 2013 at 10:41 PM, Andrew Ochsner <
aoch...@cs.stanford.edu> wrote:

I noticed the elasticsearch user's home directory gets set to
"/usr/lib/elasticsearch" It doesn't automatically create the directory (i
think that would be option -m). The problem I end up having is that when I
setup some cron jobs under elasticsearch user's crontab, it fails with
"CROND[25231]: (CRON) ERROR chdir failed (/usr/lib/elasticsearch): No such
file or directory"

Just checking if this is intentional. I'd actually probably prefer
the elasticsearch's home directory to be the ES_HOME
(/usr/share/elasticsearch)...

Thoughts?

On Monday, April 15, 2013 5:22:12 AM UTC-5, Jörg Prante wrote:

Just to add some thoughts because you mention mysql...

  • on every mysql upgrade, the user is recommended to backup the
    data first

  • the mysql server daemon does not touch tables or user generated
    data
    when being started after upgrade, instead, the user must run an
    extra
    upgrade script to get the data touched

  • there are different RPM-based upgrade "strategies" for
    Fedora/RHEL/Centos/OEL, where OEL customers must have a support
    agreement with Oracle, (there is also OpenSuse which I am not
    familiar with)

Fedora/Centos: Remi's repo, http://rpms.famillecollet.com/
MySQL RPM download: http://dev.mysql.com/downloads**
/mirror.php?id=411922http://dev.mysql.com/downloads/mirror.php?id=411922
(Oracle account needed for download)
Oracle Linux: public YUM repo at
http://public-yum.oracle.com/r****epo/OracleLinux/OL6/MySQL/
x86_****64/http://public-yum.oracle.com/repo/OracleLinux/OL6/MySQL/x86_64/

As you can see from Remi's effort

https://github.com/remicollet/remirepo/blob/master/mysql55/
m
ysql55.spechttps://github.com/remicollet/remirepo/blob/master/mysql55/mysql55.spec

and

https://github.com/remicollet/remirepo/blob/master/mysql56/
m
ysql56.spechttps://github.com/remicollet/remirepo/blob/master/mysql56/mysql56.spec

there are different RPM package spec per version, so you can easily
install MySQL 5.5 and 5.6 beside each other. Although I would
prefer
installing with "rpm -i" and "rpm -U" for install/update of
different
version.

Note the vendor-specific differences of handling mysql in RPM.
Usually
the mysql daemon is restarted (with try-restart). From what I can
read
in OEL's mysql.5.5.27.spec in
http://public-yum.oracle.com/r****epo/OracleLinux/OL6/MySQL/
x86_****64/mysql-5.5.27-1.el6.src.**rpmhttp://public-yum.oracle.com/repo/OracleLinux/OL6/MySQL/x86_64/mysql-5.5.27-1.el6.src.rpm
the mysql server daemon is stopped when being uninstalled, but not
started after installation. Since Oracle offers commercial support,
this
should be considered as a feature.

In the current state of ES without backup/restore tooling and
upgrade
scripts, the risk is that many first time users will simply run
rpm,
while a restarted elasticsearch will then touch their data and
maybe
ignore/modify/delete it (or just move a shard to another node,
whatever). This is definitely not the mysql way of thinking and I
assume
this could be very demanding for offering successful support.

Note, you must always have superuser privileges to change files
under
/usr or /etc , so in the suggested directory layout offered in the
ES
RPM, ES is targeted to sysadmins but not to users. Maybe not true
for
certain desktop-only Linux variants or VM instances, but I think
RPM
managed ES will always run in a server environment.

Jörg

Am 15.04.13 08:35, schrieb Alexander Reelsen:

If you install mysql it should work similar to elasticsearch by
starting after installing, etc... so you can start playing around
with it.

--
You received this message because you are subscribed to the Google
Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to elasticsearc...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_outhttps://groups.google.com/groups/opt_out
.

--
You received this message because you are subscribed to the Google
Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to elasticsearc...@**googlegroups.com.
For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out
.

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearc...@googlegroups.com <javascript:>.
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.