-
```
Hi
I have a mysql cluster with one master node and two hot standby slave nodes.
All reads and writes go to master. The three node cluster is managed by
corosync pacemaker that has a VIP for the…
-
```
Hi
I have a mysql cluster with one master node and two hot standby slave nodes.
All reads and writes go to master. The three node cluster is managed by
corosync pacemaker that has a VIP for the…
-
```
Hi
I have a mysql cluster with one master node and two hot standby slave nodes.
All reads and writes go to master. The three node cluster is managed by
corosync pacemaker that has a VIP for the…
-
```
Hi
I have a mysql cluster with one master node and two hot standby slave nodes.
All reads and writes go to master. The three node cluster is managed by
corosync pacemaker that has a VIP for the…
-
## Issue Description
Type: *feature request*
## Issue Description
Type: *feature request*
As we know, we can use the `Kubefile` to define a `Sealer Image` that can be shared and de…
-
1.Deployment structure: proxysql + mysql group replication
2.mysql version: 5.7.25(percona)
3.proxysql version: ProxySQL version 2.0.5-37-gc8e32ee, codename Truls
4.question:
mysql replication …
-
Based on same testing env as issue: #304
Same check has been executed against both scenarios:
* mysql-router:database mysql-test-app
* mysql-k8s:database mysql-test-app
Downscaling from 3->1 …
-
```
What steps will reproduce the problem?
1. Run replicator against MySQL 5.6 with Innodb enabled
What is the expected output?
No warnings are displayed
What do you see instead?
INFO | jvm 1 …
-
## Is this a BUG REPORT or FEATURE REQUEST?
BUG REPORT
## Versions
**MySQL Operator Version**:8.0.12
**Environment**:
- **Kubernetes version** (use `kubectl version`):Client Vers…
-
Hi there,
There is issue in creating PolarDB instance.
### Terraform Version
```
Terraform v0.12.21
+ provider.alicloud v1.74.1
```
### Affected Resource(s)
- alicloud_polardb_cluste…