The datasource restore
command may fail when using
xtrabackup if the file
ownership for the backup files is wrong.
Dataservice has different "composite" status depending on how
its status is called.
The switch command does not
validate command line correctly.
Composite recovery would fail because a replicator that was
previously a master tries to re-apply a transaction that it had
cctrl would let you shun the master
During a failover, the master could be left in read-only mode.
On occasion, the manager would fail to restart after being hung.
The ping command in cctrl wrongly identifies
witness server as unreachable.
The failure of primary data source could go unhanded due to a
The manager reports composite recovery completion although the
operation has failed.
A transient error can cause a confused state.
Composite recovery could fail, but the manager says it was
The internal Call to
during transition from online to offline results in a
Relay does not fail over when the database server is stopped.
The cctrl would raise an error when running a
backup from a master.
Tungsten manager may report false host failures due to a
temporary problem with name resolution.
cctrl could report a manager as
ONLINE even though the
datasource would in fact be
The manager would not see a secured replicator.
Slave replicators never come online after a switch when using
cctrl complains of missing security file when
security is not enabled.
Switch in relay site fails and takes offline all nodes.
A switch in the relay site sets the relay to replicate from
In a composite deployment, a switch in the primary site is not
propagated to the relay.
cctrl exposes security passwords
The master datasource is not available following the
The manager does not support a non-standard replicator RMI port.
In a multi-site deployment, automatic failover does not happen
in maintenance mode, due to replicator issues.
During the recovery of a composite dataservice, the restore of a
shunned master could fail because the previous and current roles
did not match.
A stopped dataserver would not be detected if cluster was in
maintenance mode when it was stopped.
Manager attempts to get status of remote replicator from the
local service - causes a failure to catch up from a relay.
A switch operation could
fail in single site deployment.
In a configuration with a relay of a composite site, if all
active data datasources are unavailable, a
switch operation would
raise invalid exception messages.
recover using fails in the
simplest case for 2.0.1.
Manager fails safe even if it is in the quorum set and primary
Single command recover does
not work - does not find datasources to recover even if they
Failover causes old master node name to disappear from
ClusterManagementHandler can read/write datasources directly
from the local disk - can cause cluster configuration
Stopping managers does not cause membership validation rules to
kick in. This can lead to an invalid group.
The manager rules could fail to fence a composite datasource for
which all managers in the service are unreachable.
recover using in a master
service could convert one of the datasources into a relay
instead of a slave.
CREATE COMPOSITE DATASOURCE
could result in an exception if the master datasource site was
The manager would throw a false alarm if the
was empty. This was due to the manager being started before the
replicator had created the required table.
Composite recovery within a cloud deployment could fail.
Errors could be raised when using the
set master and
recover using commands
Composite recovery could fail in a site with multiple masters.
A failed master within a dataservice would cause the datasource
names to disappear.
Running switch command
after performing recovery could fail within a multi-site
Performing a switch
operation when there are active witness could cause an error
message indicating a fault, when in fact the operation completed
After performing a switch operation, a slave
could report to the previous, not active, relay.
Running operations on active witness datasources would raise
Issues: TUC-1944, TUC-1945
Errors would be reported in the log when deserializing
configuration information between the manager and connector.
Automatic failover would fail to run if an active witness was
the coordinator for the dataservice.
Connectors would disappear after restarting the coordinator.
The coordinator would attempt to check database server liveness
if a manager on a witness host goes away.
Composite recovery using a streaming backup results in a site
with multiple masters.
Installing a composite dataservice would create two master