Tuesday, April 30, 2019

[google-cloud-sql-discuss] Re: Renaming of table causes update to fail, refers to old table name.

Hello Jayaram,


For the purposes of clarity, would you be able to confirm if you are using the same steps for connecting to your Cloud SQL instance via MySQL workbench as outlined here?


You may have to update the Hostname parameter once you have changed your Cloud SQL instance name.


Let us know how it goes!

On Monday, April 29, 2019 at 7:09:04 PM UTC-4, Able3 Ventures (Jayaram) wrote:
This is probably something simple but I am unable to proceed.

I had a table named LMdata and I renamed it to WFData.

Now, when I try to update a value in the renamed table using MySQL Workbench, it is still looking for the old table name.

Executing:
UPDATE `lmlaser`.`WFData` SET `B1LaserQty` = '0' WHERE (`RowNum` = '1624');

Operation failed: There was an error while applying the SQL script to the database.
ERROR 1146: 1146: Table 'lmlaser.LMdata' doesn't exist


Can someone please tell me how I can fix this issue?

Thanks,
Jayaram

--
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/57fb75a7-fdc4-4ccf-89a5-894cb023f7ae%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Posted by at No comments:

[google-cloud-sql-discuss] Re: Read Replica Stalled/Delayed

Hi,

Thanks for your reply - I tried enabling log_slow_slave_statements via the console but it does not appear to be a supported flag in CloudSql (https://cloud.google.com/sql/docs/mysql/flags?hl=en_GB)?

Thanks
Simon


On Friday, 26 April 2019 21:56:08 UTC+1, yka...@google.com wrote:
Hello,

Usually the typical cause of replication lag is slow queries on the slave. These are discoverable by enabling log_slow_slave_statements and fixing them.

If you are not aware of any read/writes that could be causing this and believe this could be an issue on the Google side, you can create an issue tracker so that we can investigate it on our end.


This e-mail and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the sender by replying to this e-mail.

Replies to this email may be monitored by the Haymarket Group
for operational or business reasons. 

Whilst every endeavour is taken to ensure that e-mails are free from
viruses, no liability can be accepted and the recipient is requested
to use their own virus checking software. 


Haymarket Media Group Limited
Registered in England no. 267189
Registered Office: Bridge House, 69 London Road, Twickenham, TW1 3SP

--
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/064c0c49-b8d6-4861-b6b2-891e1063f4da%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Posted by at No comments:

Monday, April 29, 2019

[google-cloud-sql-discuss] Renaming of table causes update to fail, refers to old table name.

This is probably something simple but I am unable to proceed.

I had a table named LMdata and I renamed it to WFData.

Now, when I try to update a value in the renamed table using MySQL Workbench, it is still looking for the old table name.

Executing:
UPDATE `lmlaser`.`WFData` SET `B1LaserQty` = '0' WHERE (`RowNum` = '1624');

Operation failed: There was an error while applying the SQL script to the database.
ERROR 1146: 1146: Table 'lmlaser.LMdata' doesn't exist


Can someone please tell me how I can fix this issue?

Thanks,
Jayaram

--
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/6e518a1e-4a61-41e0-8dda-63e2b04aa796%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Posted by at No comments:

Re: [google-cloud-sql-discuss] Cannot Connect to Cloud SQL from Cloud Shell by Proxy

Hello Jerry,


I was searching for the thread that was being referenced and could not find it due to this post being close to two years old. I would suggest that you follow the official guide provided by Google for connecting MySQL Client with the use Cloud SQL Proxy here. This will ensure you are not following any of the outdated steps mentioned above.

Please let me know if you encounter any issues when attempting to this guide.  

--
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/e7eef723-6fc9-4a88-b2fd-9921e7c94392%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Posted by at No comments:

Friday, April 26, 2019

[google-cloud-sql-discuss] Re: Read Replica Stalled/Delayed

Hello,

Usually the typical cause of replication lag is slow queries on the slave. These are discoverable by enabling log_slow_slave_statements and fixing them.

If you are not aware of any read/writes that could be causing this and believe this could be an issue on the Google side, you can create an issue tracker so that we can investigate it on our end.

--
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/66ed8f1d-8563-4bd4-b2b9-2d1fb67f6ac5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Posted by at No comments:

Thursday, April 25, 2019

Re: [google-cloud-sql-discuss] Cannot Connect to Cloud SQL from Cloud Shell by Proxy

Which thread? I tried to search but keywords did me no favor

On Friday, February 17, 2017 at 11:34:27 AM UTC-6, David Newgas wrote:
Please see my reply in the other thread.

On Fri, Feb 17, 2017 at 1:59 AM, Yin-Shen Chao <yin...@gmail.com> wrote:
Dear google-cloud-sql-discuss,


I tried to connect to a cloud sql instance from cloud shell by proxy. The API seems to go through, but I don't know why I cannot connect. The context is following,

Error message from Proxy

couldn't connect to playground-158007:asia-east1:auth-instance2": dial tcp 104.199.247.40:3307: getsockopt: connection timed out"

Error Message from Client

ERROR 2013 (HY000): Lost connection to MySQL server at 'reading initial communication packet', system error: 0

Steps:

1. have the sql instance running.
2. create a service account with Cloud SQL API permission
3. Get the JASON file to connect, and the API log shows the successful connection.Part of the API log

serviceName: "cloudsql.googleapis.com"

methodName: "cloudsql.instances.connect"

./cloud_sql_proxy -instances=playground-158007:asia-east1:auth-instance2=tcp:3306 -credential_file=playground-3d345c8ab9b3.json

4. "gcloud beta sql connect auth-instance2 --user=root" can connect.

My db instance: playground-158007:asia-east1:auth-instance2

Please let me know if you have some clue. Any pointer for debugging is welcome.

Thanks in advance.

Yin-shen

--
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/57b8c98f-9d77-4e84-9b42-fbf4fadae2a3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
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/c9d19663-19cd-45bc-8ccc-86d1cb05593c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Posted by at No comments:

[google-cloud-sql-discuss] Read Replica Stalled/Delayed

Hi,

My CloudSQL read replica appears to have stalled yesterday and is not recovering. I have tried stopping and starting it, I have also done a manual backup (in the GCP CloudSQL console) and then setup a new read replica but that one is also not keeping up with the master and there is a constant straight line growth on the replication delay graph.

RRdelay.jpeg


When I run SHOW SLAVE STATUS on the replica instance it all looks ok


# Slave_IO_StateWaiting for master to send event
Master_Host35.189.67.3
Master_Usercloudsqlreplica
Master_Port3306
Connect_Retry60
Master_Log_Filemysql-bin.097078
Read_Master_Log_Pos42673946
Relay_Log_Filerelay-log.000002
Relay_Log_Pos13383109
Relay_Master_Log_Filemysql-bin.096559
Slave_IO_RunningYes
Slave_SQL_RunningYes
Replicate_Do_DB
Replicate_Ignore_DB
Replicate_Do_Table
Replicate_Ignore_Table
Replicate_Wild_Do_Table
Replicate_Wild_Ignore_Table
Last_Errno0
Last_Error
Skip_Counter0
Exec_Master_Log_Pos87918742
Relay_Log_Space55226562178
Until_ConditionNone
Until_Log_File
Until_Log_Pos0
Master_SSL_AllowedYes
Master_SSL_CA_Filemaster_server_ca.pem
Master_SSL_CA_Path/mysql/datadir
Master_SSL_Certreplica_cert.pem
Master_SSL_Cipher
Master_SSL_Keyreplica_pkey.pem
Seconds_Behind_Master110511
Master_SSL_Verify_Server_CertNo
Last_IO_Errno0
Last_IO_Error
Last_SQL_Errno0
Last_SQL_Error
Replicate_Ignore_Server_Ids
Master_Server_Id1845083005
Master_UUIDebcd15bd-8e39-11e7-8142-42010a9a001f
Master_Info_Filemysql.slave_master_info
SQL_Delay0
SQL_Remaining_Delay
Slave_SQL_Running_StateReading event from the relay log
Master_Retry_Count86400
Master_Bind
Last_IO_Error_Timestamp
Last_SQL_Error_Timestamp
Master_SSL_Crl
Master_SSL_Crlpath
Retrieved_Gtid_Setebcd15bd-8e39-11e7-8142-42010a9a001f:262566099-263012216
Executed_Gtid_Setebcd15bd-8e39-11e7-8142-42010a9a001f:1-262566121
Auto_Position1
Replicate_Rewrite_DB
Channel_Name
Master_TLS_Version


Here are the settings for the global settings for the master database


# Variable_nameValue
Aborted_clients830
Aborted_connects0
Binlog_cache_disk_use2171
Binlog_cache_use25206
Binlog_stmt_cache_disk_use0
Binlog_stmt_cache_use754
Bytes_received18366478810
Bytes_sent133342023108
Com_admin_commands11812
Com_assign_to_keycache0
Com_alter_db0
Com_alter_db_upgrade0
Com_alter_event0
Com_alter_function0
Com_alter_instance0
Com_alter_procedure0
Com_alter_server0
Com_alter_table55
Com_alter_tablespace0
Com_alter_user0
Com_analyze0
Com_begin0
Com_binlog0
Com_call_procedure0
Com_change_db14
Com_change_master0
Com_change_repl_filter0
Com_check0
Com_checksum0
Com_commit109569
Com_create_db0
Com_create_event0
Com_create_function0
Com_create_index127
Com_create_procedure0
Com_create_server0
Com_create_table301
Com_create_trigger0
Com_create_udf0
Com_create_user0
Com_create_view0
Com_dealloc_sql0
Com_delete599
Com_delete_multi0
Com_do0
Com_drop_db0
Com_drop_event0
Com_drop_function0
Com_drop_index0
Com_drop_procedure0
Com_drop_server0
Com_drop_table433
Com_drop_trigger0
Com_drop_user0
Com_drop_view0
Com_empty_query0
Com_execute_sql0
Com_explain_other0
Com_flush0
Com_get_diagnostics0
Com_grant0
Com_ha_close0
Com_ha_open0
Com_ha_read0
Com_help0
Com_insert21011
Com_insert_select0
Com_install_plugin0
Com_kill1
Com_load0
Com_lock_tables0
Com_optimize0
Com_preload_keys0
Com_prepare_sql0
Com_purge0
Com_purge_before_date0
Com_release_savepoint0
Com_rename_table0
Com_rename_user0
Com_repair0
Com_replace0
Com_replace_select0
Com_reset0
Com_resignal0
Com_revoke0
Com_revoke_all0
Com_rollback17142310
Com_rollback_to_savepoint0
Com_savepoint0
Com_select32129834
Com_set_option34562276
Com_signal0
Com_show_binlog_events0
Com_show_binlogs0
Com_show_charsets1
Com_show_collations1
Com_show_create_db0
Com_show_create_event0
Com_show_create_func0
Com_show_create_proc0
Com_show_create_table4
Com_show_create_trigger0
Com_show_databases5
Com_show_engine_logs0
Com_show_engine_mutex0
Com_show_engine_status478
Com_show_events0
Com_show_errors0
Com_show_fields937
Com_show_function_code0
Com_show_function_status5
Com_show_grants0
Com_show_keys207
Com_show_master_status4
Com_show_open_tables0
Com_show_plugins0
Com_show_privileges0
Com_show_procedure_code0
Com_show_procedure_status5
Com_show_processlist0
Com_show_profile0
Com_show_profiles0
Com_show_relaylog_events0
Com_show_slave_hosts0
Com_show_slave_status479
Com_show_status1448
Com_show_storage_engines1
Com_show_table_status0
Com_show_tables553
Com_show_triggers4
Com_show_variables2498
Com_show_warnings0
Com_show_create_user0
Com_shutdown0
Com_slave_start0
Com_slave_stop0
Com_group_replication_start0
Com_group_replication_stop0
Com_stmt_execute0
Com_stmt_close0
Com_stmt_fetch0
Com_stmt_prepare0
Com_stmt_reset0
Com_stmt_send_long_data0
Com_truncate149
Com_uninstall_plugin0
Com_unlock_tables0
Com_update5246
Com_update_multi12
Com_xa_commit0
Com_xa_end0
Com_xa_prepare0
Com_xa_recover0
Com_xa_rollback0
Com_xa_start0
Com_stmt_reprepare0
Connection_errors_accept0
Connection_errors_internal0
Connection_errors_max_connections0
Connection_errors_peer_address0
Connection_errors_select0
Connection_errors_tcpwrap0
Connections30484
Created_tmp_disk_tables1433
Created_tmp_files322
Created_tmp_tables15307
Delayed_errors0
Delayed_insert_threads0
Delayed_writes0
Flush_commands1
Handler_commit18615431
Handler_delete638
Handler_discover0
Handler_external_lock59946763
Handler_mrr_init0
Handler_prepare62200
Handler_read_first216234
Handler_read_key131595283
Handler_read_last120
Handler_read_next1850999215
Handler_read_prev0
Handler_read_rnd35201345
Handler_read_rnd_next882659892
Handler_rollback17142222
Handler_savepoint0
Handler_savepoint_rollback0
Handler_update22357397
Handler_write18882926
Innodb_buffer_pool_dump_statusDumping of buffer pool not started
Innodb_buffer_pool_load_statusBuffer pool(s) load completed at 190425 14:22:30
Innodb_buffer_pool_resize_status
Innodb_buffer_pool_pages_data307368
Innodb_buffer_pool_bytes_data5035917312
Innodb_buffer_pool_pages_dirty8232
Innodb_buffer_pool_bytes_dirty134873088
Innodb_buffer_pool_pages_flushed567914
Innodb_buffer_pool_pages_free2176877
Innodb_buffer_pool_pages_misc6123
Innodb_buffer_pool_pages_total2490368
Innodb_buffer_pool_read_ahead_rnd0
Innodb_buffer_pool_read_ahead58171
Innodb_buffer_pool_read_ahead_evicted0
Innodb_buffer_pool_read_requests3434235197
Innodb_buffer_pool_reads148050
Innodb_buffer_pool_wait_free0
Innodb_buffer_pool_write_requests132222590
Innodb_data_fsyncs109874
Innodb_data_pending_fsyncs0
Innodb_data_pending_reads0
Innodb_data_pending_writes0
Innodb_data_read3399471616
Innodb_data_reads207889
Innodb_data_writes655781
Innodb_data_written22894386176
Innodb_dblwr_pages_written431725
Innodb_dblwr_writes29147
Innodb_log_waits0
Innodb_log_write_requests13284835
Innodb_log_writes44425
Innodb_os_log_fsyncs44730
Innodb_os_log_pending_fsyncs0
Innodb_os_log_pending_writes0
Innodb_os_log_written6477446144
Innodb_page_size16384
Innodb_pages_created348510
Innodb_pages_read207482
Innodb_pages_written570346
Innodb_row_lock_current_waits0
Innodb_row_lock_time0
Innodb_row_lock_time_avg0
Innodb_row_lock_time_max0
Innodb_row_lock_waits0
Innodb_rows_deleted676
Innodb_rows_inserted24723254
Innodb_rows_read2772197512
Innodb_rows_updated5210135
Innodb_num_open_files389
Innodb_truncated_status_writes0
Innodb_available_undo_logs128
Key_blocks_not_flushed0
Key_blocks_unused6689
Key_blocks_used9
Key_read_requests306
Key_reads21
Key_write_requests0
Key_writes0
Locked_connects0
Max_execution_time_exceeded0
Max_execution_time_set16
Max_execution_time_set_failed0
Max_used_connections208
Max_used_connections_time2019-04-25 17:31:37
Not_flushed_delayed_rows0
Ongoing_anonymous_transaction_count0
Open_files36
Open_streams0
Open_table_definitions1073
Open_tables1601
Opened_files8951
Opened_table_definitions1882
Opened_tables4332
Performance_schema_accounts_lost0
Performance_schema_cond_classes_lost0
Performance_schema_cond_instances_lost0
Performance_schema_digest_lost0
Performance_schema_file_classes_lost0
Performance_schema_file_handles_lost0
Performance_schema_file_instances_lost0
Performance_schema_hosts_lost0
Performance_schema_index_stat_lost0
Performance_schema_locker_lost0
Performance_schema_memory_classes_lost0
Performance_schema_metadata_lock_lost0
Performance_schema_mutex_classes_lost0
Performance_schema_mutex_instances_lost0
Performance_schema_nested_statement_lost0
Performance_schema_prepared_statements_lost0
Performance_schema_program_lost0
Performance_schema_rwlock_classes_lost0
Performance_schema_rwlock_instances_lost0
Performance_schema_session_connect_attrs_lost0
Performance_schema_socket_classes_lost0
Performance_schema_socket_instances_lost0
Performance_schema_stage_classes_lost0
Performance_schema_statement_classes_lost0
Performance_schema_table_handles_lost0
Performance_schema_table_instances_lost0
Performance_schema_table_lock_stat_lost0
Performance_schema_thread_classes_lost0
Performance_schema_thread_instances_lost0
Performance_schema_users_lost0
Prepared_stmt_count0
Qcache_free_blocks1
Qcache_free_memory1031832
Qcache_hits0
Qcache_inserts0
Qcache_lowmem_prunes0
Qcache_not_cached18495620
Qcache_queries_in_cache0
Qcache_total_blocks1
Queries1016139751
Questions70390764
Rpl_semi_sync_master_clients0
Rpl_semi_sync_master_estimated_slave_lag0
Rpl_semi_sync_master_net_avg_wait_time0
Rpl_semi_sync_master_net_wait_time0
Rpl_semi_sync_master_net_waits0
Rpl_semi_sync_master_no_times1
Rpl_semi_sync_master_no_tx25946
Rpl_semi_sync_master_statusOFF
Rpl_semi_sync_master_timefunc_failures0
Rpl_semi_sync_master_tx_avg_wait_time0
Rpl_semi_sync_master_tx_wait_time0
Rpl_semi_sync_master_tx_waits0
Rpl_semi_sync_master_wait_pos_backtraverse0
Rpl_semi_sync_master_wait_sessions0
Rpl_semi_sync_master_yes_tx0
Rpl_semi_sync_slave_statusOFF
Rsa_public_key
Select_full_join47817
Select_full_range_join0
Select_range5716712
Select_range_check0
Select_scan176228
Slave_open_temp_tables0
Slow_launch_threads0
Slow_queries0
Sort_merge_passes3824
Sort_range378
Sort_rows7026863
Sort_scan1524
Ssl_accept_renegotiates0
Ssl_accepts0
Ssl_callback_cache_hits0
Ssl_cipher
Ssl_cipher_list
Ssl_client_connects0
Ssl_connect_renegotiates0
Ssl_ctx_verify_depth18446744073709551615
Ssl_ctx_verify_mode1
Ssl_default_timeout7200
Ssl_finished_accepts0
Ssl_finished_connects0
Ssl_server_not_afterAug 31 10:48:01 2019 GMT
Ssl_server_not_beforeAug 31 10:47:01 2017 GMT
Ssl_session_cache_hits0
Ssl_session_cache_misses0
Ssl_session_cache_modeSERVER
Ssl_session_cache_overflows0
Ssl_session_cache_size128
Ssl_session_cache_timeouts0
Ssl_sessions_reused0
Ssl_used_session_cache_entries128
Ssl_verify_depth18446744073709551615
Ssl_verify_mode1
Ssl_versionTLSv1.1
Table_locks_immediate4684
Table_locks_waited0
Table_open_cache_hits18566458
Table_open_cache_misses4332
Table_open_cache_overflows1497
Tc_log_max_pages_used0
Tc_log_page_size0
Tc_log_page_waits0
Threads_cached3
Threads_connected187
Threads_created243
Threads_running5
Uptime14345
Uptime_since_flush_status14345



Can anybody help or point me in the right direction, as you can see from the graph it can normally deal with the replication load with ease ?


Thanks

Simon



This e-mail and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the sender by replying to this e-mail.

Replies to this email may be monitored by the Haymarket Group
for operational or business reasons. 

Whilst every endeavour is taken to ensure that e-mails are free from
viruses, no liability can be accepted and the recipient is requested
to use their own virus checking software. 


Haymarket Media Group Limited
Registered in England no. 267189
Registered Office: Bridge House, 69 London Road, Twickenham, TW1 3SP

--
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/d817a93d-0671-4e4f-9003-d439d97ab8c6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Posted by at No comments:
Subscribe to: Posts (Atom)