title: LOG4j2 async logger blocking functionality
body: <p>background:</p>
  
  <p>in log4j2 when using an asyncappender you have the ability to set the parameter "blocking" to false for the logger so any logs which overflow the buffer size will be discarded and not slow up the main thread. (see here under asyncAppender <a href="https://logging.apache.org/log4j/2.x/manual/appenders.html" rel="nofollow">https://logging.apache.org/log4j/2.x/manual/appenders.html</a>)</p>
  
  <p>I am upgrading our application to the glorious asyncLogger structure found here: <a href="https://logging.apache.org/log4j/2.x/manual/async.html" rel="nofollow">https://logging.apache.org/log4j/2.x/manual/async.html</a></p>
  
  <p>while I see I can set the ring buffer size, I do not see anything stating that I can stop it from blocking the applications main thread,</p>
  
  <p>question: </p>
  
  <p>so just to be certain I am asking here as I dont see anything in the docs, if one has more logs coming in than logs going out(say we are stashing them in a DB and the insert is taking awhile) so the ringbuffersize is exceeded when using asyncloggers what happens to the extra logs? and will the main thread be slowed in any way?</p>
  
  <p>thanks!</p>