You have not shed any light on what the reason for the container restart was, and there is too little information about your setup and Solr usage to guess what goes on. Whether 4Gb is sufficient or not depends on how much data and queries you plan for each shard to handle, how much heap you give to Solr out of those 4G and many other factors.
Jan > 11. sep. 2018 kl. 08:05 skrev solrnoobie <raphaeldegra...@yahoo.com>: > > So we have a dockerized aws environment with the solr docker container having > only 4 gigs for max ram. > > Our problem is whenever we index, the container containing the leader shard > will restart after around 2 or less minutes of index time (batch is 50 docs > per batch with 3 threads in our app thread pool). Because of the container > restart, indexing will fail because solrJ will throw an invalid content type > exception because of the quick container restart. > > What can possible casue the issues above? > > > > -- > Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
