Hey Ann,
Thanks for your patience. As it turns out, altering this flag on replicas is not possible, and it's been an oversight to have left this flag alterable in the interface / API. We'll have this corrected. Since it appears you'd like to have this flag be alterable on the replica instances, you can file a Feature Request in the Public Issue Tracker for Cloud SQL detailing the feature you'd like to see, why you'd need to use it, etc. and we'll quickly get it logged and considered going forward.
Cheers,
Nick
Cloud Platform Community Support
On Saturday, January 7, 2017 at 5:45:21 AM UTC-5, Ann Su wrote:
-- Thanks for your patience. As it turns out, altering this flag on replicas is not possible, and it's been an oversight to have left this flag alterable in the interface / API. We'll have this corrected. Since it appears you'd like to have this flag be alterable on the replica instances, you can file a Feature Request in the Public Issue Tracker for Cloud SQL detailing the feature you'd like to see, why you'd need to use it, etc. and we'll quickly get it logged and considered going forward.
Cheers,
Nick
Cloud Platform Community Support
On Saturday, January 7, 2017 at 5:45:21 AM UTC-5, Ann Su wrote:
Nick, any updates on this?Ann
On Saturday, December 31, 2016 at 2:48:39 AM UTC+1, Ann Su wrote:Hi Nick,many thanks for a quick turnaround!Ann
On Friday, December 30, 2016 at 10:14:50 PM UTC+1, paynen wrote:Hey Ann Su,
I've replicated this and will be making sure it's seen by the relevant Cloud SQL specialists. I'll return to this thread to post a Public Issue Tracker link where you can follow the progress on this issue.
Cheers,
Nick
Cloud Platform Community Support
On Wednesday, December 28, 2016 at 9:22:17 AM UTC-5, Ann Su wrote:Google Console interface allows to set up "read-only" flag to OFF for a read replica. However, regardless of the flag's value, which according to:$ gcloud sql instances describe {{replica}}
is correctly set:
[...]
- name: read_only
value: 'off'
the global variable in mysql is still set to ON:mysql> show variables like "read_only";
+---------------+-------+
| Variable_name | Value |
+---------------+-------+
| read_only | ON |
+---------------+-------+
Is this a bug?I'm aware of all related risks of writing to a replica and am willing to do that anyway. If I can't disable read_only mode for built-in replicas, what are my options? Can I manually configure replication using SQL instances in a way that such replica wouldn't get into read_only mode?
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/f90ffce2-1e50-46e4-8e4f-8887a7705996%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment