Tuesday, January 26, 2016

Re: [google-cloud-sql-discuss] Google Cloud SQL (Second Generation) - Read Replica Instances Inoperable - Bug Report


On Tue, Jan 26, 2016 at 11:47 AM, Graphics Geeks <graphicsguru600@gmail.com> wrote:
Ok, I added a user on the master with a new password. And I made sure it had all the same privileges as the root.

I also flushed the privileges.

Doesn't seem to connect still? Does it take a day or something to be replicated over into the slave?

The changes are near-instantly propagated. Please send an email to cloud-sql@google.com with the instance details and the commands that you are running to help you debug this issue. (Also, ignore its auto reply).
 

I totally appreciate your help. From the google architecture side of things though this all seems pretty crazy. 

Why not just have a configurable user list on the control panel? I know making forms is a pain, but come on - seriously?

The feature still needs work to be enabled for Second Generation instances.
 

On Tuesday, January 26, 2016 at 7:25:33 PM UTC+1, Vishnu Fafat wrote:
Hi,

The users from the master are replicated to the replica. So, you should be able to connect to the replica if you provide the right information. These are the steps I followed:

1. Add a user on master instance for all hosts. (CREATE USER 'abcdefg'@'%' IDENTIFIED BY 'abcdef';)
2. Flush privileges.
3. Connect to the replica instance.


On Tue, Jan 26, 2016 at 9:31 AM, Graphics Geeks <graphic...@gmail.com> wrote:
Hello Lee,

Thanks for helping me.

I'm a bit confused about this, since it doesn't seem from the interface that I can even set any users for a read replica instance.

And setting the root password is not allowed for the replica - it says it has to be the same as the master?



Kind regards




On Tuesday, January 26, 2016 at 6:00:57 PM UTC+1, Lee S. wrote:
You need to set the user passwords for the replica separately.  You can do this from the cloud console under 'access control > users'.  The system tables don't get replicated so the users have to be created on each replica separately.


--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/98c7fec1-e5cb-443f-8122-c2a53a072caa%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.



--
Vishnu Fafat

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/36317033-2900-4e20-adad-6a56f027dfd0%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.



--
Vishnu Fafat

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/CAPVxmMDrAOWET_CyKYzCr7WKV2iTHK5yi45Yr9b8d8zbMMydOQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment