-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I recently recovered a mysql instance and all of it's databases to a
point in time using a file generated with mysqldump, and then the binary
logs. The binary log file had a "change master to.." command in it. Now
the instance is genarting relay logs. How do I stop that? There is no
replication involved here. I think it was the "change master" that told
it to start generating those logs.

TIA
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with PCLinuxOS - http://enigmail.mozdev.org

iEYEARECAAYFAkeyDzkACgkQzIf+rZpn0oT6IwCgj+qi0koMk6 Q29dFxpVKUNHkw
UxsAoI1HRAwmHcCGN8tblFFxUL3H9caL
=f66b
-----END PGP SIGNATURE-----

If you do not need replication, run the following commands.

stop slave;

change master to master_host = ' ', master_user= ' '

That should take care of it.

On Feb 12, 1:27 pm, Chuck <skilover_nos...@bluebottle.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I recently recovered a mysql instance and all of it's databases to a
> point in time using a file generated with mysqldump, and then the binary
> logs. The binary log file had a "change master to.." command in it. Now
> the instance is genarting relay logs. How do I stop that? There is no
> replication involved here. I think it was the "change master" that told
> it to start generating those logs.
>
> TIA
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (GNU/Linux)
> Comment: Using GnuPG with PCLinuxOS -http://enigmail.mozdev.org
>
> iEYEARECAAYFAkeyDzkACgkQzIf+rZpn0oT6IwCgj+qi0koMk6 Q29dFxpVKUNHkw
> UxsAoI1HRAwmHcCGN8tblFFxUL3H9caL
> =f66b
> -----END PGP SIGNATURE-----

Visu wrote:
> If you do not need replication, run the following commands.
>
> stop slave;
>
> change master to master_host = ' ', master_user= ' '
>
> That should take care of it.
>
> On Feb 12, 1:27 pm, Chuck <skilover_nos...@bluebottle.com> wrote:
> I recently recovered a mysql instance and all of it's databases to a
> point in time using a file generated with mysqldump, and then the binary
> logs. The binary log file had a "change master to.." command in it. Now
> the instance is genarting relay logs. How do I stop that? There is no
> replication involved here. I think it was the "change master" that told
> it to start generating those logs.
>
> TIA

Thanks. I discovered another command that took care of it too - RESET SLAVE.