title: Google Cloud SQL instance always in Maintenance status & Binary logs issue
body: <p>I've had some of Google Cloud SQL MySQL 2nd Gen 5.7 instances with failover replications. Recently I noticed that the one of the instance overloaded with the storage overloaded with binlogs and old binlogs not deleted for some reason.
  I tried restart this instance but it wont start since 17 March. </p>
  
  <p>Normal process with binlogs on other server:
  <a href="https://i.stack.imgur.com/SuCiz.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/SuCiz.png" alt="normal server"></a></p>
  
  <p>Problem server. Binlogs not clearing and server wont start and always under maintenance in the gcloud console. 
  <a href="https://i.stack.imgur.com/CyoTL.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/CyoTL.png" alt="problem server"></a></p>
  
  <p>Also I created one other server with same configuration and not binlogs never clearing. I have already 5326 binlogs here when on normal server I have 1273 binlogs and they are clearing each day.
  <a href="https://i.stack.imgur.com/dNX52.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/dNX52.png" alt="new server"></a></p>
  
  <p>What I tried with the problem server:
  1 - delete it from the Google Cloud Platform frontend. Response: The instance id is currently unavailable.
  2 - restart it with the gcloud command. Response: ERROR: (gcloud.sql.instances.restart) HTTPError 409: The instance or operation is not in an appropriate state to handle the request. Same response on any other command which I sent with the gcloud.</p>
  
  <p>Also I tried to solve problem with binlogs to configure with <code>expire_logs_days</code> option, but it seems this option not support by google cloud sql instance.</p>