contd..
when can the discrepancy in the index arise. Any specific example?
I can not pin point any exact situation. I was referring to situations
which can hamper data replication, consistency adversely. e.g. single or
multiple Node failures/recovery
anything specific to stratio-lucene-index
Hi,
when can the discrepancy in the index arise. Any specific example?
any documentation which says the index automatically rebuilds/keeps itself
> up to date after updations and deletions
I was unable to locate anything saying this in Apache C* docs. But here is
Datastax link if that is
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
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
Hi,
How frequently one should run nodetool rebuild_index and what's its impact
on performance in terms of iops,cpu utilisation etc.
Regards
