On a side note, does adding docvalues to an already indexed field, and then optimizing, prevent the need to reindex to take advantage of docvalues? I was under the impression you had to reindex the content.
> On Nov 3, 2018, at 4:41 AM, Deepak Goel <deic...@gmail.com> wrote: > > I would start by monitoring the hardware (CPU, Memory, Disk) & software > (heap, threads) utilization's and seeing where the bottlenecks are. Or what > is getting utilized the most. And then tune that parameter. > > I would also look at profiling the software. > > > Deepak > "The greatness of a nation can be judged by the way its animals are > treated. Please consider stopping the cruelty by becoming a Vegan" > > +91 73500 12833 > deic...@gmail.com > > Facebook: https://www.facebook.com/deicool > LinkedIn: www.linkedin.com/in/deicool > > "Plant a Tree, Go Green" > > Make In India : http://www.makeinindia.com/home > > >> On Sat, Nov 3, 2018 at 4:30 AM Wei <weiwan...@gmail.com> wrote: >> >> Hello, >> >> After a recent schema change, it takes almost 40 minutes to optimize the >> index. The schema change is to enable docValues for all sort/facet fields, >> which increase the index size from 12G to 14G. Before the change it only >> takes 5 minutes to do the optimization. >> >> I have tried to increase maxMergeAtOnceExplicit because the default 30 >> could be too low: >> >> <int name="maxMergeAtOnceExplicit">100</int> >> >> But it doesn't seem to help. Any suggestions? >> >> Thanks, >> Wei >>
