we also came across this issue. I think it is not caused by gc time, but the optimize action, though I did not read the source code, I think when optimize the index in master internally, it will produce the replicate log file, and the replicates synchronize the log file, just like the DB master and slave theory, it will consumes much CPU and the IO will be very high. but It is OK, and will take some time.
2016-07-12 10:19 GMT+08:00 Jason <hialo...@gmail.com>: > hi, all. > > I'm running solr instance with two cores and JVM max heap is 32G. > Each core index size is 68G, 61G repectively. > I'm always keeping on optimization after update index. > BTW, on last week, document update is completed but optimize phase cpu is > very high. > I think that is because long gc time. > How should I solve this problem? > welcome any idea. > thanks, > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/High-cpu-and-gc-time-when-performing-optimization-tp4286704.html > Sent from the Solr - User mailing list archive at Nabble.com. >
