Does freeradius support redis cluster and if yes in which release - freeradius

While searching I found that the latest version of freeradius which is 3.2.X doesn't support using redis cluster. but in the github repository I found that they support it in the redis rlm configuration file but I do not where do I found it or if this version is stable or not.
I am expecting to make a configuration for the accounting requests to use redis cluster as a back-end database. Thank you for your help.

Redis clusters are only supported in the unreleased development version (that will become v4). It's not supported in any released stable version.
It's possible to use a Redis proxy that supports clusters in between FreeRADIUS and Redis to work around it if needed.

Related

How can I set a password for Elasticsearch 2.3.0 running in Docker?

I am trying to modify an existing installation of Elasticsearch (I believe it's version 2.3.0) running on Docker. Most of the information I'm finding online is for newer versions of Elasticsearch, but I'm hoping to avoid having to update the whole thing.
I need to restrict access to Elasticsearch for security reasons. I'm trying to set a password, but so far I haven't had any luck. Most of the tutorials I've found (apart from being about later version of Elasticsearch) talk about using X-Pack, but I don't think this is installed in the docker container. Is it necessary to install X-Pack, or is there another way?
2.3 is super old, there was no security back then and was only added in 5.6
you will need to use something like nginx to manage, or ideally, upgrade to a supported version. Security is free these days as well

Downgrade etcd API version from 3 to 2 on MacOS

I have etcd installed through Homebrew on Mac.
etcdctl version
etcdctl version: 3.5.1
API version: 3.5
I would like to downgrade the API version to v2, however when I cheekily set the environment variable it then renders the cluster unhealthy.
export ETCDCTL_API=2
etcdctl cluster-health
cluster may be unhealthy: failed to list members
Error: unexpected status code 404
It may seem counter-productive to downgrade API version, however I am working with a legacy app and I am not ready to upgrade quite yet.
The cluster in question is only on my local development environment so I have no issue blowing it away if need be, but i'm unsure if that will get me to API v2.
Is there a way to get back to API v2?

Elasticsearch::UnsupportedProductError (The client noticed that the server is not a supported distribution of Elasticsearch

Getting this error when using searchkick with elasticsearch on mac.
Searchkick version: searchkick (4.5.2)
$ elasticsearch --version
warning: no-jdk distributions that do not bundle a JDK are deprecated and will be removed in a future release
Version: 7.10.2-SNAPSHOT, Build: oss/tar/unknown/2021-01-16T01:41:27.115673Z, JVM: 16.0.2
To reproduce
Product.reindex
If you are using Python elasticsearch client, you need to downgrade or install version before 7.14.0.
pip install elasticsearch<7.14.0
It worked fine after degrading to elastic search < 7.14. So basically added a gem to restrict the version upgrade
gem elasticsearch, "< 7.14"
Elasticsearch::UnsupportedProductError is raised when your Elasticsearch server version don't match with Ruby's Elasticsearch client (gem elasticsearch). In order to fix this properly you need a server that is up to date with latest Elasticsearch (ES) releases
that means if you are on ES provider like https://cloud.elastic.co/ where you work with latest versions of cluster it's easy peasy => server gets upgraded => this is not an issue
if you however work with provider that is slow to catch up with latest ES releases (like AWS Elasticsearch / AWS Opensearch where last version is 7.10 and will not get upgraded anytime soon) your only option is to use gem elasticsearch, "< 7.14" (Siddhant's answer in this discussion ...and yes this means no potential security updates
other solution may be to silence the verification by overriding method verify_with_version_or_header as proposed in https://github.com/elastic/elasticsearch-ruby/issues/1429#issuecomment-958162468
but reality is both of this solutions are just "not recommended" workarounds. The real fix is a server upgrade

Cassandra and Analytics on single node

With DataStax Enterprise, is it possible to set up a cassandra cluster that can do cassandra "realtime" and analytics on a single machine? Obviously, this is not for production, but for tiny little proof of concepts / logical experiments, I'd rather fire up a single linux vm, rather than 2 or 3. Would this be possible with a tarball install, if not through apt-get?
Yes. On the latest versions of dse 3.1.x, 3.2.x, and 4.0.x it should be possible to turn both the Solr and Hadoop features on, on the same node for development purposes.

Is MariaDB usable in production with Ruby on Rails?

http://en.wikipedia.org/wiki/MariaDB
MariaDB is a community-developed branch of the MySQL database, the
impetus being the community maintenance of its free status under the
GNU GPL, as opposed to any uncertainty of MySQL license status under
its current ownership by Oracle. The contributors are required to
share their copyright with Monty Program AB.
The page goes on to say that MariaDB 5.5 is binary-compatible with the MySQL of the same version and adds a couple of database engines of its own to choose from.
I also read that Fedora 19 is going to remove MySQL packages in favor of MariaDB.
So the question is, is Ruby on Rails 3+ MariaDB compatible? Are there any future plans to integrate MariaDB features as they start to deviate from MySQL?
Red Hat, Debian, Fedora, OpenSuse, Slackware, and even Wikipedia moved (or are moving) to MariaDB. This means it is stable. Also, MariaDB (and Percona Server) seems to fix security issues much faster than Oracle.
Since MariaDB is compatible with MySQL, all APIs are compatible, including Ruby on Rails API.
(Well, MariaDB 10.0 is not totally compatible with MySQL 5.6, but the incompatibilities are not at API-level!)
You can use Mariadb with any compatible MySQL client. I am using MySQL .NET connector and it just work.

Resources