Ashraf Sharif
- Total activity 320
- Last activity
- Member since
- Following 0 users
- Followed by 0 users
- Votes 0
- Subscriptions 118
Comments
Recent activity by Ashraf Sharif Sort by recent activity-
Hi Chintan, I believe, at the time of this writing, ClusterControl still does not support importing MySQL InnoDB Cluster, or group replication. When you imported the cluster into ClusterControl, wh...
-
Hi, Yes, MySQL 5.7 is no longer supported in the current release of ClusterControl 1.9.8 since it reached the end of its life in October 2023. You may use the older version of ClusterControl to ins...
-
Official comment Hi, Upgrading OS is out of the scope of our product support. You may refer to the operating system's vendor or many other online resources about steps to upgrade to Debian 11. After upgrading to 11...
-
Hi, ProxySQL deployment requires a mysql client, as in this case, the provider is percona-server-client-5.7. The following lines tell us more about why the installation failed: [21:51:23]:<em style...
-
Hi, Unfortunately, deployment and management of load balancers are not available in the Community edition. This is true for both GUI and CLI. Regards,Ashraf
-
Hi Thorin, ClusterControl has a specific role like a virtual DBA, to automate and simplify database management, with agentless and agent-based approaches, and can be deployed in an offline environm...
-
Hi Le, This deserves a deeper investigation and troubleshooting. If the problem still happening, do you mind creating a new support ticket at https://severalnines.zendesk.com/hc/en-us/requests/new ...
-
Yes, you are spot on. Redis was configured as a standalone in that blog post. For production setup, it should be configured with HA, but it was not the focus at that time. Starting from v1.9.0, Cl...
-
Official comment Hi, A simple rule of thumb is to allocate the majority of the resources to the data nodes, and the number of data nodes must have always come in pairs (2, 4, 6, 8 data nodes). In a fraction of 10, ...
-
Official comment Hi Oliver, It looks like the pod creation was terminated/rescheduled before the pod start-up process completes. As you can tell from the output, the entrypoint on 1.8.0 and later has been added wit...