How To Solve “gcs log flush sync” Wait Event


In busy databases you may encounter this wait event. The general reason is the low redo log I/O performance or the slow interconnect connection.

As a solution of this wait event;

  • You can increase the performance of Interconnect network. For example, instead of 1g cards, you can create an interconnect interface on 10g cards.
  • You can move Redo log files onto faster disks.
  • Or, you can set the value of the _cr_server_log_flush parameter to false. This is not suggested.

You can change the value of the parameter as follows.

Author: dbtut

We are a team with over 10 years of database management and BI experience. Our Expertises: Oracle, SQL Server, PostgreSQL, MySQL, MongoDB, Elasticsearch, Kibana, Grafana.

Leave a Reply

Your email address will not be published. Required fields are marked *