title: Changing log4j to logback for Cassandra?
body: <p>We have a java application created by our developers, that I've been asked to load balance, this application basically takes queries from our web frontend, queries our Cassandra backend, and returns results back to the frontend.  </p>
  
  <p>I've got everything set up via Nginx/round robin as far as balancing, however I'm trying to figure out the best way to set up logging since each instance of this application (which run on individual machines) will log whatever activity it is responsible for.  </p>
  
  <p>One possible solution would be to share out a central log file via NFS, and allow all the nodes to write to it.  The problem is that we are using log4j and after some research (and some testing) I see that there are some problems and various log entries are cut off/corrupted, so I started looking for a solution.  I've read that logback classic could be used in "prudent" mode which would allow the nodes to lock down the log while writing.  </p>
  
  <p>My question is how/can this be implemented without having to rewrite our code (I'm not a developer)?  I know where the configuration files for our logging are, and I know where the log4j-1.2.17.jar and  slf4j-log4j12-1.7.2.jar files live as well (as relates to our application).</p>
  
  <p>Is there a simple way to switch over to logback, or is this something that needs to be modified within the application itself?</p>
  
  <p>PS I can always go the route of having each instance create its own log, but I'm hoping I can figure out a way to allow them to use the same log file</p>