I see the forum discussing the end-of-life process of the Amazon RDS for MySQL 5.6 here
I am using Aurora MySQL 1.19.5, which is compatible with MySQL 5.6. Do I need to upgrade it to Aurora MySQL 2.* before Amazon RDS MySQL 5.6 reaches the end-of-life?
Official EOL dates for Aurora MySQL 1.* (MySQL 5.6) will be announced separately, not related to RDS MySQL 5.6 EOL date. Typically AWS give customers 6-months’ notice before moving a database major version to EOL. So my answer to your question is: No, you don't need to upgrade your Aurora instance until AWS announce EOL for Aurora MySQL 1.*
Related
Is it possible to get the OS Cassandra is installed on using CQL?
For example in PostgreSQL you can run the query select version(); which will return:
PostgreSQL 11.12 (Debian 11.12-0+deb10u1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 8.3.0-6) 8.3.0, 64-bit
Essentially, it returns the version of PostgreSQL and the OS type installed on.
Unfortunately, it isn't possible to do this in Cassandra through CQL.
It isn't particularly relevant since some deployments are serverless like K8ssandra.io where Cassandra is deployed in Kubernetes.
There are also some architectures where the coordinators are Stargate.io nodes which are not Cassandra nodes in the cluster. Astra DB is an example of this where it's serverless and truly cloud-native. Cheers!
Are you using Cassandra 4.0? If so, you should be able to query the os.name key from the system_views.system_properties table:
> SELECT * FROm system_properties WHERE name='os.name';
name | value
---------+----------
os.name | Mac OS X
(1 rows)
Although, as Erick pointed out the info isn't terribly useful. You could be running in an Alpine Linux container on an Ubuntu host, but Cassandra would only have visibility to Alpine.
My goal is to migrate from freeipa v3 to v4. Both versions are a cluster of two nodes.
v3 is centos 6 and v4 is centos 7.
I want to migrate the dns entries from the old cluster to the new one. Both have the same dns zone(s) and after all dns entries are on both clusters I will migrate all hosts to the new cluster.
Also the users will be created manually. Goal is to have a fresh freeipa environment.
Which commands do I need to know or use to achieve that?
Also an export and import function will do the trick.
This is all documented in the official documentation in the "MIGRATING IDENTITY MANAGEMENT FROM RED HAT ENTERPRISE LINUX 6 TO VERSION 7" section:
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/linux_domain_identity_authentication_and_policy_guide/migrate-6-to-7
The key is not to start from scratch but rather add CentOS 7 replicas to CentOS 6 deployment, move services over to CentOS 7 replicas and then decommission CentOS 6 machines. This is, in general, much easier and more reliable to do than to start from scratch by importing older data.
I'm trying to use Cassandra for mod_mam in Ejabberd 16.09. Does that version of Ejabberd support Cassandra? If it does, how to configure Ejabberd to use Cassandra?
Also, I found some Erlang-Cassandra driver such as Cqerl, Erlcass, and Erlang-cassandra-cql. Can I use them to connect Ejabberd and Cassandra?
ejabberd doesn't support Cassandra as a database backend. The only available backends at the moment are: internal (i.e. Mnesia), Riak, MySQL, PostgreSQL, MS SQL, sqlite and other ODBC compatible databases.
Of course you can use mentioned Erlang drivers, but this will not be very easy to write a new database backend using them: some experience in Erlang and ejabberd is required.
Using DataStax OpsCenter v5.2.4 (currently the latest) installed using AMI ami-8f3e2bbf provided by DataStax and following DataStax's instructions on how to create a cluster on EC2, all DSE nodes fail during creation with this error:
Install Errored: Could not find a matching version for package dse-libpig
Is there a work around for this?
Note that during the process I selected Package: DataStax Enterprise 4.8.1, which is the latest available in the list at this time.
I faced the same issue and taking a clue from BrianC's comment resolved by removing a trailing '#' in my datastax account password
I just launched a datastax cassandra ami.
Noticed that the opscenter is by default running.
Do I have to disable the opscenter for each of the ami I launched?
What linux command to ensure opscenter won't run as a service?
Ultimately I want to run opscenter on my local server, remotely connecting to the cluster in AWS.
http://www.datastax.com/documentation/cassandra/2.0/cassandra/install/installAMILaunch.html
instance can be configured
--opscenter [no] Optional. By default, DataStax OpsCenter is installed on the first instance. Specify no to disable.
Sorry guys, I should have read the documents more carefully.