Hi, This looks good but when can the discrepancy in the index arise. Any specific example? Is there any documentation which says the index automatically rebuilds/keeps itself up to date after updations and deletions. Also if there anything specific to stratio-lucene-index.
Regards Akshit Jain 9891724697 On Fri, Apr 27, 2018 at 9:59 AM, Anup Shirolkar < anup.shirol...@instaclustr.com> wrote: > Hi, > > The secondary indices in Cassandra are maintained continuously as data is > written. Also index rebuilding is kicked off automatically when you create > a new index. So, there is no good reason to schedule nodetool rebuild_index > regularly. > > However, if you find any discrepancy in the index and data you should run > it. Ideally, this should not happen but if it is required as a result of > any major activity/failure you can use it. > > Talking about the load it puts on system, it depends upon the size of > index itself. Although it will consume resources, it should not give a > major performance hit to the system. > > Regards, > Anup > > On 27 April 2018 at 13:46, Akshit Jain <akshit13...@iiitd.ac.in> wrote: > >> Hi, >> How frequently one should run nodetool rebuild_index and what's its >> impact on performance in terms of iops,cpu utilisation etc. >> >> Regards >> >> >
