OK!
On 24 March 2016 at 21:11, Magnus Kessler wrote:
> Hi Oleksiy,
>
> On 24 March 2016 at 14:55, Oleksiy Krivoshey wrote:
>
>> Hi Magnus,
>>
>> Thanks! I guess I will go with index deletion because I've already tried
>> expiring the trees before.
>>
>> Do I need to delete AAE data somehow or r
Hi Oleksiy,
On 24 March 2016 at 14:55, Oleksiy Krivoshey wrote:
> Hi Magnus,
>
> Thanks! I guess I will go with index deletion because I've already tried
> expiring the trees before.
>
> Do I need to delete AAE data somehow or removing the index is enough?
>
If you expire the AAE trees with the
Hi Magnus,
Thanks! I guess I will go with index deletion because I've already tried
expiring the trees before.
Do I need to delete AAE data somehow or removing the index is enough?
On 24 March 2016 at 13:28, Magnus Kessler wrote:
> Hi Oleksiy,
>
> As a first step, I suggest to simply expire th
Hi Oleksiy,
As a first step, I suggest to simply expire the Yokozuna AAE trees again if
the output of `riak-admin search aae-status` still suggests that no recent
exchanges have taken place. To do this, run `riak attach` on one node and
then
riak_core_util:rpc_every_member_ann(yz_entropy_mgr, exp
This is how things are looking after two weeks:
- there are no solr indexing issues for a long period (2 weeks)
- there are no yokozuna errors at all for 2 weeks
- there is an index with all empty schema, just _yz_* fields, objects
stored in a bucket(s) are binary and so are not analysed by yokozu
