Hello Alexander, Can you send us the logs? I’d like to see the errors that occurred after the time of the node name change.
In terms of getting your data back into the indexes, I’d recommend letting AAE handle the situation by removing the `yz_anti_entropy` directory and letting the keys re-index. You can even remove the search index directories, e.g. https://github.com/basho/riak_test/blob/master/tests/yz_core_properties_create_unload.erl#L94 <https://github.com/basho/riak_test/blob/master/tests/yz_core_properties_create_unload.erl#L94>, and let the them get recreated, which will still re-index via AAE. Nonetheless, we’d like to see the logs and try and reproduce the issue in a test when the node name changes. Thanks. Zeeshan Lakhani programmer | software engineer at @basho > On Jun 8, 2015, at 8:30 AM, Alexander Popov <[email protected]> wrote: > > I was perform all nodes upgrade in x6 nodes cluster > and at same time 4 of them was prooceed with node name changed by steps: > http://docs.basho.com/riak/latest/ops/running/recovery/failed-node/#Node-Name-Changed > > <http://docs.basho.com/riak/latest/ops/running/recovery/failed-node/#Node-Name-Changed> > > after that search indexes becomes completely broken - many data missed, > returns different results on every requests. > > Does it have any options now except re-save entire data in bucket to fix it? > _______________________________________________ > riak-users mailing list > [email protected] > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
_______________________________________________ riak-users mailing list [email protected] http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
