Installation issues for fan-in cluster when masters are in the same host

[GoogleCodeExporter]

What steps will reproduce the problem?

1.Configure some host name aliases for the master (for fan-in topology)
2.Configure a fan-in topology which masters are in the same host (each master 
uses one host name alias).
3.Install the cluster

What is the expected output?

The fan-in cluster is installed, the master host has several installation 
directories for different services.

What do you see instead?

ERROR >> srv1 >> Failed: rsync -aze 'ssh -A -oStrictHostKeyChecking=no' 
--delete --exclude='tungsten-*' --exclude='gossiprouter' 
--exclude='bristlecone' /veris/tungsten/tungsten-replicator-3.0.1-64/ 
tungsten@srv1:/tmp/tungsten-replicator-3.0.1-64_pid96575//tungsten-replicator-3.
0.1-64, RC: 23, Result: , Errors: 
ERROR >> srv2 >> Failed: rsync -aze 'ssh -A -oStrictHostKeyChecking=no' 
--delete --exclude='tungsten-*' --exclude='gossiprouter' 
--exclude='bristlecone' /veris/tungsten/tungsten-replicator-3.0.1-64/ 
tungsten@srv2:/tmp/tungsten-replicator-3.0.1-64_pid96575//tungsten-replicator-3.
0.1-64, RC: 23, Result: , Errors: 
or
ERROR >> srv1 >> Unable to execute scripts on 
/tmp/tungsten-replicator-3.0.1-64_pid94120/tungsten-replicator-3.0.1-64/ is 
noexec set? (WriteableTempDirectoryCheck)

ERROR >> srv2 >> Unable to execute scripts on 
/tmp/tungsten-replicator-3.0.1-64_pid94120/tungsten-replicator-3.0.1-64/ is 
noexec set? (WriteableTempDirectoryCheck)

What version of the product are you using?

Tungsten Replicator 3.0.0 or 3.0.1

On what operating system?

Redhat 6.3

Please provide any additional information below.

Notes:

The tungsten seems install different nodes in parallel. For masters for fan-in 
in the same host, it copy the files in the same temp location 
/tmp/tungsten-replicator-3.0.1-64_pid94120/tungsten-replicator-3.0.1-64/, and 
do some checks in the same directory. For tungsten replicator 2.2, it generates 
different pid number, so it's OK.

Maybe it has different installation method (One installation instance hosts 
several services). But in the doc, it is not mentioned.

Original issue reported on code.google.com by 164771...@qq.com on 6 Jan 2015 at 1:37

[GoogleCodeExporter]

Please show the tpm command used for installing.
When using several servers in the same host, you need to differentiate the 
installation path, the replicator ports, and the database instance.

Original comment by g.maxia on 6 Jan 2015 at 2:07

• Changed state: Invalid

[GoogleCodeExporter]

./tools/tpm configure ODS \
--masters=crm,bill \
--members=ods,crm,bill \
--master-services=crmsrv,billsrv \
--topology=fan-in

./tools/tpm configure ODS --host ods \
--install-directory=~/ods \
--thl-port=20000 \
--rmi-port=30000 \
--java-user-timezone=CET \
--java-file-encoding=UTF8 \
--privileged-master=false \
--privileged-slave=false \
--datasource-type=mysql \
--datasource-user=tungsten \
--datasource-password=tungsten \
--datasource-host=tedw2 \
--datasource-port=3308 \
--datasource-mysql-conf=/etc/my_3308.cnf \
--mysql-use-bytes-for-string=false \
--skip-validation-check=InstallerMasterSlaveCheck,HostsFileCheck,MySQLPermission
sCheck \
--svc-parallelization-type=disk \
--channels=5

./tools/tpm configure ODS --host crm \
--install-directory=~/crm \
--thl-port=20015 \
--rmi-port=30015 \
--java-user-timezone=CET \
--java-file-encoding=UTF8 \
--privileged-master=false \
--privileged-slave=false \
--datasource-type=mysql \
--datasource-user=tungsten \
--datasource-password=tungsten \
--datasource-host=crm \
--datasource-port=5310 \
--datasource-mysql-conf=/etc/my_5310.cnf \
--mysql-use-bytes-for-string=false \
--skip-validation-check=InstallerMasterSlaveCheck,HostsFileCheck,MySQLPermission
sCheck \
--svc-parallelization-type=disk \
--channels=5

./tools/tpm configure ODS --host bill \
--install-directory=~/bill \
--thl-port=20025 \
--rmi-port=30025 \
--java-user-timezone=CET \
--java-file-encoding=UTF8 \
--privileged-master=false \
--privileged-slave=false \
--datasource-type=mysql \
--datasource-user=tungsten \
--datasource-password=tungsten \
--datasource-host=bill \
--datasource-port=5320 \
--datasource-mysql-conf=/etc/my_5320.cnf \
--mysql-use-bytes-for-string=false \
--skip-validation-check=InstallerMasterSlaveCheck,HostsFileCheck,MySQLPermission
sCheck \
--svc-parallelization-type=disk \
--channels=5

./tools/tpm configure crmsrv \
--master-thl-port=20015

./tools/tpm configure billsrv \
--master-thl-port=20025

Original comment by 164771...@qq.com on 6 Jan 2015 at 2:16

[GoogleCodeExporter]

And crm and bill MySql instances are in the same host.

Original comment by 164771...@qq.com on 6 Jan 2015 at 2:54

[GoogleCodeExporter]

This is not a bug. 
Tungsten assumes that a separate hostname is a physical host, and since the 
installation happens in parallel, there is a conflict in the installation 
directory.

A workaround would be installing each node separately, instead of using a 
single command.

Original comment by g.maxia on 6 Jan 2015 at 3:04

[GoogleCodeExporter]

Thank maxia very much. Tungsten Replicator 2.2 is OK for this scenario. BTW 
What does tpm do when specifying fan-in cluster? And if install nodes 
separately, So I can use it to install. Can you give me some references?

Original comment by 164771...@qq.com on 6 Jan 2015 at 3:15

[GoogleCodeExporter]

Please use the discussion group for these requests

Original comment by g.maxia on 6 Jan 2015 at 3:21