4 Gb is very small for Solr. Solr is not designed for Dockerized, fail-often use.
We use a LOT of Docker ECS, but all of our Solr servers are on EC2 instances. That’s about sixty instances in several clusters. We run an 8 Gb heap for all our Solr instances. Instances in our biggest cluster (in terms of index size and doc count) are c4.8xlarge, with 36 vCPU and 60 Gb of RAM. wunder Walter Underwood wun...@wunderwood.org http://observer.wunderwood.org/ (my blog) > On Sep 10, 2018, at 11:05 PM, solrnoobie <raphaeldegra...@yahoo.com> wrote: > > 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
