search

tejeswarp / tungsten-replicator

Automatically exported from code.google.com/p/tungsten-replicator
0 stars 0 forks source link

native-slave-takeover fails in master-slave mode #300

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?

1. install the replicator on top of an existing MySQL replication using the 
--native-slave-takeover option

What is the expected output?

the replicator should take over the replication from MySQL replication, same as 
the slave in --direct mode does

What do you see instead?

The master goes OFFLINE:ERROR, because the installer apparently tries to take 
over a slave on that server.

/tools/tungsten-installer \
    --master-slave \
    --disable-relay-logs \
    --master-host=r1 \
    --datasource-user=tungsten \
    --datasource-password=secret \
    --service-name=dragon \
    --home-directory=$TUNGSTEN_BASE \
    --cluster-hosts=r1,r2,r3,r4 \
    -a --java-mem-size=1024 \
    --native-slave-takeover \
    --start

trepctl -host r1 status
Processing status command...
NAME                     VALUE
----                     -----
appliedLastEventId     : NONE
appliedLastSeqno       : -1
appliedLatency         : -1.0
clusterName            : default
currentEventId         : NONE
currentTimeMillis      : 1328603483609
dataServerHost         : qa.r1.continuent.com
extensions             : 
latestEpochNumber      : -1
masterConnectUri       : thl://:/
masterListenUri        : thl://qa.r1.continuent.com:2112/
maximumStoredSeqNo     : -1
minimumStoredSeqNo     : -1
offlineRequests        : NONE
pendingError           : Replicator unable to go online due to error
pendingErrorCode       : NONE
pendingErrorEventId    : NONE
pendingErrorSeqno      : -1
pendingExceptionMessage: Error getting slave status; is MySQL replication 
enabled?
resourcePrecedence     : 99
rmiPort                : 10000
role                   : master
seqnoType              : java.lang.Long
serviceName            : dragon
serviceType            : unknown
simpleServiceName      : dragon
siteName               : default
sourceId               : qa.r1.continuent.com
state                  : OFFLINE:ERROR
timeInStateSeconds     : 103.056
uptimeSeconds          : 104.772
Finished status command...

If I try to install the master separately, to avoid the above problem, I get a 
different error

./tools/tungsten-installer \
    --master-slave \
    --disable-relay-logs \
    --master-host=r1 \
    --datasource-user=tungsten \
    --datasource-password=secret \
    --service-name=dragon \
    --home-directory=$TUNGSTEN_BASE \
    --cluster-hosts=r1 \
    -a --java-mem-size=1024 \
    --start-and-report

./tools/tungsten-installer \
    --master-slave \
    --disable-relay-logs \
    --master-host=r1 \
    --datasource-user=tungsten \
    --datasource-password=secret \
    --service-name=dragon \
    --home-directory=$TUNGSTEN_BASE \
    --cluster-hosts=r1,r2,r3,r4 \
    -a --java-mem-size=1024 \
    --native-slave-takeover \
    --start-and-report

#####################################################################
# There are errors with the values provided in the configuration file
#####################################################################
---------------------------------------------------------------------
ERROR >> Host : DNS hostname
ERROR >> > Message: Value must consist only of letters, digits, underscore (_) 
and periods
ERROR >> > Prompt Class: HostPrompt
---------------------------------------------------------------------
ERROR >> Datasource : Database server hostname
ERROR >> > Message: Value must consist only of letters, digits, and underscore 
(_)
ERROR >> > Argument: --datasource-host
ERROR >> > Prompt Class: DatasourceDBHost
---------------------------------------------------------------------
ERROR >> Replication service dragon_: On what host would you like to deploy 
this service?
ERROR >> > Message: Value must consist only of letters, digits, and underscore 
(_)
ERROR >> > Prompt Class: ReplicationServiceDeploymentHost
---------------------------------------------------------------------

What is the possible cause?

N/A

Original issue reported on code.google.com by g.maxia on 7 Feb 2012 at 8:42

GoogleCodeExporter commented 9 years ago

Original comment by jeffm...@gmail.com on 18 Sep 2012 at 5:22

GoogleCodeExporter commented 9 years ago

Original comment by jeff.m...@continuent.com on 9 Jan 2013 at 2:11

GoogleCodeExporter commented 9 years ago

Original comment by jeff.m...@continuent.com on 9 Jan 2013 at 2:13

GoogleCodeExporter commented 9 years ago

Original comment by jeff.m...@continuent.com on 26 Mar 2013 at 12:53

GoogleCodeExporter commented 9 years ago 
We'll use 2.1.0 instead of 2.0.8, hence moving the issues.

Original comment by linas.vi...@continuent.com on 27 Mar 2013 at 3:13

GoogleCodeExporter commented 9 years ago

Original comment by jeff.m...@continuent.com on 18 Jun 2013 at 4:39

GoogleCodeExporter commented 9 years ago

Original comment by linas.vi...@continuent.com on 26 Aug 2013 at 1:51

GoogleCodeExporter commented 9 years ago

Original comment by linas.vi...@continuent.com on 17 Sep 2013 at 10:12

GoogleCodeExporter commented 9 years ago

Original comment by jeff.m...@continuent.com on 23 Sep 2013 at 4:58

GoogleCodeExporter commented 9 years ago

Original comment by jeff.m...@continuent.com on 14 Aug 2014 at 9:53