You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Brandon Williams (Jira)" <ji...@apache.org> on 2021/07/13 21:20:00 UTC
[jira] [Comment Edited] (CASSANDRA-14500) Debian package to include
systemd file and conf
[ https://issues.apache.org/jira/browse/CASSANDRA-14500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17380171#comment-17380171 ]
Brandon Williams edited comment on CASSANDRA-14500 at 7/13/21, 9:19 PM:
------------------------------------------------------------------------
The comments about increasing the limits are spot on, they are far too low in the patch as-is.
Regarding autostarting on install, this has been a long argument with polarized sides for some time, so in my opinion it's a matter of preference and this way was chosen to match other packaged services at the time, because installing and _not_ starting is something that also bites new users. I believe where it was last left was that we could make it configurable with debconf or something like that, but we'd still have to pick a default. In any case it's probably too large a conversation for this ticket and worthy of its own if we'd like to revisit that behavior.
was (Author: brandon.williams):
The comments about increasing the limits are spot on, they are far too low in the patch as-is.
Regarding autostarting on install, this has been a long argument with polarized sides for some time, so in my opinion it's a matter of preference and this way was chosen to match other packaged services at the time, because installing and _not_ starting is something that also bites new users. I believe where it was last left was that we could make it configurable with debconf or something like that, but we'd still have to pick a default.
> Debian package to include systemd file and conf
> -----------------------------------------------
>
> Key: CASSANDRA-14500
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14500
> Project: Cassandra
> Issue Type: Improvement
> Components: Packaging
> Reporter: Lerh Chuan Low
> Assignee: Lerh Chuan Low
> Priority: Low
>
> I've been testing Cassandra on trunk on Debian stretch, and have been creating my own systemd service files for Cassandra. My Cassandra clusters would sometimes die due to too many open files.
> As it turns out after some digging, this is because systemd ignores */etc/security/limits.conf.* It relies on a configuration file in <service-name>.d/<service-name>.conf. There's more information here: [https://www.freedesktop.org/software/systemd/man/systemd-system.conf.html].
> So, for example, for */etc/systemd/system/cassandra.service*, the ulimits are read from */etc/systemd/system/cassandra.service.d/cassandra.conf*.
> Crosschecking with the limits of my Cassandra process, it looks like the */etc/security/limits.conf* really were not respected. If I make the change above, then it works as expected. */etc/security/limits.conf* is shipped in Cassandra's debian package.
> Given that there are far more distributions using Systemd (Ubuntu is now as well), I was wondering if it's worth the effort to change Cassandra's debian packaging to use systemd (or at least, include systemd service). I'm not totally familiar with whether it's common or normal to include a service file in packaging so happy to be corrected/cancelled depending on what people think.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org