Re: Frequency of rebuild_index

2018-05-02 Thread Anup Shirolkar
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

If you want to use extensive search like functionality or special kind of
secondary indexing you can explore the stratio-lucene-index option.

Thanks,
Anup

On 3 May 2018 at 10:02, Anup Shirolkar 
wrote:

> 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 good for you
> https://docs.datastax.com/en/cassandra/3.0/cassandra/dml/
> dmlIndexInternals.html?hl=secondary%2Cindex
>
>
>
> On 30 April 2018 at 17:51, Akshit Jain  wrote:
>
>> 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  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


>>>
>>
>


Re: Frequency of rebuild_index

2018-05-02 Thread Anup Shirolkar
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 good for you
https://docs.datastax.com/en/cassandra/3.0/cassandra/dml/dmlIndexInternals.html?hl=secondary%2Cindex



On 30 April 2018 at 17:51, Akshit Jain  wrote:

> 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  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
>>>
>>>
>>
>


Re: Frequency of rebuild_index

2018-04-30 Thread Akshit Jain
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  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
>>
>>
>


Re: Frequency of rebuild_index

2018-04-26 Thread Anup Shirolkar
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  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
>
>