using MMM on mysql servers running on different port question

[Tomas]

Dear all experts,

I try to do a test with the latest 2.0.10 version and I found
something wrong.
I am not sure if it is because of my settings or not.

My DB which MMM based on in on port 3911, but even I set that
parameter
"mysql_port 3911" in mmm_common.conf
file, the write IP still point to "3306" port for connections.
Which is another mysql instance running, I am not sure if it is a bug
or it is because I do not configure my MMM right.

here is my mmm_common.conf file:


active_master_role writer


<host default>
cluster_interface eth0

pid_path /var/run/mmmd_agent.pid
bin_path /usr/bin/mysql-mmm/

replication_user repadmin
replication_password rep

agent_user rep
agent_password rep
</host>

<host db1>
ip 192.168.0.14
mode master
peer db2
mysql_port 3910
</host>

<host db2>
ip 192.168.0.13
mode master
peer db1
mysql_port 3911
</host>


<role writer>
hosts db1, db2
ips 192.168.0.20
mode exclusive
prefer db1
</role>

<role reader>
hosts db1, db2
ips 192.168.0.21, 192.168.0.22
mode balanced
</role>

IS that ALL MMM mysql instance best using the same port 3306 ?


Thanks a lot.

Yours Tomas

[Baron Schwartz]

Tomas,

On Tue, Nov 24, 2009 at 3:29 PM, Tomas <hous...@gmail.com> wrote:
> Dear all experts,
>
> I try to do a test with the latest 2.0.10 version and I found
> something wrong.
> I am not sure if it is because of my settings or not.
>
> My DB which MMM based on in on port 3911, but even I set that
> parameter
> "mysql_port                              3911"  in mmm_common.conf
> file, the write IP still point to "3306" port for connections.
> Which is another mysql instance running, I am not sure if it is a bug
> or it is because I do not configure my MMM right.

I would guess that it is because your application is connecting to
port 3306. MMM doesn't control ports. It only controls IP addresses.
Your application can connect to any port on that IP address.

Baron