title: Rebooting a AWS RDS Aurora master/writer also reboots the readers?
body: <p>I'm trying to evaluate AWS RDS Aurora as future replacement for our local MySQL databases, but I'm noticing some strange behaviors. </p>
  
  <p>I have a basic cluster with a DB master (writer) and a replica (reader). My idea was to use the reader as an always available datasource, even when the writer in unavailable. But when I'm rebooting the master, it takes down the reader as well, making the setup quite worthless.</p>
  
  <p>Looking at the reader replica log, this is what happens when the it notices that the writer is down:</p>
  
  <p><a href="https://i.stack.imgur.com/cQ3uZ.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/cQ3uZ.png" alt="enter image description here"></a></p>
  
  <p>Does anyone know how to have a Aurora read entry point that never goes down even if the writer is offline or busy for a brief time? </p>
  
  <p>Or does the write/read "out of sync" always take down the reader entry points no matter the size of the cluster?</p>