Great to hear. This bug will be fixed then I guess:
https://youtrack.jetbrains.com/issue/UP-6943
Thanks a lot!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1578080
Title:
percona cluster hits
> Will my systemd scripts with TasksMax setting keep working?
Yes, this only changes the builtin defaults if there is no explicit
TaskMax= setting.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Will my systemd scripts with TasksMax setting keep working?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1578080
Title:
percona cluster hits resource limits in HA Openstack cloud with xenial
To
This bug was fixed in the package systemd - 229-4ubuntu6
---
systemd (229-4ubuntu6) xenial-proposed; urgency=medium
* Add a DHCP exit hook for pushing received NTP servers into timesyncd.
(LP: #1578663)
* Revert "enable TasksMax= for all services by default, and set it to
** Changed in: systemd (Debian)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1578080
Title:
percona cluster hits resource limits in HA Openstack cloud with
I've upgraded systemd across my cluster to 229-4ubuntu6, removed all my
custom tweaks to systemd settings, reloaded the daemon and both rabbitmq
and mysql appear to be working fine on my openstack cluster. I'll be
throwing a bit more load at it, but usually by this point mysql has
fallen over, so
This bug was fixed in the package systemd - 229-6ubuntu1
---
systemd (229-6ubuntu1) yakkety; urgency=medium
* Merge with Debian unstable. Remaining Ubuntu changes:
- Hack to support system-image read-only /etc, and modify files in
/etc/writable/ instead.
systemd (229-6)
Hello Brad, or anyone else affected,
Accepted systemd into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu6
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Description changed:
I'm trying to deploy Mitaka Openstack using the 16.04 charms on Xenial
using Juju 1.25.5 and MAAS 1.9.2, with as many components of Openstack
being HA as possible.
When deployed, after running for a while mysql (which is a 3 node
cluster) starts refusing
Debian unstable/yakkety fix:
http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=fe4d9d3ba0
Xenial backport:
http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu-xenial=643089b1d
** Changed in: systemd (Ubuntu)
Status: In Progress => Fix Committed
--
** Changed in: percona-cluster (Juju Charms Collection)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1578080
Title:
percona cluster hits resource limits in HA
+1 on your proposed approach Martin
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1578080
Title:
percona cluster hits resource limits in HA Openstack cloud with xenial
To manage notifications
** Changed in: systemd (Debian)
Status: Unknown => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1578080
Title:
percona cluster hits resource limits in HA Openstack cloud with
Upstream report: https://github.com/systemd/systemd/issues/3211
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1578080
Title:
percona cluster hits resource limits in HA Openstack cloud with xenial
This was discussed upstream last November:
https://lists.freedesktop.org/archives/systemd-
devel/2015-November/035006.html
And then enabled by default in 228 in
https://github.com/systemd/systemd/commit/9ded9cd14.
So in retrospect, having a default limit there was not such a good idea
after all:
Raising systemd task and assigning to Martin...
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Re "Failed to allocate directory watch: Too many open files" message - I
think that you might be on the right track, but it might not
specifically be to the tasks limit systemd is imposing.
I have seen this message during testing on an alternative architecture,
but assumed it was not related...
FWIW I'm also seeing limits hit in other areas, rabbitmq-server seems to
be a common one. I'm also randomly seeing:
Failed to allocate directory watch: Too many open files
on the command line. I suspect its related to the percona and rabbitmq
services hitting limits, but I'm not exactly
Raising a package bug for this one; there is also an ongoing
conversation about whether this limit should be dropped at the systemd
level as an SRU, but that's still not decided AFAIK.
** Also affects: percona-xtradb-cluster-5.6 (Ubuntu)
Importance: Undecided
Status: New
--
You
19 matches
Mail list logo