iocage VS aioredis

Pains me immensely to say this, but that's the direction things have been moving in for a while now. The list of services I run on FreeBSD versus Linux hosts is steadily growing smaller. iocage hasn't had any changes in a year and a half and I'm not convinced iXsystems will still be developing CORE in the five-to-ten year timeframe.

I am was considering writing a PR for iocage but looking through the github (https://github.com/iocage/iocage) I see there have been no commits in a year and A PR for a decent features has sat waiting for review for over a year and a half. There are also open multiple PR's for bug fixes which are failing CI, with multiple contributors saying it's the CI tests that are broken, not their code.

Install https://github.com/iocage/iocage, it will make your life a lot easier

While trying to move jails between servers using iocage export and import, I found that iocage 1.2 (the currently packaged version) was reading the entire imported file into RAM. For a large jail, this is a clear problem. I found that there was a bug filed for it - and even a fix! - but a version containing the fix had not been released.

That looks like a solid guide. I use iocage to manage my jails. It takes care of a lot of details. Certainly more user-friendly for the first time getting jails set up.

First, it was aioredis library. We are using sentinel based client because with this we can achieve failover easily. Aioredis spawn pool of connections, that transparently reconnects (and here third thing — FOREVER, hello DDOS) to our sentinel nodes, and then to master node. It supposed to do so. Also, we found that if you are not limiting maximum connections count, library will do it for you and set it as 2 ** 31 (here you can see it) — this is fourth thing. Furthermore, pool in our version (2.0.1) not closing automatically, and it makes the problem worse.

I'm hoping to leverage Redis with my project, and I was curious as to if anyone had any general pointers as to how best to manage the DB connection. I'm using aioredis such that I can leverage the async functionality, but I haven't been very happy with the library's documentation surrounding how best to leverage the connection pool. Most of the examples create and tear down the pool immediately without showing how best to manage its lifespan.